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.

Sign up for GitHub

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

Jump to bottom

Translation: export XLIFF #37

Closed
svenseeberg opened this issue Oct 25, 2018 · 2 comments
Closed

Translation: export XLIFF #37

svenseeberg opened this issue Oct 25, 2018 · 2 comments
Assignees
@svenseeberg
Labels
🍺 hackathon Task that can be done in a hackathon 💡 feature New feature or request
Milestone
Base Functionality

Comments

@svenseeberg
Copy link
Member

svenseeberg commented Oct 25, 2018 •
edited

Enable exporting pages to XLIFF file.

Take translation state of pages into account. Unchanged pages or minor changes do not require translations.
@svenseeberg svenseeberg added the 💡 feature New feature or request label Oct 25, 2018
@svenseeberg svenseeberg modified the milestones: Feature Completion, Proof of Feasability, Base Functionality Oct 25, 2018
@svenseeberg svenseeberg self-assigned this Oct 30, 2018
@svenseeberg
Copy link
Member Author

svenseeberg commented Oct 30, 2018 •
edited

https://github.com/translate/translate

@svenseeberg svenseeberg modified the milestones: Base Functionality, Proof of Feasability Nov 18, 2018
@svenseeberg svenseeberg mentioned this issue Jan 14, 2019
Closed
8 tasks
@timobrembeck timobrembeck removed this from the Proof of Feasability milestone Mar 16, 2019
@svenseeberg svenseeberg added the 🍺 hackathon Task that can be done in a hackathon label Jun 4, 2019
@svenseeberg svenseeberg mentioned this issue Jun 4, 2019
Closed
@timobrembeck
Copy link
Member

It would be perfect, if the direction of the xliff files follow the language tree of the specific site, in the moment we have default language into all other language, but ideally the root node of the langauge tree is the source language of its children, and so on. so in the example of a language tree DE -> EN -> AR we would have xliff files for DE to EN and for EN to AR. This is because sometimes translations from english to arabic are cheaper than from german to arabic.

@timobrembeck timobrembeck added this to the Base Functionality milestone Feb 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@svenseeberg svenseeberg

Labels
🍺 hackathon Task that can be done in a hackathon 💡 feature New feature or request
Projects
None yet
Milestone
Base Functionality
Development

No branches or pull requests
2 participants
@svenseeberg @timobrembeck