On Tue, May 17, 2011 at 5:10 AM, noriko <noriko(a)fedoraproject.org> wrote:
Kévin Raymond さんは書きました:
> Hi guys,
> I know that release time is a really busy time for everyone, but this
> release was not really funny for every projects.
> First of all, release notes was not easy to find in transifex, as
> there were not linked to the Fedora Documentation project.
> This is why there are only 4 languages mostly translated while last
> time for Fedora 14 release, we had 10 languages 100% translated.
I've heard that there was some issue for making a link at tx.net
team has been required to learn Tx and move their documentation to
within very short time frame, thus it is not hard to imagine that book
owners have experienced the hardest time. So I echo your concern
completely that F15 has less documentation localized than F14.
Good new is that the release note now should be appeared under Fedora
> We should work closer between docs and l10n teams.
Indeed, it will be nice if l10n team can be notified by docs team when
especially release note is ready for translation. Besides, it also is
encouraged that translators join #fedora-docs channel on freenode to
discuss any concern.
I do. My apologies to all translators, I've been there to follow the
release notes integration and was finally told that an announce would
be done in the mailing list, but didn't notice that it was not done.
> I can't see neither Dutch, nor Chinese nor French release notes
> version under docs.fpo. Would it be linked in GA time ?
This is left for docs team to answer...
> What about
> packages already available in our F15 systems? Those files are not up
> to date. Should we fill a trac ticket to get a rebuild? There should
> be an issue building the french one, I can't build it locally but I
> don't really know publican (a tag should be missing in the po file).
What does 'package' refers to?
It refers to the package which should be embedded in the iso file,
that's why the deadline was important.
Software translation deadline was over. Any string freeze break
For publican, there is Publican User Guide. This might help.
In fact my issue is coming from the po file, there should be a missing
tag in a string, but msgmerge didn't help. Gonna see later on.
> In an other hand, docs maintainers created two teams for french while
> only one is existing. Could anyone fix it?
This should be able to fix by Transifex team once tx client is released.
Both teams were created, hence tx push was working. But yeah, it could helps.
> Last words, it seems that not all guides have moved to transifex.net
> I can't find the security one. Could someone check them?
Sometime ago, I read the post in docs lists, which said that this guide
owner have had no time for F15 and looked for help. I am just guessing
that this guide might be given up for F15.
This email was also in order to see if some translators could join the
This doc only need to be pushed in transifex.net
, and to be built
frequently. (I don't know the process, every book maintainer has to
built its own book?).
It doesn't need to be updated to the GNOME 3 environment (nor has been
other guides pushed to transifex.net
I understand that learning how to use the new transifex.net
takes time (I still see developers who didn't notice major changes).
So far, hard work has been done, thank you guys!