We have just created the new fedoraproject.org f17-alpha resource under
transifex, for you to translate few added string on time for alpha
release (the 28th).
See all available resource there:
We should block translations on fedoraproject.org master branch in few
days. Please translate now only on fedoraproject-org-f17-alpha.
Actually the website is built against "fedoraproject.org master branch"
but will switch to "fedoraproject-org-f17-alpha" the 28th.
By that time, you're able to read your translations on the staging
instance, at http://stg.fedoraproject.org/
Same should appear for beta an Dday! (New content is comming, sorry
could not write it before).
Noyabrsk, YANAO, Russia
Fedora Account System Nickname - ArtKun
About myself: I'm an IT enthusiast. I have a good experience in working with Windows and Mac. For the first time I've tried Linux in 2010, when Ubuntu 10.04 came out. Since that time I've tried all the popular distributions, and I chose Fedora. I'm happy to use it since the time F15 came out.
My native language is Russian.
I'll be glad to do anything that can help Fedora Project. I'm ready to translate even very long texts as I'm very interested in learning English and obtaining translation skills.
[artkun@ArtKun-Desktop ~]$ gpg --fingerprint 2E041303
gpg: checking the trustdb
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
pub 2048R/2E041303 2012-02-17
Key fingerprint = E11F 1C85 6A72 A76E 0F16 A02C 154A C11B 2E04 1303
uid Artyom Kunyov <artkun(a)guitarplayer.ru>
sub 2048R/F9CE99BA 2012-02-17
We have moved to transifex.net long ago now, and still some projects
are not alive to us!
Some devels just don't know how to deal with transifex and
transifex-client, some does not know that they have to pull (or fill
the hook URL on the project setup), and some just never build update
with our translations.
That's really painful for us, who spend so much time providing translations.
And know, we have the ability to proofread translations, but devels
simply don't know about it cause they don't read transifex release
notes. And they are devels, not translators, they should not have to.
How could we efficiently deal with them?
Writing on devel? Too noisy there.
Filling trac tickets? Probably the best solution, but take lot of time
for the reporter to explain what is needed.
IMHO, our FLSCo members should do that, but this is a lot for few
people (how many of our FLSCo seats are alive???).
The most important to me is to clean our projects.
Could we have a list of dead upstream to ping? By dead uptream, I mean
projects without any maintainer, without anyone which is pulling our
translations and pushing pot back.
This could be done by filtering projects with wrong maintainers like
Dimitris (linked to ), and also the one who have never pushed a
pot for a long time (or even never pulled if possible, dunno what we
can see from the Indifex side).
On Tue, Feb 21, 2012 at 8:38 AM, Lennart Poettering
> We need (and in fact
> every Open Source project should require) proper attribution for the
> patches we merge into our projects, and that means that commits are
> properly split up.
I feel commits are not the best way to handle neither translation nor
attribution for a number of reasons.
The attribution issue was fixed in the following way: Transifex
remembers every single translation and adds the copyright information
in the PO file header itself, which is probably the optimal way to
give attribution. You can use this information in your release notes.
If needed, we can provide an API call to provide you with this
# Diego Búrigo Zacarão <diegobz(a)indifex.com>, 2011.
# Zbyněk Schwarz <zbynek.schwarz(a)gmail.com>, 2011, 2012.
> I have not been following development of Tx closely, so maybe there's
> now some toolset available to convert the combined translation updates
> as individual git commits. Is there?
There hasn't been a high enough demand for this to sit down and
develop it. There's a quite rich API available and a git-like client
which can be tweaked to produce git-like commits.
Founder and CEO, Transifex
US Tel: +1.650.440.2308
Social Localization Crowdsourcing
http://www.transifex.com/ -- http://angel.co/transifex
Le mardi 21 févr. 2012 à 10:46:35 (+0100), Jim Meyering a écrit :
> > [D] iwhd
> I deliberately switched iwhd from transifex to http://translationproject.org
> because the latter provides anonymous rsync access, while transifex requires
> that one register and use an account merely to download translations:
Thanks for letting us known, I'll ask for this project to be removed
The problem that I see is that the translators that have spent time
translating it has just seen their project removed, and an other guy is
able to continue translating. While some translators are expert, some
other just don't take enough time to get quality. I would have been
really desapointed in that case.
The translationproject.org is great, but you have one to many files
assigned to one translators (and not one to many translators in one
file), and you NEED to sign the Disclaimer with the FSF…
I am still waiting for them to let me translate… If the make project
would have been in transifex, I would have corrected (lot of) typo by
December. I still not have acces while the assigned translator is not
> If you're used to version-controlling your project's .po files, you may
> not see the point, since then, downloading .po files is usually done only
> by the maintainer. However, if you do not VC the .po files, but rather
> pull them via a bootstrap script, as done by upstream coreutils, grep,
> diffutils, parted, etc., then everyone who builds from a just-cloned
> directory must download the .po files. I don't want to impose the
> burden of registering on those folks.
Yes I understand. You could probably ship pos without tracking them on
the history as other projects do (yum I think).
Hope to see the authentification removed soon (yeah your ticket is old
As always, there is no perfect tool/setup, thanks for telling us.
> devel mailing list
SSSD has been in string freeze since Feb 7 for its upstream 1.8.0
release (which is going into Fedora 17). I made an announcement through
Transifex and on the sssd-devel list, but so far I've seen only two
languages provide any updates: Ukrainian (now 100% complete) and French
(now 55% complete).
We are planning to finalize the 1.8.0 release one week from today, on
Feb 28th. I would be highly appreciative if any interested translators
would please look into at least the manpage translations at
I apologize for not posting to this list earlier, but I was under the
incorrect assumption that making a Transifex announcement would carry to
this list. As a side-note, it would be very nice if we could make that
I translated the remaining messages in the Swedish translation of
Anaconda, the f17 branch yesterday. I upload the file and things
looks fine. But the statistics remain on 98%, and when I download it
again today the new messages remain untranslated. I uploaded the
translated version again today, twice, but again it seems it doesn't
Is there any explanation for this?