Ar an ceathrú lá déag de mí Eanair, scríobh Stephen J. Turnbull:
Aidan> :-) I just loaded up an sjt-xft-enabled gnus, and I
_can’
Aidan> t_ see the Unicode apostrophes on my posts. I suppose it
Aidan> varies with font converage.
It does. The next thing I need to do is support font-preference-by-
character-set (Mule charset, FC language, FC charset, query font for
character set, probably in that order).
Do you get warnings, or just little boxes in the display?
For the left double quote, I get a horizontal bar (not the Han character for
1, more like a logical not sign at a point size too small to see the
vertical), and this to stdout;
checking if Courier handles Japanese
Unexpected type of lang value (FcTypeLangSet)
confirming charset for font instance Sazanami Mincho
FcNameParse'ed name is Sazanami Mincho
FcConfigSubstitute'ed name is Sazanami Mincho:rgba=1
FcDefaultSubstitute'ed name is Sazanami
Mincho-12:slant=0:weight=100:width=100:pixelsize=12.5:hintstyle=3:hinting=True:verticallayout=False:autohint=False:globaladvance=True:dpi=75:rgba=1:scale=1:fontversion=2147483647
checking if Sazanami Mincho handles Japanese
Unexpected type of lang value (FcTypeLangSet)
and then this to the " *Message-Log*" buffer:
Notice: Unable to instantiate font for charset japanese-jisx0208, face default
For the right single quote, it displays fine, and I get this to stdout
FcNameParse'ed name is
FcConfigSubstitute'ed name is :rgba=1
FcDefaultSubstitute'ed name is
-12:slant=0:weight=100:width=100:pixelsize=12.5:hintstyle=3:hinting=True:verticallayout=False:autohint=False:globaladvance=True:dpi=75:rgba=1:scale=1:fontversion=2147483647
Xft font -misc-fixed-medium-r-normal--14-130-75-75-c-70-iso8859-1 supports en
attempting to initialize font spec
Caslon-12:style=Roman:slant=0:weight=100:width=100:pixelsize=12.5:foundry=unknown:hintstyle=3:hinting=True:verticallayout=False:autohint=False:globaladvance=True:index=0:outline=True:scalable=True:dpi=75:rgba=1:scale=1:fontversion=65536
initialized Xft font
Caslon-12:style=Roman:slant=0:weight=100:width=100:pixelsize=12.5:foundry=unknown:hintstyle=3:hinting=True:verticallayout=False:autohint=False:globaladvance=True:index=0:outline=True:scalable=True:dpi=75:rgba=1:scale=1:fontversion=65536
width of font
Caslon-12:style=Roman:slant=0:weight=100:width=100:pixelsize=12.5:foundry=unknown:hintstyle=3:hinting=True:verticallayout=False:autohint=False:globaladvance=True:index=0:outline=True:scalable=True:dpi=75:rgba=1:scale=1:fontversion=65536
is 31, larger than its height 19
initialized Xft font
Caslon-12:style=Roman:slant=0:weight=100:width=100:pixelsize=12.5:foundry=unknown:hintstyle=3:hinting=True:verticallayout=False:autohint=False:globaladvance=True:index=0:outline=True:scalable=True:dpi=75:rgba=1:scale=1:fontversion=65536
and this to the messages buffer:
Warning: ("unknown charset" #<charset greek-iso8859-7 "ISO8859-7"
"ISO8859-7 (Greek)" "ISO8859-7 (Greek)" 96 l2r cols=1 g1
final='F' reg=iso8859-7 0x1b6>)
Aidan> Stephen, I’m getting font names treated as Latin 1
where,
Aidan> I believe, they should be treated as UTF-8.
Damned if I know. Let's add the freetype and Xft manuals to the
general-docs package.
If the info isn’t in the manuals--ce qui se peut bien--fcfreetype.c:567 does
indicate they’re in UTF-8.
--
“Ah come on now Ted, a Volkswagen with a mind of its own, driving all over
the place and going mad, if that’s not scary I don’t know what is.”