<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:p =
"urn:schemas-microsoft-com:office:powerpoint" xmlns:oa =
"urn:schemas-microsoft-com:office:activation" xmlns:st1 =
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1106" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"
downloadurl="http://www.5iantlavalampft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="country-region"
downloadurl="http://www.5iantlavalamp.com/"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"
downloadurl="http://www.5iamas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"
downloadurl="http://www.5iamas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"
downloadurl="http://www.microsoft.com"></o:SmartTagType><!--[if !mso]>
<STYLE>st1\:* {
BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Verdana;
}
@font-face {
font-family: Arial Black;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
P.MsoPlainText {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
LI.MsoPlainText {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
DIV.MsoPlainText {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
SPAN.EmailStyle17 {
FONT-WEIGHT: normal; COLOR: black; FONT-STYLE: normal; FONT-FAMILY: Arial; TEXT-DECORATION: none; mso-style-type: personal-compose
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=534095520-24112005>Hello
Sivia,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=534095520-24112005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=534095520-24112005>Having
managed L10N to both Asian and European languages for 10 years, I can sympathize
with your L10N manager. Frame does not offer an in-depth change tracking
facility as Word does, and for his purposes, I think you need more than
just change bars that show only the lines where changes have been
made.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=534095520-24112005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=534095520-24112005>To
solve his problem, you need a content management system or at least a
version control system for the FM docs, online help, release notes,
etc. This will allow better trackjing of changes to the docs and
help. A tool such as MS Visual Source Safe or Rational Clear Case, which
may already be in use at your company by Engineering, allows you to check-in and
check out documents. If the files are ASCII, these tools can do a diff on
the contents to show what the changes are. Obvioiusly, this does not apply to
the binary FM files, but if you save them to text and do diff on the
text files, you can highlight the actual text changes and provide only the
changed text to the L10n vendor. This saves considerable time and
cost. Note that your L10N vendor can also do that with the TM.
The only problem with having the vendor do it is that you have less control and
it costs a lot more. You can also use Trados to do this, and that actually
is probably the best tool for the jobl but you would have to buy it and learn to
use it, while your company probably alreay has a version contol system in
house.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=534095520-24112005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=534095520-24112005>I also
understand the needs of your company. Simultaneous delivery of localized
and source-language documents is desirable, but requires a lot of advance
planning and close cooperation between engineering/development, tech pubs, and
localization. Localization should begin with the Beta docs and software,
and the L10N vendor should use a TM so that changes can easily be made. In
addition, Engineering must agree that the scope of any changes after Beta will
not require major changes to the docs and help. Remember, L10N is
expensive, especially if you are localizing to multiple languages, and
particularly if you are localizing to Japanese, any scandinavian language,
or any language that uses Cyrillic fonts (Russian, for example) and similar
languages, and possibly cost more if you are starting with Hebrew.
</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=534095520-24112005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=534095520-24112005>Your
L10N manager may find some useful information in a book called Localization and
Framemaker. You can find the book on the net at <A
href="http://www.bapmf.net/resources/2000_localization_FM/locandfm.pdf">http://www.bapmf.net/resources/2000_localization_FM/locandfm.pdf</A>.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=534095520-24112005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=534095520-24112005>Hope
this helps.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=534095520-24112005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=534095520-24112005>Diane
Gaskill</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=534095520-24112005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=534095520-24112005>========================</SPAN></FONT></DIV>
<DIV><FONT size=+0><SPAN class=534095520-24112005></SPAN></FONT><FONT
face=Tahoma><FONT size=2><SPAN class=534095520-24112005><FONT face=Arial
color=#0000ff></FONT></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Tahoma><FONT size=2><SPAN
class=534095520-24112005> </SPAN>-----Original Message-----<BR><B>From:</B>
framers-bounces+dgcaller=earthlink.net@lists.frameusers.com
[mailto:framers-bounces+dgcaller=earthlink.net@lists.frameusers.com]<B>On Behalf
Of </B>Sivia Atar<BR><B>Sent:</B> Thursday, November 24, 2005 12:46
AM<BR><B>To:</B> 'framers@lists.frameusers.com'<BR><B>Subject:</B> Document
Localization Process?<BR><BR></DIV></FONT></FONT>
<BLOCKQUOTE>
<DIV class=Section1>
<P class=MsoPlainText><FONT face="Courier New" size=2><SPAN
style="FONT-SIZE: 10pt">Hi,<o:p></o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT face="Courier New" size=2><SPAN
style="FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT face="Courier New" size=2><SPAN
style="FONT-SIZE: 10pt">At Mercury we write our source product documentation
in <B><SPAN style="FONT-WEIGHT: bold">FrameMaker</SPAN></B> 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 wants to
reach the point where it can ship localized versions of its products at the
same time as the English Versions. <o:p></o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT face="Courier New" size=2><SPAN
style="FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT face="Courier New" size=2><SPAN
style="FONT-SIZE: 10pt">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.<o:p></o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT face="Courier New" size=2><SPAN
style="FONT-SIZE: 10pt"> <o:p></o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT face="Courier New" size=2><SPAN
style="FONT-SIZE: 10pt">I would like to hear how other companies manage the
process of localizing documentation (workflow, communication, and tools).
<o:p></o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT face="Courier New" size=2><SPAN
style="FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT face="Courier New" size=2><SPAN
style="FONT-SIZE: 10pt">Thanks in advance for any information you can
provide.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal
style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT face=Arial
color=gray size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: gray; FONT-FAMILY: Arial">____________________________<BR></SPAN></FONT><FONT
color=black><SPAN style="COLOR: black"><BR></SPAN></FONT><STRONG><B><FONT
face=Verdana color=black size=1><SPAN
style="FONT-SIZE: 8pt; COLOR: black; FONT-FAMILY: Verdana">Sivia
Atar</SPAN></FONT></B></STRONG><FONT face=Verdana color=black size=1><SPAN
style="FONT-SIZE: 7.5pt; COLOR: black; FONT-FAMILY: Verdana">,
</SPAN></FONT><st1:PersonName w:st="on"><FONT face=Verdana color=gray
size=1><SPAN
style="FONT-SIZE: 7.5pt; COLOR: gray; FONT-FAMILY: Verdana">Documentation</SPAN></FONT></st1:PersonName><FONT
face=Verdana color=gray size=1><SPAN
style="FONT-SIZE: 7.5pt; COLOR: gray; FONT-FAMILY: Verdana"> Infrastructure
Leader,</SPAN></FONT><FONT color=gray><SPAN style="COLOR: gray">
</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"><A
href="mailto:satar@mercury.com"><FONT face=Verdana color=gray size=1><SPAN
style="FONT-SIZE: 7.5pt; COLOR: gray; FONT-FAMILY: Verdana">satar@mercury.com</SPAN></FONT></A><BR></SPAN></FONT><FONT
face=Verdana color=gray size=1><SPAN
style="FONT-SIZE: 7.5pt; COLOR: gray; FONT-FAMILY: Verdana">direct
972.3.539.9288 fax 972.3.553.1617</SPAN></FONT><FONT color=black><SPAN
style="COLOR: black"><BR></SPAN></FONT><st1:address w:st="on"><st1:Street
w:st="on"><FONT face=Verdana color=gray size=1><SPAN
style="FONT-SIZE: 7.5pt; COLOR: gray; FONT-FAMILY: Verdana">19 Shabazi
Street</SPAN></FONT></st1:Street><FONT face=Verdana color=gray size=1><SPAN
style="FONT-SIZE: 7.5pt; COLOR: gray; FONT-FAMILY: Verdana">, <st1:City
w:st="on">Yehud</st1:City>, <st1:country-region
w:st="on">Israel</st1:country-region></SPAN></FONT></st1:address><FONT
face=Verdana color=gray size=1><SPAN
style="FONT-SIZE: 7.5pt; COLOR: gray; FONT-FAMILY: Verdana"> 56100<BR></SPAN></FONT><FONT
face=Verdana color=black><SPAN
style="COLOR: black; FONT-FAMILY: Verdana"><BR></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>