Bug 149674

Summary: Quote field missing from Writer
Product: LibreOffice Reporter: Gabor Kelemen (allotropia) <kelemeng>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: NEW ---    
Severity: enhancement CC: dgp-mail, heiko.tietze
Priority: medium    
Version: 7.5.0.0 alpha0+   
Hardware: All   
OS: All   
URL: https://support.microsoft.com/en-us/office/field-codes-quote-field-26f0d723-07a8-4076-9097-a71459f3d44c
See Also: https://bugs.documentfoundation.org/show_bug.cgi?id=149672
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 107739    
Attachments: Screenshot MSO

Description Gabor Kelemen (allotropia) 2022-06-22 12:30:03 UTC 
This is split from bug 149672

The example file attachment 180896 [details] has in and before the paragraph numbered (5) a Quote field, which is not imported by Writer (as seen on attachment 180897 [details]), since there is no similar field yet.

This is to request the creation of this Quote field.

Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 3b852f274696a5e2a44bb4107c37cea9d291758e
CPU threads: 14; OS: Windows 10.0 Build 19044; UI render: default; VCL: win
Locale: en-US (hu_HU); UI: en-US
Calc: threaded
Comment 1 Heiko Tietze 2022-07-27 08:00:17 UTC 
Created attachment 181432 [details]
Screenshot MSO

Adding this to Fields > Variables (or Functions?) sounds straightforward but I wonder how we can achieve the complexity of nested fields like { IF "a"="b"{ Quote 34 True 34 }{ Quote "This is a " 34 false 34 "
statement" }}, see http://www.wordbanter.com/showthread.php?p=29424

If you plan to start with simply reading and accessing the field another list item doesn't affect usability. Do you have any special question, Gabor?
Comment 2 Gabor Kelemen (allotropia) 2022-07-27 11:49:48 UTC 
I don't have a question, I did not add the keyword.
This is just one more field for which Writer has no equivalent.
Comment 3 Dieter 2022-08-03 10:21:42 UTC 
(In reply to Gabor Kelemen (allotropia) from comment #2)
> This is just one more field for which Writer has no equivalent.

I thought this would require changes in UI and so I've added needsUXEval as keyword. Since Heiko supports that idea (that's how I understand his comment 1) I would say we can change status to NEW (although there seems to be some qustions on how to implement this). Please correct me, if I'm wrong.