ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Lei Wang" <lwang@swt.edu>
Subject: Writing Japanese using ConTeXt
Date: Tue, 17 Jun 2003 02:15:12 -0500	[thread overview]
Message-ID: <007101c334a0$34b0a770$6f684442@wang> (raw)

I have posted the following to the list. But it seems disappeared. :-)
So again.

> One other point that may or may not matter is that ... I'm not sure if
> this is the correct terminology, but the code points of the Japanese
> character sets are arrayed in a sparse matrix (?). Each plane is
> 194x194, rather than 256x256. I used to know why.

Although the plane only have 194 characters each, many Japanese
fonts used by TeX were split by 256 per subfonts as that in Chinese 
CJK compact mode. 

----- Original Message ----- 
From: "Lei Wang" <leiwang@swt.edu>
To: <ntg-context@ntg.nl>
Sent: Wednesday, June 11, 2003 11:50 AM
Subject: Re: [NTG-context] Writing Japanese using ConTeXt


> Right. Although there are many Chinese unicode fonts, Both unix and windows 
> remap them to GBK or GB when used. As for Japanese in ConTeXt, I think
> it may be better to support the SJIS or other common used encoding, too.
> UTF8 is good, but it is inconvenience since I found few editor can save your file
> in UTF8 encoding under Windows. So I have to use convert tools to convert 
> my files.
> 
> I am not familiar with the Japanese encodings. But I think it can be implement in
> ConTeXt as Chinese because many things are in the same way. Remap them
> according their encodings (JIS, SJIS,etc.) should work if we can solve the
> one problem that Japanese SJIS encoding has some one-byte characters in the range
> 0XA1 - 0XDF while Chinese and Korean only have two-byte characters. 
> 

 Wang

             reply	other threads:[~2003-06-17  7:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-17  7:15 Lei Wang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-08 11:48 Tim 't Hart
2003-06-09 14:16 ` Matthew Huggett
2003-06-09 16:33   ` Tim 't Hart
2003-06-10  8:18     ` Hans Hagen
2003-06-10 20:02       ` Tim 't Hart
2003-06-11  2:35         ` Matthew Huggett
2003-06-09 23:24 ` Matt Gushee
2003-06-10  7:41   ` Matthew Huggett
2003-06-10  8:13   ` Hans Hagen
2003-06-10 19:36     ` Tim 't Hart
2003-06-15 21:03 ` Hans Hagen
2003-06-15 22:22   ` Matt Gushee
2003-06-16  7:55     ` Hans Hagen
2003-06-16  4:37   ` Tim 't Hart
2003-06-16  7:51     ` Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='007101c334a0$34b0a770$6f684442@wang' \
    --to=lwang@swt.edu \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).