Gimp-docs Digest, Vol 55, Issue 7
This discussion is connected to the gimp-docs-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.
This is a read-only list on gimpusers.com so this discussion thread is read-only, too.
| mailman.5.1229889608.8857.g... | 07 Oct 20:29 | |
| Gimp-docs Digest, Vol 55, Issue 7 | Vitaly Lomov | 22 Dec 10:35 |
| Gimp-docs Digest, Vol 55, Issue 7 | Ulf-D. Ehlert | 22 Dec 21:32 |
Gimp-docs Digest, Vol 55, Issue 7
First impressions: OMG!!! What do I do? :-) Now, I just checked a few .xml files and filters/filters_introduction.xml still has some non-en content. It doesn't affect me, just a bug report.
I use Cygwin and when I tried to 'make xml-ru' after configure I got this: can't find dblatex(1), dot(1),docbook2odf(1),xml2po(1) - PDF/PNG/ODF/SVG generation is disabled - fine by me. can't find msgfmt(1) - you will need it to build the help files - this is a show stopper because it doesn't let me continue. If somebody knows, what Cygwin package should I install to go pass that?
Other questions:
Why do I need to generate xml by itself? Is it not just a middle step
now for html/pdf... generation? Or is it that big xml file with only
my content?
Is there a way to get only en and my language without getting other
language po files?
Can wiki be updated with the new workflow? It still references 2.0. A
link to pot/po help on gnu site will help, but more on how it fits
with gimp-docs.
Can I just chug along and correct po files, commit as is (without make
xml-ru), and wait till validation is in place to fix errors
afterwards? Will it affect anybody else but my language?
Vitaly. ps season's greetings!
1. Merged xml2po and migrated content (Roman Joost) Hi folks,
I merged the xml2po branch and migrated the content. I hope I squeezed most translations out of the xml files thanks to Ulfs astonishing work. He worked most of the time on the migration and content splitting scripts (check the tools directory).
That means from now on new documentation is written in English *only*. Translations go in their designated po directories. With everything new and shiny, there are of course some downsides. There is currently no way of creating HTML files or validating. That's what need to be revamped, because the whole workflow of creating HTML (or other formats) has changed now.
I hope the work on this will be more transparent now and errors can be faster spotted. Please let us now what your first impressions are. Don't hesitate to ask questions.
Speaking of first impressions: You may find po files, with incorrect translations. That's where you come in to fix that. Every author can create new po files for it's language with the following makefile target:
make po-[language code]
example (creating po files for German): make po-de
The creation of po files are dependant on pot files, so they should be created automatically.
Similar to this way, you're also able to create (translated) XML files. Just type (make xml-de for example) to get the DocBook/XML files (for German) created. I think it's just a snap from being able to create HTML files.
Ulf will probably reply to my mail and talk about his future plans. There is a Makefile.GNU in the root of the module. It's his playground of an automake-free gimp-help-2 module. If you want to try out the Makefile, just rename it to 'Makefile' and *don't* run ./autogen.sh or configure afterwards.
Gimp-docs Digest, Vol 55, Issue 7
Vitaly Lomov (Montag, 22. Dezember 2008, 10:35):
First impressions: OMG!!!
Is "OMG!!!" good or bad?
Now, I just checked a few .xml files and filters/filters_introduction.xml still has some non-en content. It doesn't affect me, just a bug report.
The scripts used for migrating are not perfect, so there will be some files - xml files as well as po files, and hopefully not too many - containing flaws or even beeing totally useless.
If this happens, you can
a) correct the xml file manually, b) report this file here, sometimes it's possible to edit the (old) multi-lang xml file and re-apply the migrating script to this file only, producing correct output files.
IMHO you should consider a) if (and only if) a single small file is affected, definitely choose b) if it's a large file or if a group of files is affected by the same problem.
I use Cygwin and when I tried to 'make xml-ru' after configure I got this: can't find dblatex(1), dot(1),docbook2odf(1),xml2po(1) - PDF/PNG/ODF/SVG generation is disabled - fine by me. can't find msgfmt(1) - you will need it to build the help files - this is a show stopper because it doesn't let me continue. If somebody knows, what Cygwin package should I install to go pass that?
I don't know Cygwin, but you should look for packages named like
- gettext (maybe gettext-runtime & gettext-tools)
which contains the required tools msgfmt, msgcat, msginit, msgmerge, and msguniq;
- gnome-doc-utils
which contains the required tool xml2po (we used a patched version of xml2po, but the "docbook" module will alway be required).
Other packages are optional:
- dblatex (http://dblatex.sourceforge.net) for making pdf, - docbook2odf (http://open.comsultia.com/docbook2odf) for odf, - graphviz (http://www.graphviz.org/) contains "dot", which is just used to visualize make's dependency graph.
Other questions:
Why do I need to generate xml by itself? Is it not just a middle step now for html/pdf... generation? Or is it that big xml file with only my content?
If everything works (--> in the future) you can type
make html-ru
to create the html files.
Then xml, pot, and po files should be updated only if necessary.
And yes, localized xml files are intermediate files:
XML(en) --> POT --> PO(ru)
XML(en) + PO(ru) --> XML(ru)
XML(ru) --> HTML(ru)
XML(ru) --> PDF(ru) etc.
Is there a way to get only en and my language without getting other language po files?
Using the "autogen.sh" script,
./autogen.sh [--without-gimp] LINGUAS="en ru"
should still work, using make try
LINGUAS="en ru" make [-f Makefile.GNU] html
or
make [-f Makefile.GNU] html-en html-ru
Again: this is how it *should* work in the future, don't know what happens now...
Can wiki be updated with the new workflow? It still references 2.0. A link to pot/po help on gnu site will help, but more on how it fits with gimp-docs.
It looks like everybody is expecting someone else to fix the wiki pages... ;-)
Can I just chug along and correct po files, commit as is (without make xml-ru), and wait till validation is in place to fix errors afterwards?
Yes! :-)
Will it affect anybody else but my language?
No. Editing the (English) source xml files or the pot files will affect every language, editing a po file will only affect the respective language.
Ulf
