MIF works fine and dandy as well and is a non-binary text format.
Going structured and to XML has its advantages, but if the only
concern is localization and using TM tools, it's a lot easier just to
use MIF than to apply structure and use XML for the sake of TM
effectiveness.
On 11/25/05, David
Hi Sivia,
I am the translation coordinator where I work. Our translation vendor uses
TRADOS to build a translation memory for each language. We version control
at the chapter level, so when we make updates to a manual, I compare each of
the modified chapters (File > Utilities > Compare Documents)
An HTML attachment was scrubbed...
URL:
http://lists.frameusers.com/pipermail/framers/attachments/20051128/6cfebd43/attachment.html
One approach to localization problems is to move to an XML-based solution.
This involves a considerable effort, but in the case of a large volume of
documentation, such as the 35,000 pages a year and large number of localized
versions at Mercury mentioned earlier, the eventual savings could be
cument Localization Process?
Hi,
At Mercury we write our source product documentation in
FrameMaker and we produce approximately 35,000 pages of documentation
each year. Most of our documentation is translated into Japanese,
Korean, and Chinese and we're now also st
Hi,
At Mercury we write our source product documentation in FrameMaker and we produce approximately
35,000 pages of documentation each year. Most of our documentation is
translated into Japanese, Korean, and Chinese and we're now also starting to
translate into some European languages.
Hi,
At Mercury we write our source product documentation in FrameMaker and we
produce approximately 35,000 pages of documentation each year. Most of our
documentation is translated into Japanese, Korean, and Chinese and we're now
also starting to translate into some European languages. Mercury
> Our Localization Manager says that his team cannot
> efficiently track changes to our FrameMaker files.
> This results in delays and makes it difficult to
> keep translation costs at a reasonable level.
Sounds like he wants to use somthing primative, like Word's revision
tracking to keep
Sent: Thursday, November 24, 2005 12:46 AM
To: 'framers at lists.frameusers.com'
Subject: Document Localization Process?
Hi,
At Mercury we write our source product documentation in FrameMaker and we
produce approximately 35,000 pages of documentation each year. Most of our
documentation
> Mercury wants to reach the point where it can ship localized versions of its
> products at the same time as the English Versions.
> Our Localization Manager says that his team cannot efficiently track changes
> to
> our FrameMaker files. This results in delays and makes it difficult to keep
>
10 matches
Mail list logo
