Hello Mesar, on behalf of the BrailleBlaster steering committee, I understand and appreciate your concern about UTF8. Clearly we should have started that way. I have a suggestion for how to settle this issue. First of all, let's make the tables work with liblouis today. My suggestion is to put everything beyond 127 into the /x notation. At some later time, I would very much like to convert to using UTF8. Vic Beckley has begun working part-time for ViewPlus on liblouis items specific to the company, and he is presently waiting on us to give him a new list of things to do. In the meantime, I have asked him to work with you to do this improvement. Okay with all concerned? Thanks!!! John Gardner -----Original Message----- From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Mesar Hameed Sent: Monday, July 02, 2012 9:53 AM To: liblouis-liblouisxml@xxxxxxxxxxxxx Subject: [liblouis-liblouisxml] Re: [liblouis] r715 committed - the last batch of files converted to utf-8. 128 to 255 is the range for codepages, which is now depricated due to its inherent problems. For example we cant write german+russian texts, or swedish+greek etc. unicode will make sure that we will be able to support all combinations of languages at once. I believe that it can be done, but in a round about and error prone way. Thanks, Mesar On Mon 02/07/12,10:16, John J. Boyer wrote: > My mistake. I meant to say 0 to 255. > > John > > On Mon, Jul 02, 2012 at 04:10:03PM +0100, Mesar Hameed wrote: > > Hi John, > > > > On Mon 02/07/12,09:52, John J. Boyer wrote: > > > 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. > > > > According to the standard 0 to 127 is exactly the same for ascii and for utf-8, so this is not a conflict. > > > > Wikipedia reitterates this: > > > > "The first 128 characters of Unicode, which correspond one-to-one > > with ASCII, are encoded using a single octet with the same binary value as ASCII, making valid ASCII text valid UTF-8-encoded Unicode as well." > > > > from: http://en.wikipedia.org/wiki/UTF-8 > > > > I could dig up a more reputable source if its required. > > > > Thanks, > > Mesar > > 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 For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com