IIRC, NT supports Unicode. However, the CharMap utility may be a bit different. It may be that the NT CharMap only views specific Unicode ranges one at a time, instead of being able to browse through all of Unicode. That might also make it hard to get to private use codepoints or other odd things.

Your friend should poke about for an option like the "advanced view" that enables full Unicode browsing in the Win 2000 and later CharMaps.

T

1. With Character Map, one is only able to access the alternate characters if they are encoded in the Private Use Area. While the Calaxie Polaris font (by Thirstype) supports this, not all OpenType fonts support PUA because, in a way, it is a sort of a "hack".

2. While the Windows NT character map looks different, it supports Unicode ranges -- just like the Windows XP character map. In the Windows NT character map, the Unicode ranges are shown in the list that in the Swedish version is labeled "Delm�ngd".

Tell your friend to scroll down that list to see something that says "Private Use Area" in Swedish. He should be able to find the alternate characters there.

Regards,
Adam

hey thanks guys, i'll direct his attention to this...

cheers

geraint

hey thanks guys, i'll direct his attention to this...

cheers

geraint

many thanks for the advice: i've spoken to him and he can now access the ranges, including the all-important private use area

incidentally adam, you say 'hack', but is there any other way to encode multiple glyphs (eg alternates, figure styles)?

Geraint,

Encoding alternates (swashes, old-style ligatures, small caps, inital versions etc.) or ligatures should be done only through advanced typographic layout features. The by far most popular and relevant advanced typographic layout system is OpenType Layout.

Practically, alternates and ligatures should not be encoded via Unicode, but only by associating them with the basic glyphs using OpenType Layout features.

Assigining PUA Unicode indexes are just a hack, its aim is to allow the user to access the alternate glyphs in applications that do not support OpenType Layout features. The main problem is that glyphs inserted into the text corrupt the text logic: a small cap "a" inserted into the text using PUA Unicodes will not be recognized by the application's spell-checker, hyphenation algorithm, or the find-and-replace feature. Similarly, copying-and-pasting the text or changing the font will result in corrupted text: square boxes instead of the actual letters.

Regards,
Adam

thanks for this useful info, adam, which i've only just noticed!

regards, geraint

"Delm�ngd"?

That makes no sense? That's a really, really bad and strange translation.