[developers] Partial success with unicode fonts
Ann Copestake
Ann.Copestake at cl.cam.ac.uk
Mon Mar 16 04:23:46 CET 2009
do you have access to an Allegro licence so you can compile the LKB?
We'll get nowhere with Franz unless we have a way of reproducing the
problems which amounts to a few lines of code, and even then I am not
optimistic. So it seems better to try and develop workarounds. I can
easily tell you where the LKB font settings are, so you can try out
various options, but I don't have time to do these experiments myself.
Ann
> Dear all,=20
>
> a few weeks ago I posted a question regarding unicode fonts in
> LKB/LOGON.=20
>
> Meanwhile I have partial success with display of unicode characters in
> LOGON: if the ISO-10646-1 encoded font appears before the ISO-8859-1
> font in my font path, display of unicode characters works at *standard*
> display size (Helvetica, Roman 12pt).=20
>
> What does not work at present is:
>
> 1. Display of bold face.=20
>
> - Simple MRS
> - Chart display
> - Leaf nodes in tree display
> - Values (e.g. ORTH) in feature structures
>
> 2. Display of sizes other than 12pt
>
> - Input dialogues (Parse|Parse input, View|Word entries)
>
> 3. Display in LUI
>
> - yzlui does not show the glyphs
> - pangolui has layout problems (bar only displays lower half of
> each char)
>
> Internally, processing of the characters =C6=99, =C9=93 and =C9=97 is fin=
> e, even
> uppercasing works.=20
>
> It seems the LKB (or CLIM) insists on using an iso8859-1 encoded font
> here. If I remove the iso8859-1 fonts (but not the iso10646 font, of
> course), I get an error message saying that the helvetica iso8859-1 font
> could not be loaded and fixed is used instead (also with iso8859-1, not
> iso10646-1).
>
> Apparently there is a problem with font initialisation, either on the
> part of the LKB or the underlying CLIM.
>
> Any help/comments/advice on the following questions would be
> appreciated:
>
> 1. I currently have a set of patched LKB function that disable use of
> bold face. Although this is not ideal, it works except for dialogues.=20
>
> So: How can I make CLIM dialogues use the default 12pt roman font
> instead of 10pt?
>
> 2. Is it possible to fix font initialisation on the LKB side? Or is that
> an upstream CLIM bug?=20
>
> If it is an LKB problem, who would be able to fix it? I can provide the
> fonts (with installation instructions) and some description to reproduce
> the bug. Anything else needed?
>
> If it is a problem with CLIM, can you pass this bug report on to Franz?
> If you need any more detail, please let me know. =20
>
>
>
> Thanks a lot in advance for your help.=20
> =20
>
> Cheers,=20
>
> Berthold
>
>
> --=-DzmbjNI89XLdFpTfrgze
> Content-Type: text/html; charset="utf-8"
> Content-Transfer-Encoding: 7bit
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
> <HTML>
> <HEAD>
> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
> <META NAME="GENERATOR" CONTENT="GtkHTML/3.24.5">
> </HEAD>
> <BODY>
> Dear all, <BR>
> <BR>
> a few weeks ago I posted a question regarding unicode fonts in LKB/LOGON. <BR>
> <BR>
> Meanwhile I have partial success with display of unicode characters in LOGON: if the ISO-10646-1 encoded font appears before the ISO-8859-1 font in my font path, display of unicode characters works at *standard* display size (Helvetica, Roman 12pt). <BR>
> <BR>
> What does not work at present is:<BR>
> <BR>
> 1. Display of bold face. <BR>
> <BR>
> - Simple MRS<BR>
> - Chart display<BR>
> - Leaf nodes in tree display<BR>
> - Values (e.g. ORTH) in feature structures<BR>
> <BR>
> 2. Display of sizes other than 12pt<BR>
> <BR>
> - Input dialogues (Parse|Parse input, View|Word entries)<BR>
> <BR>
> 3. Display in LUI<BR>
> <BR>
> - yzlui does not show the glyphs<BR>
> - pangolui has layout problems (bar only displays lower half of each char)<BR>
> <BR>
> Internally, processing of the characters ƙ, ɓ and ɗ is fine, even uppercasing works. <BR>
> <BR>
> It seems the LKB (or CLIM) insists on using an iso8859-1 encoded font here. If I remove the iso8859-1 fonts (but not the iso10646 font, of course), I get an error message saying that the helvetica iso8859-1 font could not be loaded and fixed is used instead (also with iso8859-1, not iso10646-1).<BR>
> <BR>
> Apparently there is a problem with font initialisation, either on the part of the LKB or the underlying CLIM.<BR>
> <BR>
> Any help/comments/advice on the following questions would be appreciated:<BR>
> <BR>
> 1. I currently have a set of patched LKB function that disable use of bold face. Although this is not ideal, it works except for dialogues. <BR>
> <BR>
> So: How can I make CLIM dialogues use the default 12pt roman font instead of 10pt?<BR>
> <BR>
> 2. Is it possible to fix font initialisation on the LKB side? Or is that an upstream CLIM bug? <BR>
> <BR>
> If it is an LKB problem, who would be able to fix it? I can provide the fonts (with installation instructions) and some description to reproduce the bug. Anything else needed?<BR>
> <BR>
> If it is a problem with CLIM, can you pass this bug report on to Franz? If you need any more detail, please let me know. <BR>
> <BR>
> <BR>
> <BR>
> Thanks a lot in advance for your help. <BR>
> <BR>
> <BR>
> Cheers, <BR>
> <BR>
> Berthold<BR>
> <BR>
> </BODY>
> </HTML>
>
> --=-DzmbjNI89XLdFpTfrgze--
>
More information about the developers
mailing list