Lars, I think I will remove those defaults, then you won't have any problem. It's just a matter of deleting a few lines of code. The defaults were originally put in to keep lazy table writers from complaining. I'll change en-us-g2.ctb I don't know what other tables might need additional noletsignbefore opcodes. John On Tue, May 04, 2010 at 08:11:38PM +0200, Lars Bj?rndal wrote: > Hi John! > > > By default, the liblouis compiler generates the following table entry: > > > > noletsignbefore . > > > > If you use a noletsignbefore opcode yourself this and other such entries > > are not generated. The same goes for noletsign and noletsignafter. > > But what if I don't want any noletsignbefore, and not the default > either, what should then be present in the table? > > > Would it be better to remove these defaults? > > If it's possible to omit them, it's OK to me. > > Thank you! > > Lars > > > On Tue, May 04, 2010 at 03:29:58PM +0200, Lars Bj?rndal wrote: > >> Hello John! > >> > >> After some more testing, I found that you are right. However, if a > >> single letter is followed by a period, then the letsign is not preceding > >> the character. Can you duplicate that? > >> > >> The uper case character is defined with uplow opcode in the Norwegian > >> tables. > >> > >> Lars > >> > >> "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx> writes: > >> > >> > Lars, > >> > > >> > Sorry it's taken me a while to get back to you. I've been busy with UTD > >> > and bugs in general. > >> > > >> > The letsign opcode works with both upper and lowercase letters in the > >> > eng-us tables. How are uppercase letters defined in your tabbles? > >> > > >> > Thanks, > >> > John > >> > > >> > On Fri, Apr 30, 2010 at 12:45:07PM +0200, Lars Bj?rndal wrote: > >> >> Hi John! > >> >> > >> >> > Lars, > >> >> > > >> >> > The English tables contain some tricks. The word "a" is given the > >> >> > opcode > >> >> > largesign. This was done before the opcodes nolletsign, > >> >> > noletsignbefore > >> >> > and noletsignafter were included. You should be able to write > >> >> > something > >> >> > like: > >> >> > > >> >> > nolitsign e > >> >> > > >> >> > Each letter requires its own entry. The liblouis compiiler assigns > >> >> > some > >> >> > letters and punctuation marks used in English to these noletsign > >> >> > opcodes > >> >> > by defaulgt. However, if you use any of them it will not do so. > >> >> > >> >> Thank you! Letsign and noletsign works for lower case letters. For upper > >> >> case, however, it doesn't. So, by using 'letsign 56', a single letter o > >> >> is translated into '<56>o', but a capital letter O is still treated as > >> >> '<6>o', not '<56><6>o'. Should that be fixed by adding the letter O as a > >> >> word? > >> >> > >> >> Lars > >> >> > >> >> > On Wed, Apr 28, 2010 at 08:05:27PM +0200, Lars Bj?rndal wrote: > >> >> >> Hi! > >> >> >> > >> >> >> I'm working on single letters and grade 2. How are you doing this for > >> >> >> the english tables in liblouis, e.g. why isn't the single letter word > >> >> >> 'a' output as '56-1' according to the tables? > >> >> >> > >> >> >> I'm aware of the letsign and noletsign, but I cannot find these > >> >> >> opcodes > >> >> >> in the English tables, neither can I find lines like 'word a 1'. > >> >> >> > >> >> >> If choosing to use noletsign, should the characters be typed > >> >> >> separated > >> >> >> by comma? > For a description of the software and to download it go to > http://www.jjb-software.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 and to download it go to http://www.jjb-software.com