[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Problem in generating kalgebra/*docbook
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2010-09-29 21:22:44
Message-ID: 201009292222.45016.aacid () kde ! org
[Download RAW message or body]

A Dimecres, 29 de setembre de 2010, Burkhard Lück va escriure:
> Am Mittwoch, 29. September 2010, um 18:03:40 schrieb Freek de Kruijf:
> > Op woensdag 29 september 2010 17:20:05 schreef Burkhard Lück:
> > > Am Mittwoch, 29. September 2010, um 00:06:19 schrieb Albert Astals Cid:
> > > > A Dimarts, 28 de setembre de 2010, Freek de Kruijf va escriure:
> > > > > Op dinsdag 28 september 2010 23:49:05 schreef Albert Astals Cid:
> > > > > > A Dimarts, 28 de setembre de 2010, Freek de Kruijf va escriure:
> > > > > > > Op dinsdag 28 september 2010 21:40:44 schreef Albert Astals
> > > > > > > Cid:
> > > > > > > 
> > > > > > > I did use "scripts/update_xml nl kdeedu kalgebra" and assumed
> > > > > > > that that would include using kalgebra_commands also, which
> > > > > > > apparently was not the case.
> > > > > > 
> > > > > > Nope, the third parameter is "single_cat" which means the single
> > > > > > catalog you want to rebuild, now the question is, does it make
> > > > > > sense for it to be a single catalog or is it better if it is a
> > > > > > "program"?
> > > > > 
> > > > > Apparently my gut feeling was that is represents a program, which
> > > > > is logical when you know that there will be a directory kalgebra
> > > > > with some docbooks.
> > > > > 
> > > > > The term single_catalog did not ring a bell, so is not obviously
> > > > > interpreted as generating a single docbook.
> > > > 
> > > > I'm ok changing it but i'd like some other people to chime in before
> > > > doing it. Burkhard? Yuri?
> > > 
> > > From my pov the sub division of a module documentation is the program
> > > documentation, no matter if it has only one or more docbooks.
> > > Afaik I have never generated a single catalog for programs with > one
> > > docbook.
> > > 
> > > With the current behavior generating a single catalog != appname the
> > > function check_xml() does not catch a buggy docbook.
> > 
> > It was not a buggy docbook. [...]
> 
> Yes I realised that already.
> 
> Seems you got me wrong. The script update_xml has a bug. If it is used with
> a "single_cat" != appname like kalgebra_commands and kalgebra_commands.po
> has xml errors, this is not detected by check_xml().
> So it can happen you generate a single docbook from a docmessage.po with
> xml errors, get no error message and commit that docbook. Building the
> language with this docbook will break.

Ok, made the third parameter be the program name, not the catalog name (only 
on trunk for the moment)

[prev in list] [next in list] [prev in thread] [next in thread]