The pronto guide's last pages are of little use : they show code pages... but only "?" signs.

Does anyone have the real thing ?

I'm too lazy to write a program to show these on the pronto for me to choose from. :-)

I can see all the codes except that F032 to F0FF are all squares.

Do you have the latest version of Acrobat Reader? That could be your problem.

The PDF is pretty much useless as the Pronto.ttf font was not embedded in it.

Run charmap.exe on a windows machine to determine the low-order byte needed for unicode encoding. For example, the DTS symbol is 254 or 255 which is 0xFE or 0xFF.

To get this symbol to display on the the pronto from script, you must use unicode characters in a string and prefix with the code group 0xF0 as follows '/uf0fe' or '/ufoff'.

I ran into a related problem which I have reportred to Philips. Take a string containing ASCII characters. copy it to a widget label and character codes like ascii 174 (the registered symbol) or ascii 96 (the apostrophe) display correctly. Take the same string and break it down in to lines (may not be necessary, but it is what failed for me) storing each line into an element of an array. Each element of the array should now be typed as a string. Copy each line to the widget of a label (I appended \n as line breaks to each word) as wlabel+=wlabel+array[i]+"\n" and suddenly funny (I suspect Unicode) characters appear for the symbols like ascii 96 and ascii 174.

I do not believe this should be happening whatever the code type. It is not logical.

Thanks Lyndel, I didn't know I was to include the F0 prefix.

I,ve got the same problem:

I have a text like "test äöü" in a variable x , if i print this with System.print(x) on the
Debug panel everything is correct. if put this var in a label like widget("test").label=x;
i got utf-8 chars, which are not correct.

Is there a workaround for this ?

Not at this time AFAIK. I had to add special code just so it would look somewhat reasonable. Philips is aware of the problem.