From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 37413@debbugs.gnu.org
Subject: [bug#37413] [PATCH 0/9] Channel news distribution mechanism
Date: Wed, 18 Sep 2019 00:02:46 +0200 [thread overview]
Message-ID: <20190917220246.qnmbim4pb3qlbgro@pelzflorian.localdomain> (raw)
In-Reply-To: <20190917194415.ripfxwfmpx337z4d@pelzflorian.localdomain>
On Tue, Sep 17, 2019 at 09:44:16PM +0200, pelzflorian (Florian Pelz) wrote:
> On Tue, Sep 17, 2019 at 08:21:18PM +0200, Julien Lepiller wrote:
> > […]
> > Channel translation is another subject, but they could provide their
> > own PO file and have them translated separately from the official Guix
> > translation process. Guix pull would then concatenate po files from
> > every channel and install that. Does it sound good/feasible?
> >
>
> I did not think about this before, but Julien’s idea how to process a
> channel’s PO files with translations for package descriptions seems
> good. Just msgcat guix-packages and the other channels’ PO files to
> the PO file for guix-packages and then run msgfmt on the result.
>
No, concatenation via msgcat is not feasible. It could fail if
translations clash, e.g. when channel A translates "Hello" as
"Bonjour" and channel B translates "Hello" as "Salut". To handle this
edge case, PO files would need to remain separate and the textdomain
procedure would need to be called by Guix before looking up package
descriptions from this channel, I think.
Regards,
Florian
>
> On Tue, Sep 17, 2019 at 08:21:18PM +0200, Julien Lepiller wrote:
> > I partially agree: on the one hand, having our own translation platform
> > only increases fragmentation of the free software translation teams,
> > and on the other hand, it means we can have a more reactive and
> > customized translation process. I also agree with Ludo that the TP is
> > probably not the right place for news translations: even if Benno
> > accepts the new translations super fast (and Benno is usually fast,
> > I just keep making mistakes when submitting a new version), it's
> > going to update all translations (guix, guix-packages and guix-manual),
> > and translators might focus on these instead of the news.
> >
>
> How about adding a comment to the POT file that we wish for
> translators to prioritize and urgently add translations for news? Is
> it really necessary to submit the entire Guix tarball to the TP for
> updating news; I thought the tarball is just for convenience of
> translators? I wonder what Benno or others from the TP think. I
> think Guix’ goals align well with those of the TP.
>
>
>
> > Using a PO file for news items seem a bit drastic too: a news item is
> > not supposed to change, except maybe for a typo.
> >
>
> PO files are simple and what the Translation Project’s translators are
> used to. I do not understand how another format could be more
> appropriate.
>
> Regards,
> Florian
>
>
>
next prev parent reply other threads:[~2019-09-17 22:03 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 22:10 [bug#37413] [PATCH 0/9] Channel news distribution mechanism Ludovic Courtès
2019-09-15 22:20 ` [bug#37413] [PATCH 1/9] pull: '--news' shows the list of channels added or removed Ludovic Courtès
2019-09-15 22:20 ` [bug#37413] [PATCH 2/9] git: 'update-cached-checkout' avoids network access when unnecessary Ludovic Courtès
2019-09-15 22:21 ` [bug#37413] [PATCH 3/9] git: Add 'commit-difference' Ludovic Courtès
2019-09-15 22:21 ` [bug#37413] [PATCH 4/9] channels: Add support for a news file Ludovic Courtès
2019-09-15 22:21 ` [bug#37413] [PATCH 5/9] ui: Add 'current-message-language' Ludovic Courtès
2019-09-15 22:21 ` [bug#37413] [PATCH 6/9] pull: Display channel news Ludovic Courtès
2019-09-15 22:21 ` [bug#37413] [PATCH 7/9] pull: '-l' displays " Ludovic Courtès
2019-09-15 22:21 ` [bug#37413] [PATCH 8/9] Add '.guix-channel' file Ludovic Courtès
2019-09-15 22:21 ` [bug#37413] [PATCH 9/9] DRAFT etc: Add channel news file Ludovic Courtès
2019-09-16 9:31 ` [bug#37413] [PATCH 0/9] Channel news distribution mechanism Ricardo Wurmus
2019-09-16 12:59 ` Ludovic Courtès
2019-09-16 13:16 ` Ricardo Wurmus
2019-09-16 15:10 ` Ludovic Courtès
2019-09-16 17:16 ` Ricardo Wurmus
2019-09-16 21:25 ` Ludovic Courtès
2019-09-16 21:49 ` Julien Lepiller
2019-09-16 22:52 ` pelzflorian (Florian Pelz)
2019-09-17 12:44 ` Ludovic Courtès
2019-09-17 13:33 ` pelzflorian (Florian Pelz)
2019-09-17 13:39 ` Ludovic Courtès
2019-09-17 14:28 ` pelzflorian (Florian Pelz)
2019-09-17 15:27 ` Ludovic Courtès
2019-09-17 17:41 ` pelzflorian (Florian Pelz)
2019-09-17 18:21 ` Julien Lepiller
2019-09-17 19:44 ` pelzflorian (Florian Pelz)
2019-09-17 22:02 ` pelzflorian (Florian Pelz) [this message]
2019-09-18 10:02 ` Ludovic Courtès
2019-09-18 11:49 ` pelzflorian (Florian Pelz)
2019-09-18 12:33 ` Ludovic Courtès
2019-09-18 9:12 ` Ludovic Courtès
2019-09-21 21:12 ` [bug#37413] [PATCH v2 00/11] " Ludovic Courtès
2019-09-21 21:12 ` [bug#37413] [PATCH v2 01/11] pull: '--news' shows the list of channels added or removed Ludovic Courtès
2019-09-21 21:12 ` [bug#37413] [PATCH v2 02/11] git: 'update-cached-checkout' avoids network access when unnecessary Ludovic Courtès
2019-09-21 21:12 ` [bug#37413] [PATCH v2 03/11] git: Add 'commit-difference' Ludovic Courtès
2019-09-21 21:12 ` [bug#37413] [PATCH v2 04/11] channels: Add support for a news file Ludovic Courtès
2019-09-21 21:12 ` [bug#37413] [PATCH v2 05/11] channels: Allow news entries to refer to a tag Ludovic Courtès
2019-09-21 21:12 ` [bug#37413] [PATCH v2 06/11] ui: Add 'current-message-language' Ludovic Courtès
2019-09-21 21:12 ` [bug#37413] [PATCH v2 07/11] pull: Display channel news Ludovic Courtès
2019-09-21 21:12 ` [bug#37413] [PATCH v2 08/11] pull: '-l' displays " Ludovic Courtès
2019-09-21 21:12 ` [bug#37413] [PATCH v2 09/11] pull: Display news titles directly upon 'pull' Ludovic Courtès
2019-09-21 21:12 ` [bug#37413] [PATCH v2 10/11] Add '.guix-channel' file Ludovic Courtès
2019-09-21 21:12 ` [bug#37413] [PATCH v2 11/11] DRAFT etc: Add channel news file Ludovic Courtès
2019-09-22 11:14 ` pelzflorian (Florian Pelz)
2019-09-23 9:13 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190917220246.qnmbim4pb3qlbgro@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=37413@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.