Hi,
What is the best practice for multi-language Webhelp output? I need to have English and German Webhelp output. My client has recommended that I have a single project and 2 targets (one in English and one in German) within it. Where should I keep the translated German files in the project? (Translation will be done in Germany - I just need to provide the Webhelp output and they will replace the English content files with the German ones.)
Any pointers on how to go about this will be much appreciated.
Thanks
Best practice for multi-language output
-
RamonS
- Senior Propellus Maximus
- Posts: 4293
- Joined: Thu Feb 02, 2006 9:29 am
- Location: The Electric City
Re: Best practice for multi-language output
You can keep it in the same project and use conditions on everything. With just two languages this will be manageable. I'd create two folders within the Content folder, one for English and one for Deutsch. That way it will be clearer to determine what is what just by the folder structure.
Is there a lot of common content such as images that are subject to change? If not, then there is really no benefit in keeping it all in one project, it is more a disadvantage as you need to make sure that the conditions are all properly set on everything, otherwise you get stuff mixed up. I'd create a second project for Deutsch and copy any common content once. I think it is less of a hassle that way.
Is there a lot of common content such as images that are subject to change? If not, then there is really no benefit in keeping it all in one project, it is more a disadvantage as you need to make sure that the conditions are all properly set on everything, otherwise you get stuff mixed up. I'd create a second project for Deutsch and copy any common content once. I think it is less of a hassle that way.
New Book: Creating user-friendly Online Help
Paperback http://www.amazon.com/dp/1449952038/ or https://www.createspace.com/3416509
eBook http://www.amazon.com/dp/B005XB9E3U

Paperback http://www.amazon.com/dp/1449952038/ or https://www.createspace.com/3416509
eBook http://www.amazon.com/dp/B005XB9E3U
-
ChoccieMuffin
- Senior Propellus Maximus
- Posts: 2650
- Joined: Wed Apr 14, 2010 8:01 am
- Location: Surrey, UK
Re: Best practice for multi-language output
I agree with Ramon, a separate project for each language is more manageable and maintainable.
Started as a newbie with Flare 6.1, now using Flare 2024r2.
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Re: Best practice for multi-language output
Thanks for the advice.. 
Re: Best practice for multi-language output
While we're on the topic of translation and best practices, what's the best way to get an estimated word count from Flare for estimating?
Sally
Sally
Re: Best practice for multi-language output
You can probably just create a word output and use Word's word counter.SallyD wrote:While we're on the topic of translation and best practices, what's the best way to get an estimated word count from Flare for estimating?
Sally
-
techwriter31
- Propellus Maximus
- Posts: 551
- Joined: Wed Mar 05, 2008 10:50 am
Re: Best practice for multi-language output
Another option is to create a blank report. Under the Project heading, check the Statistics checkbox. Then generate the report, and it should provide a word count. I'm assuming this is only a topic word count, and may not include translatable text from other files (TOCs, targets, etc.).
Kellie