From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Use Anaconda in any language except English
The online help in the Graphical installer is a sgml file, and its not available
in the translation CVS system. Each time new things are added to the original
file its up to each individual translator to notice this and update it correctly.
I'd really like to see that file turned into a .po file and added to the
it *is* in the i18n CVS in anaconda/anaconda-online-help
If you don't have that, you may have to do 'cvs checkout' again
instead of 'cvs update'.
When you do 'cvs update', notice when the untranslated file changes,
do 'cvs log $FILE' to see the release numbers and then
'cvs diff -u -r $OLD_RELEASE $FILE to see the changes.
yes, not so comfortable as .po, but Works Good Enough for Me(tm).
This is a good suggestion. The anaconda help is actually in DocBook XML format
now, not SGML. I'll see how much work it would be to convert the DocBook XML
files to po files.
Any news on this yet ? :)
Yes, now that we switched to XML for the anaconda help, we should be
able to use xml2pot and po2xml from the kdesdk-kbabel package to
convert back and forth between po and xml formats. We are trying it
on a smaller set of files to see if there are any major bugs.
Fantastic :) Then I'll wait for the .po file for the online help and not work
on the XML file :) Prehaps an announcement on i18n-list when its ready ?
*** Bug 74529 has been marked as a duplicate of this bug. ***
Now that the .po files appeared in CVS without content, should I wait for the
content to appear or convert it manually?
Paul is working on this. I am reassigning to him so he can close it when he is
finished and has sent out an email.
The pot file contains this message:
I guess the etraction script still needs some refinement? Should a seperate bug
be logged for this? Against which component?
I have just sent an email to firstname.lastname@example.org explaining the conversion to .po file format
so please see that email for further information.
Miloslav, if your language .po file was empty (or untranslated) then I was unable to
programatically convert the existing .xml file into .po file format and you will need to convert it
Christian, there is an empty '<title></title>' in the master .xml file and in this case the
xml2pot/po2xml toolchain is doing the right thing.