unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, ayanokoji.takesi@gmail.com
Subject: Re: translation of Emacs manual into Japanese
Date: Wed, 28 Sep 2016 22:21:55 -0700	[thread overview]
Message-ID: <e1ef06b8-83ef-aa6e-2d3e-f24b249c852e@cs.ucla.edu> (raw)
In-Reply-To: <83oa37o2mu.fsf@gnu.org>

Eli Zaretskii wrote:
> That'd need to figure out where to install it by "make install".  Are
> there any GNU conventions for that?

Not as far as I know. We could install it as 'emacs-ja', I suppose.

After more looking I found a cache of Japanese translations of GNU manuals, here:

http://www.ring.gr.jp/pub/doc/gnu-info-j/index.html.en

They look like they haven't been maintained since they were created many years 
ago, and it's reasonable to worry that this might happen to the Emacs manual. We 
could install a Japanese translation that's marked as being for a recent 
version. If it isn't maintained we could eventually remove it.



  reply	other threads:[~2016-09-29  5:21 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 [this message]
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
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=e1ef06b8-83ef-aa6e-2d3e-f24b249c852e@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=ayanokoji.takesi@gmail.com \
    --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).