Localization -WritePoint & Net Translators
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Localization -WritePoint & Net Translators

on

  • 1,112 views

This joint presentation was given at the Techshoret Communicators Conference in Jerusalem by Paula Stern of WritePoint and David Sommer of Net Translators.

This joint presentation was given at the Techshoret Communicators Conference in Jerusalem by Paula Stern of WritePoint and David Sommer of Net Translators.

Statistics

Views

Total Views
1,112
Views on SlideShare
1,112
Embed Views
0

Actions

Likes
0
Downloads
7
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • POINT 1 POINT 2 POINT 3: For example if you are translating instructions on how to assemble a baby carriage, you would expect that the baby carriage will look the same way once a native speaker has assembled it irrespective of the language, on the other hand if it takes an English speaker 10 minutes, but a French speaker half an hour, then you know something is wrong. The reader should not have to scratch his head trying to figure out the instructions. POINT 4, simplicity is the key to success and it starts byt the TW using Plain, precise language, appropriate vocabulary, for example were you aware that ICF (informed consent forms) need to be written to a 8 th grade level, but our scientist colleagues always seem to feel that they need to confuse the patient! Furthermore conventional text along with correct document formatting are all keys to success, it could be something as simple as maintaining consistency when referring to figures and not switching back and forth between figure and drawing or some other synonyms. While I know that we are all frustrated novelists, we nonetheless must keep in mind that
  • OK so let me formally introduce myself, my name is David Sommer I am the Senior LPM at net-translators, I deal with methodologies and strategic accounts at NT and I am here to give you a small taste of my experience dealing with TW’s My experience tells me that the relationship between the TW and us is usually the closest of any person in the company, management generally sees (erroneously I might add) that the TW’s have so mush extra time on their hands that they should eb the focal point for translation issues, this is great for me since a vendor should come in and help you guys as much as possible in this. So not “Kitbag questions” If your company chooses on the other hand not to use a vendor and make you the translation slave, then you will need to make sure that you choose the right translator, and there are lots of them out there, and to be honest, only very few can actually do it right, and on the other hand you should do it WRITE too
  • I’d like to just take a quick look at these assumptions for a moment 1-You should always use a translator familiar with Help files if that is what you are translating 2-So essentially this means that one hidden cost both in terms of time and Money will be engineering the HTMLs 3-You know I have seen more than my share of “talkbacks” on the Tecshoret list about TW’s struggling with this issue especially the index fields 4-If your translator is using a text editor to translate with…change translators ! Seriously though, using the right CAT tools (Translation tool set) ensures more than just translation but the correct encoding as well as providing automatic verification tools which check things like Missed translations, non-use of glossary terms, deleted or change tags etc. The bottom line is that you should expect your translator to be as professional as you are.
  • Paula, again why would a technical writer want to manage complicated localization projects? I think that there are a LOT better things a TW could do than add the headache of managing localization. I know I have already said this, but it bears saying again. But you know I won’t bother you any more, please proceed, it is important perhaps that you all know more about this, in fact if you are only doing a single language it may be that management wants you to take on this entire task, and in that case you will definitely need to know more about how to get localization do right AND start at the ground floor.
  • OKAY now we’re talking, what we view as paramount to translation is quality, quality is a manageable factor for the translation company. The quality of a translation must be defined before the translation begins and this quality depends on the following factors: Define key areas Set requirements Monitor the process Evaluate results For each of these you have to ask. What (e.g. elements and other material) Who (generally Target audience) Why (Knowing the purpose of the translation and communicating this to your resources) Where (knowledge of the region, this will mitigate misunderstandings due to regional, dialectical or other differences) When –By this I mean planning, involve the translator at the very first stage even before you write a translation guide in fact) How much – Know the complete cost of translation and factor in all of the variables OH YES AVOID CULTURAL REFERENCES
  • You know on the translation side you would want to be aware that the translation if you are managing it is not a “drag and drop” function and you should certainly plan it well, Prepare what we call a translation kit which includes the files for translation, the reference files the TM Glossaries, instructions (which may or may not include the Style Guide) Payment information etc. Then its off to what we call TEP, translation editing and proofing, and of course thorughout the process we would recommend running QC checks an if you have autmatic tools then do so And of course, by using industry standard quality metrics (I prefer the TQI) then you should be able to collect that data too.
  • Paula, I much appreciate your bringing this up, perhaps the most important factor for localization success is the glossary, I have a standard presentation I give to new employees at Net-Translators, and I always mention that the three most important things are GLOSSARY GLOSSARY GLOSSARY A termbase is a database containing terminology and related information. Most termbases are multilingual and contain terminology data in a range of different languages. It is HIGHLY recommended to maintain a proper termBase an example termbase is here once you have it you can make it more portable by saving it as a TBX xml based open exchange format, this makes migration between translators easier if you need to change translators if you are managing in-house the process. This is a good opporttunity for me to explain the two types of “Databases” we use A temrbase is a repository of accepted translations for the afforementioned customer prepared glossary A Translation Memory is a repository of previously translated material which enables better consistency over time as well as ability to leverage previosu transaltions saving both time and money
  • We actually call this process content review and Pre QA, this is also extremely critical keep in mind that if you have a document for translation into 5 languages and it has 50 content issues e.g. missing words, soft or hard line breaks in the middle of a sentence etc, then you will get 250 MISTAKES!!! Now I ain’t no math genius, but I think that it takes less time to fix 50 problems than 250!
  • Single-sourcing lowers localization costs by eliminating redundancies, and reducing the translation volume. Information that is shared by different products, or presented in several display formats (like Help, and printed or PDF docs), can be translated and edited once, and then automatically folded into the different manual versions or formats for all required languages. Many smaller localization vendors discourage applying single-sourcing techniques and I can let you in on the secret as to why, it is because single sourcing saves you money on Localization, really and truly, but if you look carefully at the business of localization you will see that the more reputable vendors encourage this migration to SS, the amount of content for translation is growing so rapidly that this is a perfect match for us MLVs.
  • Keep in mind that capitalization rules change from language to language

Localization -WritePoint & Net Translators Presentation Transcript

  • 1. Localization and Technical Writing: Living together in perfect harmony?
  • 2. Start With the Basics
    • TW has the largest impact on localization (l10n)
    • Good TW leads to good translation t9n
    • Translating technical doc is not translating lit.
    • Simplicity is the key
  • 3. Set the Pace/Plan
    • Consider writing up a Translation Guide
  • 4. Translation Guide
    • Typically written by Documentation Manager or technical writer
      • Tasks that need to be completed
      • Who needs to do what
      • Deadlines for each stage
      • What is transferred in each stage
      • Final goals and deliverables
  • 5. Translation Guide
    • DO YOU REALLY WANT THE EXTRA WORK??
    • Save yourself time and grief
    • Vendor vs. DIY
      • MLV vs. SLV
    • Kitbag ?
    • There are a LOT of translators out there
    • Choose one who will do it “RIGHT”!
    • Do it “Write” the first time
  • 6. Translation Guide
    • Specify Assumptions
    • Do you assume translators have experience with help files, complicated formats, templates?
    • Who is working with what tool (versions)
  • 7.  
  • 8. Translation Guide
    • Define the Tasks
    • Technical Writers (today’s focus)
    • Translators
    • Engineers / Developers
    • QA Team
  • 9. Technical Writing Tasks
    • Writing documentation
    • Producing online help files (if any)
    • Transfer of files to translators
    • Be available for questions
  • 10. Translation Guide
    • Define key areas
    • Set requirements
    • Monitor the process
    • Evaluate results
    • This will enable you to hit a home run each and every time
  • 11.
    • From the initial stages
      • Project Planning
      • LocKit
      • Translation
      • Testing
      • Linguistic quality checks with industry defined metrics
      • Automated checks
  • 12. Writing Rules
    • Use active tense
      • Easier to translate
      • Less complex
      • Less likely to be misunderstood/mistranslated
    • For instructions, use the imperative mood
      • “ Select on option from the combo list, then click Save .
  • 13. Writing Rules
    • Standard Technical Writing Rules Apply
    • Write clearly
    • Write concisely
    • Write consistently
  • 14. Writing Rules
    • If you use a word as a noun, don’t also use it as a verb or to describe something different
      • Example: “account” has specific meaning in finance, so don’t say “account for the missing values in the user account”
  • 15. Writing Rules
    • Don’t use idiomatic phrases (as a rule of thumb, on-the-fly, etc.)
    • Avoid cultural examples
    • Avoid country-specific examples
    • Use serial commas in a list, so that it’s clear which item goes with what (e.g., red, blue, and white)
    • Avoid using compound sentences
      • Translations into some languages produce much longer sentences
  • 16. Writing Process
    • Prepare a glossary that you can give to the translators.
    • Verify that all technical writers are using it.
    • Verify that all translators receive it.
    • Use it as a style guide for the rest of the translation.
  • 17. Writing Process
    • Glossary=TermBase
    • Two types of Databases
      • Translation Memory
      • TermBase
    • TW for t9n is not a creative writing class, do not use synonyms (what’s another word for synonym), if you use socket an outlet you will need to add another entry to your glossary
  • 18. Do FULL QA BEFORE Translation
    • Page breaks don’t matter…but these do:
      • Formatting/styling
      • Punctuation
      • Heading structure
      • Organization
      • Clear sentences, no missing words
  • 19. Pre QA and Content review
    • Localization is the one place you don’t want to recycle
    • Content review allows us to identify possible failure points before translation
    • Pre-DTP allows us to address issues such as:
      • Identify text which may be embedded in an image
      • Delete extra spaces
      • Prepare documentation which is being translated but not having the UI translated WORD “WORD”
      • Adding correct and consistent styles or fonts which support other languages
      • Change Shift+ENTER with spaces
      • etc
  • 20. Working with Graphics
    • Link to graphics rather than embedding them (where possible)
      • Saves time
      • Don’t need to reinsert them
    • Graphics need to be translated via a graphics editor, not in the text translation tool.
      • Save them in editable format.
      • Consider using numbers instead of text for callouts.
  • 21. Single-Sourcing
    • To keep your costs down, use single sourcing
      • Avoid lengthy topics and unnecessary verbage
      • Don’t send topics that haven’t changed and therefore don’t need translating again.
      • Keep track of your files and graphics, so that you know what has changed.
  • 22. Single Sourcing et al
    • Reusability
    • Process
    • Save on DTP time and effort
    • Consistency
    • SAVE $$$$$$$$$$$$$
    • ROI is very short when translating
  • 23. Round Two Realities
    • Be careful what you change.
    • Example:
    • Round 1: The Events Window can be used to schedule events.
    • Round 2a: The Events Window can be used to create events.
    • Round 2b: Use the Events Window to create events.
  • 24. Round Two Changes
    • Don’t change text needlessly
    • Alert translators to major changes
      • Blocks of text that have been added or deleted
      • Changes in terminology
  • 25. Define Rules for Translation
    • According to company rules of look and feel
      • Capitalization
      • Abbreviations, acronyms, and trademarks
      • Copyright statements
      • Graphic presentation and titling
      • Reference usage and listing
      • Numerical and unit conventions
      • Others specific to your business
  • 26. Technical Writing Tasks
    • Define terms that remain in English
      • Company name
      • Default passwords
      • Product name
      • Interface options (?)
  • 27. Managing a Translation Project
    • Set the goals: what gets translated
    • Organization of the source content
    • Scheduling of the content release, along with the translated content
    • Managing of freelancers/agencies
    • Communication between engineers/technical writers/translators/customer or end use
  • 28. Managing a Translation Project
    • Check whether translator/agency uses translation memory software
      • Decreases your costs dramatically
      • Protects source code in help files
  • 29. How the customer sees the project 3
  • 30.  
  • 31. Thank you… Questions?