On Thu, 2006-09-07 at 20:59 +0100, Caolan McNamara wrote: > On Fri, 2006-09-08 at 16:59 +0200, Alan Yaniger wrote: > > Hi Caolan, > > > > I found that Miriam is included in the font list in the WW8Fonts > > constructor, with index 3. > > I also found that ftcStandardChpCTLStsh has the value 0. > > If in my debugger, I change ftcStandardChpCTLStsh's value to 3, Miriam's > > index - lo and behold, the text is displayed in the Miriam font. So now, > > given the four possibilities you listed of what went wrong, how do I go > > about finding out which is correct? > > That's the tricky bit. > > Does ftcStandardChpCTLStsh actually get *read* from the file as 0, or is > it 0 because it remained at the default value of 0. > > i.e. if a breakpoint is put on > rSt >> ftcStandardChpCTLStsh; > in ww8scan.cxx is it triggered ? > > Maybe also send me an empty .doc which shows this behaviour and I might > be able to hazard a better guess as to what the problem is.
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]
