В Вск, 21/12/2008 в 19:08 +0100, 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. > > That's currently all I have to say :) Looks great, congratulations. Is there any particular reason it uses so small po for a single file? Having a single catalog would be more correct: 1. It's easier for translator to work with it. 2. Many translations are joined thus providing a basis for translation consistency. 3. It's easier to get statistics :) Currently it looks a bit complicated.
Attachment:
signature.asc
Description: =?koi8-r?Q?=FC=D4=C1?= =?koi8-r?Q?_=DE=C1=D3=D4=D8?= =?koi8-r?Q?_=D3=CF=CF=C2=DD=C5=CE=C9=D1?= =?koi8-r?Q?_=D0=CF=C4=D0=C9=D3=C1=CE=C1?= =?koi8-r?Q?_=C3=C9=C6=D2=CF=D7=CF=CA?= =?koi8-r?Q?_=D0=CF=C4=D0=C9=D3=D8=C0?=
_______________________________________________ Gimp-docs mailing list Gimp-docs@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs