Localization Beyond Translation

DevRelCon Tokyo

Transcript

1. Ayana Yokota, Developer Advocate at JFrog
2. Ayana Yokota (Twitter: @ihcomega) •Developer Advocate at JFrog •Living in Kyoto temporarily with a lovely robot
3. My Experiences with Development... •Backend web developer at 3 different companies •Developer advocate at JFrog •Administrator of 2 Java communities My talk is based on various perspectives.
4. Localization
5. 3 Tips
6. bad practices •“Translate everything we publish!” •“We never localize. Read in English.”
7. 1. Filter contents “by type” Is it... •a manual? •a press release? •a blog article? •a post on social media?
8. •manual •press release •blog article •post on social media 1. Filter contents “by type”
9. manual •Updated many times •Can be accurate by auto translation •Read when users want PR, blog, social media... • Rarely updated • Comparatively difficult to use auto translation • Read when publishers want (Don’t miss the first glance!) 1. Filter contents “by type”
10. 1. Filter contents “by topic” Is that topic popular in Japan? It is so simple, but you may need somebody who knows Japan to help.
11. Bad practice •“Share our contents on LinkedIn!” •“Advertise on LinkedIn!”
12. 0% 10% 20% 30% 40% 50% 60% 70% 80% Facebook Instagram LinkedIn Usage rate (100% = population) U.S. Japan 2. Know Difference of Social Media Usage
13. •Social media is essential. •This is also cultural, but even people who are not familiar with Japan can know the fact by statistics. 2. Know Difference of Social Media Usage Throw away your assumptions!
14. Bad practice •“It takes much time to review...” •“Publish contents as soon as they get ready!”
15. 3. Think about the timing •Keep contents fresh •Consider time zone
16. •What to choose? •Where to offer? •When to release? Think about them, prioritize your tasks, and give us your great contents! Tips for localization
17. and…
18. Translation is of course important ＼Don’t undermine your efforts!／
19. Thank you!