Since Nickolay started to come up with another way of creating documentation, I'm still interested in discussing it. Seems at least for most of the authors an easier way to write documentation. We already came to the conclusion, that including po file processing assembles both worlds: writing new documentation in XML docbook and providing translation by using *.po files if the authors really want it. But, we need a reference which should probably be the English part of the manual. Since this reference isn't finished in writing, I want to ask Sally, Julien and other authors how much it would be, to finish writing the missing pieces of the english manual. Are only 5 sections missing, or maybe 20? Can someone figure this out? I think it would be wise to have everyone participate in finishing the English part, even if he's not a native speaker. The native speakers are probably be able to proof read those parts and fix the remaining errors. Are there still any concerns or votes against an integration of the "*.po strategy"? Greetings, -- Roman Joost www: http://www.romanofski.de email: romanofski@xxxxxxxx
Attachment:
pgplHCU8HhiN2.pgp
Description: PGP signature
_______________________________________________ Gimp-docs mailing list Gimp-docs@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
