ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Tim 't Hart" <tim@t-hart.com>
Subject: Re: CJK support in ConTeXt
Date: Wed, 27 Aug 2003 09:15:35 +0200 (CEST)	[thread overview]
Message-ID: <31160.2927199148$1061968862@news.gmane.org> (raw)

Jin-Hwan Cho wrote:

>It's time to discuss the topic "CJK support in ConTeXt" in a more
>public place.

I couldn't agree more! :-)

>The current version of ConTeXt supports Chinese only. But the same
>mechasism enables Korean too. The remaining language is Japanese.
>In some sense, it is possible to support Japanese in the current
>subfont mechanism. But several issues (e.g. Japanese kerning system
>as explained by Okumura) may occur.

Could you explain what these issues are? For the past couple of
months I've been busy writing Japanese support for ConTeXt, based
on the Chinese module. I'm not an expert in this, so I'm sure the
method I used for writing Japanese support is wrong and can be
improved. But for my own personal use it has already proven to be
quite useable. If anyone else is interested in what I've produced so
far, please let me know.

I would like to know what the issues with Japanese kerning are. I do
not know a lot about Japanese typography and would like to know what
the limitations of code based on the Chinese module are.

>My suggestion for supporting CJK characters in ConTeXt is to write a
>new module using e-Omega. Even though e-Omega does not produce PDF
>format directly, there are not much problem with DVIPDFMx.

When I first tried to use Japanese with ConTeXt, I first looked at
e-Omega. The reason I gave up and tried to adapt the Chinese module
was that e-Omega was unstable on my machine. Version 1.23 crashed
immediately (got stuck in a loop producing [] characters). I tried
1.15 because I heard that was more stable. I got some Japanese
output with this version, but when I tried creating more than a
paragraph, it locked as well. But this was all a few months ago.
Does anybody know if things with e-Omega have improved recently?

Anyway, I would like to see a common CJK module for ConTeXt, where
Chinese, Korean and Japanese are based on the same base code. It
doesn't matter to me if it's implemented using subfonts or on using
e-Omega, as long as it's stable and useable. Therefore, I would
like to offer my help in creating CJK support.

My best,
Tim

             reply	other threads:[~2003-08-27  7:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-27  7:15 Tim 't Hart [this message]
     [not found] <005401c36cc5$49e494a0$0e604442@wang>
2003-08-28  2:52 ` Hong Feng
2003-08-28 17:32   ` Tim 't Hart
  -- strict thread matches above, loose matches on Subject: below --
2003-08-27 10:07 Re[2]: " Giuseppe Bilotta
     [not found] ` <".134.221.25.121.1061968535.squirrel"@www.t-hart.com>
2003-08-27 11:29   ` Re[3]: " Hans Hagen
2003-08-27 11:38     ` Re[4]: " Giuseppe Bilotta
2003-08-27 16:08       ` Idris S Hamid
2003-08-28 11:26         ` Alan Hoenig
2003-08-28  8:47   ` Hans Hagen
2003-08-27  2:39 Jin-Hwan Cho
2003-08-27  6:29 ` Hans Hagen
2003-08-27  9:04 ` Hong Feng

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='31160.2927199148$1061968862@news.gmane.org' \
    --to=tim@t-hart.com \
    --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).