From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, matias_jose_seco@autoproduzioni.net
Subject: Re: Website translation
Date: Fri, 12 Jul 2019 07:35:39 +0200 [thread overview]
Message-ID: <20190712053539.htszj5w2b2sxws64@pelzflorian.localdomain> (raw)
In-Reply-To: <877e8owqkg.fsf@gnu.org>
On Thu, Jul 11, 2019 at 05:15:11PM +0200, Ludovic Courtès wrote:
> Ah yes, I believe the issue you raised in that message (“lego
> translations”) is not addressed by Florian’s approach.
>
> However, the #_ form you propose doesn’t quite work either because
> xgettext in its current form wouldn’t be able to extract it.
>
> sirgazil proposed a solution that’s similar to format strings to address
> that:
>
> https://lists.gnu.org/archive/html/guile-user/2017-12/msg00071.html
>
> Worth a try!
>
So:
1) We could put everything in a single string, which works with
xgettext and is somewhat easy to use for translators but not quite
Scheme-like.
2) We could use something like sirgazil’s format string solution. It
works with xgettext, but is not nice for translators.
I wrote in <https://lists.gnu.org/archive/html/guile-user/2017-12/msg00069.html>:
> This interleaving is like a format string and is common in
> applications, but it separates the value of ~SPORT~ from the context
> in which it should be translated.
3) We could write our own PO file writer and MO file reader and use it
with either Christopher’s lego translation and sirgazil’s format
strings to use whatever format we want for developers and translators.
sirgazil’s format strings could probably be used now and improved with
a custom PO/MO reader/writer later on.
The MO file format is well documented at
<https://www.gnu.org/s/gettext/manual/html_node/MO-Files.html#MO-Files>
but “it is expectable that MO file format will evolve or change over
time”.
Such a custom reader/writer could be part of Gettext or could be a
separate library. I am not going to write it though.
Regards,
Florian
next prev parent reply other threads:[~2019-07-12 5:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 12:50 Guix beyond 1.0: let’s have a roadmap! matias_jose_seco
2019-07-07 14:20 ` Ludovic Courtès
2019-07-07 16:57 ` Website translation (was: Re: Guix beyond 1.0: let’s have a roadmap!) pelzflorian (Florian Pelz)
2019-07-07 18:00 ` pelzflorian (Florian Pelz)
2019-07-07 22:28 ` Christopher Lemmer Webber
2019-07-11 15:15 ` Website translation Ludovic Courtès
2019-07-12 5:35 ` pelzflorian (Florian Pelz) [this message]
2019-07-14 14:12 ` Ludovic Courtès
2019-07-14 14:26 ` pelzflorian (Florian Pelz)
2019-07-15 12:33 ` Ludovic Courtès
2019-07-15 14:57 ` Julien Lepiller
2019-07-15 15:54 ` pelzflorian (Florian Pelz)
2019-07-17 21:16 ` Ludovic Courtès
2019-07-18 15:08 ` pelzflorian (Florian Pelz)
2019-07-18 16:59 ` Ricardo Wurmus
2019-07-18 20:28 ` pelzflorian (Florian Pelz)
2019-07-18 20:57 ` pelzflorian (Florian Pelz)
2019-07-19 12:29 ` pelzflorian (Florian Pelz)
2019-07-26 11:11 ` pelzflorian (Florian Pelz)
2019-07-26 11:23 ` pelzflorian (Florian Pelz)
2019-08-05 13:08 ` pelzflorian (Florian Pelz)
2019-08-07 22:33 ` pelzflorian (Florian Pelz)
2019-08-22 21:13 ` Ludovic Courtès
2019-08-23 6:03 ` pelzflorian (Florian Pelz)
2019-08-23 12:18 ` Ludovic Courtès
2019-08-23 13:54 ` pelzflorian (Florian Pelz)
2019-08-23 14:08 ` Jelle Licht
2019-08-23 20:47 ` pelzflorian (Florian Pelz)
2019-08-25 18:58 ` pelzflorian (Florian Pelz)
2019-08-26 3:08 ` pelzflorian (Florian Pelz)
2019-09-06 14:27 ` pelzflorian (Florian Pelz)
2019-07-18 17:06 ` sirgazil
2019-07-15 12:59 ` Ricardo Wurmus
2019-07-18 5:06 ` pelzflorian (Florian Pelz)
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=20190712053539.htszj5w2b2sxws64@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=matias_jose_seco@autoproduzioni.net \
/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).