I guess a kind of topic would be better posting to the trans list.
----- 元のメッセージ -----
| first let me introduce myself:
| My name is Oliver Burger and I am the substitute leader of the Mageia
| While setting up / creating the infrastructure for Mageia we decided
| to use
| transifex for our i18n work.
| Lot's of things were discussed and done on i18n side as well as on
| While looking into transifex we found at least two annoying issues
| with it. We
| have created a page in our temporary wiki (which will be replaced by a
| new mediawiki installation soon but trying to preserve the contents)
| transifex. It's mainly a howto for the translators but at the end of
| it we are
| listing all things, we have problems with.
| If you agree with me (as some of you have done on the #fedora-l10n irc
| channel, please feel free to add things to it, comment on it either
| here on
| this ml or directly in the wiki page.
| Thank you, hoping for a good collaboration/cooperation between
| http://www.mageia.org/ - Mageia, the magic continues
| Oliver Burger aka obgr_seneca
| web team
| i18n team
| packaging team
| i18n mailing list
>On Tue, 1 Mar 2011, Dimitris Glezos wrote:
>> On Tue, Mar 1, 2011 at 2:35 PM, Piotr Drąg <piotrdrag at gmail.com>
>>>> 2011/3/1 Dimitris Glezos <glezos at indifex.com>:
>>>> We should use one language team; it will make things much easier (ie
>>>> not have to administrate two memberships etc). I guess the correct one
>>>> is cs.. this is the standard Czech locale, right?
>>> Yes. The problem is that Publican uses XML language codes (cs_CZ,
>>> uk_UA etc.), and software uses only cs, uk etc locales. The right
>>> solution would be linking cs_CZ and cs-CZ translations with cs team.
>> I think Publican (or the Fedora toolchain around it) should be adapted
>> to support cs.
>>> Do you want us to file a ticket on this?
>> We could have a ticket filed. Fwiw, support for multiple languages per
>> team is quite a big change in the codebase.
>And would it be very hard to constantly mirror the team members to
>"language"? If it is inevitable, I may start another team for cs_CZ and
>ask people to join them both, but surely this is not very comfortable.
>> Dimitris Glezos
> Adam Pribyl
I think that untill Transifex supports more locales for a team, creating
a new "empty" teams for other locale/language variant and outsourcing
access to the other team/locale is the only working solution.
For illustration, now there is under the fedora project in Transifex.net
currently 'cs' team created, so 'cs_CZ' needs to be created and
outsourced access to it for the 'cs' team. Consequently, 'cs_CZ' will
stay "empty", and the 'cs' team's members will become its members. If my
understanding of outsourced access is correct.
On 02/17/2011 12:43 AM, Zach Oglesby wrote:
> Over the last few days it has been decided that we are going to move
> all of Fedora's translation efforts away from a self hosted solution
> and on to transifex.net.
This decision has greatly saddened and disappointed me. With all respect
to Dmitris and his team, to me, it seems like Fedora is giving up a key
part of our infrastructure and our independence.
Therefore, I have obtained permission from my manager to put time and
resources into packaging Transifex 1.1 for fedoraproject.org. I have
also had the time and skills of two Red Hat sysadmins allocated to get
Fedora's own instance of Transifex upgraded and migrated ASAP.
I believe that if the Fedora Localization Project is open to the idea,
we could have an up-to-date and fully functional local instance of
Transifex 1.1 available within a week.
Does this seem acceptable?
I also want to take this opportunity to thank Dmitris for his extremely
generous offer to host this massive project on behalf of Fedora.
However, apart from the reasons I gave earlier, I also can't help but
feel that this direction would be grossly unfair on Dmitris and his
business. Indifex is, after all, a commercial venture, and server
resources and bandwidth aren't free of charge -- especially on the scale
contemplated for Fedora. Just before I came to work for Red Hat, I owned
a small IT business myself, and know that every penny counts! :)
Tomorrow we will host the last Test Day of our L10N/I18N testing
marathon . The L10N Desktop Test Day will focus on translations
quality in desktop applications, specially Fedora configuration tools.
Translators and contributors from around the world are invited to test
and post results for their languages.
Fell free to edit the wiki with your results and join us in
#fedora-test-day if you have any doubts.
Igor Pires Soares
Fedora I18N/L10N QA
Fedora Ambassador (Brazil) - Member of FAmSCo
Name: Martin Minar
Location: Brno, Czech Republic
Profession or Student status: Working
About You: I work as Senior QE in Red Hat. When I was a lot younger, I
worked as translator for Czech Television and for some computer
literature related publishers. I also wrote one book. It has been some
time now and I'm missing those days a bit, so I decided I need to
train my brain cells again.
You and the Fedora Project: I'm using Fedora for... well I begun with
Linux a long time ago on Red Hat 5.1 - it was like 199X. Since in Red
Hat I work with Satellite/Spacewalk Project, I would like to start
with translation of Spacewalk. Didn't look beyond that.
[mminar@sarah ~]$ gpg --fingerprint 3A26C460
pub 4096R/3A26C460 2010-08-02
Key fingerprint = 1506 2A89 AD07 CC93 3883 8337 E67D 8137 3A26 C460
uid Martin Minar <mminar(a)redhat.com>
sub 4096R/C5C89839 2010-08-02
-------- Original Message --------
Subject: ACTION REQUIRED: Important hanges to Fedora translation workflow
Date: Thu, 3 Mar 2011 10:46:28 -0500
From: Jared K. Smith <jsmith(a)fedoraproject.org>
To: devel-announce <devel-announce(a)lists.fedoraproject.org>
The Fedora translation workflow has changed. If you are a developer
of a package being translated by the Fedora Translation (L10n)
Project, you must change your workflow slightly if you want translated
strings to appear in your software package. Tools and assistance are
available to make this workflow as simple as possible for developers.
Read below for details.
Over the past couple of weeks, we've made some improvements and
infrastructure changes to the Fedora translation system. We've moved
from a self-hosted version 0.7 instance of the Transifex software to a
hosted version of the 1.1-dev version at Transifex.net. The upgrade
from version 0.7 to version 1.0 (and beyond) introduces a number of
important changes for developers and packagers. Please pay close
attention to this email, particularly if your software package uses
translations provided by the Fedora Translation team. While the
changes aren't terribly complicated, they do have a bigger impact on
the developer than they do on the translation team.
The most visible change is that Transifex’s native integration with
source code management systems has been replaced by a mechanism for
automatic updates. Transifex now watches an HTTP view of a repository
for change notifications. In addition, there is now a more secure
command-line tool for project maintainers and translators. This new
command-line tool has been packaged for Fedora in the
"transifex-client" package. It is currently available in Rawhide
(pre-F16), and in the "updates-testing" repositories for Fedora 13,
14, and 15, and EPEL 5 and 6.
Here's the new workflow:
This series of steps only needs to be run once for a project.
* The developer installs the "transifex-client" package:
yum --enablerepo=updates-testing install transifex-client
* The developer runs the "tx init" command in the top level folder of
* The developer runs the "tx set" command according to the
transifex-client user guide found at:
creates a small config file, .tx/config, which can be committed in the
repository for re-use, if desired.
This series of steps are run on as as-needed basis:
* The developer updates and commits his or her POT file to the
project's repository at string-freeze time or as needed.
* Transifex watches an HTTP link to that POT file and auto-updates its
English strings regularly, *OR* the developer can also push the POT
file to Transifex (either manually or as part of a
build script) by using the "tx push" command.
* Translators work inside Transifex. Translated strings are stored
inside of Transifex, and are *not* pushed automatically to the
* Before rolling a release, the developer runs 'tx pull' (either
manually or from a build script) to fetch the latest translation files
from Transifex. Translation files do not need to live in
the repo, although the developer may commit and store copies if desired.
For more details on the features of the new version of Transifex and
more help on using the transifex client, please refer to either
http://help.transifex.net/user-guide/one-dot-zero.html or the
Fedora-specific wiki page at
you have technical questions, feel free to ask questions in the
#fedora-l10n or #transifex IRC channels or on the devel mailing list.
Fedora Project Leader
devel-announce mailing list
There are difficulties with uploading po files to Fedora projects in
transifex.net. I am experiencing the same problem like here . It
seems that there is a mismatch within Transifex concerning languages
teams variants (e.g. 'cs' vs. 'cs_CZ'). So I had to use 'cs' language to
upload a fully new Czech translation of Fedora docs project
website/Labels_cs_CZ.po in the upload dialog. However, I am still not
able to upload an updated Welcome.po.
Could you - or someone with appropriate privileges (that's why I also
cc'ing the FLP) to change the team language as suggested in the solution
to the problem?
2011/3/2 Simon Yan <simonyanix(a)gmail.com>:
> On Wed, Mar 2, 2011 at 1:10 AM, Domingo Becker <domingobecker(a)gmail.com> wrote:
>> 2011/3/1 Ville-Pekka Vainio <vpivaini(a)cs.helsinki.fi>:
>>> ti, 2011-03-01 kello 13:40 -0300, Domingo Becker kirjoitti:
>>>> I didn't check the current LiveCD, but for selecting language and
>>>> keyboard layout in GDM you must first choose a user, at least since
>>>> F13 on an already installed Fedora. In a LiveCD, as the live cd user
>>>> has no password, it would mean to start right after selecting the user
>>>> without the chance to choose a language.
>>> GDM has changed between F13/F14 and F15. In F14, you get the panel at
>>> the bottom of the screen, which lets you choose the keyboard layout and
>>> the language, even before automatic login on a live CD.
>> Perhaps in the LiveCD.
>> I normally don't use it to install a system.
>> But I just checked on an installed F14 x86_64 and it's the same as in
>> F13, you need to first choose a user and then it will let you choose
>> the language and keyboard layout.
> I can reproduce this issue from a live CD. Not able to change lang or
> keyboard layout after selecting an user.
> (Well, the only user available is "Automatic Login", I assume it's liveuser)
> Attached with screenshot.
GDM is different than in previous releases. I saw it yesterday after
installing F15 Alpha 2.
Would you file a bug report?
It will affect all potential new users trying Fedora from the LiveCD.
Domingo Becker (es)
Forwarding to Localization Mailing List.
-------- Mensagem encaminhada --------
De: He Rui <rhe(a)redhat.com>
Para: test-announce <test-announce(a)lists.fedoraproject.org>
Cc: Jens-Ulrik Petersen <petersen(a)redhat.com>, Igor Pires Soares
Assunto: I18n Desktop Test Day Tomorrow (Mar 3)
Data: Wed, 02 Mar 2011 15:56:49 +0800
Tomorrow we will continue the localization and internationalization test
day focusing on: I18n Desktop. Tests on this day will mainly cover
the yum langpack, font/rendering in applications as well as the input
If you are interested, feel free to post your results on wiki and join
us in #fedora-test-day(freenode) to discuss your queries.
FAS Name: Rhe
IRC nick: rhe #fedora-qa #fedora-zh
Sorry if this was asked already, there is so many emails about transifex
now, I am not able to read all of them.
We have similar problem to that described in
While I created Czech team on Transifex as "cs", there are projects that
have language as "cs_CZ". Do we have to create two teams? As cs is more or
less equal to cs_CZ, I'd love to have the same team for both... is it