Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||WW8: unspecified CTL language breaks export of default style's CTL font|
|Component:||save-export||Assignee:||AOO issues mailing list <issues>|
|Status:||CONFIRMED ---||QA Contact:|
|Priority:||P3||CC:||issues, komgrit, markpeak, samphan, tantai|
|Issue Type:||DEFECT||Latest Confirmation in:||---|
|Issue Depends on:|
|Issue Blocks:||41707, 92549|
Description jjc 2005-04-22 04:04:44 UTC
Steps to reproduce: 1. In language settings, ensure that CTL support is enabled and that the default CTL language is None. This is the initial state after installation on a Windows machine with a Thai system locale. 2. In OOo, create a new text document. 3. Change the keyboard layout to Thai and type a few Thai characters. 4. Observe that the characters are in the Tahoma font (as specified in the default style). 5. Save the document as Word 97/2000/XP .doc. 6. In OOo, close the document. 7. Open the document in Word 2003, Thai version. 8. Observe that the characters are in the Angsana New font rather than the Tahoma font. The same problem still occurs if you change the CTL font of the default style. Workaround: ensure default CTL language is set to Thai before creating the document. The problem appears to be that OOo generates a 0x485F SPRM (sprmCLidBi) with a parameter of 0xFF and this gets Word confused.
Comment 1 jjc 2005-04-22 04:07:48 UTC
Created attachment 25325 [details] .doc file created by OOo; OOo and Word see a different font
Comment 2 michael.ruess 2005-04-22 12:05:08 UTC
MRU->FLR: can it be solved without having a valid language attribute?
Comment 3 jjc 2005-04-22 12:43:50 UTC
Any in-range language value seems to be sufficient for Word. For example, if I tweak the .doc to change the 0xff parameter to 0x41d (Swedish), that works, even though it's not the language of a complex script. 0x400 (No proofing) doesn't work though.
Comment 4 jjc 2005-04-22 12:45:15 UTC
Created attachment 25346 [details] thai.doc manually tweaked to change 0xff parameter to 0x41d
Comment 5 jjc 2005-04-27 17:42:20 UTC
This problem does not occur with Word 2000.
Comment 6 andreas.martens 2005-05-26 08:22:43 UTC
Considering the effort, the priority, the risk and our resource planning I've to retarget this issue to OOo Later.
Comment 7 Mathias_Bauer 2006-08-30 14:55:25 UTC
assigned to hbrinkm