I have built the Fedora 12 Translation schedules using the same
methodology from Fedora 11.
Please tell me what needs to be corrected, added, or changed by
referencing the task number here:
As an added bonus I've also created a combined view with the
Documentation schedule (notice the overlay in different colors). The
intention if this version is to place the Translation tasks in the
context of the rest of the release:
And if that wasn't enough, I'm also generating iCal files for this
release that are team specific. So pop this into to your favorite
calendar application and tell me which additional tasks you'd like to
see or have removed. To keep the presentation clean it only includes
the more important tasks/milestones.
It would be most helpful to get your feedback as soon as possible. If I
don't hear anything by Friday I will assume these are done.
One other question... who is representing the Translation team at the
"Release Readiness Meetings" for Fedora 12? It was disappointing not to
have representation from the translation team for the Fedora 11 preview
and final release readiness meeting or the Fedora 11 retrospective.
I've just set up a new project to fill in some missing translations in
the docbook stylesheets. These stylesheets are a set of XML templates
used to produce documentation, and are especially important for Fedora
docs because our documentation tool (Publican) relies on them. For
example, the names of elements like "Chapter", "Appendix", "Example",
and "Table" in Publican documents come from docbook.
The project is located here:
In some ways, translating these stylesheets should be pretty easy — each
po file contains only around 200 words, most of them very common.
However, almost each of these words is in a separate string by itself
without any context. In most cases, the lack of context shouldn't be a
problem; for example, words like "Book", "Author", or "January" are
self-explanatory. Where it looks like context might be a problem, I've
included comments in the PO file that should be visible in whatever
software you use to do your translations. If anything is still unclear,
or you think that I could have explained something better, please ask!
I'd be very grateful for your feedback and suggestions.
One further point to be aware of is that the docbook stylesheets often
include different versions of a word with different capitalisation. For
example, there are separate entries for "warning", "Warning", and
"WARNING". If your language distinguishes between upper- and lower-case
letters, please pay careful attention to the English capitalisation and
follow it as appropriate for your language. Of course, if your language
doesn't have different cases for characters, then you can just use the
same translation to represent all the differently-capitalised English words.
Thanks in advance for anyone who can help out with this! (And thanks to
Piotr who took Polish from around 60% to 100% before I even sent out
As I dug into John Poelstra's schedule in more detail, I noticed a few
issues that I hadn't noticed in earlier reviews. Specifically, very long
times on some short tasks with short times on some more difficult tasks, and
tasks out of order.
Since I don't have a really good feel for the guides, I put together what I
thought was a more workable schedule for release notes only. Eric was going
to look at guides. My strawman is at:
I fixed major milestones to the same dates that John had so hopefully we
don't affect other teams. However, I did put a couple of L10N tasks on the
list since they are tied closely to us. I have not, however, had any
discussion with L10N as to whether these times make any sense at all to
John suggested we get together in a Gobby/Talk meeting to get this schedule
into sync with his. I think we need to get the guides schedule integrated
with this and include a representative from L10N in that meeting.
Because of the new definition of alpha and beta, our schedule looks a lot
different than earlier releases. Specifically, since alpha should be
"feature complete", we should have almost everything we need for release
notes by alpha. That means the bulk of our work is between alpha and beta.
However, since Beta should include more or less complete release notes, L10N
will need time to translate them. That pushes Docs work forward some,
meaning we will have a real scramble right around alpha, and L10N will have
a pile of work just before beta. The upside is that the work before GA
should be a little less onerous, and there should be little left to
If we can make our plan of a table for all changes and prose only for
significant effort required to convert plus highlighting high-profile
features, there should be a lot less prose to write (and translate) than
previous releases. We will, however, need some pretty aggressive wiki
gardening to allow us to convert to XML quickly.
I would like everyone to take a really close look at this, and comment on it
on this list. I think I have the major tasks identified, but it is always
good to have more input.
Bruno Wolff III said the following on 07/28/2009 04:27 PM Pacific Time:
> On Tue, Jul 28, 2009 at 15:26:27 -0700,
> John Poelstra <poelstra(a)redhat.com> wrote:
>> Unfortunately I've found that it is extremely hard (as you may be seeing
>> already) to create a really solid schedule over email, particularly when
>> more than one team is involved and questions have been raised in
>> response to tasks or dates someone has previously suggested.
> It may be kind of late to consider this, but maybe it would help to use
> taskjuggler to look at the timing for the release process. If it does work,
> you'd be able to mostly reuse the projects from release to release. I think
> it would also make it easier for groups to give feedback on their pieces
> while allowing the new information to be easily used for the whole project.
I've already been doing this for several releases :-)
If you look at the source file you'll see very few hard coded dates.
The problem I've had is getting teams to do a detailed review of the
dates and cross-team dependencies. The other difficulty is that each
release the task methodology changes as teams tweak their processes and
attempt to learn from the previous release. Due to the different
nature of each team's work, there is very little reuse of task structure
between the teams.
Each release we've made the schedules a little tighter a little better,
but it's feeling like Fedora 12 could be the "break out" release for
making substantial progress!
Check out this directory if you'd like to explore more:
Though I'd started translations on Fedora more than two years ago,
I'd never sent a self-introduction to this mailing list.
I'd started translations just before starting the Transifex project.
I had committed many translations via CVS access between Fedora 8 and 9.
I also translated Release Notes into Japanese on this period.
When the Transifex started, I'd tried but couldn't submit my translations.
I didn't know the actual reason, but I supposed it was because of my poor
operations or poor understanding on the Transifex.
So, I gave up submitting translations via the Transifex.
When all the translations works were moved to the Transifex, I stopped
Today, I tried the Transifex and succeeded. So, I can restart translations.
BTW, TQSG says "the pencil icon labeled a translation for this language next
to each project" (on 3.3 Committing Projects), many of the projects don't
have the pencil icon. Does it mean that it is not ready for updating the
translations? And how do I request to show the pencil icon?
Power up the Internet with Yahoo! Toolbar.
Since many of languages have been updated, so I again pushed all
languages except Dutch. I need a little more time to fix Dutch, but
promise it won't long.
* As those published as new, it may have some problem so let's see.
Bosnian, Indonesian, Malay, and Swedish
German, Greek, Spanish, French, Hungarian, Italian, Japanese, Punjabi,
Polish, Brazilian Portuguese, Portuguese, Russian, Serbian and Chinese
I identified my bad operation and made correction.
Now Translation Quick Start Guide (below languages and en_US) will be
again published at next sync which should happen every 6 hours or so
afaik, with the updates and translations made by UTC 24-July 00:00
(cross my fingers).
Updated POs should be available now.
Let me know anything unexpected.
Russian, Chinese (Simplified), Spanish, German, Hungarian, Greek,
Brazilian Portuguese, Portuguese, English
Build error language:
Indonesian, Swedish, Malay, Dutch
Location: Lepoglava/Zagreb, Croatia; CET(GMT+1)
U/N: shumi12321 Language: Croatian (HR)
Student status: Graduate Student of Mathematics and Computing at
University of Zagreb (PMF-MO)
School: Prirodoslovno-matematički fakultet Zagreb, Matematički odjel
I'm using Fedora as only OS on all my computers for more than two years ;)
I'm interessted in joining other projects which are not only
I've been working at similar translation projects, such as Facebook Translator.
Computer skills: programming (C/C++ and Java oriented); high interests
in artificial intelligence, metaheuristics, etc.
pub 1024D/2FB99F53 2009-07-25
Key fingerprint = E245 37C8 7816 8F10 C33C 2CE7 77DF F8E2 2FB9 9F53
uid Josip Šumečki (shumi) <shumi.1337(a)gmail.com>
sub 2048g/933ACDB2 2009-07-25