On Thu, May 25, 2006 at 11:35:53AM +0200, Jakub Friedl wrote: > > > This way I think we would lose the one GIMP manual. We instead would > > have a dozen books that more and more will diverse or even die. > > Be sure I know many of the multi-language annoyances in our files, > > but anyway I think they are the only way to get ONE manual in > > different languages. This stays true as long as we work on a day by > > day basis on the (en) manual, not having a strong focus on en an > > timing. To change that would mean we'd need a schedule with fixed(!) > > deadlines. "Somebody" would write and finish (!) the en book and then > > all the "ohters" would take that bible and translate it into their > > respective language. - AFAIK is this not the style of work that fits > > our needs and pleasures. > > I do not agree. There is no need to keep all the manuals same (and it is not > the case now, anyway). What we need is to keep the same basic structure, > which is basically defined by help IDs. No need to have identical books. But it's _MUCH_ simpler!!! > I actually thought that there was already a consensus to split the files > and it wasnt done yet because of technical reasons. Definitely it is not the only reason... > Keeping all languages in same files is not the way to go. It will become > PITA once some languages start lagging behind - restructuring chapters, for > example, while there is noone available to do it for some of the languages, > would be a problem. There is no solution about the translators missing, whichever method you consider and there is no validation problems not solvable by a good old <!-- --> ;-) > Please, lets split them Please don't! Translating is one thing, restructuring the manual, another. What if some languages different from english take different directions? It _must_ be a _master_ language (english) to make all the other teams in the condition of being able to only translate and not to recreate another manual (still with the same IDs). I know that this is more an organizative problem, not really technical but I do not consider it a good idea if it means to produce different versions of the manual, one per language. The python scripts are already there and working (well) to do the job but, before the split we should consider seriously the organizative problem. It definitely should never happen to have some, say german or chinese content, not present in the english manual that the majority of all it is not able to uderstand and translate in the mother tongue. I'll agree at this "logical" decision only after someone assuring me about a "master" english version as a template for all the others an with the help and collaboration of all of us to make it "one and complete". bye -- Marco Ciampa +--------------------+ | Linux User #78271 | | FSFE fellow #364 | +--------------------+ _______________________________________________ Gimp-docs mailing list Gimp-docs@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
