From: Patrick McCarty <patrick.mccarty at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] [PATCH] src/cpu/cpu.cpp: Fix typo in error message: freque*nc*y
Date: Wed, 06 Feb 2013 11:49:14 -0800 [thread overview]
Message-ID: <20130206194914.GB1738@linux.intel.com> (raw)
In-Reply-To: CAE4GLsukpGOJxhPtzea6TCK3fE6H59rAjPAO3FTTayeYi23f8A@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
On Wed, Feb 06, 2013 at 11:50:26AM +0100, Thomas Spura wrote:
> On Tue, Feb 5, 2013 at 5:06 PM, Paul Menzel
> <paulepanter(a)users.sourceforge.net> wrote:
> > Am Dienstag, den 05.02.2013, 10:18 +0100 schrieb Thomas Spura:
> >> By then all translations will be marked as fuzzy and won't work
> >> anymore. When also updating the typo in the translations, this won't
> >> be needed.
> >
> > The question is if Transifex is able to deal with that, that means, it
> > notices the changes of translation files in the repository. Do you know
> > if it does?
>
> IIUC, you need to send the "what to translate" files manually to
> Transifex so it should be a manually step by the powertop translations
> manager.
At one point, we were pushing powertop.pot to Transifex manually, but
now we have the Transifex project configured to automatically pull
the raw POT file from the github repo. IIRC, it pulls the latest POT
daily.
So, as long as powertop.pot is up-to-date in the github repo, the
maintainer does not need to update it anywhere else.
Integrating the *PO* files from Transifex into PowerTOP is the manual
step, because Transifex no longer supports version-control integration,
i.e. pushing automated commits that update translations.
Regards,
Patrick
next reply other threads:[~2013-02-06 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 19:49 Patrick McCarty [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-06 10:50 [Powertop] [PATCH] src/cpu/cpu.cpp: Fix typo in error message: freque*nc*y Thomas Spura
2013-02-05 18:03 Kristen Carlson Accardi
2013-02-05 16:06 Paul Menzel
2013-02-05 9:27 Sergey Senozhatsky
2013-02-05 9:18 Thomas Spura
2013-02-04 19:02 Kristen Carlson Accardi
2013-02-03 22:36 Paul Menzel
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=20130206194914.GB1738@linux.intel.com \
--to=powertop@lists.01.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 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.