Hi Matt,

> > suitable characters anyway, is it possible for V to convert the &xxx;
> > codes into custom-rendered "glyphs" on the fly?
> 
> It's possible.. kinda.. sort of.. to get glyphs from the outline engine.
> 
> But rendering them to the screen is more of a chore than anyone
> wants to be bothered with. 
[...]

Ah, right. I wondered if it was fairly straightforward because you
already render the blobs for lists, and lines for <HR> and table
borders and suchlike.

> Basically a Unicode font is done in a funny way for compatibility,
> characters 0-255 are as the ISO-8859-1 (Latin 1) codepage is
[...]
> What the Windows 1252 codepage does is make TTF library make
> certain characters available in some special slots when you ask
[...]
> You could supply ISO-8859-2 to get Cyrillic characters: and the
[...]

> At present there is no way to get ttf.library to give you a specific
> character set on the fly: it's per font, and/or globally per system,
> not per app. Plus it's still limited to 255 fixed characters.

Rather than have another load of calls or a new API capable of
rendering specific codepages, would it be possible to add a single
function to the OS (or ttf.library maybe) which says "use this
codepage". You pass it a pointer to the conversion table and then all
rendering calls coming from that task will get that codepage.  By
default, an old app which doesn't know about codepages will get the
Latin 1 page because it won't ask for another.

It would be fairly pointless embedding this into the existing OS
text() etc. calls since they mostly deal with 8-bit fixed bitmap fonts
anyway. Those things which can deal with it, like ttf.library, are the
things which would need changing.  (Not that I have the faintest idea
of the ttf.lib API, or anything about codepages beyond what you've
written, so sorry if this is all rubbish).

> I added support for &beta; &bull; and &bullet; today. I can't find the code
> for alpha in the normal character set.

It's good to have support for what you can reasonably do under the
current situation, at least. :)

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

Reply via email to