On Sun, 30 Mar 2014 04:17:50 -0400 Eduard Dumitrescu <edumi...@uottawa.ca> wrote: > Hi, > > This appears to be an 'apertium-dbus' bug (not 'apertium-tolk'). It > seems the code in 'src/command_line.py' used the deprecated 'os.popen3' > function and did not encode the input to UTF-8 before attempting to send > it over (nor did it decode the output). Switching to 'subprocess.Popen' > and adding the required encode/decode UTF-8 calls appears to have fixed > this bug. > > Patch attached.
I can confirm your patch works for me. Thank you. I had the same problem before the patch (in jessie armhf). I looked upstream and http://svn.code.sf.net/p/apertium/svn/trunk/apertium-dbus/src/command_line.py seems to have it solved too (since dec.2012), but I haven't tried that. They don't seem to have done any new release, just commits. According to the upstream log they migrated to python3 before fixing this, and the current apertium-dbus packages depend on python 2, so maybe it would be easier to use your patch, at least until the whole packaging updates its code and dependencies. Should I open a bug in apertium-dbus ? Thank you very much -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
