Hi,
This was reported by a Debian user. Please retain
339586-forwar...@bugs.debian.org in your responses, so that the Debian
BTS may have a copy of your response.
ICCCM specifies WM_NAME, as an uninterpreted string, in the
latin-1 domain, I think, EWMH specifies _NET_WM_NAME as
2009/7/9 Manoj Srivastava :
> Hi,
>
> This was reported by a Debian user. Please retain
> 339586-forwar...@bugs.debian.org in your responses, so that the Debian
> BTS may have a copy of your response.
>
> ICCCM specifies WM_NAME, as an uninterpreted string, in the
> latin-1 domain,
2009/7/9 Thomas Adam :
> 2009/7/9 Manoj Srivastava :
>> Hi,
>>
>> This was reported by a Debian user. Please retain
>> 339586-forwar...@bugs.debian.org in your responses, so that the Debian
>> BTS may have a copy of your response.
>>
>> ICCCM specifies WM_NAME, as an uninterpreted s
2009/7/9 Vincent Lefevre :
> On 2009-07-09 22:43:55 +0100, Thomas Adam wrote:
>> Oh -- and I ought to mention, the application itself has to understand
>> UTF8 since it sets the _NET_WM_NAME XAtom in the first place. You can
>> do this for yourself (I assume you're running under a UTF8 locale,
>>
On 2009-07-09 22:43:55 +0100, Thomas Adam wrote:
> Oh -- and I ought to mention, the application itself has to understand
> UTF8 since it sets the _NET_WM_NAME XAtom in the first place. You can
> do this for yourself (I assume you're running under a UTF8 locale,
> etc., already):
No, on my machin
On 2009-07-09 23:33:04 +0100, Thomas Adam wrote:
> I think part of the problem is your continued assertion that WM_NAME
> is used in preference of _NET_WM_NAME, and it's being blind-sighted a
> little. So please, I'd like you to detail step-by-step here, exactly
> what it is we would need to do to
2009/7/10 Vincent Lefevre :
> On 2009-07-09 23:33:04 +0100, Thomas Adam wrote:
>> I think part of the problem is your continued assertion that WM_NAME
>> is used in preference of _NET_WM_NAME, and it's being blind-sighted a
>> little. So please, I'd like you to detail step-by-step here, exactly
>>
