Issue updating source strings in XLIFF with English (Developer) source #16764
Unanswered
ddeveloperuch
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Weblate Team,
I’d like to clarify the correct procedure when using
English (Developer)as the source language, since this setup seems to behave differently than expected.Here are the current project settings:
XLIFF 1.2 translation file_Translations/*.xliffEnglish (Developer)As a result, the component includes the following languages:
At first glance this configuration looks logical, and everything appears fine. The confusion arises in a typical use case where:
Current pseudo state of
en.xliff:String_A.outdated- deletedString_B.outdated- deletedString_C.activeString_D.outdated- deletedString_E.newString_F.newExpected behavior
When uploading the new
en.xliff, I would expect Weblate to:English (Developer)andEnglishsource sets so that they contain only:String_C.activeString_E.newString_F.newString_A.outdated,String_B.outdated,String_D.outdated)String_E.new,String_F.new)Actual behavior and findings
From what I can see, there are currently two possible approaches:
wlc: unfortunately, wlc upload does not support XLIFF at all (Error: The file format does not support updating source strings #16691)Gitrepository: after pushing the newen.xlifffile and syncing, only theEnglishlanguage was updated. TheEnglish (Developer)source set remained unchanged, and the other target languages were not updated either.Could you please clarify the correct workflow to update the source strings in this setup?
English (Developer)be updated when using XLIFF as the file format?Beta Was this translation helpful? Give feedback.
All reactions