unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Meiyo Peng <meiyo@riseup.net>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: guix-devel@gnu.org
Subject: Re: Let’s translate!
Date: Sat, 13 Apr 2019 17:33:51 +0800	[thread overview]
Message-ID: <87a7guxn9c.fsf@riseup.net> (raw)
In-Reply-To: <20190413064552.bgsnu4bfvofcin7k@pelzflorian.localdomain>

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’ 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) wrote:
>> I’m 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 translate
>> #  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 warning
>> 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…
>>      # 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’s 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/

  parent reply	other threads:[~2019-04-13  9:34 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11  9:54 New template for 'guix-manual' made available Translation Project Robot
2019-04-12 20:43 ` Let’s translate! Ludovic Courtès
2019-04-13  1:56   ` Meiyo Peng
2019-04-13  6:45     ` pelzflorian (Florian Pelz)
2019-04-13  7:49       ` pelzflorian (Florian Pelz)
2019-04-13  9:33       ` Meiyo Peng [this message]
2019-04-13  7:14     ` Julien Lepiller
2019-04-13  9:27       ` Meiyo Peng
2019-04-23  0:42       ` [PATCH 0/2] Removal of generated files (was Re: Let’s translate!) Miguel
2019-04-23  0:43         ` [PATCH 1/2] bootstrap: Break automake dependency on generated files. " Miguel
2019-04-23  7:28           ` Julien Lepiller
2019-04-23 10:28             ` Miguel
2019-04-26  9:30               ` Julien Lepiller
2019-04-26 11:05                 ` Miguel
2019-04-26 18:55                   ` Julien Lepiller
2019-04-26 22:10                     ` Ludovic Courtès
2019-04-27 12:32                       ` Julien Lepiller
2019-04-27 13:52                         ` Ludovic Courtès
2019-04-23 14:30             ` Ludovic Courtès
2019-04-23 22:51               ` Miguel
2019-04-24 10:37                 ` Julien Lepiller
2019-04-25  8:50                   ` Ludovic Courtès
2019-04-25  9:54                     ` Julien Lepiller
2019-04-26  8:39                       ` Ludovic Courtès
     [not found]         ` <20190423024427.10cd6e87@gmail.com>
2019-04-23 22:42           ` [PATCH 2/2] doc: Add Spanish translation. " Ludovic Courtès
2019-04-13  7:49     ` Let’s translate! znavko
2019-04-13  9:46       ` Meiyo Peng
2019-04-15 12:38     ` Ludovic Courtès
2019-04-13  5:11 ` znavko

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a7guxn9c.fsf@riseup.net \
    --to=meiyo@riseup.net \
    --cc=guix-devel@gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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/guix.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).