OK duly noted. It is only about, 1-2 hour work, when I program the work, so it might be an X-mas gift :-)
The merge will by the way be a bit more intelligent than originally planned, it will also generate a "terminology" file, with words/sentences used more than once. That should be a great help to the teams, and also later as a QA of the translation (control that the terminology is used consistent). Jan I. On 17 November 2012 12:19, Andrea Pescetti <[email protected]> wrote: > jan iversen wrote: > >> - How about we make the 30+ files as normal, but also a couple of extra >> files called "to_be_translated", they just contain the text in need of >> update, that would be very easy for the merge program to do ?? >> > > Personally, I wouldn't benefit from it since the biggest improvement would > be the one already planned (consolidate the current 276 files into ~40 > files) and in general I tend to look around in the file to keep the same > style (not only the glossary, I mean the overall feeling of the > translation). > > But maybe some teams would instead be happy of having it, and it would > surely be helpful for point releases where only a couple of strings have > changed. So it's not essential, but it could be "nice to have". > > Regards, > Andrea. >
