Skip to content
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

Support configuring target state for autotranslation #156

Open
abierbaum opened this issue Jan 13, 2020 · 1 comment
Open

Support configuring target state for autotranslation #156

abierbaum opened this issue Jan 13, 2020 · 1 comment

Comments

@abierbaum
Copy link

We are using poedit as part of our workflow for reviewing translation files. We also use the awesome xliffmerge support for auto-translation.

So our workflow looks like:

  • Extract strings from angular application (using angular cli)
  • Run xliffmerge to update language files and auto-translate new strings
  • Send xliff files to translator to review, update, approve translations
  • Merge confirmed translations back into translation files

We are running into a problem with the last two steps because xliff merge generates autotranslations with the target element state set to translated. This conflicts with the workflow supported by poedit. All I can find that poedit supports is toggling "Needs work" which changes the state between "needs-adaptation" (needs-work) and "translated" (not needs-work).

If anyone knows how to make poedit instead support a workflow of "translated" coming from xliffmerge as still needing review and then allow setting"final", that would be great.

Otherwise, what I am suggesting/requesting is the ability to configure the name of the state that xliffmerge initially puts autotranslated targets into. For example in my workflow above, if I could configure xliffmerge to set the autotranslated state to "needs-adaptation" I think this would work better with poedit.

Is that an easy change or is there another way to handle this I am missing?

@martinroob
Copy link
Owner

Sorry for the late response. Will check soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants