Streamlining the User Assistance Localization Process
Upcoming SlideShare
Loading in...5
×
 

Streamlining the User Assistance Localization Process

on

  • 950 views

Presentation delivered by Cecilia Dobner at Technical Communication UK 2011.

Presentation delivered by Cecilia Dobner at Technical Communication UK 2011.

Statistics

Views

Total Views
950
Views on SlideShare
949
Embed Views
1

Actions

Likes
1
Downloads
5
Comments
1

1 Embed 1

http://www.docseek.net 1

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…
  • A better version (including all the video sequences) is available from the Technical Communication UK (see http://www.technicalcommunicationuk.com/index.php?/general/tcuk-2011-resources.html) website.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Abstract visualization using Autodesk(R) 3ds Max(R) software.Expiration Date: 2099-01-01 No image credit required.
  • Minimize the amount of time needed to produce localized images after the release of the localized screenshooting builds Minimize the amount of time needed to update images from one release to the next: scripts can often be reused from release to release with minimal updating work required Help improve quality Reduce the peak resource demand; the script creation can occur on the English builds, before the localized screenshooting builds are available Support Authoring teams by providing English screenshots; part of the script creation process involves testing the scripts on the English UI-freeze build
  • “Text” layer:with dynamic text boxes visible as unique strings in Strings panel, at right of Flash screen“Graphics” layer: allows expansion of the table cells at the left to accommodate longer translations“Mask” layer: consists of white rectangles hiding the English text in the original image“Background” layer: contains the original ‘flat’ image“Comp guide” layer: contains the original ‘flat’ image for reference if a new image is used in the ‘Background’ layerText can be changed from one language to another by changing the Stage language in the Strings panel
  • Captivaterecords a screenshot each time the UI changes, along with timing and cursor positioningthe resulting video is a stylized reproduction of the original actionall components of the video are editable and replaceablewell suited to more formal instructional videos, and videos that may need to be edited and updatedwhen used with scripted screenshooting, can minimize the time from loc UI freeze to releaseCamtasiarecords UI interaction like a video recorder with up to 30 screenshots recorded per secondthe resulting video is an exact duplicate of the recorded actiona recorded sequence has less potential for editing and updatingwell suited to videos that benefit from a more human feelmost localization time is spent after release of loc UI freeze, so longer time to release, but overall cost is comparable
  • 2 perspectives: AuthorsLocalizationBackground Captivate - only need to replace the screenshots that show itCamtasia – need to re-record the sequenceEasy update when UI is updated Captivate - videos can be created using early builds and then just replace the background screenshots with those showing the final UI.Likewise, videos from a previous release can be easily updated by simply capturing new screenshots from the new UICamtasia – need to re-create the video every time the UI is updatedLoc Time after loc UI freeze Camtasia ~ 5 times longer than CaptivateCaptivate - involves only executing scripts, then replacing screenshots in CaptivateCamtasia – loc videos need to be created from scratch once loc UI freeze build is releasedClosed Captions export/import for translationCaptivate – Closed Captions (subtitles) can be exported as XML (or .doc)Camtasia - Closed Captions (subtitles) can be exported as .srt (common subtitles format which is easily translated)Callouts export/import for translationCaptivate – callouts (annotations) can be exported as XML (or .doc)Camtasia - callouts (annotations) cannot be easily exported for translationTable of Contents + InteractivityCaptivate is more full-featured in this regardControl over timing and precisionCaptivate – every element in the project including the cursor is individually editable for timing and locationCamtasia – recorded footage can be edited, but not cursorFidelity of user experienceCaptivate – final video is generated with ‘mathematical’ precision, so doesn’t look like the interaction of a real personCamtasia – video is actual recording of a real person, so looks more naturalAuthoring time requiredCamtasia is generally faster to get a usable result, but when editing and updating is taken into account total time would be similar on averageEasy to useCamtasia is more intuitive and faster to learnPurchase CostCamtasia - $299 vs.Captivate - $799Captivate can be obtained as part of the eLearning suiteLocalization cost is independent of amount of editing and captionsCaptivate – regardless of project complexity localization is simply the batch replacing of screenshots and calloutsCamtasia – the more complex the project is, the more time it takes to localize, since the project needs to be fully recreated for each languageTotal localization costCaptivate – more preparation time needed in writing/updating scripts, less execution time after loc UI freeze, less time needed for future updatesCamtasia – less preparation time, more execution time after loc UI freeze, more time needed for edits and updates
  • Use graphics instead of new text where possibleAvoid visible English strings that are not essential to the messageReduce the number of localizable screenshots in animationsAdd closed captions to voiceover videosProvide Audio Runsheets for voiceover videosProvide Steps-to-Reproduce documents where necessaryAssist with art tagging in the Content Management System of choicePost all source data for Localization teams

Streamlining the User Assistance Localization Process Streamlining the User Assistance Localization Process Presentation Transcript

  • Streamlining the User Assistance
    Localization Process: Graphics & Multimedia
    Cecilia Dobner & David ThomassonProcess Analysts Manager - Localization Services Publishing Technologies
  • Introduction – Who am I?
    How I started, how I got here
    My evolution at Autodesk
    My role today
  • Today’s trends and Autodesk’s response
    Graphics are growing
    Collaboration between UA teams: Dev and Loc
    Videos are growing
    Graphics translation cost doesn’t have to be so high
    Quick turn-around time
    Cost savings and fast moving into market
    Thinking global – Cooperation
  • Documentation Localization Cost Split
  • Cost considerations
    Graphics + Multimedia localization cost is a small fraction of total documentation localization costs
    Costs can be reduced by using graphics instead of creating new text
    Costs will increase if existing text is replaced by newgraphics
    Costs are increasing due to new voiceover movies
  • Agenda
    Graphics Automations
    Videos
    Saving cost with Visual Elements
  • Automations
  • Automations
    Intro / Overview
    Benefits
    Scripted or Manual
    Demos
    Requirements
  • Intro / Overview
    Screenshot > Scripts to automate screenshot capture
    Annotated and Composite graphics > Flash/Captivate projects to automate the localization
  • Benefits
    Minimize the amount of time needed to produce localized images
    Minimize the amount of time needed to update images from one release to the next
    Minimize the gap between release of English product and localized
    Improve quality
    Reduce the peak resource demand
    Support Authoring teams by providing English screenshots
  • Scripted or Manual
    Average process times
    These times take into account all related project overhead:
    • Setting up virtual machines
    • Downloading builds
    • Installing builds
  • Screenshot Automation Demo
  • Flash Annotations Loc Project
  • How does it work?
    Text layer
    Graphics layer
    Mask layer
    Background layer
    Comp guide layer
    Greenland Icecap
  • Requirements
    Minimum 3 languages
    Need for screenshots to be reused next release, with updated UI
    Minimum 20 localizable screenshots
    Type of documentation: tutorials are the best fit for scripting
    Nature of the software: some applications are more difficult to script than others
  • Videos
  • Different Video Formats
    Captivate Video
    Video with Audio
    Camtasia Video
  • Samples
    CaptivateCamtasia
    Notice how….
    Cursor movement: Captivate is generated, Camtasia is recorded
    Drawing Area motion: Captivate is a succession of stills, Camtasia is full motion
    Animated Graphics: Camtasia makes it easy to add animated graphics
  • Captivate vs. Camtasia
  • Video with Audio
    Initially we used expensive linguistic experts familiar with each language to do the video engineering work
    Costs were significantly reduced by using a process that allowed engineers without linguistic expertise to synchronize localized audio with localized video
  • Audio Runsheet example
  • New technologies: Text-To-Speech
    Benefits:
    Avoid reliance on individual voice talents, for the duration of the project
    Avoid voice talent and studio recording costs
    Avoid costly delays when rework is needed
    Challenges:
    High cost of professional TTS systems
    Establishing guidelines on acceptable quality
    Manual post-editing to achieve acceptable quality
  • Saving cost with visual elements
  • Words vs. Annotated image
    Assumptions
    • $0.16 per new word
    • 12 languages
    • annotated image is created in Flash by author
    11 new words
    Global image with 5 words of callouts
    $22
    12languages
    Using 1annotated image instead of writing 12+ new words will result in a saving.
    (Replacing 11 existingwords with a graphic will actually increase the cost.)
  • Words vs. Screenshot
    Assumptions
    • $0.16 per new word
    • 12 languages
    • screenshot would be refreshed twice
    44 new words
    Screenshot
    $85
    12languages
    Using 1 screenshot instead of writing 44+ new words will result in a saving.
    (Replacing 44 existingwords with a screenshot will actually increase the cost.)
  • Words vs. Composite
    Assumptions
    • $0.16 per new word
    • 12 languages
    • screenshot would be refreshed twice
    • composite image is created in Flash by author
    76 new words
    Screenshot with 12 words of callouts
    $146
    12languages
    Using 1 composite image instead of writing 76+ new words will result in a saving.
    (Replacing 76 existingwords with new ones will actually increase the cost.)
  • Words vs. Animation with Captions
    Assumptions
    • $0.16 per new word
    • 12 languages
    • 15 background screenshots in animation
    • 50 words of captions in animation
    • UI would be refreshed twice
    543 new words
    Animation
    15 screens + 50 words in captions
    $1040
    12languages
    Using 1 animation of this type instead of writing 543+ new words will result in a saving.
    (Replacing 543 existingwords with new ones will actually increase the cost.)
  • Words vs. Animation with Voiceover
    Assumptions
    • $0.16 per new word
    • 12 languages
    • 15 background screenshots in animation
    • 300 words of voiceover + closed captions
    • UI would be refreshed twice
    2,290 new words
    $4,400
    Animation
    15 screens + 300 words of voiceover + closed captions
    12languages
    Using 1 animation of this type instead of writing 2,290+ new words will result in a saving.
    (Replacing 2,290 existingwords with new ones will actually increase the cost.)
  • Rewards
    Use more Graphics with no extra cost
    Use more Videos with no extra cost
    Receive final screenshots from localization team
    Later freeze date for screenshots in docs
    Fewer questions from localization team
    Think Global – Cooperate
  • Tools
    SilkTest: used for screenshot scripting
    Flash and Captivate: used for annotation and composite automations
    ImageMagick: used for post-editing automations
    AutoIT: general Windows automation
  • Q&A
  • cecilia.dobner@autodesk.com