You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
we are facing a problem using Weblate to handle the translation of our Angular application.
I think we are missing something, but we're not able to figure out what.
The source strings are extracted in XLIFF (1.2) format using the standard Angular tools, but when the source messages are uploaded to weblate for translation, every variable used in the strings is stripped. We don't know if we need to write these variables in a certain way to make them work.
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger.
In case your question is already answered, making a donation is the right way to say thank you!
Using placeables I generate units like this: <trans-unit id="4666442495607243569" datatype="html"> <source>Data di riferimento <x id="refDate" equiv-text="item.reference_date"/></source> <context-group purpose="location"> <context context-type="sourcefile">src/app/sections/communications/components/side/edit/edit.config.ts</context> <context context-type="linenumber">42</context> </context-group> </trans-unit>
but looking at the string in weblate, it's only 'Data di riferimento ', so the variable is lost in the translation.
Also, i'm not able to use placeables using i18n tags but only with localize (but this is more a Angular problem, I think)
Describe the issue
Hello,
we are facing a problem using Weblate to handle the translation of our Angular application.
I think we are missing something, but we're not able to figure out what.
The source strings are extracted in XLIFF (1.2) format using the standard Angular tools, but when the source messages are uploaded to weblate for translation, every variable used in the strings is stripped. We don't know if we need to write these variables in a certain way to make them work.
Source string example:
<trans-unit id="2085829909901977917" datatype="html"> <source>rinnovabile <x id="PH" equiv-text="getYearFromDate(this.coupon.fixed_license_expire)"/></source> <context-group purpose="location"> <context context-type="sourcefile">src/app/_shared/components/coupon-modal-accountant/coupon-display/coupon-description/coupon-description.component.ts</context> <context context-type="linenumber">17</context> </context-group> </trans-unit>
Spanish version created from weblate
<trans-unit id="2085829909901977917" datatype="html" xml:space="preserve" approved="no"> <source>rinnovabile</source> <target state="translated">renovable</target> <context-group purpose="location"> <context context-type="sourcefile">src/app/_shared/components/coupon-modal-accountant/coupon-modal-accountant.component.ts</context> <context context-type="linenumber">112,111</context> </context-group> </trans-unit>
Of course the result is the correct string in the base language, and only "rinnovabile" in spanish.
Thank you for your support
Isaia
I already tried
Steps to reproduce the behavior
Expected behavior
No response
Screenshots
No response
Exception traceback
No response
How do you run Weblate?
Docker container
Weblate versions
No response
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: