In message <gemini.jj7oxl02zn5h1033w.druck@xxxxxxxxxxxx> "David J. Ruck" <druck@xxxxxxxxxxxx> wrote: > Martin Wuerthner <lists@xxxxxxxxxxxxxxx> wrote: >> In message <gemini.jj7m2q02xfs2a033w.druck@xxxxxxxxxxxx> >> "David J. Ruck" <druck@xxxxxxxxxxxx> wrote: >> >>> Paul Sprangers <Paul@xxxxxxxx> wrote: >>>> Quite a lot of my older documents use EFF's London Regular as their >>>> main font. However, at some point in history, this font suddenly >>>> refused to display properly. [...] >> >>> Its probably an issue with a font encodings file. Anyway this isn't in >>> any way Iyonix specific >> >> I would not be that sure at this stage - the Unicode font manager treats >> encodings rather differently from the way they are treated by the RO3/4/6 >> FontManager. So, this specific case might well turn out to be an Iyonix >> issue. > > If it worked before on the Iyonix and reinstalling the font does not fix > it, the thing like to have changed is a new encodings file being > introduced, probably from a TTF conversion. But how would a new global encodings file affect the display of a font with its own font-specific encodings file? That could only happen if the newly introduced encodings file was in a directory with the same name as the EFF font. Another theory: The culprit could be a font converted by RiScript, but then, that would only by visible while RiScript is running (because only then, the converted fonts are added to the global font path). So, Paul, if you always have RiScript running, then check its generated fonts directory. That would explain the symptoms (and it would also mean that the issue is not Iyonix-specific). Martin -- --------------------------------------------------------------------- Martin Wuerthner MW Software lists@xxxxxxxxxxxxxxx --------------------------------------------------------------------- --- To alter your preferences or leave the group, visit //www.freelists.org/list/iyonix-support Other info via //www.freelists.org/webpage/iyonix-support