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 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 s
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 in
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 vriende
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
5 matches
Mail list logo
