From: Takesi Ayanokoji <ayanokoji.takesi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: translation of Emacs manual into Japanese
Date: Sun, 2 Oct 2016 03:10:09 +0900 [thread overview]
Message-ID: <CAN7WbiYu_K=pzEKciOgg2mkvUNc=secOiO1NPLG3dnPwFEOafg@mail.gmail.com> (raw)
In-Reply-To: <83oa37o2mu.fsf@gnu.org>
>> We could copy this contribution into doc/emacs-ja and distribute it as a
>> standard part of GNU Emacs.
>
> That'd need to figure out where to install it by "make install". Are
> there any GNU conventions for that?
I checked internationalized info document, and I can't find any conventions
such like a internationalized man-pages.
Example of localized info I only found is TexLive's latex2e.info files
(latex2e.info and latex2e-es.info).
These info files are installed to
'/usr/local/texlive/2015/texmf-dist/doc/info/'
and that is not standard info directory.
If follow this example, japanese localized info name will be emacs-ja.info
and it will be installed Emacs data-directory's subdirectory(i.e. info/)
like Emacs TUTORIALs.
Regards.
---
Ayanokoji Takesi <ayanokoji.takesi@gmail.com>
next prev parent reply other threads:[~2016-10-01 18:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 12:26 (unknown) Takesi Ayanokoji
2016-09-28 17:05 ` none John Wiegley
2016-09-28 20:28 ` translation of Emacs manual into Japanese Paul Eggert
2016-09-28 21:39 ` Michael Albinus
2016-09-29 2:34 ` Eli Zaretskii
2016-09-29 5:21 ` Paul Eggert
2016-09-29 6:59 ` Takesi Ayanokoji
2016-09-29 15:10 ` Eli Zaretskii
2016-09-29 22:03 ` Takesi Ayanokoji
2016-10-01 18:10 ` Takesi Ayanokoji [this message]
2016-09-29 7:19 ` Katsumi Yamaoka
2016-09-30 3:27 ` Takesi Ayanokoji
2016-09-30 10:12 ` Katsumi Yamaoka
2016-09-30 13:28 ` Takesi Ayanokoji
2016-09-29 13:52 ` (unknown) Byung-Hee HWANG (황병희, 黃炳熙)
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN7WbiYu_K=pzEKciOgg2mkvUNc=secOiO1NPLG3dnPwFEOafg@mail.gmail.com' \
--to=ayanokoji.takesi@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).