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?
Alan
Caolan McNamara wrote:
Hmm, as you say all 3 default fontids are 0, but the Miriam font is the
4th font. It might be that Word totally ignores this value, I'll look
into it.
Perhaps hexpoking the .doc file at the ftcStandardChp*Stsh value
locations and setting to other different but valid indexes into the font
table and reloading in Word itself will show if word actually honours
that setting at all, or only for e.g. western and otherwise always uses
its internal default font as the top of the tree font setting, i.e. word
might be hardcoded to use Miriam for the default CTL font when the
"Normal" doesn't explictly set it.
C.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
