Hi Bert, That patch is only for UTF-8 output, unless I missed something? My patch is based on iconv, which I would say is preferable on *nix systems... As I suggested earlier, we could introduce a new function, showStringUnicode() which in turn could use iconv (if available), and fallback on hand-crafted UTF-8 on encoder on *nix and hand-crafted encoder for UTF-16 on windows (or simply use the windows API). Since we are _probably_ only going to output a limited subset of Unicode, i.e. U+2800..U+28FF, we don't have spend that much time on handling edge-cases, we can simply error-out on anything that isn't a braille-pattern, or? Best, Simon On 15 January 2015 at 19:28, Bert Frees <bertfrees@xxxxxxxxx> wrote: > Hi Simon, > > I thought I had added a unicode option to lou_translate, but it was > lou_trace > and it's on a branch: > > https://github.com/liblouis/liblouis/commit/0b162ae430317713db5594d342f0a598813e79a3. > Your > patch is probably similar? Maybe we could combine our stuff, make sure > it's done > consistently etc. So if you want you can add changes to my branch, > otherwise > I'll assume it's okay and I just add the option to lou_translate. > > Thanks, > Bert > > > Simon Aittamaa writes: > > > Hi, > > > > Is there any way to output unicode from lou_translate? For example: > > > > $ echo "Α" | lou_translate -uf unicode.dis,en-ueb-g1.ctb > > ⠰⠠⠨⠁ > > > > I've currently patch lou_translate for this, but I was wondering if there > > is a "standard" way of doing this? > > > > Best, > > Simon > > For a description of the software, to download it and links to > project pages go to http://www.abilitiessoft.com >