In the section on Writing Translation Tables in the documentation it is stated that character-definnition opcodes should proceed everything else except display opcodes. I will check just what is said and maybe state this more forcefully. John On Sun, Sep 12, 2010 at 01:09:17AM +0200, Samuel Thibault wrote: > Hello, > > Birkir Gunnarsson, le Sat 11 Sep 2010 21:38:59 +0000, a ?crit : > > Have not heard anything about committing these tables to liblouis. > > It takes time to find out time to have a look at them :) > > I have translated them to the brltty format and sent Dave Mielke a > patch, so it'll be in brltty. > > For liblouis, lou_checktable doesn't complain on the 8dot table, and > produces the following warnings on the 6dot table: > > ? lou_checktable /tmp/is-chardefs6.cti > is-chardefs6.cti:32: Dot pattern \3456/ is not defined. > is-chardefs6.cti:33: Dot pattern \6/ is not defined. > is-chardefs6.cti:34: Dot pattern \6/ is not defined. > is-chardefs6.cti:34: Dot pattern \6/ is not defined. > is-chardefs6.cti:35: Dot pattern \6/ is not defined. > is-chardefs6.cti:35: Dot pattern \6/ is not defined. > is-chardefs6.cti:37: Dot pattern \4/ is not defined. > is-chardefs6.cti:37: Dot pattern \34/ is not defined. > is-chardefs6.cti:38: Dot pattern \34/ is not defined. > is-chardefs6.cti:38: Dot pattern \4/ is not defined. > is-chardefs6.cti:40: Dot pattern \4/ is not defined. > is-chardefs6.cti:40: Dot pattern \456/ is not defined. > is-chardefs6.cti:41: Dot pattern \456/ is not defined. > is-chardefs6.cti:41: Dot pattern \4/ is not defined. > 14 errors found. > > AIUI, this is because you need to define these patterns before using > them in numsign & such. Just moving these "Braille Indicators" lines to > the end of the file fixes things. > > On another side, your 8dot file gives non-ascii characters to the > sign/lowercase/etc. commands, and your file is apparently encoded in > latin1. To make sure things work ok on all systems independently on > its default charset, you should replace these with unicode numbers. > Non-ascii characters in comments are fine, however, but should probably > be encoded in utf-8. If you don't know how to produce a utf-8 file, > just send it as you have already done and we'll convert it to utf-8. > > Samuel > For a description of the software and to download it go to > http://www.jjb-software.com -- John J. Boyer, Executive Director GodTouches Digital Ministry, Inc. http://www.godtouches.org Madison, Wisconsin, USA Peace, Love, Service For a description of the software and to download it go to http://www.jjb-software.com