ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Tim 't Hart" <tim@t-hart.com>
Subject: RE: Writing Japanese using ConTeXt
Date: Mon, 16 Jun 2003 06:37:20 +0200	[thread overview]
Message-ID: <000001c333c0$fc2f6dd0$0a01a8c0@TIMBO> (raw)
In-Reply-To: <5.2.0.9.1.20030615225437.089e2500@localhost>

Hans Hagen wrote:

> you mix up two mechanisms:

Yes, after studying the Chinese module for a while, I also came to the
conclusion that I mixed up bad! :-)

So instead of enjoying the nice weather during the weekend, I wrote some
mapping files that will create subfonts for EUC-JP encoding. Each subfont
contains glyphs with the same first byte, just like the idea behind the
Chinese module. 

Then I wrote a basic 'font-jpn.tex' file and now I can write Japanese in
EUC-JP encoding, including basic line breaking!

I was still working on this and wanted to release it when it was more
useful, but I guess I have to speed things up now. Also, since I'm not an
expert in ConText, I'm sure I'm doing some things completely the wrong way,
so I think it's good if someone else will take a look at it. There is a lot
to improve! :-)

> - How are the rules for breaking?

The rules are basically the same as in Chinese. Japanese also contains
smaller versions of the kana (hiragana and katakana) glyphs, and breaking
before those is not allowed as well. Also, there seems to be different
classes of breaking: for some characters breaking is strictly forbidden, and
for some it is slightly forbidden. (I guess they mean that you should not
break slightly forbidden characters, but if the penalty is too bad, break
them anyway)

> Can you make a small test suite?

Yes, I am at work right now, but when I get back, I'll send you the mapping
files to make the fonts, the font-jpn file I was working on, and some other
things like sample files and line breaking rules.

My best,
Tim

  parent reply	other threads:[~2003-06-16  4:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2003-06-16  7:51     ` Hans Hagen
2003-06-17  7:15 Lei Wang

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='000001c333c0$fc2f6dd0$0a01a8c0@TIMBO' \
    --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).