all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: bob@rattlesnake.com, rms@gnu.org, emacs-devel@gnu.org
Subject: support of Japanese in makeinfo
Date: Fri, 04 Mar 2005 13:52:27 +0900	[thread overview]
Message-ID: <b9yzmxk57xw.fsf_-_@jpl.org> (raw)
In-Reply-To: b9yk6opaqs8.fsf@jpl.org

[-- Attachment #1: Type: text/plain, Size: 2290 bytes --]

Hello,

I was encouraged by Richard Stallman and send this message.  I'm
participating in the development of some Emacs Lisp softwares and
have the chance to write the TexInfo manuals in Japanese.  Since
the makeinfo command doesn't support Japanese text, I always put
the rule which uses the Emacs Lisp based makeinfo, that is, the
texinfo-format-buffer function, into those Makefiles.  Probably,
developers in China and Korea will do the same because of the
same reason, although I'm not familiar with those languages.

Is there a chance that the makeinfo command supports Japanese
text?  I heard someone in Japan has tried to modify it so as to
support Japanese text years ago, however it didn't seem to have
been successful.  I wish the makeinfo command could support
languages which correspond to many locales defined in the
/usr/lib/locale directory.  Unfortunately, I'm not good at C.

There are four encodings which are generally used for Japanese
text; they are ISO-2022-JP, EUC-JP, SHIFT_JIS and UTF-8.
ISO-2022-JP uses only 7-bit data, but some characters which are
special to makeinfo, for example, `@' and `{', will appear in
the raw data.  EUC-JP uses only 8-bit data, is popular in the
Unix-like systems as well as ISO-2022-JP.  SHIFT_JIS uses a
mixture of 7-bit and 8-bit data, mainly used in MS Windows.

In addition, there are special conventions used in Japanese
text.  The typical ones are as follows:

1. Japanese words are not separated by spaces as if they look
   "Japanesewordsarenotseparatedbyspaces".

2. Lines can be broken even in the middle of a word.  However,
   ASCII words embedded in Japanese sentences cannot be broken.

3. There's no space between the Japanese comma or the Japanese
   period and the beginning of the next sentence.

4. There are special rules called `kinsoku'.  Some characters
   including Japanese comma, period and dash, small kana
   characters and the right parenthesis should not be places at
   the beginning of lines.  Contrarily, the left parenthesis and
   so forth should not be placed at the end of lines.  In Emacs,
   they are defined in the lisp/international/kinsoku.el file.

I would greatly appreciate making the makeinfo command support
them.  I attach an example of the Japanese TexInfo file below.

Best regards,


[-- Attachment #2: jugemu.texi.gz --]
[-- Type: application/x-gzip, Size: 380 bytes --]

\x1f

[-- Attachment #3: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  reply	other threads:[~2005-03-04  4:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-28  9:18 `texinfo-format-buffer' doesn't fold long lines Katsumi Yamaoka
2005-02-28 15:11 ` Robert J. Chassell
2005-02-28 23:57   ` Katsumi Yamaoka
2005-03-01  4:36     ` Eli Zaretskii
2005-03-01  5:32       ` Katsumi Yamaoka
2005-03-01 19:42         ` Eli Zaretskii
2005-03-01 15:30       ` Robert J. Chassell
2005-03-02 11:22     ` Richard Stallman
2005-03-02 12:21       ` Katsumi Yamaoka
2005-03-03 11:03         ` Richard Stallman
2005-03-03 11:54           ` Katsumi Yamaoka
2005-03-04  4:52             ` Katsumi Yamaoka [this message]
2005-02-28 21:53 ` Richard Stallman
2005-02-28 22:09   ` Stefan Monnier
2005-02-28 22:31     ` Katsumi Yamaoka
2005-03-02 11:22     ` Richard Stallman

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=b9yzmxk57xw.fsf_-_@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=bob@rattlesnake.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.