On 28 July 2010 14:48, Richard Quadling <rquadl...@gmail.com> wrote: > On 28 July 2010 12:31, Hannes Magnusson <hannes.magnus...@gmail.com> wrote: >> On Wed, Jul 28, 2010 at 13:24, Richard Quadling <rquadl...@gmail.com> wrote: >>> On 28 July 2010 12:08, Hannes Magnusson <hannes.magnus...@gmail.com> wrote: >>>> If you take care of bumping the revision for the translation (if it >>>> was already up2date) then thats fine. >>>> >>>> -Hannes >>>> >>> >>> So, for a file in /en ... >>> >>> <!-- $Revision: 297028 $ --> >>> >>> and in /es (randomly chosen), the same file has ... >>> >>> <!-- $Revision: 297973 $ --> >>> <!-- EN-Revision: 297028 Maintainer: jpberdejo Status: ready --> >>> >>> As the revisions match, I can make the change to both files. >>> >>> I assume I commit /en and get the revision and then do the same >>> changes to the /es and update EN-Revision. >> >> Correct >> >> >>> What about for translations NOT uptodate? Which I suspect will be a >> >> Not bumping revision, but still make the change. It will be up to the >> translator to figure out the untranslated changeset and sync it and >> then bump the revision. >> >> -Hannes >> > > But not worth doing until PhD is released with the functionality to > support <void/> as a return type. >
For what it is worth, there are 2950 files in the translations using <type>void</type> for the return type. Of that, only 41 are not upto date (i.e. EN-Revision numbers not matching). So, a total of 4045 files to change <type>void</type> to <void/>. The pedant in me wants to push commit ... Richard.
