StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I use Putty mainly to interact with my Ubuntu vm-boxen so I do spend some time getting the visual configuration correct. Basically, I set the font to MS Gothic, 9pt (for monospaced and Japanese), UTF-8 for received data, and terminal-type string to <code>xterm-256color</code>. I leave most of the Terminal settings alone because the defaults seem to work well.</p> <p>On the Ubuntu side, I set <code>LANG=en_US.UTF-8</code>, <code>aptitude install ncurses-term</code> for additional terms. I check the terminal colorness via a <a href="http://www.frexx.de/xterm-256-notes/" rel="nofollow noreferrer">nice script</a>, and double check within a <code>GNU Screen</code> session and <code>GNU Emacs</code> (<code>M-x list-colors-display</code>). <code>GNU Screen</code> is not compiled with 256 color option so i re-compile it. I check the language by using <code>Emacs</code> (<code>M-x view-hello-file</code>) and also <code>tig</code> a <code>git</code> directory with i18n utf-8 log commits.</p> <p>Unfortunately I still do get the weird "lqqqqk" thing on <code>aptitude</code> (line art missing?) but the spacing is still correct. Also pressing backspace in <code>aptitude</code> does a character insert, which I still have not conquered. Also I tested your command line w3m on my system and it looks nice. I rather use w3m from emacs, tho. :-)</p> <p>Truth be told, I use a <a href="http://yebisuya.dip.jp/Software/PuTTY/" rel="nofollow noreferrer">Japanese fork of Putty called Gottani (PuTTY ごった煮版)</a> that helps more with Japanese but I think its pretty close to the normal Putty.</p> <p>Aside: I also set Terminal > Features > Disable remote-controlled terminal resizing because `GNU Screen" overrides my window size setting.</p> <p>All of the above is tested on Ubuntu 8.04 LTS "Hardy Heron".</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload