Re: docs to svn business

Hi > When a translator updates a translation (a file), they write which CVS > Revision in EN it's synced to. So, later when the EN version is > updated we then know that the translated is outdated. And all of our > translation tools rely on the incremental nature of CVS revision > numbers. Quick and simple way is to require/use svn:keyword Id. It is easily as unique as the CVS revision number. Drawback is it ties the sync to a VCS specific method which would need rethinking next time the repository is moved. > As for PO files, I do like the fuzzy feature and ease for translators > to find and update fuzzy strings. To me, fuzzy means "in need of a > review" > > I'm unsure what you mean by a fuzzy markup tag (in translation XML > files) or how that'd work but am intrigued by the idea. > > Regards, > Philip > -- Niel Archer niel.archer (at) blueyonder.co.uk