<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Le 15/12/2011 17:18, Akihiro Sagawa a écrit :
<blockquote cite="mid:20111216011729.0D6A.375B48EC@gmail.com"
type="cite">
<pre wrap="">On Wed, 14 Dec 2011 19:35:34 +0100, Eric Pouech wrote:
</pre>
<blockquote type="cite">
<pre wrap="">this doesn't solve the printing issue as the always infer that any char has
the same size
how is this printed on real windows with your character set ?
</pre>
</blockquote>
<pre wrap="">
See the attachment, please. It was taken in my Windows 7 PC with
Japanese Terminal font. Most of Japanese characters take up the double
width of the ASCII characters. For example, the first Japanese character
(KATAKANA LETTER DO, U+30C9) is as same width as `:¥' (=two halfwidth
characters).
Unicode Standard Annex #11, East Asian Width (*), may help understanding
East Asian character width.
* ... <a class="moz-txt-link-freetext" href="http://www.unicode.org/reports/tr11/">http://www.unicode.org/reports/tr11/</a>
In the document, some characters are defined as ambiguous. And its
recommendation is that ambiguous characters always map to fullwidth
characters when mapping Unicode to East Asian legacy characters.
But actually it depends on locales or encodings. For instance, as shown
in the bottom echo line in the snapshot, U+E1 (LATIN SMALL LETTER A WITH
ACUTE) is halfwidth and U+B1 (PLUS-MINUS SIGN) is fullwidth in Japanese
environment.
In my humble opinion, printing issue is not good especially for users.
But, as far as I know, it doesn't occur in ASCII characters. And it is
better than showing the error message, "Couldn't find a decent font,
aborting," at starting up.
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">
</pre>
</blockquote>
as pointed out in
<a class="moz-txt-link-freetext" href="http://blogs.msdn.com/b/buckh/archive/2005/09/11/463427.aspx#2250089">http://blogs.msdn.com/b/buckh/archive/2005/09/11/463427.aspx#2250089</a><br>
those Japanese characters need to be stored in two adjacent "cells"
in the console infrastructure code...<br>
<br>
your patch will actually print them on top of two cells, while it's
going to be stored only in one...<br>
it would then lead to making all the output (and internal encoding)
be wrong<br>
<br>
A+<br>
<br>
<pre class="moz-signature" cols="72">--
Eric Pouech
"The problem with designing something completely foolproof is to underestimate the ingenuity of a complete idiot." (Douglas Adams)
</pre>
</body>
</html>