httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Malo ...@perlig.de>
Subject Re: svn commit: r111593 - /httpd/httpd/trunk/docs/manual/new_features_2_2.xml.ko
Date Sat, 11 Dec 2004 09:41:59 GMT
* Paul Querna wrote:

> > -<!-- English Revision: 105989 (outdated: 111589) -->
> > +<!-- English Revision: 105989 (outdated: 111592) -->
>
> As it currently stands, every time you invalidate a translation, you
> should do two commits.  First commit creates the new English version,
> second commit updates all the outdated files...
>
> Is there a better way to do this?

No [1]. To keep it clean, I'm following the strategy to commit the English 
xml first, then doing build all and then commit the whole transformation at 
once. That even matches the "atomic commit" policy better :)

But you may or may not modify the other languages. They get updated at 
least, when the particular translator builds and commits a change to his 
language. I'm just doing the `build all`, if I see something missing or 
from time to time *to* see if something's missing (whatever comes 
first ;-)). Mostly in conclusion with `build validate-xml`.

[1] The point is, that use the rev numbers, which are changed *after* the 
commit (of course) and I don't know a better automatically changed token we 
could rely on (they give us also a hint about what to diff to update the 
translation)

nd
-- 
my @japh = (sub{q~Just~},sub{q~Another~},sub{q~Perl~},sub{q~Hacker~});
my $japh = q[sub japh { }]; print join       #########################
 [ $japh =~ /{(.)}/] -> [0] => map $_ -> ()  #            André Malo #
=> @japh;                                    # http://pub.perlig.de/ #

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Mime
View raw message