Re: [tlug] Re: font encoding question

[<burlingk@example.com>]

> ------------------------------
> 
> Message: 6
> Date: Wed, 20 Jun 2007 22:53:49 +0900
> From: "Stephen J. Turnbull" <stephen@example.com>
> Subject: [tlug] Re: font encoding question 
> To: Tokyo Linux Users Group <tlug@example.com>
> Message-ID: <87myyu68b6.fsf@example.com>
> Content-Type: text/plain; charset=iso-2022-jp
> 
> burlingk@example.com writes:
>  > I had read somewhere that if you tried to use Chinese, Japanese, 
>  > and Korean together, that sometimes UTF-8 ran into issues.  
> 
> No, there are people who have issues.  "ichi" is "ichi" no 
> matter which language.  The problem that people have is that 
> they want to visually distinguish text in Japanese from text 
> in Chinese with different fonts.  But it's more or less like 
> asking for a different charset for writing C keywords and 
> Python keywords, and claiming that C "for" is a different 
> word from Python "for".  You solve it the same

I see.
>From what I have seen, the main difference stylistically is that
often times the Japanese versions will be more pretty for text,
and the Chinese version more pretty for T-shirts. ^^;;  In the
world of billboards and advertisements that is Japan, the more
"Chinese looking" kanji seem to be a lot more popular.  :P

My point is, why freak out over whether or not your character
looks more printed or drawn, or just how the lines slant in the
character nichi.  ^^;; To a foreigner it is just as readable
either way, and apparently it is to an add agency also. :P

How well does this work out in a document that contains both.
For instance, a document describing what Chinese words mean
in Japanese.  <insert Chinese phrase for ohayogozaimasu>ga
ohaiyougozaimasudesu.
 :P