Re: [dev] Help to debug window name with special characters

2023-07-08 Thread NRK
On Thu, Jul 06, 2023 at 10:23:45AM -0300, Dr. André Desgualdo Pereira wrote:
> Second, xprop change from
> WM_NAME(STRING) = "André Desgualdo Pereira.odt - OpenOffice Writer"
> to 
> WM_NAME(STRING) = "André Desgualdo Pereira.odt - OpenOffice Writer"
> and also a new attibute seems to be added:
> _NET_WM_NAME(STRING) = "Andr\303\251 Desgualdo Pereira.odt - OpenOffice 
> Writer"

"\303\251" is a utf8 sequence (in octal) which maps to U+00E9 (é):
https://www.compart.com/en/unicode/U+00E9

DWM (and dmenu) deals specifically with utf8 IIRC. I'm not sure what
encoding those other two are using, but it's probably not using utf8
which is why it's not working.

Try to see if there's some settings in those application (or their
gui libraries) to make them use utf8.

- NRK



Re: [dev] Help to debug window name with special characters

2023-07-07 Thread Dr . André Desgualdo Pereira
Reporting a progress: I suspect the problem is OpenOffice and LibreOffice 
expect a working Tkinter module for python2.7 but Debian deprecated python2.7. 
So no _NET_WM_NAME is set. 
Weird thing is that somehow the name is set correctly if it cointains a 
japanese character (even with latin letters like ã,á,é,ó, etc) or if it doens't 
contains any of those latin letters. Even with no _NET_WM_NAME setted. 

On 05/07/2023 21:40, NRK wrote:
> On Wed, Jul 05, 2023 at 08:11:39AM -0300, Dr. André Desgualdo Pereira wrote:
> > Also xprop show the window name correctly, but wmctrl shows "N/A".
> 
> You might want to share the full output of xprop. Otherwise just sharing
> the `*_NAME` properties is fine too: `xprop | grep _NAME`
> 
> Since you said it works on debian 11, it might also be useful to share
> the output of them from debian 11 and compare with 12 to see if anything
> changed.
> 
> (Specifically, I'm interested in the "type" of the property. If it's
> anything other than STRING or UTF8_STRING then that might be a hint.)
> 
> - NRK
> 

-- 
Dr. André Desgualdo Pereira
Psiquiatra - CRM/SP: 120218 - RQE: 61032
WhatsApp: (11) 985-847-809 - email: des...@gmail.com
Consultório Lapa: Rua Clélia, 2208 - sala 307
Consultório Santana: Av. Gen. Ataliba Leonel, 93 - sala 61



Re: [dev] Help to debug window name with special characters

2023-07-07 Thread Dr . André Desgualdo Pereira
lol you are funny. I wish I didn't have to use anything else, it would be so 
much easier.
On 05/07/2023 18:50, Nikita Krasnov wrote:
> > Some window name are incomplete on dwm status (screenshot attached). The 
> > name is "cut" after the first special character (for example: if a window 
> > name is "André Desgualdo Pereira" it will show only "Andr").
> 
> Everyone knows that special characters are bloat, duh. Your system must use
> only use ASCII.
> 
> (sarcasm)
> 
> -- 
> Nikita
> 

-- 
Dr. André Desgualdo Pereira
Psiquiatra - CRM/SP: 120218 - RQE: 61032
WhatsApp: (11) 985-847-809 - email: des...@gmail.com
Consultório Lapa: Rua Clélia, 2208 - sala 307
Consultório Santana: Av. Gen. Ataliba Leonel, 93 - sala 61



Re: [dev] Help to debug window name with special characters

2023-07-06 Thread Dr . André Desgualdo Pereira
I notice a change in xprop if I run:

xdotool search --name "André Desgualdo Pereira.odt - OpenOffice Writer" 
set_window --name "André Desgualdo Pereira.odt - OpenOffice Writer"

First, after renaming it (to exactly the same name xprop gives), the name shows 
just fine on dwmstatus (and also on wmctrl -l), 

Second, xprop change from
WM_NAME(STRING) = "André Desgualdo Pereira.odt - OpenOffice Writer"
to 
WM_NAME(STRING) = "André Desgualdo Pereira.odt - OpenOffice Writer"
and also a new attibute seems to be added:
_NET_WM_NAME(STRING) = "Andr\303\251 Desgualdo Pereira.odt - OpenOffice Writer"

On 05/07/2023 21:40, NRK wrote:
> On Wed, Jul 05, 2023 at 08:11:39AM -0300, Dr. André Desgualdo Pereira wrote:
> > Also xprop show the window name correctly, but wmctrl shows "N/A".
> 
> You might want to share the full output of xprop. Otherwise just sharing
> the `*_NAME` properties is fine too: `xprop | grep _NAME`
> 
> Since you said it works on debian 11, it might also be useful to share
> the output of them from debian 11 and compare with 12 to see if anything
> changed.
> 
> (Specifically, I'm interested in the "type" of the property. If it's
> anything other than STRING or UTF8_STRING then that might be a hint.)
> 
> - NRK
> 

-- 
Dr. André Desgualdo Pereira
Psiquiatra - CRM/SP: 120218 - RQE: 61032
WhatsApp: (11) 985-847-809 - email: des...@gmail.com
Consultório Lapa: Rua Clélia, 2208 - sala 307
Consultório Santana: Av. Gen. Ataliba Leonel, 93 - sala 61



Re: [dev] Help to debug window name with special characters

2023-07-05 Thread Dr . André Desgualdo Pereira
Thank you so much NKR!

The full output of xprop is the following:

WM_LOCALE_NAME(STRING) = "en_US.UTF-8"
WM_ICON_NAME(STRING) = "André Desgualdo Pereira.odt - OpenOffice Writer"
WM_NAME(STRING) = "André Desgualdo Pereira.odt - OpenOffice Writer"
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0xf, 0x1, 0x1, 0x0, 0x0
WM_CLIENT_LEADER(WINDOW): window id # 0xe1
_NET_WM_PID(CARDINAL) = 26922
WM_CLIENT_MACHINE(STRING) = "desguai7"
WM_NORMAL_HINTS(WM_SIZE_HINTS):
program specified location: 0, 17
window gravity: Static
WM_CLASS(STRING) = "VCLSalFrame", "OpenOffice 4.1.14"
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
bitmap id # to use for icon: 0xe0825f
bitmap id # of mask for icon: 0xe08260
window id # of group leader: 0xe08248
XdndAware(ATOM) = BITMAP

I upgraded my machine to Debian 12, unfortunatelly I can't test it back on 
Debian 11. 

desgua

On 05/07/2023 21:40, NRK wrote:
> On Wed, Jul 05, 2023 at 08:11:39AM -0300, Dr. André Desgualdo Pereira wrote:
> > Also xprop show the window name correctly, but wmctrl shows "N/A".
> 
> You might want to share the full output of xprop. Otherwise just sharing
> the `*_NAME` properties is fine too: `xprop | grep _NAME`
> 
> Since you said it works on debian 11, it might also be useful to share
> the output of them from debian 11 and compare with 12 to see if anything
> changed.
> 
> (Specifically, I'm interested in the "type" of the property. If it's
> anything other than STRING or UTF8_STRING then that might be a hint.)
> 
> - NRK
> 




Re: [dev] Help to debug window name with special characters

2023-07-05 Thread Nikita Krasnov

Some window name are incomplete on dwm status (screenshot attached). The name is "cut" after the 
first special character (for example: if a window name is "André Desgualdo Pereira" it will show 
only "Andr").


Everyone knows that special characters are bloat, duh. Your 
system must use only use ASCII.


(sarcasm)

--
Nikita



Re: [dev] Help to debug window name with special characters

2023-07-05 Thread NRK
On Wed, Jul 05, 2023 at 08:11:39AM -0300, Dr. André Desgualdo Pereira wrote:
> Also xprop show the window name correctly, but wmctrl shows "N/A".

You might want to share the full output of xprop. Otherwise just sharing
the `*_NAME` properties is fine too: `xprop | grep _NAME`

Since you said it works on debian 11, it might also be useful to share
the output of them from debian 11 and compare with 12 to see if anything
changed.

(Specifically, I'm interested in the "type" of the property. If it's
anything other than STRING or UTF8_STRING then that might be a hint.)

- NRK



[dev] Help to debug window name with special characters

2023-07-05 Thread Dr . André Desgualdo Pereira
I would really appreciate some help on debugging a problem on displaying 
certain windows names.

Some window name are incomplete on dwm status (screenshot attached). The name 
is "cut" after the first special character (for example: if a window name is 
"André Desgualdo Pereira" it will show only "Andr"). 

It doesn't happen with every program, but it happens with OpenOffice and 
Libreoffice. 

Also xprop show the window name correctly, but wmctrl shows "N/A".

Also it didn't happen with Debian 11. It is happening with Debian 12.

I already recompiled dwm and reconfigured libc6 libglib2.0-0:amd64 
libxmu6:amd64 libx11-6:amd64

Any help on wherelse to check would be really appreciated. 

~ $ locale
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

desgua