On Wednesday 15 September 2004 10:54, Nikolai Prokoschenko wrote: > On Wed, Sep 15, 2004 at 01:36:08AM +0200, Frans Pop wrote: > > Yes, that works. I have split the file into bookinfo.xml and > > preface.xml. I will try to check all .xml files for the same kind of > > errors. > > Great, one problem solved :) There are quite a few more with the same problem: en/appendix/files.xml en/boot-installer/alpha.xml en/boot-installer/arm.xml en/boot-installer/i386.xml en/boot-installer/ia64.xml en/boot-installer/intro-cd.xml en/boot-installer/intro-hd.xml en/boot-installer/intro-net.xml en/boot-installer/m68k.xml en/boot-installer/mips.xml en/boot-installer/powerpc.xml en/boot-installer/s390.xml en/boot-installer/sparc.xml en/hardware/supported-peripherals.xml en/install-methods/download/arm.xml en/install-methods/floppy/m68k.xml en/partitioning/partition/ia64.xml en/preparing/bios-setup/i386.xml en/preparing/bios-setup/s390.xml en/preparing/bios-setup/sparc.xml en/preparing/nondeb-part/alpha.xml en/preparing/nondeb-part/m68k.xml en/preparing/nondeb-part/sparc.xml en/using-d-i/modules/ia64/elilo-installer.xml en/welcome/doc-organization.xml In most cases, there are several <sectX> for the same level after each other. I wouldn't really like to split the arch-dependent files, so I guess some other solution will have to be found... > However, we can help ;) I could get reasonable results using a pipe: > | sed 's/&POXML_LINEFEED;/\\n\"\n\"/g' | sed 's/&POXML_SPACE;/\ /g' > > So split2po might be usable after all. I've adapted my scripts (attached) to do this as well for now, and I guess you've seen my mail to Stephan Kulow. > > > > split2po: - preface.xml: I had added a <para> in the Dutch .xml > > > > explaning that the translation is Work in progress; > > > > > > Shouldn't this be a conditional <para> in every translation, which > > > would get disabled on some occasion? > > > > Can you suggest something? > > <para condition="translation">Note from the translator: as you might > notice....</para> > <para condition="work_in_progress">This is work in progress!</para> > > This would remove some flexibility for the translators, but I think the > manual should be consistent and thus there should be defined places for > such translators' commentaries. Hmmm. That would work for maybe one or two places as _all_ para's with the same condition be activated at the same time. (Or you would need a different condition for each one, but that is hard to maintain. Maybe best to just drop the extra para or maybe include it using \n for linefeeds (I'll have to test if that works first). > > So today you're making some changes, neat ;) BTW, I'm thinking about > coming to Oldenburg too, I'm not _that_ far away. Would be nice. Maybe we could finalize something there. Cheers, FJP Here are my current scripts (to be run from ./manual/). I'm currently writing everything to a .manual/po/ directory, but I think in the end we should create a po/ directory under each dir containing the untranslated .xml files.
Attachment:
create_po.sh
Description: application/shellscript
Attachment:
update_pot.sh
Description: application/shellscript