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 mailing list Gimp-docs@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
