Hi John, On Tue 03/07/12,10:05, John J. Boyer wrote: > If UTF8 is allowed in the character argument of opcodes, no characters > above 127 can be used. This would invalidate any tables using Latin-1. Yes, they are already been converted to utf8, i.e. no byte uses values above 127 as per the unicode standard. If they need to represent aumlouts greek symbols etc, they are correctly encoded using utf8. > People would not be able to simply type letters on their keyboards. Sorry i think you are mixing computer representation, with human readable representation. The point of utf8 is: * for everyone to be able to use their keyboards, and directly see on the screen what characters they have typed. * their text independant of location of the reader, is exactly what the author wrote. I can quite happely write swedish text and send it to you, and you can receive it perfectly fine, as long as the file is utf8 encoded. If i send it as latin1, I am presuming that you will open it in latin1, and if you dont then you will not be able to read the content correctly. To reiterate, At this moment in time, no tables are using values above 127, but they are displaying correctly for everyone, because they use utf8. so we wish opcodes to accept utf8 operands. Of course, when it comes to sending for printing, these values are correctly mapped using the dis files to fall in within the characters that the hardware accepts. Mesar For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com