Bug#473561:

2014-11-11 Thread xdrudis
On Sun, 30 Mar 2014 04:17:50 -0400 Eduard Dumitrescu 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

Bug#473561:

2014-03-30 Thread Eduard Dumitrescu
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 addin

Bug#473561: Interprets input data as ascii rather than utf8

2010-04-22 Thread jean . michel . philippe
Hello, I tried the trick written in the Apertium wiki but this did not work because module “sys” doesn't have a “setdefaultencoding” function. Nevertheless after many tries, I finally had it work using temporary files instead of stdin/stdout to transfer text to and from Apertium. I modified th

Bug#473561: Interprets input data as ascii rather than utf8

2008-03-31 Thread Francis Tyers
El lun, 31-03-2008 a las 13:28 +0200, Jelmer Vernooij escribió: > Package: apertium-tolk > Version: 0.2-2 > Severity: normal > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Apertium-tolk will try to interpret all input data as ascii. However, > since it is a GTK+ app, all input will be

Bug#473561: Interprets input data as ascii rather than utf8

2008-03-31 Thread Jelmer Vernooij
Package: apertium-tolk Version: 0.2-2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Apertium-tolk will try to interpret all input data as ascii. However, since it is a GTK+ app, all input will be in UTF-8, causing it to traceback when non-ascii characters are entered: org.freed