From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Rafal Luzynski <digitalfreak@lingonborough.com>,
libc-alpha@sourceware.org, Carlos O'Donell <carlos@redhat.com>
Subject: Re: [COMMITTED] Update Translations
Date: Fri, 17 Jan 2020 22:29:29 +0530 [thread overview]
Message-ID: <4682a3a9-2d91-8c4b-ad09-a51e9cc48333@sourceware.org> (raw)
In-Reply-To: <efd088a2-0dda-ded1-7cfa-506ec27c9c40@sourceware.org>
On 17/01/20 9:45 am, Siddhesh Poyarekar wrote:
> Revert done, only translations where the file seems newer have been
> retained:
>
> https://sourceware.org/git/?p=glibc.git;a=commit;h=def9c08c94da60bfb746644d56cffbe7a9de3477
OK so I had a chat with the translation project coordinator about this
and he told me that one needs to run msgmerge on the downloaded po files
to get the updated po files.
I read the Release wiki page and it looks like it was updated to add
another little scriptlet to download translations from a different
page[1]. Benno confirmed that those have been obtained by using
msgmerge, so we could either run the scriptlet or fix the
update-translations target to run msgmerge --no-wrap --previous.
I've done the latter and it seems to produce correct results now. I'll
share the Makefile update shortly.
Siddhesh
[1] https://translationproject.org/domain/libc.html
next prev parent reply other threads:[~2020-01-17 17:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 14:17 [COMMITTED] Update Translations Siddhesh Poyarekar
2020-01-16 23:02 ` Rafal Luzynski
2020-01-17 4:02 ` Siddhesh Poyarekar
2020-01-17 4:15 ` Siddhesh Poyarekar
2020-01-17 16:59 ` Siddhesh Poyarekar [this message]
2020-01-17 22:54 ` Carlos O'Donell
2020-01-17 23:52 ` Siddhesh Poyarekar
2020-01-18 1:23 ` Carlos O'Donell
2020-01-18 7:33 ` Siddhesh Poyarekar
2020-01-19 5:18 ` Siddhesh Poyarekar
2020-01-20 2:12 ` Carlos O'Donell
2020-01-20 3:17 ` Siddhesh Poyarekar
-- strict thread matches above, loose matches on Subject: below --
2020-02-12 14:48 [COMMITTED] Update translations Siddhesh Poyarekar
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/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4682a3a9-2d91-8c4b-ad09-a51e9cc48333@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=carlos@redhat.com \
--cc=digitalfreak@lingonborough.com \
--cc=libc-alpha@sourceware.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.
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).