On Tuesday 10 June 2008, julien wrote: > Hi, > > IMO, getting grouped para in .pot would be too much hard a work. > .pot are created with the xml2po command which extracts 'en' > strings into .pot msgid strings. > To get grouped para we should have to modify hundreds of xml files, > each of them particular, in every language! > Not exactly modifying by hand. The idea of XML files is that they are eaily processed with scripts. We'd jsut need to either modify po2edit or create another script for doing that. (And yes, I could do that) > Reading fluency is not a problem since we can have the 'en' html > file on the same screen. The problem is nto about reading - although I am a bit concerned about this since most PO editing tools (Kbabel, bluefish) do show the _current string_ out of the flow of the adjacent strings (although they can be seen nearby - it is not the same as looking at the text. This is a problem of one extra featire in .po editor programs, so it does not concern us at this point. The ability of re-writing the paragraphs and transfer the information around so that translations are not paragraph by paragraph, but block by block, is deeper than that, IMHO, and a an important thing to preserve the text enjoyable accross different languages. > > A real problem is how to built all .pot files (a .pot file per xml > file) automatically. Hmm? I thought this was the work of po2edit - what is hard about feeding the xml files to a pot writting script? Sorry, but this sounds much more like a technical thing that can be worked around in a couple of hours (if not minutes) than a "real" problem. Being able to do out of order paragraph translation is IMHO much more an issue than being able to use a "for" statement in bash or any script language. > Another more difficult problem is how to automatically transfer > translated strings from xml to msgstr strings in .pot files. > Roman is working on that... Roman - are you? How are you doing? The experience I had in parsing these files 2 years ago might come handy here. js -><- > > Julien > > _______________________________________________ > Gimp-docs mailing list > Gimp-docs@xxxxxxxxxxxxxxxxxxxxxx > https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs _______________________________________________ Gimp-docs mailing list Gimp-docs@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
