TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: translation and wiki docs From:Bill Swallow <techcommdood -at- gmail -dot- com> To:Sally Derrick <sjd1201 -at- gmail -dot- com> Date:Tue, 8 Feb 2011 12:00:24 -0500
For internal docs, you may just want to ensure all users have a
machine translation tool installed in their browser. You don't want to
hinder internal communication waiting for translation of individual
posts and comments when getting the gist will do. If there are
"finished" entries that you want to make formal, you would want to get
those edited for international/standardized language and then
translated. Had this been an external customer resource, I'd have
different opinions. This is coming from a guy working for a
translation company who manages content strategy solutions. :)
On Tue, Feb 8, 2011 at 11:50 AM, Sally Derrick <sjd1201 -at- gmail -dot- com> wrote:
> Many organizations are beginning to use wikis for technical docs. One of
> the big benefits is enabling users to add comments and content. I'm
> thinking of the model in which corp content is reviewed and labeled as
> 'proven'. User input is identified as such, but must be reviewed and
> approved before it is incorporated with corp data.
>
> I'm curious how these orgs handle translation. Is there anyone out there
> doing wiki docs for an international company?
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-