| Summary: | FILEOPEN Date field shows date in English while it should show it in the document's original language. | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | jackolantern |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | cno, documentfoundation, ilmari.lauhakangas, jluth, kelemeng, leandroknorre, libreoffice, martijn |
| Priority: | medium | Keywords: | filter:docx, preBibisect |
| Version: | 3.5.0 release | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=115780 | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 112969 | ||
| Attachments: |
Word 2016 document with date field
Word 2007 document with date field |
||
Confirmed. Arch Linux 64-bit, KDE Plasma 5 Version: 5.2.0.0.alpha1+ Build ID: 334599030e7b45153107a3075f9049a7463aac80 CPU Threads: 8; OS Version: Linux 4.5; UI Render: default; Locale: fi-FI (fi_FI.UTF-8) Built on April 22nd 2016 the same in 3.6.7 3.3.4 shows "2-12-16" *** Bug 104697 has been marked as a duplicate of this bug. *** same happens to me in Portuguese, version 5.4.0.3 Created attachment 135881 [details]
Word 2007 document with date field
*** Bug 115780 has been marked as a duplicate of this bug. *** *** Bug 122935 has been marked as a duplicate of this bug. *** To quote myself from the duplicate: "It has been like this since it started working in 5.0. Version 4.4 and older do not save the date or date field." (How to reproduce) Writer: Insert, Field, Date Word: Insert, Modules, Field, Date This could be related source code: https://opengrok.libreoffice.org/xref/core/oox/source/drawingml/textfield.cxx?r=c6e5d551#58 (In reply to Buovjaga from comment #8) > To quote myself from the duplicate: "It has been like this since it started > working in 5.0. Version 4.4 and older do not save the date or date field." Are you sure that the problem is on saving? When I open http://bugs.documentfoundation.org/attachment.cgi?id=124268 today in 3.3.0.4 I see 15-02-19 (which is OK in Dutch) 63-master I see Friday 15 February 2019 (is no Dutch) (In reply to Cor Nouws from comment #11) > (In reply to Buovjaga from comment #8) > > To quote myself from the duplicate: "It has been like this since it started > > working in 5.0. Version 4.4 and older do not save the date or date field." > > Are you sure that the problem is on saving? > > When I open http://bugs.documentfoundation.org/attachment.cgi?id=124268 > today in > > 3.3.0.4 I see 15-02-19 (which is OK in Dutch) > 63-master I see Friday 15 February 2019 (is no Dutch) 3.3.0 saves the date as plain text, yes, but not as field (my "or date field" condition). (In reply to Buovjaga from comment #12) > 3.3.0 saves the date as plain text, yes, but not as field (my "or date > field" condition). But a docx with such a field, shows at least Dutch formatted date in 3.3.0 and not in master. Or do I miss something? (In reply to Cor Nouws from comment #13) > (In reply to Buovjaga from comment #12) > > > 3.3.0 saves the date as plain text, yes, but not as field (my "or date > > field" condition). > But a docx with such a field, shows at least Dutch formatted date in 3.3.0 > and not in master. Or do I miss something? Ok, let's call it preBibisect. I noticed the fieldness is present in 3.5.0 (English date). Dear jackolantern, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug Still present in: Version: 7.1.2.2 / LibreOffice Community Build ID: 10(Build:2) CPU threads: 8; OS: Linux 5.11; UI render: default; VCL: x11 Locale: fr-FR (fr_FR.UTF-8); UI: en-US Ubuntu package version: 1:7.1.2~rc2-0ubuntu2 Calc: threaded I assume we are talking about
<w:r>
<w:fldChar w:fldCharType="begin"/>
</w:r>
<w:r>
<w:instrText xml:space="preserve"> DATE \@ "dddd d MMMM yyyy" \* MERGEFORMAT
</w:instrText>
</w:r>
<w:r>
<w:fldChar w:fldCharType="separate"/>
</w:r>
<w:r w:rsidR="00B124D3">
<w:rPr>
<w:noProof/>
</w:rPr>
<w:t>dinsdag 15 maart 2016</w:t>
</w:r>
<w:r>
<w:fldChar w:fldCharType="end"/>
</w:r>
So, if you don't know about date fields (and LO 3.5 already does know), then you will just display the string of text (which is neither a date, nor Dutch, but just a string of characters) and it will be "perfect".
So this looks like an enhancement request. In LO, the field has a language setting attached to it, instead of just pulling the language from the paragraph character properties. So the importer probably has to be smart enough to find the current language setting and apply it to the imported date field.
(In reply to Justin L from comment #17) > So, if you don't know about date fields (and LO 3.5 already does know), then > you will just display the string of text (which is neither a date, nor > Dutch, but just a string of characters) and it will be "perfect". > > So this looks like an enhancement request. In LO, the field has a language > setting attached to it, instead of just pulling the language from the > paragraph character properties. So the importer probably has to be smart > enough to find the current language setting and apply it to the imported > date field. Makes sense. Thanks for the insight. *** Bug 137610 has been marked as a duplicate of this bug. *** This (and the duplicates) are fixed in LO 7.4 with commit 115599cc3478e37879cd2fa0b6c6c9dabde7dfd1 Author: Justin Luth on Sat Apr 9 18:06:24 2022 +0200 tdf#132475 writerfilter: use proper date-field defaults |
Created attachment 124268 [details] Word 2016 document with date field I have a Word 2016 docx document in a Dutch Word 2016. I inserted a date field into that document to show me the Dutch date.When I open the docx file in Writer it shows the date in English.