Yes it is me again. Now I want make my project which is Mac OS X Unicode
savvy a bit more international savvy under Classic.
Within the great TextUtilities library which were shipped with the RB 4.5
Previews there was the following code line:
GetFontTextEncoding("System")
Of course it was wrapped within a lot of nil checks, I really liked the
approach. Within a MacCentralEuropean environment for example this would run
quite character safe.
But it always returns nil here on my german Mac OS 9 system. It works if I
change the meta value "System" to a real available font.
This would be great if it would work with "System" and "SmallSystem", too.
Otherwise I have to offer a selectable Control.TextFont list. Do I have to
realbug and "Feature Request" it, or is there a better way?
When this line never worked, why was it used by RB within TextUtilities?
On the other hand I can avoid using a Textconverter list if I use the
current situation with GetFontTextEncoding(<selectedFont>). Communicating
the proper usage of such a list is difficult in my opinion.
|