Bug 90907 - FILEOPEN: OOXML TIME field locale always en-US
Summary: FILEOPEN: OOXML TIME field locale always en-US
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
Version:
(earliest affected)
4.4.1.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Fields-Variable
  Show dependency tree / graph
 
Reported: 2015-04-28 08:11 UTC by Peter Szucs
Modified: 2024-12-23 06:30 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
test document with a single date field only (13.59 KB, application/zip)
2015-04-28 12:24 UTC, Peter Szucs 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Szucs 2015-04-28 08:11:21 UTC 
The original XML field definition is:
            <w:r>
                <w:rPr>
                    <w:rFonts w:ascii="Verdana" w:hAnsi="Verdana"/>
                    <w:szCs w:val="20"/>
                </w:rPr>
                <w:instrText xml:space="preserve"> TIME \@ "yyyy. MMMM d." </w:instrText>
            </w:r>

It is imported as a new style:
        <number:date-style style:name="N10120" number:language="en" number:country="US">
            <number:year number:style="long"/>
            <number:text>. </number:text>
            <number:month number:style="long" number:textual="true"/>
            <number:text> </number:text>
            <number:day/>
            <number:text>.</number:text>
        </number:date-style>

and field definition:
<text:time style:data-style-name="N10120" 
  text:time-value="2015-04-27T11:00:54.995000269">
  2015. April 27.
</text:time>

The problem is the month name. The converter process the format string and 
prepare the order and separator characters properly. I think the 
- number:language and
- number:country attributes should be assumed from the sytem locale settings, instead of using en-US. In my case this produce the value of
"2015. April 27." instead of "2015. április 27."

Only date formats with month names are affected.
Comment 1 Buovjaga 2015-04-28 12:09:24 UTC 
Would be nice to have an example document.

Set to NEEDINFO.
Change back to UNCONFIRMED after you have attached the document.
Comment 2 Peter Szucs 2015-04-28 12:24:04 UTC 
Created attachment 115161 [details]
test document with a single date field only
Comment 3 Buovjaga 2015-04-28 12:42:38 UTC 
I saved the docx from LibreOffice as docx, unzipped it and tried searching through the files for text:time style and number:date-style. Got 0 results.

In the document.xml of my saved file I have:

<w:r>
  <w:instrText> TIME \@&quot;yyyy&apos;. &apos;MMMM\ d\.&quot; 
</w:instrText>
</w:r>
<w:r>
  <w:fldChar w:fldCharType="separate"/>
</w:r>
<w:r>
  <w:t>2015. April 28.</w:t>
</w:r>

Maybe I don't understand this.
Someone else can confirm.

Win 7 Pro 64-bit Version: 5.0.0.0.alpha1+ (x64)
Build ID: f0edb677f09ad338e22ac3b5d91497b4479e0b3c
TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-27_01:54:20
Locale: fi_FI
Comment 4 Peter Szucs 2015-04-28 13:04:27 UTC 
It seems I cannot properly file a report, sorry.

1:
Open the attached DOCX. It will show the English month name instead of your local

2:
Save As ODF Text (.odt). This will produce the xml output, I reported.

3: 
double click the date field to receive the Edit Fields dialog. Click on "Additional formats..." and see the language setting is English for the date field.
Comment 5 Buovjaga 2015-04-28 13:08:41 UTC 
(In reply to Peter Szucs from comment #4)
> It seems I cannot properly file a report, sorry.
> 
> 1:
> Open the attached DOCX. It will show the English month name instead of your
> local
> 
> 2:
> Save As ODF Text (.odt). This will produce the xml output, I reported.
> 
> 3: 
> double click the date field to receive the Edit Fields dialog. Click on
> "Additional formats..." and see the language setting is English for the date
> field.

Thanks. Confirmed.

Win 7 Pro 64-bit Version: 5.0.0.0.alpha1+ (x64)
Build ID: f0edb677f09ad338e22ac3b5d91497b4479e0b3c
TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-27_01:54:20
Locale: fi_FI
Comment 6 QA Administrators 2016-09-20 09:33:35 UTC Comment hidden (obsolete)
Comment 7 Peter Szucs 2016-09-27 08:57:29 UTC 
Tested on v5.2.1. The bug is still present, no change in behavior.
Comment 8 Xisco Faulí 2017-09-29 08:53:15 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2019-12-03 14:37:32 UTC Comment hidden (obsolete)
Comment 10 Svatopluk Vít 2021-03-01 08:36:56 UTC 
Bug is still present 

Version: 7.1.1.1 / LibreOffice Community
Build ID: 575c5867c4cc13d7ae78f9ce39a54a52ed38c769
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: kf5
Locale: cs-CZ (cs_CZ.UTF-8); UI: cs-CZ
Calc: threaded
Comment 11 QA Administrators 2023-03-02 03:25:29 UTC 
Dear Peter Szucs,

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://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug