Issue 71302 - WW8: Hours in Danish time field is not recognised correctly
Summary: WW8: Hours in Danish time field is not recognised correctly
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: OOo 2.0.4
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2006-11-07 15:52 UTC by stp
Modified: 2017-05-20 11:17 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Word document with time field (32.50 KB, application/msword)
2006-11-07 15:53 UTC, stp
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description stp 2006-11-07 15:52:10 UTC
In the attached Word-document the footer includes a time field. Writer does not
recognise the hours. Minutes and seconds is correctly imported. 

Related Issue: The Danish locale setting in OOo uses T as hours instead of H. I
could easily fix this to H in the Danish locale settings xml file. But this is
not something worth messing around with at the moment according to Eike.

Søren
Comment 1 stp 2006-11-07 15:53:19 UTC
Created attachment 40402 [details]
Word document with time field
Comment 2 ooo 2006-11-07 17:50:03 UTC
Unfortunately, for legacy reasons, Danish is one of the few languages with
localized number format code keywords. Actually what needs to be done by the
Writer for Danish document content is to transform the 'H' hour keyword codes to
the localized 'T' codes, similar to what is already done with some date formats
for other locales. For an overview of localized codes please see
http://l10n.openoffice.org/i18n_framework/LocaleData.html near the bottom of
that page.
Comment 3 michael.ruess 2006-11-08 12:29:55 UTC
MRU->HBRINKM: it is a similar problem (may be the same) problem as issue 29646.
The time/date field conversion does not take care of certain "foreign" formats.

We should keep this as single issue though it may be a duplicate.
Comment 4 openoffice 2007-10-01 10:08:34 UTC
The fix for issue 29646 does not cover this one. :-(
Comment 5 Mathias_Bauer 2007-12-03 17:04:48 UTC
according to release status meeting: target 3.x
Comment 6 Mathias_Bauer 2007-12-03 17:09:17 UTC
.
Comment 7 stp 2008-10-04 18:10:55 UTC
please set target
Comment 8 Marcus 2017-05-20 11:17:37 UTC
Reset assigne to the default "issues@openoffice.apache.org".