Import and link content from original and translated word file
We want to migrate our Word based documentation to Confluence in combination with Scroll Translations. The documentation is already translated in german and french, each translation is a seperate word file and has the same name and the same structure like the original file. Is there a way to import and link the translated files to the original one or do I have to hit "Translate" and paste every translated single chapter?
Greetings Philipp
-
Hi Philipp, thanks for your question.
Due to how Scroll Translations is implemented in Confluence, it's not possible to import Word files into specific language. You would have to hit Translate and paste the content manually into non-default language.
If you have any other questions, please let me know.
Cheers,
Roman. -
Hi Roman,
it would be a good idea to have this feature:
- importing a docx direct to a language or
- Copying / moving a no-scroll-translations-page to a language of a page. In this case you could import a docx file on the native Confluence way and then copy / move pages to an existing page as non-default languages.
In sum we had to copy / paste hundred of pages instead of using a better strategy.
Regards
Martin
-
Hi Martin.
I have discussed your proposal with developers and we thought that it would be better to provide a way to import a page tree (which could have been prepared by importing a docx file) into a translation.
A big problem to solve for that would be to map the imported pages to the ones in the managed space so that each translation is stored in the correct confluence page (and some attachment confilct handling).
I have created a feature request, which you can vote for and watch: https://k15t.jira.com/browse/VSN-4142. Feel free to add comments to the Jira issue to provide your use-case and importance to your workflow.
Cheers,
Roman. -
Hi Roman,
importing a page tree means you can select the language to which the import should be done? This would be my second proposal and would help a lot.
I agree that mapping is the big problem.
Solution 1
Perhaps you can show a list of the target pages and a list of the source pages which can be dragged and dropped near each of the target pages. Some kind of a graphical mapping.
Solution 2
Or you put a special macro into the source pages which users have to link to the target pages. Import could than be done in two steps: Analysing If the macro is present for all the pages in the source tree have the macro, the import could be finished.
Please sign in to leave a comment.
Comments
6 comments