🚀 go-pugleaf

In article <5578@uhccux.uhcc.hawaii.edu> lee@uhccux.uhcc.hawaii.edu (Greg Lee) writes:
>From article <3313@jarthur.Claremont.EDU>, by dhosek@jarthur.Claremont.EDU (D.A. Hosek):
|>In article <20926@unix.cis.pitt.edu> jbw@unix.cis.pittsburgh.edu (Jingbai  Wang) writes:
|>...
|Here is what I have so far, in case it might be of interest to anyone:
|...
|1) A set of 34 TeX-compatible subfonts, in 4 sizes, derived from the
|24x24 bit Chinese font available by ftp from hanauma.stanford.edu
|in pub/zhongwen.  The subfonts are pk and tfm files, meant to
|be used with JTeX (or JTeX slightly modified).
|
Yeah, that's how jTeX fonts were built.
|2) A program p2ps, derived from the JTeX utility k2ps (which came
|in turn from a2ps) for printing unformatted text with a mixture
|of ordinary roman and Chinese on a PostScript printer.  It uses
|the fonts mentioned in 1).

I am not impressed by k2ps, try out my WStroff which can not only
print unformatted text, but can also format text with Chinese fonts
of different sizes, Adobe fonts in any family. Chinese fonts are from
a whole set instead of subset.

|Now, it may be I'll just give up my little project once I can
|try out JB's Chinese TeX.  I don't know -- my real interest in
|all this is in working toward some generalized facilities for
|composing and using large fonts -- not just Japanese and
|Chinese.  But now I have some questions:

Why? We are using totally different approaches. It is alwasys good have
different ways of solution to a problem as in academic journals.

|Don Hosek mentions a variety of JTeX that uses one big font
|instead of a bunch of subfonts (did I get that right?).  That
|interests me.  Where can I get it?

I don't read TUGboat (because I was really a Scribe hacker and C
programmer, instead of TeX one), but I knew there were articles there
about it. Well, a font of more 256 characters should not surprise anybody
as computer text evolves, since 256 = 2^8 (8-bit representation or one byte
representation), and JIS (Japanese) and GB (Chinese) and Big-5 (Taiwan 
Chinese) are using 2 bytes, it is 2^16 = 65536. However, we only use
#161~#254 in both bytes because there are only 7000 some commonly used
Chinese characters or Japanese Kanji (HanZi, in Chinese PinYin), and we do
want to distinguish Chinese bytes from standard ASCII ones (#33~#126), 
remembering also not to use the control characters (#0~#31 and #127~#159).
#32 and #160 (128+32) are reserved for <space).  Thus,
65536 has only of theorectical beauty. If METAFONT also uses 16-bit encoding
instead of 7-bit or 8-bit, 65536-char font set should not scare anybody.
In my previous posting, I did not mean it was not possible to generate
Chinese fonts with Metafont, of course you can enven with 8-bit scheme. Just
break it up into subsets. The really problem is the efficiency of TeX and
printing. VM is a serious problem uf you have many distinct characters in
a page. After eash page, you can flush it, as Hosek said, but not in the
middle of the page.

Adobe is in an effort to support multiple bytes encoding scheme (two to
three bytes), this will make programmer's life easier. The only thing is that
the cumstomers have to pay bigger bucks for memory expansion  and Adobe
PS licensing (which is included in the printer price).

|
|What's the right convention for escaping Chinese text?  I'm
|just using the JIS conventions now.  What about texts that
|have roman + Japanese + Chinese and maybe other character
|sets?  Is there any agreed on convention?

I developed ChTeX before I saw JTeX, and thus I do not stick to JIS, and I
don't think any Chinese from China, Hong Kong, Taiwan, Singapore and overseas
will. GB is the way to go as far as I can see.

|
|What about editing?  Is there any public domain editing
|software for Chinese, like maybe a Chinese version of emacs?

I have it in ChTeX.tar.Z for mainframe systems. It is called ChText. It
follows the most natural way (and some completely new ideas) fro you to 
type in Chinese just like typing English. Chinese emacs may not be too
hard to design for some particular hardware with graphic capability, and
indeed for DOS PC somebody already adopted emacs/epsilon commands in a 
Chinese editor. The key issue in inputting Chinese, however, is how to
make inputting natural to human mind and international key board.

|			Greg, lee@uhccux.uhcc.hawaii.edu


JB Wang