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.
Re: User manual: cell merging vis a vis translation
Subject:Re: User manual: cell merging vis a vis translation From:Julie Stickler <jstickler -at- gmail -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 14 Feb 2017 10:38:13 -0500
Even if there are no text changes, the translation company will charge for
having to reformat the page and re-generate the doc and/or Help system. I
really dug into this at my last company, because I just did not understand
some of the line items on our bills. Small changes end up being fairly
expensive if they're done alone, because of the translation workflow:
- Pull everything out of the original source files into the translation
tool (This is the step that many people don't realize is happening, your
source files are not being used by the translators. Tour text is being
extracted, translated, and then the text is put back into your files. That
transform is a significant expense.)
- Compare the new files to the translation memory and identify changes.
- Translate any new content.
- Port all the translated strings back into the original source format
(Word, FrameMaker, RoboHelp, Flare, etc.)
- Quality assurance that the transform worked properly.
- Additional desktop publishing tweaks due to the text strings in the new
language being different (page breaks, heading wraps, table column sizing,
- Files get shipped back to you.
If you can, save that change for a major version bump, when you have more
changes to absorb the engineering costs for the entire conversion process.
On Tue, Feb 14, 2017 at 10:06 AM, Chris Morton <salt -dot- morton -at- gmail -dot- com>
> User manual has several pages of tabular stuff pertaining to UI error
> messages. Many of the items in the far right column are the exact same
> message: "Call <company> at <number> for service."
> I think such cellular repetition looks dumb, so I'm inclined to merge
> adjacent cells that convey the same thing.
> PM is upset, telling me that now PM will have to deal with 28 translations
> (all of which have to change anyway due to other new content).
> Pray tell, how in the world does merging such cellular items affect any
> translation, when "Call <company> at <number> for service" has previously
> been translated in all 28 languages?
> Chris Morton
> â Substantive Editing â Technical Writing â Proofreading
> â Marketing Expertise â Mentoring
> Click to
> Visit TechWhirl for the latest on content technology, content strategy and
> content development | http://techwhirl.com
> You are currently subscribed to TECHWR-L as jstickler -at- gmail -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com