Andrea Turrini
Now, according to the svn log, I completely reviewed yast strings with commitments between r65427 and r66900; however in the meanwhile there were three merges (r65613, r65990, r66461) that may have introduced other wrong strings in already reviewed files.
If that's the case, the wrong string could originate from the memory files. If wanted, we can reset the memory files, this means I can easily rebuild them from good .po files.
For the three merges, I think it should be enough to dump a diff between merge revision and the previous one and then look for non-fuzzy changed translations, so after this I am sure that files at revision 66900 are OK (except for my possible errors).
Now, what is the best way to try to find other wrong sentences, if any? I think that dumping a diff between 66900 and HEAD will introduce a lot of false positives but it is the safest approach (less safer than reviewing completely yast files, but this requires a lot of time).
With the gettext tools (msgcomm) it is possible to filter out identical messages. Messages that only differ in line-numbers or line-breaks could also count as identical. Then normalize the remaining messages (msgcat) and finally diff them. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org