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

IDML Translation & InDesign XML Tags #4468

Closed
draganstudios opened this issue Sep 8, 2020 · 4 comments
Closed

IDML Translation & InDesign XML Tags #4468

draganstudios opened this issue Sep 8, 2020 · 4 comments
Labels
question This is more a question for the support than an issue. wontfix Nobody will work on this.

Comments

@draganstudios
Copy link

Hi there,

We are doing some testing with Weblate 4.2.1 and using the Adobe InDesign Markup Language (IDML) files. We understand IDML support was recently added and it's still in beta.

While we are still learning and discovering Weblate, we were able to successfully import the IDML file, translate it, and download the translated version. Works great!

My question is about the InDesign XML tags that are visible in the textarea for translators. Is this the expected behavior?

<x id="22" xid="idPkg:Story[0]/{}Story[0]/{}ParagraphStyleRange[1]/{}CharacterStyleRange[4]/{}Br[0]"/><x id="23" xid="idPkg:Story[0]/{}Story[0]/{}ParagraphStyleRange[1]/{}CharacterStyleRange[4]/{}Br[1]"/></g>

(Ignore the encoding issues, we are looking into that, assuming that's on us to configure properly.)
idml-translation

Is there a way to manage these InDesign XML tags? We understand that some tags are needed, e.g. a tag to indicate bold or italic in the middle of a string, but we are concerned that the translator might accidentally delete a tag and break it.

idml-xml-error

Unfortunately I was not able to find much documentation about IDML support, or how to properly configure them, so this could be totally on our side. If you can point me to the right direction, that would be much appreciated.

If there is a way to improve it, we are open to help and contribute back to the project.

Thank you for your help,
D.

@draganstudios draganstudios added the question This is more a question for the support than an issue. label Sep 8, 2020
@github-actions
Copy link

github-actions bot commented Sep 8, 2020

This issue looks like a support question. We try to answer these reasonably fast, but in case you are looking for faster resolution, please consider purchasing support subscription and make Weblate stronger.

@nijel
Copy link
Member

nijel commented Sep 8, 2020

I think the code just takes the inner XML and presents it to the translator. However, I have no knowledge of IDML format either... The code for it is in https://github.com/translate/translate/blob/master/translate/storage/idml.py and https://github.com/translate/translate/blob/master/translate/storage/xml_extract/extract.py.

Weblate XML markup check should be able to catch this and report properly to the translator. You can configure it as enforcing check to mark such strings as needing review, but that still won't prevent Weblate from saving it. This might be addressed by #3745, but it's currently not on our roadmap.

@draganstudios
Copy link
Author

Hi @nijel ,

Thank you for your reply! We'll take a look at the code and see what we can do.

We are still looking into the encoding issue with IDML files. We have tried JSON files with no issues, the files are encoded perfectly, but with IDML we're still experiencing issues. We'll keep looking...

Thanks again and have a great day,
D.

@stale
Copy link

stale bot commented Sep 20, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix Nobody will work on this. label Sep 20, 2020
@stale stale bot closed this as completed Oct 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question This is more a question for the support than an issue. wontfix Nobody will work on this.
Projects
None yet
Development

No branches or pull requests

2 participants