From mboxrd@z Thu Jan 1 00:00:00 1970 From: Meiyo Peng Subject: Re: =?utf-8?Q?Let=E2=80=99s?= translate! Date: Sat, 13 Apr 2019 17:33:51 +0800 Message-ID: <87a7guxn9c.fsf@riseup.net> References: <87zhovlztm.fsf@gnu.org> <87wojyllbk.fsf@riseup.net> <20190413064552.bgsnu4bfvofcin7k@pelzflorian.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:49701) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hFF2u-0006Ik-1c for guix-devel@gnu.org; Sat, 13 Apr 2019 05:34:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hFF2s-0002qs-Uh for guix-devel@gnu.org; Sat, 13 Apr 2019 05:34:00 -0400 In-reply-to: <20190413064552.bgsnu4bfvofcin7k@pelzflorian.localdomain> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: "pelzflorian (Florian Pelz)" Cc: guix-devel@gnu.org Hi pelzflorian, pelzflorian (Florian Pelz) writes: > On Sat, Apr 13, 2019 at 09:56:31AM +0800, Meiyo Peng wrote: >> I have no previous experience with i18n. What should I know in order to >> translate the Guix manual? How do I edit the ".pot" file? Is there an >> emacs package for the job? >> > > emacs=E2=80=99 po-mode is part of gettext. > > You will also need to join the Translation Project: > > https://translationproject.org/team/index.html > > > > You need to put your translations in a .po file, not in the .pot file. > This is what I did back then (once there is a po file it is no longer > this complicated). I am not sure if there are easier ways to test an > initial po file. > > On Sat, Oct 27, 2018 at 02:55:10AM +0200, pelzflorian (Florian Pelz) wrot= e: >> I=E2=80=99m not sure what doc/htmlxref.cnf is for, but I did this to my = copy >> of Guix to get the PO going, now that Julien Lepiller has paved the >> way by adding PO4A: >> >> cd ~/git/guix >> guix environment guix --ad-hoc po4a >> > > Then I did this but it was not the right command: > >> # if you do not have a po file yet: >> msginit -i po/doc/guix-manual.pot -o po/doc/guix-manual.de.po -l de_DE > > You should not need to do this msginit. You should instead use the po > file at the Translation Project if they have one for your language > team. If not, then you should not use po/doc/guix-manual.pot as I did > but use the .pot file at > https://translationproject.org/domain/guix-manual.html or else the > Translation Project will not accept the po. > > Then: > >> # (in the newly created po file, adjust the version.texi to be >> # version-de.texi, contributing.texi to be contributing-de.texi and tra= nslate >> # the table of contents) >> # (adjust doc/htmlxref.cnf doc/local.mk po/doc/local.mk to list your >> # language next to the existing translations, in lexicographic order) >> >> # then: >> po4a-translate -f texinfo -m doc/guix.texi -p po/doc/guix-manual.de.po \ >> -M UTF-8 -k 0 -l doc/guix.de.texi # ignore outdated warni= ng >> po4a-translate -f texinfo -m doc/contributing.texi -p po/doc/guix-manual= .de.po \ >> -M UTF-8 -k 0 -l doc/contributing.de.texi # ignore warning >> ./bootstrap >> ./configure >> make # only needs to run past MAKEINFO; probably some of the GEN doc/os-= config=E2=80=A6 >> # and po4a steps do the right thing >> ./bootstrap # only now bootstrap will detect that it needs guix.de.info >> ./configure >> >> make doc-pot-update # if desired >> make po/doc/guix-manual.de.po >> >> rm doc/guix.de.texi >> rm doc/contributing.de.texi >> make doc/guix.de.info >> > > You should check if you get a working manual before submitting the po > file to the Translation Project robot=E2=80=99s e-mail. > > Regards, > Florian I am still not clear of the procedures. But thank you anyway! I will start the work as soon as possible. -- Meiyo Peng https://www.pengmeiyu.com/