The correct opcode is part of the multipass opcode set. None of these currently work in back-translation as far as I know. It would be good to fix this. John On Thu, May 01, 2014 at 07:32:32PM +0200, Bue Vester-Andersen wrote: > Hi, > > I would like to suggest that the "correct" opcode should be changed to also > work in back-translation as an extra pass after the actual back-translation. > It was primarily meant to deal with scanos and the like, and currently only > works in forward translation. However, it would also be very useful in > back-translation, because the result of back-translation is sometimes > ambiguous, simply because Braille was made to be read by humans, not > machines. > > I don't have any good examples in English, but I am sure that others could > find them. In Danish, for instance, all accented letters are written in the > same way in 6 dots regardless of which accent is used. e acute and e grave > look the same (5-15). Yes, what a system, but I don't have the power to > change it, unfortunately. (smile) There must be similar if not so stupid > examples in other languages. > > Alternatively, one could of course use "nofor always", but it is less safe, > more messy, and harder to decipher. besides, in my case, I would have to > include the entries twice, once for grade 1 and once for grade 2. > > I know this would create an incompatibility with tables that already use the > "correct" opcode for scanos. They would have to write "noback correct" in > stead. > > Best regards > Bue Vester-andersen > > > 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