unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Takesi Ayanokoji <ayanokoji.takesi@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: translation of Emacs manual into Japanese
Date: Thu, 29 Sep 2016 18:10:11 +0300	[thread overview]
Message-ID: <83eg42oi7g.fsf@gnu.org> (raw)
In-Reply-To: <CAN7WbiawfawGa8e33QFytXEN8U5oFNMPz8gQS5otZXVotY2PtA@mail.gmail.com> (message from Takesi Ayanokoji on Thu, 29 Sep 2016 15:59:49 +0900)

> From: Takesi Ayanokoji <ayanokoji.takesi@gmail.com>
> Date: Thu, 29 Sep 2016 15:59:49 +0900
> 
> Instead, I extracted translatable string from emacs-24.5's texi to PO files by using po4a utility, and then
> translate these PO file.
> After translation, I generate translated emacs-24.5's texi files from original texis and translated PO file by using
> po4a utility again.
> 
> Up to that, this was a heavy work for me because I translated over 600 pages manual from nearly scratch.
> But after then, emacs-25.1 was released, updating translated manual was easy.
> 
> I extracted translatable string from emacs-25.1's texi to PO files by using po4a utility, and then translate these
> PO file from emacs-24.5's translated PO files by using gettext's merge utility.
> 
> At this point, this merged emacs-25.1's PO files ware almost Japanese but a few part that made changes in
> this release remain English.
> 
> I translated untranslated part of PO files, and then generate Japanese manual in fact.
> 
> But if I did not translate these PO manually, this cause emacs-25.1 manual almost Japanese a few English.
> 
> This not means that the manual is outdated, it means up-to-date but not completely translated.

AFAIU, the technique you used makes every paragraph of the manual a PO
string, and then translates each such string.  This, of course, avoids
translating the same text again for the next version, but it will
leave any changed paragraphs in their English form.  With time, more
and more of the manual will become English if the translation is not
updated, so the danger of becoming outdated still exists, sort of.

Thanks.



  reply	other threads:[~2016-09-29 15: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 [this message]
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=83eg42oi7g.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=ayanokoji.takesi@gmail.com \
    --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).