Multiple projects vs. single-sourcing

This forum is for Single-Sourcing your Flare content to multiple outputs.
Post Reply
Ineffable
Sr. Propeller Head
Posts: 152
Joined: Mon Jan 15, 2007 3:08 pm
Location: Bay Area, CA

Multiple projects vs. single-sourcing

Post by Ineffable »

My current project is in English. I have now been tasked with creating a French version.

Should I create a new French project (Save As... the English version) or try to single-source the English one by using conditionals/targets/whatever other means?

Would Lingo be a part of either workflow?

Please share your real world experiences.

Thanks!
RamonS
Senior Propellus Maximus
Posts: 4293
Joined: Thu Feb 02, 2006 9:29 am
Location: The Electric City

Re: Multiple projects vs. single-sourcing

Post by RamonS »

As usual...it depends! First thing to consider is size of project and how many other languages you may need to support in the future. Other things to think about are any potential for sharing content (images, screen shots) and how the contents get translated.
If you work on a large project it may become difficult to condition the two parts appropriately, especially if you already have conditions in place. If there will be more languages in the future you will have to add the condition sets in each time and my guess is that after three languages and three conditions each things start to get really messy.
If you want to use Lingo you will end up with a separate project. Lingo for sure makes it easier to keep things updated and it allows making use of translation memory. It may also be a tool that a translator is more open to than Flare. As mentioned above, that is something to consider in regards to how the content gets translated.
So far I did projects that were German and English, but I was the one translating, so I didn't start screaming when using Flare or Lingo.
Post Reply