Date: Tue, 7 Mar 1995 01:08:00 -0800 From: asami@cs.berkeley.edu (Satoshi Asami/=?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=) To: ports@FreeBSD.org Subject: Japanese packages Message-ID: <199503070908.BAA29816@silvia.HIP.Berkeley.EDU>
next in thread | raw e-mail | index | archive | help
I'll be getting a bunch of Japanese packages in the next few days, and
I'm wondering where I should put them. I've been following the
regular convention so far, i.e., spreading them out by function, and
these are what we have now:
utils/Canna kana-kanji conversion engine
utils/Wnn ditto
utils/nkf kanji code conversion filter
x11/kterm xterm with kanji support
editors/mule multilingual extension of emacs
(Note: mule is not for Japanese only)
Soon I'll be adding "Japanized" versions of less, tex, dvips, xdvi,
ghostscript, chimera, and such.
I think it might be easier for users to find them if I just put them
all under a new directory under /usr/ports, say /usr/ports/japanese or
something like that, instead of adding subdirectories "jless"
"jchimera" and such next to the "original" versions.
Of course, this will ruin the "orthogonal" appearance of the
/usr/ports hierarchy, by adding a subdirectory for a specific user
group, so that's why I'm asking here.
What do other people think?
Satoshi
P.S. Actually, I think it will be great if we can have
/usr/ports/korean and /usr/ports/chinese as well, but we need to
find somebody to take care of them first. (BTW, these two came
up to my mind as languages that use huge multi-byte charsets, no
offense to other non-English speakers. :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503070908.BAA29816>