Issue 29670 - MS Word Export: Garbled Japanese variable date field
Summary: MS Word Export: Garbled Japanese variable date field
Alias: None
Product: Internationalization
Classification: Code
Component: code (show other issues)
Version: OOo 1.1.1
Hardware: PC Windows XP
: P3 Trivial with 4 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
: 31210 (view as issue list)
Depends on:
Reported: 2004-05-29 10:55 UTC by kasey
Modified: 2017-05-20 11:13 UTC (History)
1 user (show)

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

Any takers? khong maybe? (73.88 KB, image/gif)
2004-06-21 13:28 UTC, kasey
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description kasey 2004-05-29 10:55:55 UTC
1. In OOo1.1.2rc3 Writer, insert a Japanese varialbe date field with the format
"YYYY[nian]m[yue]d[ri]", where [nian], [yue], and [ri] stand for respective
Chinese ideographs.
2. Export and open the document into MS Word 2002. -> The field becomes corrupt.
Comment 1 kasey 2004-06-02 05:39:17 UTC
For cjk savvy browsers, [nian], [yue], [ri] stand for 年, 月, 日, respectively.
Comment 2 kasey 2004-06-21 13:28:57 UTC
Created attachment 16047 [details]
Any takers? khong maybe?
Comment 3 thorsten.ziehm 2004-06-28 09:01:36 UTC
Hi Eike, this is a task for you. Is it possible to fix it for OOo1.1.3 or should
we set it to the next major step, OOo2.0?
Comment 4 thorsten.ziehm 2004-06-28 09:04:25 UTC
Assigned to Eike.
Comment 5 ooo 2004-06-28 15:01:44 UTC
I doubt that this is my construction site. Seems to be related to how number
formats are converted during MS-Word export => reassigning to Martin.

Martin, if we need some additional support in
SvNumberformat::GetMappedFormatstring() please tell me.

Comment 6 ooo 2004-06-28 15:21:54 UTC
MS-Word export/import of variable date field seems to be generally broken. A
field inserted as "MM/DD/YY" displays correctly 06/28/04, but when saved as
MS-Word and reloaded displays 06/tt/jj, with tt and jj being the German format
code keywords for day respectivley year. Seems upon import the format code is
added to the number formatter without converting it to the target locale, en_US
in this case.
Comment 7 michael.ruess 2004-07-08 08:39:59 UTC
*** Issue 31210 has been marked as a duplicate of this issue. ***
Comment 8 michael.ruess 2004-07-09 10:54:39 UTC
Retargeted to 1.1.4.
Comment 9 vandan 2004-08-16 00:44:02 UTC
Just found an earlier report of same bug:
Comment 10 martin_maher 2004-09-06 16:01:56 UTC
MM: Due to lack of resources I have to move this to "OO Later"
Comment 11 vandan 2005-01-07 00:06:29 UTC
According to this issue
has been fixed in OO 680m56.

Does someone with the correct permissions want to close this bug?
Comment 12 martin_maher 2005-04-13 17:14:32 UTC
mmaher->flr: Yours I think
Comment 13 apienk01 2006-02-14 14:20:26 UTC
This issue is far from being closed, and seems to affect all fields, not only
the date. Here's one example:

I use the following header line in all my documents:

   Last edited by: FullName; Last printed: 13.2.2006 12:11:00 PM

The data after colons are fields: "docInformation/Modified/Author" and
"docInformation/Last printed/Date" with a modified format to incorporate both
date and time. When I save the file in MS Word format, and the reopen, the line
looks like this:

   Last edited by: H十八N十八十八十三L; Last printed: 13/2/2006 12:11:00 A2/P2

(with question marks being empty square boxes, denoting unrecognizable
character). When I get into the properties of the first field, I see the
language is set to Japanese, instead of the default locale (US). And when I open
this file in MS Word 2000, I get an error saying that there's "an unsupported
character in the format string" - but there are actually two errors here. When
shown, the first field code looks like this:


First,'s "Modified/Author" field (denoting the person) has been
translated to Word's "SAVEDATE" field (denoting the time), instead of
"LASTSAVEDBY". Second, "GENERAL" format string is unrecognized in MS Word,
because the parser only allows "dd.MM.yyyy" type of strings. The second field
("Last printed") looks OK, except for the strange "A2/P2".

The quilty one is the MS Word Export module of OOo, still buggy in 2.0.1. The
import module works as it should.
Comment 14 Mathias_Bauer 2006-08-30 15:30:28 UTC
assigning to hbrinkm
Comment 15 apienk01 2007-01-05 14:29:14 UTC
UPDATE: In Ooo2.1 the bug is gone. Only one thing is wrong: if the value of
DocInformation:LastPrinted field is null (document was never printed), after
saving the document in Word format the field is deleted.
Comment 16 Marcus 2017-05-20 11:13:38 UTC
Reset assigne to the default "".