From: Matthew Huggett <mhuggett@zam.att.ne.jp>
Subject: Re: Writing Japanese using ConTeXt
Date: Mon, 09 Jun 2003 23:16:27 +0900 [thread overview]
Message-ID: <3EE496BB.1010605@zam.att.ne.jp> (raw)
In-Reply-To: <000001c32db3$f5e81750$0a01a8c0@TIMBO>
Tim 't Hart wrote:
>Recently, I've made the 'unwise' decision to start studying Japanese next
>year, and of course I want to keep on using ConTeXt to write my school
>papers. [....] So I decided to find a way to
>write Japanese in ConTeXt.
>
>First I tried using the eOmega/ConTeXt combination since I have some great
>OTPs for it, but soon found out that Omega is still "the TeX of the future",
>in other words, not the "TeX of today" and extremely unstable.
>
>Then I decided to try ConTeXt's UTF-8 support. I created the following test
>
>
I asked about Japanese a while back. Hans requested more information on
encodings, fonts, etc. I don't know enough about these things or
ConTeXt to know what is needed exactly.
From what I've read, unicode is not that popular in Japan itself. The
most common encodings here are
a) iso-2022-jp (7bit)
b) japanese-iso-8bit (a.k.a euc-japan-1990, euc-japan, euc-jp)
c) japanese-shift-jis (shift jis 8bit; common under MS Windows)
"Describe Language Environment" under MULE in Gnu Emacs gives some info.
Ken Lunde of Adobe has a book or two on processing Japanese.
Typesetting Japanese could be more complicated than Chinese because of
the concurrent use of four writing systems:
a) Kanji (Chinese Characters)
b) Hiragana (Syllabic script for representing grammatical endings and
words for which Kanji are not commonly used.)
c) Katakana (Syllabic script for representing foreign words, some
scientfic words (flora, fauna), and for emphasis)
d) Romaji -- lit. "Roman Characters" (Sometimes foreign languages,
especially English, are represented in latin script) It is more common
than you might imagine.
I guess I need to track down a few sample documents. I tried to turn up
some info on Japanese typesetting rules but had no luck.
best wishes,
Matt
next prev parent reply other threads:[~2003-06-09 14:16 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 [this message]
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
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=3EE496BB.1010605@zam.att.ne.jp \
--to=mhuggett@zam.att.ne.jp \
--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).