On 28 July 2010 00:00, Richard Quadling <rquadl...@gmail.com> wrote: > On 27 July 2010 20:35, Hannes Magnusson <hannes.magnus...@gmail.com> wrote: >> On Tue, Jul 13, 2010 at 20:17, Richard Quadling <rquadl...@gmail.com> wrote: >>> On 13 July 2010 19:00, Hannes Magnusson <hannes.magnus...@gmail.com> wrote: >>>> No. mirrors dont use PhD and I dont actually remember if the rsync box >>>> does 'pear upgrade' before generating the builds.. I dont believe so >>>> though. >>>> >>> So, new features and corresponding XML is an issue then? >> >> Yes. You cannot use features in the markup that haven't made it into >> PhD release yet as the result of that is undefined obviously. >> >> >>> Actually <type>void</type> is fine. <type> is part of the sequence for >>> methodsynopsis, but I like <void />. >> >> I don't have a preference there, other then keeping thing consistent. >> <type>void</type> is probably used literally several thousands of >> times, and changing that "just because we can" is useless and simply >> requires more work from all the translators.. >> >> -Hannes >> > > Thanks for getting back. >
Consistency ... the joy of open source ... Just doing a straight count of 11,014 xml files in /en. <type>void</type> 1206 matches in 1104 files. <void/> 1184 matches in 1161 files. <void /> 911 matches in 893 files - all of these are corrected when viewed in .manual.xml The I searched for those that precede the <methodname> tag (allowing for whitespace also). <type>void</type><methodname 1197 matches in 1095 files. <void/><methodname 150 matches in 150 files - all of these are in en\internals2\ze1. <void /><methodname 7 matches in 2 files - all of these are corrected when viewed in .manual.xml So, no need to change the 1197 because we can. Though I could easily apply the change to all the translations in 1 go. Regards, Richard.
