Hi Mesar, Why can't you just use the ucBrl mode bit? It must be used together with dotsIO , for example, dotsIO|ucBrl Unicode by default would change the way liblouis operates and would break many things. John On Sat, Aug 18, 2012 at 10:17:13AM +0100, Mesar Hameed wrote: > Hi John, all, > > I think we have discussed this issue before, but I cant seem to locate the > previous thread. > > We want liblouis to output unicode braille by default where no dis file has > been defined. > > for example put these 4 lines in a test.cti: > --cut-- > letter a 1 > letter n 1345 > letter t 2345 > letter h 125 > --cut-- > > currently if we do: > echo "hat" | ../tools/lou_translate -f test.cti > we get "hat" printed to the terminal. > We want the unicode braille for 125 1 2345 i.e. "⠓⠁⠞" to be printed instead > > because then we can see that the translation really has happend. > > for legacy devices that do not accept unicode they can simply use a dis table > as their first > table in the list of tables just before printing. > > motivation for this change: > 1. a clearer seperation between language table, and hardware translation. > if I have a document I can just process it to produce unicode braille, then > if the document > needs to be printed on various printers, i just have to preload the the dis > file for that > manufacturer. > we would have index.dis, tiger.dis brf.dis etc. > 2. it is more understandable for a braille transcriber to see what has > happend when they > do the translation in the terminal or in a gui. > They can see exactly what dots will be printed, no need to double translate > in their head "h" > gives "125", "a" gives "1" etc. > This will reduce the transcribers mental load and cut the number of errors. > 3. will solve a bug for when users switch between using their > screenreader+liblouis and > on the other hand brltty directly. > (for an example of this bug see: > https://bugzilla.gnome.org/show_bug.cgi?id=651264) > > I have discussed this change with Bert and they already do this in Odt2brl > > 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