XML2PO .vs. intltool
by Tommy Reynolds
Does anyone have experience using the stuff from the intltool RPM?
I'm seeing some nasty interactions between locales, <xi:include> and XML
in general with XML2PO.
I'm not asking for recommendations yet, I'm just wondering if anyone has
already looked into intltool's capabilities?
--
I'm already an anomaly, I shall soon be an anachronism, and I have
every intention of dying an abuse!
18 years, 2 months
Need some info
by Zaw Thet Aung
Hi, Greeting to all of you. I have sign-up with Fedora translation project last year but I haven't check out any file yet. Unfortunately, I didn't back up my private key when I upgrade from Fedora 3 to Fedora 4. Now, I cannot connect to CVS server without the private key.
Is there any way I can retrieve my private key? I have tried to find the contact info in Fedora project page but I can't find it.
Anybody can provide me with contact info to project administrators?
Thanks.
18 years, 2 months
[RFC] FDP locale "en" considered harmful
by Tommy Reynolds
Hello, Doc'ers and I18N'ers!
Before we get a possible exponential explosion as more documents
appear in our project, we have a problem.
In the FDP early days, we mistakenly used the string "en" as a label
to identify English-language file, such as "foo-en.xml".
Later, we added I18N support and the labeling changed to
"foo-${LANG}.xml", where ${LANG} was an ISO locale designator such
"ru" or "pt_BR".
Much later, we changed the filename scheme to use the ${LANG} locale
as a subdirectory specifier, such as "${LANG}/foo.xml".
Embarrassingly enough, we forgot to change the pseudo-locale "en"
into a real locale string such as "en_US". Because of this, some
tools complain about not having an "en" locale, .POT/.PO files are
being generated using the fictitious locale "en" as a reference, and
undoubtedly other issues that I haven't figured out yet.
So (gulp) I propose to change all references to the "en"
pseudo-locale to the legal "en_US" string. This will require some
directory renaming, Makefile ${PRI_LANG} surgery, and some
search-and-destroy "s/en/en_US/g" in every .POT/.PO file to date.
AIUI, this will not corrupt the existing translations, it's just a
change in the comment locating the replacement string:
#: entities-en.xml:6(title)
would become
#: entities-en_US.xml:6(title)
and no translation hiccups should occur. This calls for a shell
script...
SUMMARY
If we ever need to do this, now is the time or forever live in a
bogus "en" locale.
Speak now or forever.. oh, you get the point.
--
I'm already an anomaly, I shall soon be an anachronism, and I have
every intention of dying an abuse!
18 years, 2 months
release notes compilation...
by Francesco Tombolini
I have some problem compiling the release notes.
I get these errors:
----------------------------------------------------------------------------
$ make
xsltproc --stringparam lang en --stringparam
fdpdir /home/tombo/Fedora_i18n/docs/release-notes/.. --stringparam doctype
articleinfo /home/tombo/Fedora_i18n/docs/release-notes/../docs-common/packaging/bookinfo.xsl /home/tombo/Fedora_i18n/docs/release-notes/rpm-info.xml
| xmlformat
-f /home/tombo/Fedora_i18n/docs/release-notes/../docs-common/bin/xmlformat-fdp.conf
>en/fdp-info.xml
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "en"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
sed -i 's#legalnotice-opl-en.xml#legalnotice-relnotes-en.xml#g'
en/fdp-info.xml
ln -f
-s /home/tombo/Fedora_i18n/docs/release-notes/../docs-common/common/entities/entities-en.ent
'locale-entities.xml'
LANG=en.UTF-8 xmlto html
-x /home/tombo/Fedora_i18n/docs/release-notes/../docs-common/xsl/main-html.xsl
-o RELEASE-NOTES-en en/RELEASE-NOTES.xml
/home/tombo/Fedora_i18n/docs/release-notes/../docs-common/bin/fdpsh: line 40:
xmlto: command not found
make: *** [RELEASE-NOTES-en/index.html] Error 127
----------------------------------------------------------------------------
what can I do?
Thank-you
--
Francesco Tombolini <tombo(a)adamantio.net>
18 years, 2 months
FC5 release notes available for ISO-bound translations
by Karsten Wade
I'm happy to announce that we have declared the Fedora Core 5 release
notes GOLD for the ISO and ready for final translation.
You can get the files from CVS.
With a CVS account:
In a clean directory do these commands:
CVS_RSH=ssh CVSROOT=:ext:YOURUSERNAME@cvs.fedora.redhat.com:/cvs/docs cvs co -r release-notes-FC-5-ISO-trans-freeze -d release-notes-FC5-trans release-notes
CVS_RSH=ssh CVSROOT=:ext:YOURUSERNAME@cvs.fedora.redhat.com:/cvs/docs cvs co -r release-notes-FC-5-ISO-trans-freeze -d docs-common docs-common
Via anonymous CVS:
CVS_RSH=ssh CVSROOT=:pserver:anonymous@cvs.fedora.redhat.com:/cvs/docs cvs co -r release-notes-FC-5-ISO-trans-freeze -d release-notes-FC5-trans release-notes
CVS_RSH=ssh CVSROOT=:pserver:anonymous@cvs.fedora.redhat.com:/cvs/docs cvs co -r release-notes-FC-5-ISO-trans-freeze -d docs-common docs-common
If you do wish to translate without full CVS access, you can file a
bugzilla using this pre-filled report:
http://tinyurl.com/r5vop
Please attach the PO/POT files to the bugzilla report you file.
There is a fair amount of new content, possibly up to 25%. Of the other
content, much of the language has been rewritten for clarity. Depending
on how you have it translated, perhaps another 30% to 50% has been
modified.
We will be performing another snapshot of the Wiki content and build for
Web-published release notes. Around 10 or 11 March we are going to have
updated content available for translation. These updates are posted as
they become available from translators. This Web-published set of notes
is directly tied to the Fedora Core 5 release schedule; if that schedule
is changed, the Web-published release notes change with it.
Thanks to the entire release notes team, the beat writers, editors,
reviewers, and translators. You all have contributed to a release notes
for Fedora Core that is the best yet. Congratulations.
- Karsten
--
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Content Services Fedora Documentation Project
http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject
18 years, 2 months
[ANN] Translatable Entities Call For Translators
by Tommy Reynolds
The infrastructure to support the I18N translation of the Fedora
DocBook entities is now ready for translators to insert the
translations.
Background:
The FDP has defined certain XML entities (&FED;) to represent
commonly-used project references. These have been hand-coded into
separate files such as "docs-common/common/fedora-entities-en.ent"
and then explicitly included into documents using their exact
filename.
Some translations for non-English locales have been added, but these
have all been manual efforts involving more hand-coding and editing.
Before these "docs-common/common/fedora-entities-${LANG}.ent" files
could be used in a translated document, that document must have been
manually edited to reference the newly-translated locale rather than
the original one. Again, this was a manual editing operation.
No more! Down with manual editing! Up with correct processes!
This announcement informs you that there is a "new world order" (NWO)
for these entities files. From now on, adding additional I18N locale
support will use the same tools and procedures already familiar to
the translation community. Per-locale XML and .ENT files will be
automatically derived from a baseline English XML file, a .PO file,
and the xml2po(1) program from the "gnome-doc-utils" RPM.
Get the new resources by updating your "docs-common/common" directory
like this:
$ cd docs-common/common
$ cvs update entities
and then look into the resulting "entities/" directory.
The "README.txt" file contains detailed instructions for adding new
locale support to the infrastructure.
If your locale is already in place, please add the appropriate
translations according to the "entities.pot" and "${LANG}.po" files.
After editing the "${LANG}.po" file, a simple:
$ make
command should do everything needed to generate the
"entities-${LANG}.ent" file. The command:
$ make help
will show the available make(1) targets. Note that adding a new
locale to the ${OTHERS} Makefile macro will automatically add all the
necessary Makefile targets for your locale.
Note to document authors: you can look at the "example-tutorial" to
see how this will affect you, but please do NOT switch to these new
entities files until I make a specific [ANN]ouncement in a few days.
Cheers!
--
I'm already an anomaly, I shall soon be an anachronism, and I have
every intention of dying an abuse!
18 years, 2 months
