Created attachment 134935 [details]
A LibreOffice document with a custom Yes/No property saved as incorrect RTF
LibreOffice has a Yes/No custom property whereas RTF has a Boolean property. LibreOffice does not save a Yes/No property properly in an RTF file and the property is lost when the file is opened in LibreOffice again. The faulty file may cause problems with other word processors when they open it.
I would suggest that the LibreOffice Yes/No property is mapped to the RTF Boolean property in a way (for LibreOffice to RTF) that Yes is mapped to 1 and No is mapped to 0 and (for RTF to LibreOffice) that 0 is mapped to No and all other values are mapped to Yes. In the latter case, only mapping 1 to Yes might be OK and produce an error in all other cases, except it might make it impossible to open a document despite it would otherwise be OK.
Created attachment 134936 [details]
The document properties when saving as RTF
Created attachment 134937 [details]
Document property missing after reopening a file with a Yes/No property saved as RTF
The property should have survived the trip through RTF but did not
Created attachment 135024 [details]
RTF file - LO 6
I can not confirm with Version: 188.8.131.52.alpha0+
Build ID: e0bafa78e3ad0df397d78cd65ad19bd5b07dc5f2
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2;
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-07-20_22:42:49
After resave I see Yes/No property in the RTF file.
Seems to be fixed in dev version. Please could you test with dev version?
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker