a. Yes, you are right - 255 seems the limit.
I read somewhere that it is 224 of which the first might need to be a space. These are mapped into the Unicode Private Use Area at U+F020 to U+F0FF.
Now I don’t understand why the series of numbers 61473+ doesn’t end 255 points later?
Decimal 61473 is hexadecimal F021. It seems that the Symbol Font way of doing things allows a font to be treated as if being from U+0020 to U+00FF within applications, so that one may access symbols using ordinary keyboard characters and some of the accented characters of some of the languages of Western Europe, whilst maintaining a situation that the glyphs are, within the font, mapped to the Unicode Private Use Area.
Some readers might like to know that the Microsoft Calculator program which arrives with Windows is, in the View | Scientific mode, useful for converting from decimal to hexadecimal and from hexadecimal to decimal. Microsoft Calculator also has capabilities far greater than its keypad suggests. For example, it can calculate the arctangent of a value by checking the Inv checkox then clicking tan. Right-clicking on a key and then left-clicking on the What’s This? panel which is displayed provides details of the facilities which the key can be used to produce.
So I created new font as Unicode character set. Copied and pasted 500 characters to the new font – the solution to my combining question.
Yes. However, please remember that this technique is limited by the fact that some (many?) applications will assume things about the characters based upon the Unicode code point value, so whereas overlaying glyphs for symbols into code point positions used for Latin letters may well be fine, overlaying glyphs for symbols into code point positions used for Arabic letters might lead to an application assuming that they are from right to left. Also, if a code point which is in regular Unicode (as contrasted with a Private Use Area code point position) is unallocated, some applications may refuse to accept that that code point is available for use.
Whilst recognizing that having symbols keyable as ordinary letters of the alphabet is helpful, and I have done it myself, I tend to use the Unicode Private Use Area quite a lot. For example, the symbols in my Quest text font.
http://www.users.globalnet.co.uk/~ngo/QUESTTXT.TTF
I have been experimenting with an idea of mine to produce a pdf using Open Office 2.0 (it’s a free package from the http://www.openoffice.org/ webspace) such that the pdf is a type tray for symbols from a font. This would mean that an end user of a font could copy symbols from such a pdf and paste them into an application, as a sort of simulation of hand setting with metal type and having to get out a type tray to find a particular sort. I am thinking of producing such a pdf for my Chronicle Text font, a type tray of the ligature characters which are located in the Private Use Area.
http://www.users.globalnet.co.uk/~ngo/CHRONTXT.TTF
William Overington