Is there any actual documentation?
by Timothy Murphy
I'm sorry to sound mean,
but I've been observing the often interesting and learned
discussions about Fedora documentation for some time,
but when I looked recently to see what documentation was around
I found remarkably little -
basically just the comments on the Release Notes.
Am I missing something?
Or will the documentation be appearing "real soon"?
I may say I always read
the very good (and beautifully produced) Fedora Weekly News.
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
18 years, 1 month
Re: install-guide/po fedora-install-guide.pot, 1.2, 1.3 zh_CN.po, 1.5, 1.6
by Yuan Yijun
2006/3/6, jtr Tommy Reynolds <fedora-docs-commits(a)redhat.com>:
> Author: jtr
>
> Update of /cvs/docs/install-guide/po
> In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28688/po
>
My god. It seems I have to revert it. Have you tried msgfmt
--statistics zh_CN.po? I think the numberz would be very interesting.
--
bbbush ^_^
18 years, 1 month
Re: install-guide/en fedora-install-guide-abouttoinstall.xml, 1.6, 1.7 fedora-install-guide-acknowledgements.xml, 1.6, 1.7 fedora-install-guide-adminoptions.xml, 1.8, 1.9 fedora-install-guide-beginninginstallation.xml, 1.7, 1.8 fedora-install-guide-bootloader.xml, 1.6, 1.7 fedora-install-guide-diskpartitioning.xml, 1.9, 1.10 fedora-install-guide-firstboot.xml, 1.8, 1.9 fedora-install-guide-installingpackages.xml, 1.6, 1.7 fedora-install-guide-intro.xml, 1.11, 1.12 fedora-install-guide-locale.xml, 1.8, 1.9
by Tommy Reynolds
Uttered "Tommy Reynolds" (jtr) <fedora-docs-commits(a)redhat.com>, spake thus:
> Log Message:
> Corrected paths to entities. Everywhere.
Since I'm frobbing with the entities as we speak, I took the liberty
of correcting the entity paths. The "en" version now builds nicely.
The zh_CN version puts msgmerge(1) into an endless loop... oh, well,
at least it's a *new* problem.
Cheers
--
I'm already an anomaly, I shall soon be an anachronism, and I have
every intention of dying an abuse!
18 years, 1 month
XML2PO is weird!
by Tommy Reynolds
It seems that xml2po(1) will sometimes expand entities and will
sometimes _not_ expand entities. There is a "-k" or a
"--keep-entities" that claims "Don't expand entities", but it lies.
Evidently there is a fallback mode in xml2po(1) where *all* entities
are expanded. I know there is an "-e" or "--expand-all-entities"
switch, but I'm not using it.
For example, generate a .POT file:
$ cd example-tutorial
$ xml2po -o the.pot en_US/example-tutorial.xml
and then apply it (UNCHANGED!) against the original XML file using
various combinations of "-e", "-k" and no switches at all:
$ xml2po -o junk-e.xml -e -p the.pot en_US/example-tutorial.xml
$ xml2po -o junk-k.xml -k -p the.pot en_US/example-tutorial.xml
$ xml2po -o junk-plain.xml the.pot en_US/example-tutorial.xml
and then compare the files using diff(1). There are NO differences.
Anybody care to explain? Or suggest a work-around?
--
I'm already an anomaly, I shall soon be an anachronism, and I have
every intention of dying an abuse!
18 years, 1 month
missing in release notes...
by Francesco Tombolini
Ciao,
While translating the release-notes I have seen 2 small problems:
1) no italian entities where used to make the documents but the english were
used instead (I have cecked it in RELEASE-NOTES.xml)
2) no Virtualization document can be translated; it not appear in the .po or
pot file.
Thanks
--
Francesco Tombolini <tombo(a)adamantio.net>
18 years, 1 month
Confusion about using CVS
by Hugo Cisneiros
Hi,
I finished the translation of the CVS' pt_BR.po for the release notes,
as you have noted by the cvs commits. But I'm a little confused about
using the CVS for release notes right now. For this reason, I'm sending
this email.
First I was told to get a updated and clean tree for docs-common and
release notes with:
============
$ cvs co docs-common release-notes
============
Then grab the translation freeze tag to begin translation:
============
$ cvs up -r release-notes-FC-5-ISO-trans-freeze \
docs-common release-notes
============
Then I created the po/pt_BR copying from the po/RELEASE-NOTES.pot and
began translating. I finished in the past two days. Then I changed the
Makefile to add the pt_BR target for building.
I commited the changes to a Non-Tagged version. So the modifications
will go to the updated and current tree. Is this right? Or Am I doing
something wrong?
I'm asking this because when I tried to build, I got this error:
============
$ make html-pt_BR
mkdir -p pt_BR
po2xml en/ArchSpecific.xml po/pt_BR.po >pt_BR/ArchSpecific.xml
mkdir -p pt_BR
po2xml en/ArchSpecificPPC.xml po/pt_BR.po >pt_BR/ArchSpecificPPC.xml
can't find
After using Open<emphasis role="strong"></emphasis>Firmware to boot the
CD, the bootloader (yaboot) should automatically boot the 64-bit installer.
in
After using Open<emphasis role='strong'></emphasis>Firmware to boot the
CD, the bootloader (yaboot) should automatically boot the 64-bit
installer. </para>
make: *** [pt_BR/ArchSpecificPPC.xml] Error 1
============
And I don't have any idea what to do. What are the procedures?
And just to finish this message, I corrected some minor speling and
grammar errors in the Wiki Beats, so based in the Wiki changes the
responsables (Bob?) could commit to cvs.
Thanks and sorry for the incovenience!
--
[]'s
Eitch
http://www.devin.com.br/eitch/
"Talk is cheap. Show me the code." - Linus Torvalds
18 years, 1 month
Re: docs-common/packaging bookinfo.xsl,1.16,1.17
by Paul W. Frields
Catching up on some commits, sorry...
On Wed, 2006-02-22 at 02:12 -0500, Yuan Yijun wrote:
> Author: bbbush
>
> Update of /cvs/docs/docs-common/packaging
> In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11008
>
> Modified Files:
> bookinfo.xsl
> Log Message:
> if revdescription is not translated, use "en" by default
Be careful with XSL, this actually broke [book|article]info generation
in a pernicious way. Fixed for now, although it needs to be converted
to en_US usage shortly.
--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Documentation Project: http://fedora.redhat.com/projects/docs/
18 years, 1 month
[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, 1 month
Re: Fedora Tour
by Mtshca＠aol.com
Hi..
I am new. I need to know a list of dialup 56k modems that will work on
Fedora Core 4 Linux9.
Very appreciatively
Michael
mtshca(a)aol.com
18 years, 1 month
