Download to read offline
Write globally for locals - Laura Stewart
- 1. Write globally forlocals by Laura Stewart lstewart@splunk.com
- 2. The UShas a wide, diverse population For some of your local customers, English is not their first language Even if you don’t translate now, write as if you do… but you probably know this Writing globally is not just about the UI and the docs Write for your local customers
- 3. Goal -Ship a sample data set with the product Starting point – A sample data set from QA Name Address Phone Zip Region Birthdate Gender Work – Expand the sample data set Sample dataset
- 4. Can’t usenames of real people or trademarked characters Can’t use all WASP names Can’t have only North America regions or cities Can’t use real looking phone numbers Can’t use real looking SSN numbers Whoa, I can’t use this!
- 5. Picked commonnames from Latin America, Europe, Asia (India, China, Japan) Names must be short – easy to type and understand Used popular cities Country capitals or popular destinations Used real cities, streets, postal codes Used obvious fake phone numbers and SSN Used “Surname”, “Postal Code”, and “ID number” How’d I fix it?
Editor's Notes
- #3 You have probably heard about writing for translation This includes ANY customer facing information.
- #4 Data set needs to grow from 50 records to 500
- #5 Can’t use names of athletes, Disney or Marvel characters Need a rich set of diversified names Not every street can be “Main St” Can’t use “Midwest” Can’t use real looking phone numbers or SSN
- #6 Drew from my own ethnic background – Scottish, Irish, English, Dutch, Portuguese, German, French, Cuban = Latin America & Europe Used friends and colleagues names – first or last – not both Pick countries that you are selling in (Japan) Goggled popular baby names and surnames for different countries, ethnic groups To fake phone numbers used numbers like 111-222-3333 or 123-456-7890 To fake SSN used 999-88-7777 or 987-65-4321