Bug 51867 - Custom document properties containing "<" are not correctly imported from docx
Summary: Custom document properties containing "<" are not correctly imported from docx
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
Version:
(earliest affected)
3.5.4 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-08 07:46 UTC by Simon Kornblith
Modified: 2015-01-21 09:38 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
File demonstrating issue (21.61 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2012-07-08 07:46 UTC, Simon Kornblith
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Kornblith 2012-07-08 07:46:56 UTC
Created attachment 63975 [details]
File demonstrating issue

Steps to Reproduce:

1. Create a new document in Microsoft Word.
2. Open "Properties" and add a new custom document property with a value starting with "<" (e.g., "<Test").
3. Save the document as a docx file.
4. Open the docx file in LibreOffice.
5. Open File->Properties.
6. The previously added property shows only as "<".


Expected behavior:

Custom document properties containing a "<" should be properly imported from docx files.


Notes:

I can only reproduce this when opening docx files. Properties are correctly imported from doc files.

I have attached a docx file that demonstrates this issue. It has a property named "Test" with the value "<Test". This property can be read correctly by Word, but LibreOffice 3.5.4.2 shows its value as "<".
Comment 1 Valek Filippov 2012-07-10 03:25:06 UTC
Confirmed with LO 3.6 beta 2
Comment 2 QA Administrators 2015-01-05 17:51:09 UTC
** 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.3.5 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)

Thank you for your help!

-- The LibreOffice QA Team
Comment 3 Buovjaga 2015-01-21 09:38:56 UTC
Property imports correctly now -> WFM.

Win 7 Pro 64-bit Version: 4.5.0.0.alpha0+
Build ID: 07e84cae983c08afdba03018413a19d01abb3006
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-01-19_06:15:38