Created attachment 54173 [details] Examle of converted MS Word document with 2 fields, mergefield and IF field (can`t be deleted). Problem description: After converting MS Word document to odt, conditional fields can`t be deleted or modified. After saving as plain xml, I found this node causes the problem: <field:fieldmark-start text:name="__Fieldmark__174_316795990" field:type=""/><field:fieldmark-end/> Steps to reproduce: 1. Create MS Word document with conditional field "IF" 2. Open in LibreOffice Writer 3. try to edit field Platform (if different from the browser): Windows
Hello Matěj, *, I can confirm it with Debian Testing AMD64 and the Germanophone version of LO 3.5.0 RC1 ... :( If I choose to insert text in the marked field, I get the error message (roughly translated) "The cursor or the selection is in an write protected area. A change cannot be accepted." ... :( HTH Thomas.
I don't what to do with the attached document, it is surely not an ODT document. Could you (Matěj or thackert) upload a MS Word with the described fields in your comment? (Not everyone has MSO to create this file for himself.) This way we can test the conversion and the possible problems.
Created attachment 56010 [details] MS Word .doc with Conditional Field
Created attachment 56011 [details] 56010 .doc saved as .odt
Thanks Matěj. OK, I can reproduce this now under LO 3.4 and 3.5. However, notice that the problem is not within the conversion from .doc to odt., the field (and its whole paragraph) is already not editable in the .doc, if opened with LO 3.4/3.5. I checked the .doc and your .odt also with OOo 3.2.1, in both cases the field text is editable - though the field is not recognized as a field but as simple text. Setting Status to NEW Adding Keyword regression (although I'm not so sure about it).
Created attachment 56144 [details] .doc with Fields saved as .odt under OOo 3.2.1
If in Word select "Show field codes" then it shows: { IF 1 = 1 "test1" "test2" \* MERGEFORMAT }
I can confirm this Bug, tested with Libreoffice 4.2.1
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
I can confirm this bug is present in LibreOffice Writer 5.0.2.2 Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe Locale: en-US (en_US) on Windows 10 for the first two attachments, #54173, #56010. I arrived here because my wife was running into "protected" fields in work forms she uses. Sometimes the problem would resolve, though we have not been able to identify the fix -- maybe save as, maybe copy, maybe copy and reopen, maybe POM.
Serge Krot committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=29378bd510226adb23659525203beec18f8708a3 tdf#43569 DOC input: insert ConditionalText field instead of field marks It will be available in 6.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Fileopen and DOC save as ODT looks fixed. Export DOC save as DOC/DOCX doesn't, can be another bug but please comment. If another bug please mark this one as fixed.
Yeah, lets mark this fixed, title says file open from .DOC - and have the export filter work as a separate task.
Bug 114537.