On Sun, 2006-09-10 at 11:11 +0200, Alan Yaniger wrote: > Hi Caolan, > > I've found that hexpoking the value of the ftcStandardChpStsh (western > font ) is honored by Word. By changing the value of 0 to 2, the text was > dislayed byWord in Arial instead of Times New Roman. > > However, when I did the same to ftcStandardChpCTLStsh (for Hebrew), I > should have gotten text in Arial, but I got it in Miriam. It seems that > if "Normal" is set to use "Miriam" for CTL, Word just acts as if CTL was > not set at all, and relies on Miriam as a default, hardcoded in Word > somewhere. > > To import a document like this into OOo, do we have to do the same? > Namely, hardcode "Miriam" as a default CTL font, when the value of > ftcStandardChpCTLStsh is 0 and the language is Hebrew (and supply other > defaults for Arabic and other RTL languages)? Or will this break > something else?
Grr, well again great work :-) I'm on the road at the moment with no access to MSWord to do a few more checks, but it begins to look like a very possible Word bug which we might indeed have to do something like this to solve. Another (vague) possibility is that word hardcodes ftcStandardChpCTLStsh to always be "3", if you hexpoke the text of the 4th font which should be "Miriam" (in unicode) to be e.g. "Niriam" or "foobar" and reload in word, does the default CTL font remain at "Miriam", showing that word is totally disregarding this fonttable for the default CTL font when unset in any style, or does it show the hexpokeed new name, showing that word may be not reading the ftcStandardChpCTLStsh value from the file and somehow hardcoded as 3, to get the fourth entry from the fonttable. We also will need to figure out whether the CJK font follow the western case of the busted-looking CTL case. C. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
