Apache OpenOffice (AOO) Bugzilla – Issue 79246
Ruby in MS Word format is broken
Last modified: 2017-05-20 10:22:33 UTC
How to reproduce: 1. open Writer 2. enter "WORD" and select it 3. chose Format->Asian Phonetic Guide 4. enter ruby text "word" for "WORD" and Apply 5. save it as "Microsoft Word 97/2000/XP" format 6. open it with MS Word Word shows incorrect format for WORD with ruby text. If you select those text and shows "Field code" with context menu, then it shows "{.....(word);WORD)}. You can replace ";" with "," to show correct ruby format. This is regression from OOo1.1.
This is reported by matuaki-san in Ja OOo community.
SBA->MRU: This is a MS Word filter issue. Please proceed. Note: Broken in OOo 2.0/SO8 final and OOo2.2.1/SO8U7 too. In word, the field code for the given example reads {EQ \* jc3 \* "Font:Thorndale" \* hps12 \o\al(\s\up 11(word);WORD)} But should read {EQ \* jc3 \* "Font:Thorndale" \* hps12 \o\al(\s\up 11(word)WORD)} to display correctly (without the semicolon before "WORD").
Reassinged to MRU.
This cannot be fixed... Word 2000 uses a "comma" in its field code - Word 2003 uses the "semicolon" (which is exported by OOo Writer). So we decided to export the field syntax of the "newer" Ms Word.
Closed.
This is from original reporter (matuaki-san) in Japanese community. --- I tried this with Japanese version of Office2003 and 2007, but both fail to display ruby correctly. Word2003 help regarding field-code says "Switching character depends on locale. If decimal separator of the language setting is '.', then the field separator is ',', and if decimal separator of the setting is ',', then the field separator is ';'. --- Japanese default decimal separator is '.' as same sa US, so the filed separator should be ','. So figuring out decimal separator and use appropriate field separoator by export fileter would be reasonable solution in this case. Ruby is popular functionality in Japanese, so adjusting just Euro locale (using ',' as decimal separator) is not appropriate.
MRU->HBRINKM: please implement in the export filter for Rubies, that the seperator should be locale-dependent. Though I currently do not understand why Word 2000 and 2003 behave differently on the same locale setting...
according to release status meeting: target 3.x
.
I have a patch for that to upstream in CWS cbosdo06.
target -> 3.3
Fixed by commit http://hg.services.openoffice.org/cws/cbosdo06/rev/9594519420b0
Reassigned to me.
Verified n CWS cbosdo06.
According to Release Status Meeting this week (see http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes#2010-09-13) setting target to OOo 3.4.