Re: cvs: phpdoc /hk bookinfo.xml preface.xml zh_hk.xml /hk/chapters config.xml install.xml intro.xml security.xml /hk/features
connection-handling.xml cookies.xml error-handling.xml file-upload.xml http-auth.xml images.xml persistent-connection

From: Date: Thu, 15 Nov 2001 09:44:25 +0000
Subject: Re: cvs: phpdoc /hk bookinfo.xml preface.xml zh_hk.xml /hk/chapters config.xml install.xml intro.xml security.xml /hk/features
connection-handling.xml cookies.xml error-handling.xml file-upload.xml http-auth.xml images.xml persistent-connection
References: 1 2  Groups: php.doc 
Request: Send a blank email to phpdoc+get-969338872@lists.php.net to get a copy of this message
Egon Schmid wrote:
Can you please explain and discuss
haven't i? (i don't want to quote all the previous mails regargind xml headers and encoing attributes here)
so huge
each language directory has a maximum of 150 xml file, one line added for every file that didn't have a proper xml header yet is a maximum of 150 lines per translation some where already fully compliant (en, cs, hu), others moslty, some not at all ...
and massive changes
i just applied a change to translations that has been in the english files for some time now so getting translations up to date with the original files is considered a massive change these days?
with the authors and editors first,
the change doesn't affect authors at all (unless they have done the exact same change without commiting yet) as the first line of a file does not change during translation no need to issue a 'megapatch-warning' as no CVS conflicts should arise from the path
before you do such useless commits?
do you realy claim XML compliance and proper encoding informations in every XML file being useless? Egon: please stop trolling and let us have a talk on this issue (and several others) on saturday in person i don't want to spend any more time explaining the bleeding obvious to you over and over again, this just eats up to much time everyone else: do you feel i have done something wrong with the XML header patches during the last week? or with the experimental docbook 4 branch? i realy don't know how to handle this situation

« previous php.doc (#969338872) next »