Bonjour,
j’ai donc demandé à Transifex (le problème persistant). Leur réponse est ci-après.
De ce que je comprends, c’est un problème de clé qui est modifiée et qui entraine l’effacement de toutes les chaines.
BC
Hello Bernard,
Thank you for reaching out to us and submitting your request.
Regarding your case, I checked this out and I assume that in the new updated version of your source file, the keys have been modified. Please note that in this case, when a key is changed, the string is considered as a completely new in Transifex.
Please let me clarify certain points regarding the way old and new source files/strings are handled by Transifex:
#1.
Modified strings (values) are considered as new ones.
This means that after source file is being updated, the previous translations won’t be available in the translation area anymore BUT they can be found in the translation history of each string since we keep track of previously submitted translations.
after updating the source file, the translation string that was applied will be removed from the translation area and the string should be translated again.
#2.
Modified strings (keys) are considered as new ones as well.
This means that after source file is being updated, the previous translations won’t be available in the translation area anymore AND also the translation history of the string won’t be available as well.
However, in this case, keep in mind that old translations are kept in the Translation Memory of your project. So, if you have the feature « Fill up resources from TM » enabled, TM will detect the old strings and will automatically kick in all the previously submitted translations if the match is 100%. In case the match is not 100% but other matches are found then they come in the editor as « Suggestions » .
If both keys and values remain the same, the translation should not be removed no matter if changes are applied to the rest of the file.
I hope that the above helps.
Please let me know if you have any further questions or concerns.
Kind Regards,