New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When synchronizing the translation units, a translation is lost if it has at the beginning an interpolation #67
Comments
Hi @olalinv, However, that is not the bug you reported, so could you provide me with a sample project which reproduces this? (Maybe it is caused by specific settings.) |
Back at it again. Found another example of reproducing this, which is when copyFromSource is used. The issue is that currently nodes nested in the target are not supported. I will look into this though. |
Hi @ rvanbekkum, This is my settings file:
I will try to prepare a sample project as soon as i can for further testing, if you need help please let me know. Thanks |
A change for this will be shipped in the next release of the extension! |
Shipped in v1.0.0. |
I've tried it and it works perfectly. Thanks a lot. |
I´ve got this translation unit in messages.xlf:
And this is the tranlation in messages.eu-ES.xlf:
By synchronizing the translation units again the translation becomes:
If I put a space (or any word) just before the interpolation then this doesn't happen:
<target state="translated"> <x id="INTERPOLATION" equiv-text="{{createResponseOK.code}}"/> eskaera behar bezala sortu da</target>
The text was updated successfully, but these errors were encountered: