UTF-8 in the opcode arguments would be a bad idea. Since the beginning, the character argument has accepted characters from 0 to 127 as valid. UTF-8 conflicts with this. I have made this point before. John On Mon, Jul 02, 2012 at 10:53:35AM +0200, Christian Egli wrote: > Hi Mesar > > Mesar Hameed <mesar.hameed@xxxxxxxxx> writes: > > > At this point all the tables are in utf-8, this does not mean that > > they are valid tables, infact I have seen several tables that have > > many errors, because they do not use \x for declaring their > > characters. > > I applaud your efforts to get the tables into a uniform state. However > since your commit I get tons of warnings on `make check`[1]. This means > that we have many tables now that do not work. I was hoping to have a > release before my vacation on July 15th, but we cannot release with this > serious regression. > > Before we change the encoding of the tables we need to either > > - change the tables to use the \xhhhh notation or > - enhance compileTranslationTable.c to accept utf-8 in the opcode > arguments > > Only once this is done we can safely change the encoding. Please revert > your changes. > > Thanks > Christian > > > Footnotes: > [1] in fact if compileTranslationTable.c would not continue to search > on the system path these warnings would be actual errors. > -- > Christian Egli > Swiss Library for the Blind, Visually Impaired and Print Disabled > Grubenstrasse 12, CH-8045 Zürich, Switzerland > > ----- > Tag der offenen Tuer > Die SBS laedt Sie herzlich ein: 30. Juni 2012 von 9 bis 16 Uhr. > Mehr Informationen erhalten Sie unter www.sbs.ch/offenetuer > For a description of the software, to download it and links to > project pages go to http://www.abilitiessoft.com -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com