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. > > > What about for translations NOT uptodate? Which I suspect will be a > lot as this is about 10% of the files and I would guess the > translations are always running behind. > > Richard. >
Yeah, that's the problem with making mass updates in en. When I converted the remaining files to UTF-8 a few months back, I wrote a tremendously ugly script to handle that. I've attached it to this email, but I'm not sure it's the final revision. -- Daniel Egeberg
<<attachment: phpdoc_utf.php>>
