Don Cox wrote,
> Voyager does display the letter � (mu) correctly. Try a search for "in
Only as the literal 8-bit character (alt-u). This is ok with me, but I
don't know if it makes it technically "correct" for the full HTML
standard, or whether it maps on all machines and fonts. It doesn't
support it as "μ".
I confess I don't fully appreciate all the significance of the
arguments being presented here about codepages and Unicode. I am
surprised to learn that Voyager uses the OS text rendering calls for
it's layout at all.
If, as was mentioned in another message, ttf fonts may contain
suitable characters anyway, is it possible for V to convert the &xxx;
codes into custom-rendered "glyphs" on the fly? It already does
support some more conventional codes like < > and stuff,
which must have some special processing going on. The ttf.library
which we all happily installed (thanks to Matt's instructions)
required some sort of mapping file IIRC which was to do with ISO
character conversion, could V internally scan a similar file?
I never actually intended for my orignial question to have more than a
yes/no answer, I didn't realise what a can of worms it was. :)
Cheers,
Ian
===
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
