Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

77
Strategies for Friendly English and Successful Localization John Collins Senior UX Content Strategist www.linkedin.com/in/johncollins @jrc_collins

description

More and more companies are striving for a friendly tone with their content. Many of those same companies are taking their content to other cultures with localized content. Those two content goals seem to be at odds. This slideshow, presented at Information Development World in October of 2014, looks at how to accomplish both goals.

Transcript of Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Page 1: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Strategies for Friendly English and Successful Localization

John Collins!Senior UX Content Strategist www.linkedin.com/in/johncollins"@jrc_collins

Page 2: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

bit.ly/idw14jrc

@jrc_collins 2

Page 3: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

3 @jrc_collins About me

Page 4: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

4 @jrc_collins

Your turn!

Page 5: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Some groundwork

© Oregon Husky – https://flic.kr/p/9jDEE | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 5

Page 6: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

What is localization?

@jrc_collins 6 © Oregon Husky – https://flic.kr/p/9jDEE | https://creativecommons.org/licenses/by-sa/2.0/

Page 7: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Localization is the process of adapting internationalized software for a specific region or language by adding locale-specific components and translating text

http://en.wikipedia.org/wiki/Internationalization_and_localization

@jrc_collins 7 © Oregon Husky – https://flic.kr/p/9jDEE | https://creativecommons.org/licenses/by-sa/2.0/

Page 8: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Why do you care?

@jrc_collins 8

Page 9: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Your audience @jrc_collins 9

Page 10: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

“Like people, UIs communicate through their personality, tone, and attitude.”

Everett McKay  

@jrc_collins 10

Page 11: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Your brand

© Derek Gavey– https://flic.kr/p/a8nY4A | https://creativecommons.org/licenses/by/2.0/ @jrc_collins 11

Page 12: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

“Your tone can help you stand out from competitors, communicate efficiently and effectively with your audience and share your personality.”

Robert Mills

© Derek Gavey– https://flic.kr/p/a8nY4A | https://creativecommons.org/licenses/by/2.0/ @jrc_collins 12

Page 13: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Content trend • Moving away from stuffy

technical jargon • Moving toward friendlier,

more natural language

@jrc_collins 13

Page 14: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

http://voiceandtone.com/ @jrc_collins 14

Page 15: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

http://www.cherryleaf.com/blog/2014/09/microsoft-moves-away-from-robot-speak-in-its-user-documentation

@jrc_collins 15

Page 16: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Business trend • Marketing communications

and technical communications converging • Rise of content strategy as a

“thing”

@jrc_collins 16

Page 17: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Avoid humor

@jrc_collins 17

Page 18: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Avoid idioms like the plague.

@jrc_collins 18

Page 19: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Avoid casual language Right, dude?

@jrc_collins 19

Page 20: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Friendly tone

© Martin Cathrae– https://flic.kr/p/a11RAq | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 20

Page 21: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Friendly tone Easy to localize

© Martin Cathrae– https://flic.kr/p/a11RAq | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 21

Page 22: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

A house divided against itself cannot stand

Friendly tone Easy to localize

© Martin Cathrae– https://flic.kr/p/a11RAq | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 22

Page 23: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

A house divided against itself cannot stand

Friendly tone Easy to localize

© Martin Cathrae– https://flic.kr/p/a11RAq | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 23

Page 24: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

You serve ALL of your audience."

© Oregon Husky – https://flic.kr/p/487RqS | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 24

Page 25: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Proper tone for all

English!

Chinese!

French!

Spanish (Mexico)!

Japanese!

Korean!

Russian! Etc.!

© Oregon Husky – https://flic.kr/p/487RqS | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 25

Page 26: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Proper tone for all

English!

Chinese!

French!

Spanish (Mexico)!

Japanese!

Korean!

Russian! Etc.!

Easy to localize

© Oregon Husky – https://flic.kr/p/487RqS | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 26

Page 27: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

That’s all well and good, "but how do I do it?

@jrc_collins 27

Page 28: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Lay a strong foundation

© Oregon Husky – https://flic.kr/p/9jDN1 | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 28

Page 29: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Lay a strong foundation •  Establish relationships with translators/

vendors

© Oregon Husky – https://flic.kr/p/9jDN1 | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 29

Page 30: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Lay a strong foundation •  Establish relationships with translators/

vendors •  Create style guides for each localization

(including English)

@jrc_collins 30 © Oregon Husky – https://flic.kr/p/9jDN1 | https://creativecommons.org/licenses/by-sa/2.0/

Page 31: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Lay a strong foundation •  Establish relationships with translators/

vendors •  Create style guides for each localization

(including English) •  Create localized glossaries

@jrc_collins 31 © Oregon Husky – https://flic.kr/p/9jDN1 | https://creativecommons.org/licenses/by-sa/2.0/

Page 32: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Add quality content

© Oregon Husky – https://flic.kr/p/9jFwW | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 32

Page 33: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Simplify

© Oregon Husky – https://flic.kr/p/9jFwW | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 33

Page 34: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Clarify

© Oregon Husky – https://flic.kr/p/9jFwW | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 34

Page 35: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Want to know some secrets?

@jrc_collins 35

Page 36: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Secret #1 Translators can do better "job when they have quality source content.

@jrc_collins 36

Page 37: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Secret #2 When your source content is high quality, it’ll be friendlier, too.

@jrc_collins 37

Page 38: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

On writing for localization …

@jrc_collins 38

Page 39: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Think like a translator

© Marshall Astor– https://flic.kr/p/3TPf3U | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 39

Page 40: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

40 @jrc_collins

Your turn!

Page 41: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Structure your content with localization in mind. •  Be careful with substitutions.

@jrc_collins 41 © Marshall Astor– https://flic.kr/p/3TPf3U | https://creativecommons.org/licenses/by-sa/2.0/

Page 42: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

{number} results Welcome, {name}.

@jrc_collins 42 © Marshall Astor– https://flic.kr/p/3TPf3U | https://creativecommons.org/licenses/by-sa/2.0/

Page 43: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

} Structure your content with localization in mind. •  Be careful with the granularity

of conditional text.

@jrc_collins 43 © Marshall Astor– https://flic.kr/p/3TPf3U | https://creativecommons.org/licenses/by-sa/2.0/

Page 44: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Plug the {hardware} into the {power source}. A solid green light turns on to show that your {hardware} is fully charged.

@jrc_collins 44 © Marshall Astor– https://flic.kr/p/3TPf3U | https://creativecommons.org/licenses/by-sa/2.0/

Page 45: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

} Structure your content with localization in mind. •  Don’t concatenate text.

© Marshall Astor– https://flic.kr/p/3TPf3U | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 45

Page 46: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Write for localization •  Use short, simple sentences.

@jrc_collins 46 © Marshall Astor– https://flic.kr/p/3TPf3U | https://creativecommons.org/licenses/by-sa/2.0/

Page 47: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Write for localization •  Use consistent terminology.

@jrc_collins 47 © Marshall Astor– https://flic.kr/p/3TPf3U | https://creativecommons.org/licenses/by-sa/2.0/

Page 48: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Write for localization •  Avoid synonyms, equivalents,

and metonyms.

@jrc_collins 48 © Marshall Astor– https://flic.kr/p/3TPf3U | https://creativecommons.org/licenses/by-sa/2.0/

Page 49: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Write for localization •  Foil homonyms. •  Date •  Engaged

•  Leaves •  Net

@jrc_collins 49 © Marshall Astor– https://flic.kr/p/3TPf3U | https://creativecommons.org/licenses/by-sa/2.0/

Page 50: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Write for localization •  Foil homonyms. •  Point •  Right

•  Type •  Stalk

@jrc_collins 50 © Marshall Astor– https://flic.kr/p/3TPf3U | https://creativecommons.org/licenses/by-sa/2.0/

Page 51: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Write for localization •  Don’t bow to homographs. •  Read •  Bow

•  Minute •  Does

@jrc_collins 51 © Marshall Astor– https://flic.kr/p/3TPf3U | https://creativecommons.org/licenses/by-sa/2.0/

Page 52: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Write for localization •  Don’t bow to homographs. •  Wind •  Sow

•  Row

@jrc_collins 52 © Marshall Astor– https://flic.kr/p/3TPf3U | https://creativecommons.org/licenses/by-sa/2.0/

Page 53: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Write for localization •  Don’t noun verbs or verb

nouns.

@jrc_collins 53 © Marshall Astor– https://flic.kr/p/3TPf3U | https://creativecommons.org/licenses/by-sa/2.0/

Page 54: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Write for localization •  Re-use content.

@jrc_collins 54 © Marshall Astor– https://flic.kr/p/3TPf3U | https://creativecommons.org/licenses/by-sa/2.0/

Page 55: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

55 @jrc_collins

Your turn!

Page 56: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

{number} results

Example

@jrc_collins 56

Page 57: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

The <person> moved "Friday’s game to Saturday "due to inclement weather.

Example

@jrc_collins 57

Page 58: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Signing up for our new notifications is a cakewalk!

Example

@jrc_collins 58

Page 59: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Done?

© Oregon Husky – https://flic.kr/p/agKR6 | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 59

Page 60: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Done? No!

© Oregon Husky – https://flic.kr/p/agKR6 | https://creativecommons.org/licenses/by-sa/2.0/ @jrc_collins 60

Page 61: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Provide context

@jrc_collins 61

Page 62: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Loc kit: reference info 62

@jrc_collins

Page 63: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Loc kit: reference info 63

@jrc_collins

Page 64: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Loc kit: source files & context 64

@jrc_collins

Page 65: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Loc kit: handoff sheet 65

@jrc_collins

Page 66: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Wait, what happened to the friendly, human English part?

@jrc_collins 66

Page 67: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Translation A faithful and accurate adaptation of your text that basically says the same thing in another language.

http://wordtrans.com/2013/06/transcreation-vs-translation/

@jrc_collins 67

Page 68: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Transcreation An adaptation of your text with the goal of evoking the same reaction to your message from readers in another language.

http://wordtrans.com/2013/06/transcreation-vs-translation/

@jrc_collins 68

Page 69: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Translation •  Write a simplified English version. "

Create a second more natural version, almost as its own localization.

@jrc_collins 69

Page 70: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

<!-- The “rewards” mentioned here are treasure chests full of coins.--> <simplified description>Use the hints we have provided to create the correct sentence. If you pronounce the sentence accurately, you will uncover a square. Some squares conceal rewards. Try to collect as many rewards as you can in the time limit.</simplified description> <localized description>Race to find buried treasure!

Use our clues to build the right sentence, and say it correctly to dig up a plot. Maybe there's treasure; maybe there's not. Collect as much as you can before time runs out.</localized description> @jrc_collins 70

Page 71: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Transcreation • Write the English you want. • Add comments for translators.

@jrc_collins 71

Page 72: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

Transcreation • Write the English you want. • Add comments for translators.

Lots of comments!!

@jrc_collins 72

Page 73: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

<!-- TRANSLATOR: This comment contains detailed notes for the translation of the "description" string below. * "Race to find buried treasure!" This is an imperative sentence that we want to sound fun. Completing the game tasks quickly

is important for achieving a good score, so "race" was chosen to suggest the time-sensitive nature of the game. * "Use our clues to build the right sentence" The game interface will have icons or graphics on the x-axis and the y-axis. Those

icons or graphics are the "clues." We used the word "clue" because it carries some game connotations. The word "cue" or "hint" could also be used, but we preferred "clue." The players will have to use those to create a sentence in their minds. For technological reasons, it can't be just ANY sentence; it must match the sentence Rosetta Stone intends. The sentences are leveled based upon the player's progress in Rosetta Course. See below for slightly more information.

* "say it correctly" The speech recognition is listening for the correct sentence and the correct pronunciation. If it doesn't detect the correct items after a certain time period, the game will prompt the player by displaying the text of the expected sentence. If it still doesn't get the correct answer after another certain time period, a native speaker will then speak the sentence. If it still doesn't detect the correct speech from the player, that particular game piece will close and the player can select a new piece.

* "to dig up a plot" When the speech recognition detects a correct sentence and pronunciation, the game will see a quick digging animation. If there's treasure, the game will indicate that with graphics and sound. If there's no treasure, that will also be indicated with graphics and sound. The word "plot" suggests a plot, or section, of land, especially on a map. Players will see a map with a 6-by-6 grid. We're using "plot" to indicate one of the 36 squares on the map. The word "plot" in English is kind of a play on words, because it also suggests the concept of plotting something on a map (choosing a course). See note on rhyme below.

* "Maybe there's treasure; maybe there's not." This is a complex sentence to suggest that some squares (plots) will have treasure, but not all of them will. You have two independent clauses in the English source separated by a semicolon. That construction may not work in all translations; please do what is appropriate for your language. We use "there's" as a contraction of "there is" in both clauses. We did purposely rhyme in English from "plot" in the previous sentence to "not" in this sentence. This was done to make the English source a little more fun and game-like. We realize that the translations probably won't be able to rhyme; if they do, it will be a nice bonus.

* "Collect as much as you can" This is an imperative in English. We used "collect" because it sounds like a gaming term in English. Many games have items that the user needs to acquire to gain points, and that is the case in this game. We want this sentence to sound fun, even though we've worded it as an imperative. The user is trying to "collect as much (treasure)" as they can. They earn points for each treasure they find.

* "before time runs out" The game is a time-based game. The goal is to collect as much treasure as possible (by speaking correctly and guessing which squares contain buried treasure).

* "Collect as much as you can before time runs out." We worded the entire sentence this way because we are trying to cover multiple use cases. In one use case, the player is playing Solo (by themself), so getting a high score is the goal. A successful solo player will quickly build the right sentences and say them correctly, and go through as many of the map squares (plots) as possible. The other use case is a Duo game, where two players are playing together. Each one is trying to get a higher score than the other. They will also have to quickly build the right sentences and say them correctly, but in this game, there is a clearly-defined winner (and loser). We can't really say that in the description, because of the Solo player, who does not have a clearly-defined "win" state. -->

<description>Race to find buried treasure! Use our clues to build the right sentence, and say it correctly to dig up a plot. Maybe there's treasure; maybe there's not. Collect as much as you can before time runs out.</description> @jrc_collins 73

Page 74: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

@jrc_collins 74

Page 75: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

@jrc_collins 75

Page 76: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

@jrc_collins 76

Page 77: Strategies for Friendly English and Successful Localization (InfoDevWorld 2014)

•  Slides: bit.ly/idw14jrc •  Twitter: @jrc_collins •  www.linkedin.com/in/johncollins

77 @jrc_collins