Closed apourche closed 3 years ago
Describe the bug
If several composats have the same translation key (with the same failed check so):
To Reproduce the bug
Create two components (testsmall1 and testsmall2 ) with the same content :
testsmall1
testsmall2
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2"> <file original="file1" source-language="" datatype="plaintext" target-language="en-US"> <body> <trans-unit id="unit1"> <source xml:space="preserve">Test...</source> <target xml:space="preserve">Test</target> </trans-unit> </body> </file> </xliff>
In testsmall1, correct the translation (addition of '...') to respond to the 'Mismatched full stop' alert :
After this action, the alert disappears in testsmall1 : OK
[ko] In testsmall2, the same character string is corrected auto translated, but the alert 'Mismatched full stop' remains signaled :
Expected behavior
Auto-update (make disappear) the checks alerts when it's necessary.
Server configuration and status
Thank you for your answer
Thank you for your report, the issue you have reported has just been fixed.
thanks @nijel !
Describe the bug
If several composats have the same translation key (with the same failed check so):
To Reproduce the bug
Create two components (
testsmall1
andtestsmall2
) with the same content :In
testsmall1
, correct the translation (addition of '...') to respond to the 'Mismatched full stop' alert :After this action, the alert disappears in
testsmall1
: OK[ko] In
testsmall2
, the same character string is corrected auto translated, but the alert 'Mismatched full stop' remains signaled :Expected behavior
Auto-update (make disappear) the checks alerts when it's necessary.
Server configuration and status
Thank you for your answer