Re: [blfs-dev] Does xterm work for UTF-8 ?
Le 10/02/2013 03:29, Ken Moffat a écrit : In connection with reviewing the TrueType fonts I build, I was going to ask if there was a reason why the book still installs legacy xorg fonts. I've only used TTF/OTF fonts for several years, and the only issue I've noticed is that xcalc can't display a square root sign on the appropriate keycap. But before asking, I thought I ought to take a look at xterm (usually, I use rxvt-unicode). When I built that - by the book, apart from putting it /usr/local but with luit in /usr - I got unpleasant results : I typed #čőäůåēũñâòğçǫŀıḅ which for anyone missing some glyphs is hash, c-caron, o-doubleacute, a-diaeresis, u-abovering, a-abovering, e-macron, u-tilde, n-tilde, a-circumflex, o-grave, g-breve, c-cedilla, o-ogonek, l-with-middle-dot, dotless-i, b-with-belowdot. Apart from the hash, those are regular european latin letters [ ok, I'll grant you that u-tilde is obsolete ]. But the following were replaced in xterm by a square indicating that the glyph did not exist: o-doubleacute u-abovering e-macron u-tilde o-ogonek l-with-middle-dot b-with-belowdot. Oddly, c-caron and g-breve _are_ rendered so it isn't a straight only support latin-1 issue. If I paste that line from my history into urxvt or libreoffice writer, it all renders fine. Changing the VT100*faceName line in /etc/X11/app-defaults/XTerm from Monospace to DejaVu Sans Mono and FreeMono did not help. According to gucharmap, all of those glyphs are in DejaVu Sans Mono. Typing random cyrillic and greek letters also produced empty squares. So, does xterm handle these glyphs in UTF-8 for anyone ? If so, what do you have in /etc/X11/app-defaults/XTerm or ~/.Xresources ? I've got the following relevant items in the environment: LANG=en_GB.UTF-8 XTERM_LOCALE=en_GB.UTF-8 XTERM_VERSION=XTerm(279) ĸen Hi Ken, I tried your line of glyphs on an xterm under icewm all built as per the book (december version), and it renders OK. The only difference I see is that I have LANG=fr_FR.UTF-8. I also tried with an xterm under KDE on a Debian system and it also renders fine. On Debian, the last four lines of /etc/X11/app-defaults/XTerm are commented out (including the faceName one), so those lines might not be the ones you want to modify. On both systems, the fonts referenced in the *VT100.utf8fonts.font? lines are installed in /usr/share/fonts/X11/misc. Maybe you are missing one of those (or you need to run mkfontdir or so). To be precise, from /usr/share/fonts/X11/misc/fonts.dir : 5x8.pcf.gz -misc-fixed-medium-r-normal--8-80-75-75-c-50-iso10646-1 6x13.pcf.gz -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1 7x14.pcf.gz -misc-fixed-medium-r-normal--14-130-75-75-c-70-iso10646-1 8x13.pcf.gz -misc-fixed-medium-r-normal--13-120-75-75-c-80-iso10646-1 9x18.pcf.gz -misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1 10x20.pcf.gz -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1 I do not see anything else I can say to help. Good luck, Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Does xterm work for UTF-8 ?
On Sun, 10 Feb 2013 02:29:58 + Ken Moffat zarniwh...@ntlworld.com wrote: So, does xterm handle these glyphs in UTF-8 for anyone ? If so, what do you have in /etc/X11/app-defaults/XTerm or ~/.Xresources ? I can confirm that XTerm renders the string correctly for me. Since I have no idea how does one configure xterm, I have attached the entire /etc/X11/app-defaults/XTerm file to this mail. I have no ~/.Xresources. I am also copy-pasting the output of the env command. HZ=100 SSL_CERT_FILE=/etc/ssl/cert.pem TERM=xterm SHELL=/usr/bin/xsacija.bash HISTSIZE=1500 HUSHLOGIN=FALSE WINDOWID=12582925 QTDIR=/usr/qt HISTFILESIZE=1500 USER=ak XTERM_SHELL=/usr/bin/xsacija.bash PATH=/bin:/usr/bin:/usr/local/bin:/usr/qt/bin:/opt/extra/bin:/usr/games/bin MAIL=/var/mail/ak INPUTRC=/etc/inputrc PWD=/home/ak PS1=\[\033[00m\]\A \[\033[0;32m\]\u\[\033[00m\]@\H \[\033[0;32m\]\w \[\033[00m\]$ SSL_CERT_DIR=/etc/ssl/certs XTERM_VERSION=XTerm(276) XTERM_LOCALE=en_US.UTF-8 HOME=/home/ak SHLVL=2 LOGNAME=ak LC_CTYPE=en_US.UTF-8 PKG_CONFIG_PATH=/usr/lib/pkgconfig:/usr/local/lib/pkgconfig:/usr/qt/lib/pkgconfig:/opt/extra/lib/pkgconfig:/usr/games/lib/pkgconfig WINDOWPATH=2 DISPLAY=:0 XAUTHORITY=/home/ak/.Xauthority _=/usr/bin/env If you need any more information, let me know. -- You don't need an AI for a robot uprising. Humans will do just fine. --Skynet XTerm Description: Binary data -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Does xterm work for UTF-8 ?
Le 10/02/2013 12:58, Pierre Labastie a écrit : On Debian, the last four lines of /etc/X11/app-defaults/XTerm are commented out (including the faceName one), so those lines might not be the ones you want to modify. Sorry, that is not accurate. I meant that the lines *VT100*locale: true *VT100*faceName: Monospace *VT100*faceSize: 10 are not in the file on Debian. They are there on LFS. OTH, I just see that comment in the file: ! xterm can switch at runtime between bitmap (default) and TrueType fonts. ! The faceSize resource controls the size of the latter. However, it was ! originally given with a size that makes the two types of fonts different ! sizes. Uncomment this line to use the same size as fixed. !*faceSize: 8 Of course, all I said in the last message applies to the default bitmap fonts. If you have set the fonts to Truetype, that might be that makes the difference. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Does xterm work for UTF-8 ?
On Sun, Feb 10, 2013 at 01:09:55PM +0100, Pierre Labastie wrote: OTH, I just see that comment in the file: ! xterm can switch at runtime between bitmap (default) and TrueType fonts. ! The faceSize resource controls the size of the latter. However, it was ! originally given with a size that makes the two types of fonts different ! sizes. Uncomment this line to use the same size as fixed. !*faceSize: 8 Of course, all I said in the last message applies to the default bitmap fonts. If you have set the fonts to Truetype, that might be that makes the difference. Regards Pierre Thanks for the comments. Yes, I ignore all the legacy fonts (you might prefer to call them traditional). The faceSize setting definitely works [ 12 for me - if I was still using the legacy fonts I would be using the 100dpi not the 75dpi ]. So, it sounds as if xterm _does_ require the legacy fonts, but only for some glyphs. I think I moved to all-truetype before I changed to urxvt, but maybe I'm wrong. Or maybe I was mostly trying to use common W. European accents in those days. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Does xterm work for UTF-8 ?
On Sun, Feb 10, 2013 at 01:08:56PM +0100, Aleksandar Kuktin wrote: On Sun, 10 Feb 2013 02:29:58 + Ken Moffat zarniwh...@ntlworld.com wrote: So, does xterm handle these glyphs in UTF-8 for anyone ? If so, what do you have in /etc/X11/app-defaults/XTerm or ~/.Xresources ? I can confirm that XTerm renders the string correctly for me. Since I have no idea how does one configure xterm, I have attached the entire /etc/X11/app-defaults/XTerm file to this mail. I have no ~/.Xresources. I am also copy-pasting the output of the env command. Thanks, but it looks as if you are using the legacy fonts. The current BLFS page for xterm shows how to set up the resources to use TTFs. If anyone tries that for a font that has spaces in its name, e.g. DejaVu Sans Mono the name needs double quotes. Oh well, perhaps (some) legacy fonts need to stay in the book for xterm. [sigh/]. Sad, because if I open Markus Kuhn's UTF-8-demo.txt in firefox (no legacy fonts installed at all) it renders all the glyphs there fine (need to zoom in a _lot_ to read the braille symbols). I haven't quite managed that in rxvt-unicode at the moment (a few of the amharic glyphs are missing - should just be a case of adding yet another font to urxvt's Xresources - everything else works there). ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Does xterm work for UTF-8 ?
On Sun, Feb 10, 2013 at 05:17:58PM +, Ken Moffat wrote: Oh well, perhaps (some) legacy fonts need to stay in the book for xterm. [sigh/]. Actually, it looks like a configure problem in xterm, prompted by a toolchain change in the last couple of years : configure:14508: checking for usable Xft/fontconfig package configure:14534: gcc -o conftest -g -O2 -D_GNU_SOURCE -DNARROWPROTO=1 -DFUNCPROTO=15 -DOSMAJORVERSION=3 -DOSMINORVERSION=8 -I/usr/include/freetype2 conftest.c -lXft -lXmu -lXt -lX11 -lXaw7 -lXt -lX11 -lSM -lICE -lXt -lX11 -lncurses 5 /usr/bin/ld: /tmp/cc2otVoJ.o: undefined reference to symbol 'FcPatternBuild' /usr/bin/ld: note: 'FcPatternBuild' is defined in DSO /usr/lib64/libfontconfig.so.1 so try adding it to the linker command line /usr/lib64/libfontconfig.so.1: could not read symbols: Invalid operation collect2: error: ld returned 1 exit status that results in configure reporting: checking for usable Xft/fontconfig package... no Interestingly, if I invoke xterm with /usr/local/bin/xterm -fa DejaVu Sans Mono -fs 12 it does appear to use the selected font, i.e. all the previous test glyphs appear, and I get a warning from fontconfig - Fontconfig warning: /etc/fonts/conf.d/50-user.conf, line 9: reading configurations from ~/.fonts.conf is deprecated. BUT it doesn't find the glyphs which are only in FreeFont. Fixing the configure is a different matter - adding LDFLAGS= or LIBS= produces the dreaded C compiler cannot produce executables - it can't find conftest.sh after creating it and adding '.' to the PATH. Xterm-289 still shows the failure to find a usable Xft/fontconfig, but it seems that fontconfig can be found with 289 if I use LIBS=. I haven't built it yet, and I'll come back to the configury of 279 later (the changelog for 289 looked irrelevant for my issues). If anyone has logs from configuring xterm-279 I would be interested in whether they see the failure to find a usable Xft/fontconfig. For my original not everything renders problem, I'm guessing that it has decided to use Bitstream Vera (which is installed at the moment so I can report on how little it covers - perhaps I should concentrate on that and then get rid of it again). ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Does xterm work for UTF-8 ?
On Sun, 10 Feb 2013 19:04:29 + Ken Moffat zarniwh...@ntlworld.com wrote: On Sun, Feb 10, 2013 at 05:17:58PM +, Ken Moffat wrote: Oh well, perhaps (some) legacy fonts need to stay in the book for xterm. [sigh/]. Actually, it looks like a configure problem in xterm, prompted by a toolchain change in the last couple of years : [snip] that results in configure reporting: checking for usable Xft/fontconfig package... no [snip] If anyone has logs from configuring xterm-279 I would be interested in whether they see the failure to find a usable Xft/fontconfig. I use xterm-276 and I do not see a failure for Xft/fontconfig. As for the configuration flags, apart from a bunch of them dealing with instalation directories, I used --enable-shared, --disable-static, --enable-luit, and --with-wide-chars. I just ran a test build with xterm-289 and fount that it both finds Xft/fontconfig and, when built and ran, displays the string from the first mail of this thread. My build system is from the LFS-6.2 era, while the versions of software packages have been updated. Fontdir for the X system is /usr/share/fonts. Aaaand.. that's about as much information as I can think of to provide. If any more is required, I'm here. -- You don't need an AI for a robot uprising. Humans will do just fine. --Skynet -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Does xterm work for UTF-8 ?
On Sun, Feb 10, 2013 at 09:25:21PM +0100, Aleksandar Kuktin wrote: On Sun, 10 Feb 2013 19:04:29 + Ken Moffat zarniwh...@ntlworld.com wrote: On Sun, Feb 10, 2013 at 05:17:58PM +, Ken Moffat wrote: Oh well, perhaps (some) legacy fonts need to stay in the book for xterm. [sigh/]. Actually, it looks like a configure problem in xterm, prompted by a toolchain change in the last couple of years : [snip] that results in configure reporting: checking for usable Xft/fontconfig package... no [snip] If anyone has logs from configuring xterm-279 I would be interested in whether they see the failure to find a usable Xft/fontconfig. I use xterm-276 and I do not see a failure for Xft/fontconfig. As for the configuration flags, apart from a bunch of them dealing with instalation directories, I used --enable-shared, --disable-static, --enable-luit, and --with-wide-chars. I just ran a test build with xterm-289 and fount that it both finds Xft/fontconfig and, when built and ran, displays the string from the first mail of this thread. My build system is from the LFS-6.2 era, while the versions of software packages have been updated. Fontdir for the X system is /usr/share/fonts. The toolchain change was somewhere around LFS-7.0, or perhaps 6.8. I think it was a binutils change - certainly it looks like binutils changed to prompt for what ought to be linked in, but perhaps a glibc or gcc change provoked the problem. We've had a number of BLFS and other packages that needed similar changes. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Does xterm work for UTF-8 ?
Ken Moffat wrote these words on 02/10/13 13:04 CST: configure:14508: checking for usable Xft/fontconfig package configure:14534: gcc -o conftest -g -O2 -D_GNU_SOURCE -DNARROWPROTO=1 -DFUNCPROTO=15 -DOSMAJORVERSION=3 -DOSMINORVERSION=8 -I/usr/include/freetype2 conftest.c -lXft -lXmu -lXt -lX11 -lXaw7 -lXt -lX11 -lSM -lICE -lXt -lX11 -lncurses 5 /usr/bin/ld: /tmp/cc2otVoJ.o: undefined reference to symbol 'FcPatternBuild' /usr/bin/ld: note: 'FcPatternBuild' is defined in DSO /usr/lib64/libfontconfig.so.1 so try adding it to the linker command line /usr/lib64/libfontconfig.so.1: could not read symbols: Invalid operation collect2: error: ld returned 1 exit status that results in configure reporting: checking for usable Xft/fontconfig package... no I have version 287 installed and have the exact same error in my configure logs. -- Randy rmlscsi: [bogomips 1003.23] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 14:51:01 up 67 days, 50 min, 1 user, load average: 0.29, 0.15, 0.06 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Does xterm work for UTF-8 ?
Randy McMurchy wrote: Ken Moffat wrote these words on 02/10/13 13:04 CST: configure:14508: checking for usable Xft/fontconfig package configure:14534: gcc -o conftest -g -O2 -D_GNU_SOURCE -DNARROWPROTO=1 -DFUNCPROTO=15 -DOSMAJORVERSION=3 -DOSMINORVERSION=8 -I/usr/include/freetype2 conftest.c -lXft -lXmu -lXt -lX11 -lXaw7 -lXt -lX11 -lSM -lICE -lXt -lX11 -lncurses 5 /usr/bin/ld: /tmp/cc2otVoJ.o: undefined reference to symbol 'FcPatternBuild' /usr/bin/ld: note: 'FcPatternBuild' is defined in DSO /usr/lib64/libfontconfig.so.1 so try adding it to the linker command line /usr/lib64/libfontconfig.so.1: could not read symbols: Invalid operation collect2: error: ld returned 1 exit status that results in configure reporting: checking for usable Xft/fontconfig package... no I have version 287 installed and have the exact same error in my configure logs. Looking at my logs: xterm-276.log:checking for usable Xft/fontconfig package... yes xterm-278.log:checking for usable Xft/fontconfig package... no xterm-279.log:checking for usable Xft/fontconfig package... no I'll note that I rarely use xterm. I generally build via ssh and use konsole on the host. Occasionally I'll bring up xterm for testing after the initial xorg build, but that's about it. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Does xterm work for UTF-8 ?
On Sun, Feb 10, 2013 at 02:53:31PM -0600, Randy McMurchy wrote: Ken Moffat wrote these words on 02/10/13 13:04 CST: configure:14508: checking for usable Xft/fontconfig package configure:14534: gcc -o conftest -g -O2 -D_GNU_SOURCE -DNARROWPROTO=1 -DFUNCPROTO=15 -DOSMAJORVERSION=3 -DOSMINORVERSION=8 -I/usr/include/freetype2 conftest.c -lXft -lXmu -lXt -lX11 -lXaw7 -lXt -lX11 -lSM -lICE -lXt -lX11 -lncurses 5 /usr/bin/ld: /tmp/cc2otVoJ.o: undefined reference to symbol 'FcPatternBuild' /usr/bin/ld: note: 'FcPatternBuild' is defined in DSO /usr/lib64/libfontconfig.so.1 so try adding it to the linker command line /usr/lib64/libfontconfig.so.1: could not read symbols: Invalid operation collect2: error: ld returned 1 exit status that results in configure reporting: checking for usable Xft/fontconfig package... no I have version 287 installed and have the exact same error in my configure logs. Thanks. If I manage to fix it, I'll commit the change. At the moment, using LIBS= and vanilla ./configure (with no options) seems to work even on the version currently in the book, I just need to find out which other setting prevents it compiling. Meanwhile, if you are using ttf fonts and have DejaVu but not Bitstream-Vera I guess that most things will work if you are using a UTF-8 locale - the only thing I've found so far, and which I can actually key, is g with stroke [ used for one of the Sami languages or orthographies, so not exactly common ]. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Does xterm work for UTF-8 ?
On Sun, Feb 10, 2013 at 11:05:27PM +, Ken Moffat wrote: On Sun, Feb 10, 2013 at 02:53:31PM -0600, Randy McMurchy wrote: I have version 287 installed and have the exact same error in my configure logs. Thanks. If I manage to fix it, I'll commit the change. At the moment, using LIBS= and vanilla ./configure (with no options) seems to work even on the version currently in the book, I just need to find out which other setting prevents it compiling. Well, I found what I was doing wrong in configure [ LDFLAGS=-lfontfonfig ] : unclear why that caused the test for a working C compiler to fail, but I've given up caring. Unfortunately, the resulting program is no different. I then went back and looked at my original DESTDIR build of xterm, and it _was_ linked to libfontconfig. So, the error message in config.log might just be a red herring. If I pass -fa DejaVuSans Mono when invoking xterm, only that font is used, which is mostly ok for what I use, but disappointing. But even with the face set for DejaVu Sans Mono in both the app default and .Xresources, and after a fresh 'startx', if I invoke it without -fa it still comes up with what is presumably Vera. In neither case does it seem to use fontconfig for glyphs which are missing in the current font, which is the behaviour I was expecting (and one of the reasons I dropped abiword from my own builds). My current view on xterm is if you use it, best to get a better term, and in the meantime use at least the Fixed legacy font. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] Does xterm work for UTF-8 ?
In connection with reviewing the TrueType fonts I build, I was going to ask if there was a reason why the book still installs legacy xorg fonts. I've only used TTF/OTF fonts for several years, and the only issue I've noticed is that xcalc can't display a square root sign on the appropriate keycap. But before asking, I thought I ought to take a look at xterm (usually, I use rxvt-unicode). When I built that - by the book, apart from putting it /usr/local but with luit in /usr - I got unpleasant results : I typed #čőäůåēũñâòğçǫŀıḅ which for anyone missing some glyphs is hash, c-caron, o-doubleacute, a-diaeresis, u-abovering, a-abovering, e-macron, u-tilde, n-tilde, a-circumflex, o-grave, g-breve, c-cedilla, o-ogonek, l-with-middle-dot, dotless-i, b-with-belowdot. Apart from the hash, those are regular european latin letters [ ok, I'll grant you that u-tilde is obsolete ]. But the following were replaced in xterm by a square indicating that the glyph did not exist: o-doubleacute u-abovering e-macron u-tilde o-ogonek l-with-middle-dot b-with-belowdot. Oddly, c-caron and g-breve _are_ rendered so it isn't a straight only support latin-1 issue. If I paste that line from my history into urxvt or libreoffice writer, it all renders fine. Changing the VT100*faceName line in /etc/X11/app-defaults/XTerm from Monospace to DejaVu Sans Mono and FreeMono did not help. According to gucharmap, all of those glyphs are in DejaVu Sans Mono. Typing random cyrillic and greek letters also produced empty squares. So, does xterm handle these glyphs in UTF-8 for anyone ? If so, what do you have in /etc/X11/app-defaults/XTerm or ~/.Xresources ? I've got the following relevant items in the environment: LANG=en_GB.UTF-8 XTERM_LOCALE=en_GB.UTF-8 XTERM_VERSION=XTerm(279) ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
