On 20/04/12 20:07, Carlos E. R. wrote:
such errors.Just as an example, in ldap-server there was a string referring to the system repair module instead of the partitioner module. I have no idea where such string comes from (I want to remark that it was changed without marking it as fuzzy).
Finding those can be time consuming, and very disappointing. Argh, now I have to read them in full. :-(
FYI, the file is storage, not ldap-server. Anyway, the wrong sentence is not present in the file at revision 71323 and it appears at the following commitment at revision 72902 (I am talking only about the Italian directory). After this commitment other 4 merges have occurred, intermixed with my translation commitments. 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. 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). Best, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org