develooper Front page | perl.perl5.porters | Postings from January 2001

Re: 8482 busted for $^V sprintf()s on OS/390

Thread Previous | Thread Next
From:
andreas.koenig
Date:
January 21, 2001 13:29
Subject:
Re: 8482 busted for $^V sprintf()s on OS/390
Message ID:
m3g0icegr9.fsf@ak-71.mind.de
>>>>> On Sun, 21 Jan 2001 20:25:43 +0000, nick@ing-simmons.net (Nick Ing-Simmons) said:

   > If you can spell out how I do that (I am running XFree86 4.02), you 
   > can expect more progress. (Does such a terminal advertise its status
   > in %ENV ? - is there one with real scrollbars yet?) 

In your .Xdefault you set

XTerm*scrollBar: True
XTerm*utf8: 1

That's it, afaik. I don't use scrollbars, but I just tried it and saw
a scrollbar. Don't know how "real" that is;)

I know of no way to find out if the terminal supports UTF-8, I see no
%ENV being set.

If the .Xdefault lines above do not work, your xterm probably has not
been compiled for UTF-8 support (I don't remember what the default
xterm did). In this case you download source from

    ftp://dickey.his.com/xterm/xterm-150.tgz

(xterm.tgz is a symlink to current version.)

Compile it with configure option --enable-wide-chars. If you want bidi
support, you need patches from Robert Brady at
http://susu.org.uk/~robert/xterm/

   > It is still not clear that UTF-8 should be the defauilt on all handles 
   > even on such a beast. HTTP sockets should still be iso8859-1 I assume. 

This depends on what they have sent as their Content-Type. If they
sent "text/html; charset=utf-8", they need to configure their socket
to send UTF-8.

Thanks for the other answers, now I start understanding some more...


-- 
andreas

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About