Translations best practices with DITA
Oxygen general issues.
-
- Posts: 68
- Joined: Tue Jun 09, 2015 6:26 pm
- Location: Canada
Translations best practices with DITA
Post by BogdanM777 »
Hi guys,
I am a little bit obnoxious, I am sorry, however I want to get up to speed fast with your tool, so that I can use it properly.
I would have another question related to translation.
I am also doing translation for my company, and I was wondering if there are any best practices in that regard.
I checked the Internet, and I found only some mentions to that, however related to best practices for when you give the project to a translation company, that will process the project with some software.
Well, in my situation, I am the software, and I do the translations in 4 languages so to say "manually".
I was talking to my colleagues in the company, and it was an idea to have one project that contains 4 different translations (English, French, German & eventually Japanese), however till now, working with Adobe RoboHelp, I had 4 different projects, each in its own language.
Would it be wise to use, let's say the element <ph product="language"> in order to have different languages. In my opinion it would be very hard to maintain and to follow having such a stuffy project, no?
From your experience did you find any other solution to this issue of mine?
Or can you recommend me a book to study on that subject?
Thank you very much.
I am a little bit obnoxious, I am sorry, however I want to get up to speed fast with your tool, so that I can use it properly.
I would have another question related to translation.
I am also doing translation for my company, and I was wondering if there are any best practices in that regard.
I checked the Internet, and I found only some mentions to that, however related to best practices for when you give the project to a translation company, that will process the project with some software.
Well, in my situation, I am the software, and I do the translations in 4 languages so to say "manually".
I was talking to my colleagues in the company, and it was an idea to have one project that contains 4 different translations (English, French, German & eventually Japanese), however till now, working with Adobe RoboHelp, I had 4 different projects, each in its own language.
Would it be wise to use, let's say the element <ph product="language"> in order to have different languages. In my opinion it would be very hard to maintain and to follow having such a stuffy project, no?
From your experience did you find any other solution to this issue of mine?
Or can you recommend me a book to study on that subject?
Thank you very much.
-
- Posts: 68
- Joined: Tue Jun 09, 2015 6:26 pm
- Location: Canada
Re: Translations best practices with DITA
Post by BogdanM777 »
I forgot to add the notification by e-mail.
Sorry.
Sorry.
-
- Posts: 9436
- Joined: Fri Jul 09, 2004 5:18 pm
Re: Translations best practices with DITA
Hi Bogdan,
We are not very familiar with how translations should be handled with a DITA project.
I would also consider that you need a separate DITA Map project for each supported translation and to have some kind of mechanism to keep in sync the topics which were translated and the topics which were not.
Our forum does not automatically notify users for each post so ideally you should write about this on the DITA Users List:
https://groups.yahoo.com/neo/groups/dita-users/info
or on the LinkedIn DITA Awareness Group if you want to receive feedback from the DITA community.
Indeed most CMSs have special support for aiding translations but we do not use a CMS internally so I do not know how exactly they accomplish this.
Regards,
Radu
We are not very familiar with how translations should be handled with a DITA project.
I would also consider that you need a separate DITA Map project for each supported translation and to have some kind of mechanism to keep in sync the topics which were translated and the topics which were not.
Our forum does not automatically notify users for each post so ideally you should write about this on the DITA Users List:
https://groups.yahoo.com/neo/groups/dita-users/info
or on the LinkedIn DITA Awareness Group if you want to receive feedback from the DITA community.
Indeed most CMSs have special support for aiding translations but we do not use a CMS internally so I do not know how exactly they accomplish this.
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
-
- Posts: 68
- Joined: Tue Jun 09, 2015 6:26 pm
- Location: Canada
Re: Translations best practices with DITA
Post by BogdanM777 »
Thank you so much for your feedback Radu.
I saw some plus points about DITA that it should handle translations or translation needs very nicely, and I was wondering if there was anything already in place that you would be aware of.
I will check the links you sent me.
Thank you.
I saw some plus points about DITA that it should handle translations or translation needs very nicely, and I was wondering if there was anything already in place that you would be aware of.
I will check the links you sent me.
Thank you.
-
- Posts: 43
- Joined: Tue Jul 26, 2016 6:31 pm
Re: Translations best practices with DITA
There are some docs at the OASIS website, e.g.BogdanM777 wrote:Hi guys,
I am also doing translation for my company, and I was wondering if there are any best practices in that regard.
https://www.oasis-open.org/committees/d ... ranslation
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ 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