The strings in rhn-client-tools package are not splitted by paragraph.
It is hard to translate them that way.
Latinos en EE.UU: noticias y artículos de interés para ti
To all translators, urgent request:
As some of you may already know, we are trying to change the default browser
splash page of FC6 to something more meaningful, like the following draft:
Since this is will be the default homepage of the user's browser, every user of
FC6 will see it every time he (she) opens his browser. We really need to
localize this page **as much as possible**.
It would be great if you spent some time translating the strings of this page.
In total there are only 24 messages. They can be found in the PO files of the
release notes on the i18n CVS server. They are located almost at the top of the
POT file and are marked with "en_US/homepage.xml", like this:
msgid "Welcome to Fedora Core 6!"
Even if you won't be able to translate the Release Notes, you can translate
these messages and we will be able to provide the user with a localized version
of this page. If you did translate it, please commit the file and let me know.
If you need more help, ask away, right away. :)
Thanks for all your hard work. We are really close to FC6, so let's all put our
best effort to make this a spectacular release.
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
I am sorry to ask this question as I am an attentive reader of this
list, but I can't find anymore how to translate firefox default homepage
Can someone be kind enough to point be the right place please ?
So many thnaks in advance :)
We launched FC6 last week with the release notes in ten languages; twice
as many as last release, and a fraction of what we are going to do for
the next release:
(Notice that link is live again after being down since the launch day.)
Ten languages is *fantastic*, considering the problems we had along the
way. Thank you so very much to our fellow contributors who dealt with
these problems, and thank you all for persevering.
Fortunately, the fedora-release-notes RPM can be easily updated. This
means the translations that weren't able to go into the ISO could be
In approximately a few weeks, we want to push out an update to this RPM.
The main reason is to get more translations into the package.
For this update, the Fedora Translation team shall have the time to do a
proper translation without rushing. Expect another email soon with
Karsten, Fedora Documentation
Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProjectquaid.108.redhat.com | gpg key: AD0E0C41
I found it useful to search in the desc file for a specific package that has
a functionality that I need for a specific job.
I learned a lot just by translating those strings. I knew packages that I
did not know they exists, although, I am a Red Hat user since version 3.1.
I think it would be very useful to have an html version of the combined desc
and summary files, together with the package name and version in the way
anaconda shows them.
But in one file or no more than 4 files, in the wiki, so one can look for
something by using Ctrl-F in that/those file(s), or by using the search
utility in the wiki.
Maybe what I am asking for is already made, if so, it is hard for me to find
it, give me the link.
If not, please consider creating an html file from the desc and summary file
for their respective languages to put it on the Fedora wiki.
I realized that some system-config-services entries that were translated
were not included on the version 0.9.1-1. It is happening almost the
same that happened with system-config-printer. The module is showing a
mix between two languages.
I filed a bug to that, please if the same is happening with your
language add a comment to the bug:
Igor Pires Soares
Brazilian Portuguese Translator
>I have finished pending work on the POT for the Fedora Core 6
>Installation Guide. Can I ask someone to please import this to
>i18n.redhat.com and make it available for translators who don't do work
>in our Docs CVS?
Oh, yes, please; I am waiting for this...