i3 FAQ - Individual question feed

i3 FAQ - Individual question feedhttps://faq.i3wm.org/questions/Frequently asked questions and answers about the i3 window managerenCopyright i3, 2012Mon, 14 Jul 2014 06:34:52 +0000UTF national characters in window title.https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/Hi, There is certainly something wrong in the way i3 handles windows titles. There are applications which work properly - like urxvt or xterm with "utf8Title" resource set and such which do not - like mupdf or libreoffice. You can reproduce it by opening a file containing in its name characters like "ążźłüäöß". Using xprop you can check that WM\_NAME property is set to a right utf-8 string (\_NET\_WM\_NAME is rarely used). Also mupdf developer swears he handles the properties the right way and it must be a problem of the WM. And indeed. I installed openbox and there all the titles are properly shown. What do you think?Thu, 15 May 2014 08:01:34 +0000https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/Comment by Adaephon for Hi, There is certainly something wrong in the way i3 handles windows titles. There are applications which work properly - like urxvt or xterm with "utf8Title" resource set and such which do not - like mupdf or libreoffice. You can reproduce it by opening a file containing in its name characters like "ążźłüäöß". Using xprop you can check that WM_NAME property is set to a right utf-8 string (_NET_WM_NAME is rarely used). Also mupdf developer swears he handles the properties the right way and it must be a problem of the WM. And indeed. I installed openbox and there all the titles are properly shown. What do you think? https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4058#comment-4058Do you use i3 4.8? If so, it leaves mostly the underlying libraries as difference. Which distribution are you using?Sun, 29 Jun 2014 05:19:11 +0000https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4058#comment-4058Comment by Adaephon for Hi, There is certainly something wrong in the way i3 handles windows titles. There are applications which work properly - like urxvt or xterm with "utf8Title" resource set and such which do not - like mupdf or libreoffice. You can reproduce it by opening a file containing in its name characters like "ążźłüäöß". Using xprop you can check that WM_NAME property is set to a right utf-8 string (_NET_WM_NAME is rarely used). Also mupdf developer swears he handles the properties the right way and it must be a problem of the WM. And indeed. I installed openbox and there all the titles are properly shown. What do you think? https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=3827#comment-3827Could you add the line from your configuration in which you set `font`, please? Also, are you sure that the font supports the characters in question?Fri, 16 May 2014 07:48:20 +0000https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=3827#comment-3827Comment by bonidydy for Hi, There is certainly something wrong in the way i3 handles windows titles. There are applications which work properly - like urxvt or xterm with "utf8Title" resource set and such which do not - like mupdf or libreoffice. You can reproduce it by opening a file containing in its name characters like "ążźłüäöß". Using xprop you can check that WM_NAME property is set to a right utf-8 string (_NET_WM_NAME is rarely used). Also mupdf developer swears he handles the properties the right way and it must be a problem of the WM. And indeed. I installed openbox and there all the titles are properly shown. What do you think? https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4101#comment-4101After reading the source in window.c I can see that all the application that do not set \_NET\_WM\_NAME won't get a proper UTF-8 title. What's the reason behind it? It seems that the other window managers take a more liberal approach with no harm.Wed, 02 Jul 2014 16:05:35 +0000https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4101#comment-4101Comment by bonidydy for Hi, There is certainly something wrong in the way i3 handles windows titles. There are applications which work properly - like urxvt or xterm with "utf8Title" resource set and such which do not - like mupdf or libreoffice. You can reproduce it by opening a file containing in its name characters like "ążźłüäöß". Using xprop you can check that WM_NAME property is set to a right utf-8 string (_NET_WM_NAME is rarely used). Also mupdf developer swears he handles the properties the right way and it must be a problem of the WM. And indeed. I installed openbox and there all the titles are properly shown. What do you think? https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4046#comment-4046This is what I also believed till I tested the same applications with openbox :-). For ALL of them openbox shows the title properly. I use the same font and the same test files.Fri, 27 Jun 2014 13:34:24 +0000https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4046#comment-4046Comment by bonidydy for Hi, There is certainly something wrong in the way i3 handles windows titles. There are applications which work properly - like urxvt or xterm with "utf8Title" resource set and such which do not - like mupdf or libreoffice. You can reproduce it by opening a file containing in its name characters like "ążźłüäöß". Using xprop you can check that WM_NAME property is set to a right utf-8 string (_NET_WM_NAME is rarely used). Also mupdf developer swears he handles the properties the right way and it must be a problem of the WM. And indeed. I installed openbox and there all the titles are properly shown. What do you think? https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=3834#comment-3834The configuration is "font pango:Droid Sans 9". Droid has all the glyphs needed.Fri, 16 May 2014 20:35:58 +0000https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=3834#comment-3834Comment by nilnull for Hi, There is certainly something wrong in the way i3 handles windows titles. There are applications which work properly - like urxvt or xterm with "utf8Title" resource set and such which do not - like mupdf or libreoffice. You can reproduce it by opening a file containing in its name characters like "ążźłüäöß". Using xprop you can check that WM_NAME property is set to a right utf-8 string (_NET_WM_NAME is rarely used). Also mupdf developer swears he handles the properties the right way and it must be a problem of the WM. And indeed. I installed openbox and there all the titles are properly shown. What do you think? https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4173#comment-4173Here is a screenshot that proves the problem is application-specific: http://imgur.com/zaTpqJ6 It shows the same URL opened in two browsers: with Opera the title is fine, with NetSurf it seems i3 did not notice the title text is utf-8 encoded. I did not find any obvious difference with xprop.Tue, 08 Jul 2014 19:29:14 +0000https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4173#comment-4173Comment by Adaephon for Hi, There is certainly something wrong in the way i3 handles windows titles. There are applications which work properly - like urxvt or xterm with "utf8Title" resource set and such which do not - like mupdf or libreoffice. You can reproduce it by opening a file containing in its name characters like "ążźłüäöß". Using xprop you can check that WM_NAME property is set to a right utf-8 string (_NET_WM_NAME is rarely used). Also mupdf developer swears he handles the properties the right way and it must be a problem of the WM. And indeed. I installed openbox and there all the titles are properly shown. What do you think? https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4227#comment-4227`WM_NAME` may use 'ISO Latin 1', 'Compound Text Encoding' (which predates UTF-8 by 3 years), or possibly C-strings (zero-teminated byte sequence without specified encoding). `_NET_WM_NAME` is designed to use UTF-8 encoding. Thus I think the issue is firmly on the side of the applications, not i3. Mon, 14 Jul 2014 06:34:52 +0000https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4227#comment-4227Comment by nilnull for Hi, There is certainly something wrong in the way i3 handles windows titles. There are applications which work properly - like urxvt or xterm with "utf8Title" resource set and such which do not - like mupdf or libreoffice. You can reproduce it by opening a file containing in its name characters like "ążźłüäöß". Using xprop you can check that WM_NAME property is set to a right utf-8 string (_NET_WM_NAME is rarely used). Also mupdf developer swears he handles the properties the right way and it must be a problem of the WM. And indeed. I installed openbox and there all the titles are properly shown. What do you think? https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4174#comment-4174And yet even NetSurf *sometimes* displays utf-8 characters as it should: See http://imgur.com/aQ6GEDz . If any developer is looking at this issue I can help reproducing / testing.Wed, 09 Jul 2014 10:48:35 +0000https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4174#comment-4174Comment by Adaephon for Hi, There is certainly something wrong in the way i3 handles windows titles. There are applications which work properly - like urxvt or xterm with "utf8Title" resource set and such which do not - like mupdf or libreoffice. You can reproduce it by opening a file containing in its name characters like "ążźłüäöß". Using xprop you can check that WM_NAME property is set to a right utf-8 string (_NET_WM_NAME is rarely used). Also mupdf developer swears he handles the properties the right way and it must be a problem of the WM. And indeed. I installed openbox and there all the titles are properly shown. What do you think? https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4045#comment-4045I did some testing on my Ubuntu machine, `font pango: Terminus 9` and latest i3. I have no problems with URxvt, libreOffice or XTerm (with utf8Titles) using greek and assorted math symbols. The existance of the XTerm option leads me to believe that it is an issue of the application used not of i3.Fri, 27 Jun 2014 13:06:06 +0000https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4045#comment-4045Comment by bonidydy for Hi, There is certainly something wrong in the way i3 handles windows titles. There are applications which work properly - like urxvt or xterm with "utf8Title" resource set and such which do not - like mupdf or libreoffice. You can reproduce it by opening a file containing in its name characters like "ążźłüäöß". Using xprop you can check that WM_NAME property is set to a right utf-8 string (_NET_WM_NAME is rarely used). Also mupdf developer swears he handles the properties the right way and it must be a problem of the WM. And indeed. I installed openbox and there all the titles are properly shown. What do you think? https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4059#comment-4059I use i3 4.8 from Debian sid. I update quite regularly so all the dependencies reflect the current state of the repository and should be more or less the same as in Ubuntu.Sun, 29 Jun 2014 10:26:25 +0000https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4059#comment-4059Answer by bonidydy for Hi, There is certainly something wrong in the way i3 handles windows titles. There are applications which work properly - like urxvt or xterm with "utf8Title" resource set and such which do not - like mupdf or libreoffice. You can reproduce it by opening a file containing in its name characters like "ążźłüäöß". Using xprop you can check that WM_NAME property is set to a right utf-8 string (_NET_WM_NAME is rarely used). Also mupdf developer swears he handles the properties the right way and it must be a problem of the WM. And indeed. I installed openbox and there all the titles are properly shown. What do you think? https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?answer=4043#post-id-4043I'd like to bump the topic. There is certainly something wrong in the way i3 handles windows titles. There are applications which work properly - like urxvt or xterm with "utf8Title" resource set and such which do not - like mupdf or libreoffice. You can reproduce it by opening a file containing in it's name characters like "ążźłüäöß". Using xprop you can check that WM\_NAME property is set to a right utf-8 string (\_NET\_WM\_NAME is rarely used). Also mupdf developer swears he handles the properties the right way and it must be a problem of the WM. And indeed. I installed openbox and there all the titles are properly shown. What do you think?Fri, 27 Jun 2014 08:19:56 +0000https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?answer=4043#post-id-4043Comment by Adaephon for I'd like to bump the topic. There is certainly something wrong in the way i3 handles windows titles. There are applications which work properly - like urxvt or xterm with "utf8Title" resource set and such which do not - like mupdf or libreoffice. You can reproduce it by opening a file containing in it's name characters like "ążźłüäöß". Using xprop you can check that WM_NAME property is set to a right utf-8 string (_NET_WM_NAME is rarely used). Also mupdf developer swears he handles the properties the right way and it must be a problem of the WM. And indeed. I installed openbox and there all the titles are properly shown. What do you think? https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4044#comment-4044I think that this is not an answer :) Just editing the question should also bump the question, with the additional benefit, that your question is still shown unanswered in contrast to just being unanswered.Fri, 27 Jun 2014 08:35:29 +0000https://faq.i3wm.org/question/3816/utf-national-characters-in-window-title/?comment=4044#comment-4044