On Tuesday, 20 December 2016 16:38:52 CET Boyuan Yang wrote:
> This version is in Debian unstable now.
>
> I tested with some non-utf8 locale (zh_CN.GB18030, es_SV aka iso-8859-1,
> zh_TW.BIG5) and UTF-8 locale. None of them crashed, so at least this NMU is
> not damaging too much. We may need s
在 2016年12月15日星期四 CST 下午8:54:38，Dominique Dumont 写道：
> And I'm worried that shutter may crash if used in a non-utf8 environment.
This version is in Debian unstable now.
I tested with some non-utf8 locale (zh_CN.GB18030, es_SV aka iso-8859-1,
zh_TW.BIG5) and UTF-8 locale. None of them crashed, so
On Friday, 16 December 2016 21:34:55 CET Torsten Schönfeld wrote:
> So it seems like the safest bet would be to try to decode the window
> name from UTF8, and if that fails, try Encode::X11 and its
> 'x11-compound-text' (Hi Kevin!).
ok, that makes sense.
For the record, here's what I'm going t
On 16.12.2016 20:02, Dominique Dumont wrote:
On Wednesday, 14 December 2016 10:54:16 CET Boyuan Yang wrote:
The original messy output, as indicated in screenshot in the Ubuntu bug,
looks like treating a latin-1-encoded binary data as UTF-8-encoded data
and showing them anyway.
In more details
[ 2nd try ]
On Wednesday, 14 December 2016 10:54:16 CET Boyuan Yang wrote:
> The original messy output, as indicated in screenshot in the Ubuntu bug,
> looks like treating a latin-1-encoded binary data as UTF-8-encoded data
> and showing them anyway.
In more details, the problematic code boils
On Wednesday, 14 December 2016 10:54:16 CET Boyuan Yang wrote:
> The original messy output, as indicated in screenshot in the Ubuntu bug,
> looks like treating a latin-1-encoded binary data as UTF-8-encoded data
> and showing them anyway.
In more details, the problematic code boils down to:
m
6 matches
Mail list logo
