Automatic extraction of language layers in an SVG
Are you missing a feature? Request its implementation here.
-
Sergio_7
- Posts: 18
- Joined: Fri Sep 15, 2023 9:56 am
Automatic extraction of language layers in an SVG
Dear team,
I would like to request a feature on the topic "Automatic extraction of language layers in an SVG".
Exemplary initial situation:
- I have a single SVG graphic with several language layers (e.g. de, en, fr, es, zh).
- The language layers have their own translation of the content and are marked accordingly with "xml:lang" as an attribute or ID (e.g. <g xml:lang="en-us" .../> or id="en-us").
Desired result:
- During the transformation to html/pdf/md etc, the xml:lang attribute in the SVG is read and compared with the dita source instance.
- The output then only shows the language level that was assigned in the topic under <topic xml:lang="en-us">. Other language layers are hidden.
Benefit of the feature:
This procedure reduces the number of individual graphics and the maintenance effort for image-intensive documentation. It is particularly suitable for software-heavy documentation that has to explain each individual element to the user in several languages.
Thank you for your feedback on this feature request.
If this feature already exists, please refer to the corresponding link.
Thank you very much!
Best regards
Sergio_7
I would like to request a feature on the topic "Automatic extraction of language layers in an SVG".
Exemplary initial situation:
- I have a single SVG graphic with several language layers (e.g. de, en, fr, es, zh).
- The language layers have their own translation of the content and are marked accordingly with "xml:lang" as an attribute or ID (e.g. <g xml:lang="en-us" .../> or id="en-us").
Desired result:
- During the transformation to html/pdf/md etc, the xml:lang attribute in the SVG is read and compared with the dita source instance.
- The output then only shows the language level that was assigned in the topic under <topic xml:lang="en-us">. Other language layers are hidden.
Benefit of the feature:
This procedure reduces the number of individual graphics and the maintenance effort for image-intensive documentation. It is particularly suitable for software-heavy documentation that has to explain each individual element to the user in several languages.
Thank you for your feedback on this feature request.
If this feature already exists, please refer to the corresponding link.
Thank you very much!
Best regards
Sergio_7
-
julien_lacour
- Posts: 806
- Joined: Wed Oct 16, 2019 3:47 pm
Re: Automatic extraction of language layers in an SVG
Post by julien_lacour »
Hello Sergio_7,
I created the feature request on our tracking system. We will analyze it.
I will notify this thread with every step of the analysis and if something become available.
Thank you for your request.
Regards,
Julien
I created the feature request on our tracking system. We will analyze it.
I will notify this thread with every step of the analysis and if something become available.
Thank you for your request.
Regards,
Julien
-
LASSE_MLE
- Posts: 48
- Joined: Mon Dec 05, 2022 3:24 pm
Re: Automatic extraction of language layers in an SVG
Hello!
I've just started the translation process of our documentation package and I have exactly the same idea
Has this item evolved since 2 years?
Thanks for your help!
Mathieu
I've just started the translation process of our documentation package and I have exactly the same idea
Has this item evolved since 2 years?
Thanks for your help!
Mathieu
-
julien_lacour
- Posts: 806
- Joined: Wed Oct 16, 2019 3:47 pm
Re: Automatic extraction of language layers in an SVG
Post by julien_lacour »
Hello,
The issue is still under analysis, I added your vote to it.
Could you indicate from which output do you want this feature?
Regards,
Julien
The issue is still under analysis, I added your vote to it.
Could you indicate from which output do you want this feature?
Regards,
Julien
-
LASSE_MLE
- Posts: 48
- Joined: Mon Dec 05, 2022 3:24 pm
Re: Automatic extraction of language layers in an SVG
Hello Julien,
Thank you for your feedback. I'm currently working on Oxygen v.26.1, build 2024091606 (planning to upgrade to v.28 soon) and we generate both WebHelp and PDF outputs.
BR
Mathieu
Thank you for your feedback. I'm currently working on Oxygen v.26.1, build 2024091606 (planning to upgrade to v.28 soon) and we generate both WebHelp and PDF outputs.
BR
Mathieu
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service