Bug 63535 - FORMATTING: Problems with custom properties in .doc
Summary: FORMATTING: Problems with custom properties in .doc
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version: 4.0.2.2 release
Hardware: Other All
: high normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-15 03:36 UTC by Ruslan Fatakhov
Modified: 2014-11-24 09:15 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Test file (15.50 KB, application/msword)
2013-04-15 03:36 UTC, Ruslan Fatakhov
Details

Description Ruslan Fatakhov 2013-04-15 03:36:24 UTC
Created attachment 77971 [details]
Test file

Problem description: 
When i add custom property name 'CREATEDATE' with type date, and insert it in document, i can see right it. But if i open one next time i see that my custom property type changed on type 'DateTime'
Steps to reproduce:
1. Open file 'Test.doc'
2. Add custom property 'CreateDate' with date type
3. Insert custom field
4. Save the file
5. Open the file

Current behavior:
i see 41136 insted date

Expected behavior:
right format date mm/dd/yyyy
              
Operating System: Ubuntu
Version: 4.0.2.2 release
Comment 1 Marc Kaulisch 2013-04-16 20:25:56 UTC
I can confirm this behaviour with the same version 4.0.2.2 under Windows 8.
This only occurs with .doc and not with .odt

With .docx there is another problem: the user-defined fields are lost.
Comment 2 Urmas 2013-04-17 13:03:22 UTC
To be precise, the VT_DATE document properties have no default format. In normal software, they are formatted as short date by default.
Comment 3 Marc Kaulisch 2014-06-27 11:12:22 UTC
still the date type of the custom property name is not kept when opened in LO 4.3.0.1 again
bug remains for .doc
Comment 4 Marc Kaulisch 2014-11-24 09:15:29 UTC
still present in 4.4.0.0.beta1
it is only a problem with doc and docx
no problems when using odt


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.