Bug#467255: unicode glyph regression
I think I'm seeing this, too. Seeing it on with kterm on sid (although instead of the question mark symbols, kterm displays empty spaces), also tried gnome-terminal from a remote Ubuntu jaunty machine, so I don't think it's a quirk of my environment. This may be an issue with upstream. I noticed on the changelog for the public crawl server at crawl.akrasiac.org ( http://crawl.akrasiac.org/issues.html ) they had to fix a couple Unicode-related bugs: For a long time Unicode didn't work. Thanks to some detective work by Napkin and greensnark, it works now. When Unicode worked properly, IBMgraphics didn't work properly until a patch came in lickety-split from greensnark. Thanks again! Unicode displays correctly for me from this host. It may be worth contacting them to figure out what they did to get it working. Unfortunately, I couldn't determine how to get in touch with the authors of this fix. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#467255: unicode glyph regression
Hello Trent, Can you verify if unicode is working properly in crawl 0.4.1-1 or if it is still broken? If it is still not working, could you tell me if you are running crawl in a virtual console, an xterm, in screen, or something else? Also include the output of env and locale. -- Met vriendelijke groet / with kind regards, Guus Sliepen [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#467255: unicode glyph regression
On Tue, Jul 29, 2008 at 02:58:40PM +0200, Guus Sliepen wrote: Can you verify if unicode is working properly in crawl 0.4.1-1 or if it is still broken? If it is still not working, could you tell me if you are running crawl in a virtual console, an xterm, in screen, or something else? Also include the output of env and locale. I believe the problem is this: # If you're using UNICODE_GLYPHS=y, and have a preferred Unicode # (UTF-8) locale you want Crawl to use, you can set it here. The # default is en_US.UTF-8. If you'd prefer that Crawl use the locale # as set in your environment LC_* variables, use UNICODE_LOCALE = . UNICODE_LOCALE = and because I do not have the en_US.UTF-8 locale compiled on my system. I've been making my own svn builds, and for those, setting UNICODE_LOCALE=. works as desired. This probably didn't show up at first because I once had US locales on my system, making it look like a regression when they went away. I haven't grabbed your 0.4.1-1 deb yet, but I can see from the .diff.gz that UNICODE_LOCALE is still unset. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467255: unicode glyph regression
On Tue, Jul 29, 2008 at 02:58:40PM +0200, Guus Sliepen wrote: Can you verify if unicode is working properly in crawl 0.4.1-1 or if it is still broken? It is still broken. If it is still not working, could you tell me if you are running crawl in a virtual console, an xterm, in screen, or something else? I can reproduce the issue with xterm -e crawl, in my normal xterm + screen environment, and as root on the linux console, with a one-line .crawlrc: char_set = unicode Also include the output of env and locale. As the problem also affects root, I have dumped its env and locale rather than my own. SHELL=/bin/bash TERM=linux HUSHLOGIN=FALSE USER=root MAIL=/var/mail/root PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin PWD=/root LANG=en_AU.UTF-8 SHLVL=1 HOME=/root LOGNAME=root _=/usr/bin/env LANG=en_AU.UTF-8 LC_CTYPE=en_AU.UTF-8 LC_NUMERIC=en_AU.UTF-8 LC_TIME=en_AU.UTF-8 LC_COLLATE=en_AU.UTF-8 LC_MONETARY=en_AU.UTF-8 LC_MESSAGES=en_AU.UTF-8 LC_PAPER=en_AU.UTF-8 LC_NAME=en_AU.UTF-8 LC_ADDRESS=en_AU.UTF-8 LC_TELEPHONE=en_AU.UTF-8 LC_MEASUREMENT=en_AU.UTF-8 LC_IDENTIFICATION=en_AU.UTF-8 LC_ALL= -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467255: unicode glyph regression
Package: crawl Version: 2:0.3.4-1 Severity: normal Crawl is not working with unicode. This may be a regression of #451028. On starting crawl with char_set = unicode in .crawlrc, I now get Warning: Crawl encountered errors during startup: Unicode glyphs are not available, falling back to ASCII. and then the map uses not ASCII, but question marks in boxes for walls and suchlike. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages crawl depends on: ii libc6 2.7-6GNU C Library: Shared libraries ii libgcc1 1:4.3-20080202-1 GCC support library ii liblua5.1-0 5.1.3-1 Simple, extensible, embeddable pro ii libncursesw55.6+20080203-1 Shared libraries for terminal hand ii libstdc++6 4.3-20080202-1 The GNU Standard C++ Library v3 crawl recommends no packages. -- no debconf information signature.asc Description: Digital signature
