A good workflow for multi language documents?
|
- This topic has 3 replies, 3 voices, and was last updated 6 years, 12 months ago by
.
-
Posts
-
-
Hi guys, I’m new here so this is basically my „HELLO“ to all of you.
I’m currently working on a rather complex folder for an international client – so currently I have a versions in German, English, Italian, Spanish and Chinese … probably more to come.
My solution for multi language documents is to use layers for each language and some for the design elements. That way I can do simple changes like swapping a photo pretty efficiently across all versions and it’s very easy to keep track with versioning. This has been working fine for rather simple projects, but this current folder pushes the limits of my technique pretty hard.
It is a rather complex document with extra layers for special finishing in print (punching and foil stamping), of course done differently for each language and the screen version needs it’s own layers, too. Toggling the visibility of the right layers for the various exports has become more of
nuisance than a help.When it comes to major design changes (the folder in question is updated once a year), i usually start from scratch anyway because you can’t design with 5 text boxes stacked upon each other …
I am open to ideas :)
-
A workflow I commonly come across is:
1. finalise (and I do mean finalise) the design elements and text of the original language version.
2. send IDML for translation into other languages (by translators using computer aided translation – CAT – tools).
3. adjust each version as needed (mostly for overset text) once the translations are done.No layers for different languages, but separate files instead.
If there are later changes, go round again, but this time the CAT tool means you only translate new/changed text.Chris.
-
Thanks for your input, Chris. Sadly, the whole point of my workflow is, that I can’t finalize the design before the translation. I’d love to, because then I could simply work with five separate documents, but the reality is that the client will make small changes after the design phase and I need to be able to make these effortless across all Versions. That’s the whole point. But thanks for taking the time and what you described is a valid option if you don’t have to deal with a client.
-
Years ago, I made a training program in different languages, each language in a separate document. After a year, I get several corrections: new courses, delete courses, changes in prices. It was a mess, to change everything in those independent documents.
Now I have everything in one document on different layers as you described. German is the master language. If this layer is finnished, I make the changes in other languages. Because everything is in one document, I must insert or delete pages only once.
Every language has it’s own set of para and char styles. Textframes are sometimes named. Because of this naming-thing, I can control the flow of text and also the visibility of layers with scripts. E.g. if you have multiple layers, you can skip the Export-Dialog and do everything with a script > make 3 layers visible, export to PDF, set the visibilty after the export to false …
To your layout question: Assume you built your document from scratch. It should be possible to work either with named frames or duplicate the finnished layer (everything with scripting), if you do not want to layout with stacking frames.
So with a bit of brainstorming before the project, many things can be improved.
Kai
-
- You must be logged in to reply to this topic.
 |