The issue is that I couldn't find certain parts of some strings from the original English version of RN in the po-files. And since the string from po-file and string from the source xml-file are different, the source string is included in the final document. So we have no chance to translate them.
I've found 3 strings where it occurs. I've opened the Bugzilla ticket  and described them in it. In short:
-- <productname> tag dissapears from <ulink> tag (File_Systems.po)
-- <productname> tag dissapears from <emphasis> tag (Desktop.po)
-- <ulink> tag with <orgname> tag in it wholly dissapears with it's content (Desktop.po)
Translators, did anybody face with the same problem? I can't understand why it happens.
 - https://bugzilla.redhat.com/show_bug.cgi?id=876506
Inna Kabanova / Russian Fedora Team
gfs2-utils is an open source project containing tools necessary for
creating, checking, tuning and manipulating gfs2 file systems. The
gfs2-utils package is required wherever gfs2 file systems are used,
particularly in Linux clusters.
I'm currently trying to improve the strings in upstream gfs2-utils for
localisation. In the meantime, I'd like to drum up interest in
progressing the translation effort. We have a Transifex project set up
and open for translations:
i18n support is a fairly recent addition to the project so the strings
likely require some work to make life easy for translators. If there are
any issues please contact me or file a bug report at
http://bugzilla.redhat.com/ under the gfs2-utils package in Fedora /
Rawhide, and I'll try to get the strings updated as soon as I can.
Whether bug reports or translations, any help you can provide in
translating gfs2-utils into different languages, and making it easier to
do so, would be greatly appreciated.
On 11/19/2012 05:27 PM, Pete Travis wrote:
> On Nov 19, 2012 12:04 AM, "Dayle Parker" <dayleparker(a)redhat.com
> <mailto:firstname.lastname@example.org>> wrote:
> > On 11/17/2012 06:51 AM, Daniel Cabrera wrote:
> >> Hi,
> >> The Spanish team has finished the translation of the Fedora
> >> Virtualization Getting Started Guide , but I'm not able to publish
> >> it. I mean, I can publish it but only in English.
> >> I've also tried to publish the Dutch and Japanese versions, with the
> >> same result.
> >> Any Help?
> >> 
> >> https://fedora.transifex.com/projects/p/fedoravirtgettingstartedguide/
> >> Thanks in advance, regards,
> >> Daniel Cabrera (es)
> > Hi Daniel,
> > Thanks for the email and for all of your team's translation work! I
> think as the doc maintainer it's my job to publish it (please correct
> me if I'm wrong).
> > Good news and bad news:
> > Good news: I was able to publish the Dutch translation [or at least
> run through the commands in 'Publishing a document':
> without any errors -- where do I verify this has been successful?
> > Bad news: I hit an error using this command (which was successful in
> Dutch and English) when publishing the guide in Spanish, plus a
> different issue in Japanese:
> > publican build --embedtoc --publish --formats
> epub,html,html-single,pdf --langs LANGUAGE_CODES
> > I might be wrong, but it looks to me like an XML error in the
> Introduction file - possibly in the xref?
> > Merging es-ES/Introduction.po >> en-US/Introduction.xml ->
> > not well-formed (invalid token) at line 4, column 238, byte 402:
> > <!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
> > ]>
> > <para>Fedora contiene paquetes y herramientas que soportan una
> variedad de entornos virtualizados. La virtualización de Fedora
> suministra el desarrollo en fases prevías para la virtualización en
> Red Hat Enterprise Linux. vea <xref linked=”chap-Guía de Inicio de
> Virtualización-Productos”/> para más información sobre los productos
> de virtualización disponibles con Fedora.</para>
> > If anyone can help, please let me know.
> > Thanks so much,
> > Dayle
> > --
> > Dayle Parker
> > Content Author
> > Engineering Content Services
> > Red Hat Asia Pacific -- Brisbane, Australia
> > dayleparker(a)redhat.com <mailto:email@example.com> | irc: dayle
> > --
> That xref tag looks suspicious. It should read ' <xref linkend= ' not
> '<xref linked='.
> I'd also test to make sure the spaces in that target don't break the
> link, just because it isn't the convention I'm used to. I wasn't even
> aware that we translated the id= and xref= strings, so this second
> concern could be misguided.
Thank you to Pete and Tomoyuki for helping out. :)
I was able to publish the Japanese translation without a problem and
it's now online.
I've gone into the es-ES .po files and fixed the XML issues and have
been able to publish normally.
Thanks to all the translation teams for your great work!
The Spanish team has finished the translation of the Fedora
Virtualization Getting Started Guide , but I'm not able to publish
it. I mean, I can publish it but only in English.
I've also tried to publish the Dutch and Japanese versions, with the
Thanks in advance, regards,
Daniel Cabrera (es)
The Fedora 18 Beta Release Notes should now be ready for translation.
You can find them at:
I want to thank all of you for your efforts, and apologize for the
late push. Something will have to be added about the Fedora 18
upgrade path, but they should be mostly complete otherwise. Hopefully
there won't be too many changes, but please get in touch if you see
room for improvements. The docs team can be reached at docs AT
lists.fedoraproject.org , though #fedora-docs , or with a bugzilla
ticket against the release notes.
> There is a "release" feature on the Transifex management page. I didn't
> want to break from SOP, but if it does what I think it should, perhaps we
> should use it in the future. I'll test it out on the technical notes later
It does not work like you would expect.
We already have 4 releases: https://fedora.transifex.net/
* Fedora Documentation
* Fedora Websites
* Fedora Uptream Projects
* Fedora Main
The "release" is updated MANUALLY by the Fedora Project Hub maintainers. I used
to do it time to times. But it is really slow (you need to add each ressource
one by one using the online interface)...
Don't expect it to be up to date.
Currently, a translator has 2 ways to find ressources from a specific project:
* Checking the project itself, like. Here for example some ressources are
out to date. But at least it features them all.
* He can get it from a specific release. Like the Fedora Documentation for
example at. But this could clearly be outdated as the maintainer (me for
example, as well as you Petr) does not know if there are updated if he is not
watching the project. And clearly, we can't watch them all. The project
maintainer has to ask us to update the release. But they don't. Sometimes I am
asking the docs maintainers. Sometimes. (I would love to be able to update that
through the transifex client tool).
One translator can also find all the ressources from the release, by clicking on
a specific ressource and then clicking on it's title to reach the main project.
Example by clicking on any ressource file at as if we would like to translate
it, we can reach the main project at the top of the opened div (box) in the
title "Ressource: Fedora Release Notes » Amateur_Radio » English".
IMHO which is safer and better is to clean the project before.
 https://fedora.transifex.com/projects/p/fedora/r/fedora-docs/ (but it is
linked at the bottom of fedora.transifex.com)
Le lundi 12 nov. 2012 à 12:00:59 (+0100), Alle X a écrit :
> I noticed this misspelling in fedoraproject.org/sv a week ago, and it seems
> like it's still there:
> Behöver du *hjölp*?
> Få det här.
> It should say "*Behöver du hjälp?*"
> Thought I'd just tell you in case you haven't noticed.
I don't remember your previous email, and could not find it.
Ccing the trans mailing list for them to correct it.
Please note that it could have been corrected on the beta branch. Which should
have been released weeks ago. Currently the translations are frozen on the alpha
Guys have to ask me to merge from the beta branch in the alpha one if they need
to fix a bad typo.
After the anaconda team updated the po file, there comes a string with
3 placeholders in it.
Here it is:
%s may not have enough space for grub2 to embed core.img when using
the %s filesystem on %s
As a translator, I can't keep the placeholders' original order in the
translation. That means the translation won't be right or even
misleading because the placeholders will be interpreted in their
So I added 1$ 2$ 3$ into the %s to make sure what the order is in the
translation. The translation is:
当在 %3$s 上使用 %2$s 文件系统时，%1$s 的空间大小可能无法让 grub2 嵌入 core.img
Does this work in anaconda? Or what can we do to keep these %s right
intepreted in translation?
This mail is also Cced to Chris Lumens.
Fedora Project Contributor
Bug ID: 863375
QA Contact: aalam(a)redhat.com
CC: diegobz(a)gmail.com, fedora(a)couf.be,
Summary: F18/QA test : Untranslated lines in im-chooser
Story Points: ---
Mount Type: ---
Product: Fedora Localization
Description of problem:
im-chooser for F18QA test seems to be untranslated for
any of the languages we support according to other reports.
Version-Release number of selected component (if applicable):
Every time "im-chooser" is entered.
Steps to Reproduce:
1.In the terminal, enter "im-chooser" as root
2.See the gui that appears.
All the entries are in English, except for "close" button for Japanese.
All lines should be localized into the languages we support.
This seems to be the upstream problem?
You are receiving this mail because:
You are on the CC list for the bug.
As you might notice Anaconda developers regularly and deliberately break
any existing string freezes during this cycle. In addition to this, they
have blocked all translations today .
Does anybody know if this is intentional behavior of Anaconda developers?
Thanks in advance for your answers.