![So What did we do?
Started a POC on an [In]Day to verify the cost of creating Xmessage in Ruby
Agreed on manual extraction to ensure high quality
Decided to write custom properties file parser and custom i18n backend to use
them](https://image.slidesharecdn.com/untitledpresentation-160629220640/75/i18n-tech-talk-9-2048.jpg)
Uploaded byHitesh Sharma
i18n tech talk
SlideShare was using a third party localization service that posed a security risk, so they moved to an internal localization stack. This involved manually extracting over 700 templates to property files, writing a custom parser and backend to support multiple languages, and localizing the templates within two days through documentation, training, and assigning tickets. Testing and involvement from the localization engineering team helped ensure high quality.
More Related Content
i18n tech talk
- 1. SlideShare i18n Moving offSmartling
- 2. What’s all thisabout? SlideShare was using a third party to serve localized pages at runtime This was identified as a big security loophole by internal security team
- 3. Why security hada problem?
- 4. What’s the fix? Moveto internal localization stack. Simple Isn’t It?
- 5. Scale of problem 75Million active users ~700 templates LinkedIn and SlideShare stack differences as SlideShare is built on Ruby
- 6. SlideShare web apprepo is not a Multiproduct Xmessage format is only supported format by LI i18n infra Ruby doesn’t supports .properties files natively SlideShare’s old version of ruby isn’t very encoding friendly No native unicode escape support No use of languages packs before ……….
- 7. So How todo it? Initial Plan Create some magic solution to crawl all code, find strings, generate properties and send to i18n team
- 8. What would itlead to? Confused Engineers Missed strings Lower quality extraction and translation missing all goodies like pluralizations, names and dates formatters and more.
- 9. So What didwe do? Started a POC on an [In]Day to verify the cost of creating Xmessage in Ruby Agreed on manual extraction to ensure high quality Decided to write custom properties file parser and custom i18n backend to use them
- 10.
- 11. Main Focus points Noresistance should be added in development process Minimum or no new method calls Keep response time unaffected No significant delays in shipping code to production. And remove Smartling ASAP as it’s a security issue
- 12. Main Focus points Noresistance should be added in development process Minimum or no new method calls Keep response time unaffected No significant delays in shipping code to production. And remove Smartling ASAP as it’s a security issue
- 13. No resistance indev process Created New repo for storing translations but tied it up with Main repo using Git Hooks. Pre-rebase and post-merge hooks ensure your translations are latest on dev without any need to rebase
- 14. Main Focus points Noresistance should be added in development process Minimum or no new method calls Keep response time unaffected No significant delays in shipping code to production. And remove Smartling ASAP as it’s a security issue
- 15. No New methodcalls added Everything happens behind I18n.t Fetch from properties, Xmessage interpolation, Name, Date formatting all behind the same method call
- 16. Main Focus points Noresistance should be added in development process Minimum or no new method calls Keep response time unaffected No significant delays in shipping code to production. And remove Smartling ASAP as it’s a security issue
- 17. Xmessage Benchmarking Generally apage has ~10 strings with placeholders
- 18. Main Focus points Noresistance should be added in development process Minimum or no new method calls Keep response time unaffected No significant delays in shipping code to production. And remove Smartling ASAP as it’s a security issue
- 19. Need to createtwo RB’s Need to push properties files separately but no deploy step for translations repo keeps the process smooth
- 20. How 700 templateswere localized? Created detailed documentation for team Conducted a Hands-on/demo to teach devs new workflow Created ~700 tickets using JIRA API Did two string extraction bashes and rewarded whoever localized the most Most of the issues created by L10n team were resolved within two days
- 21. Created detailed documentation Theteam was new to this stack Never created properties files before Never used Xmessage placeholders before New flow for pushing translations
- 22.
- 23. Involved L10n teamat every step
- 24. In Documentation Reviews L10nengineering team reviewed our documentation and suggested needed edits before we released it to team
- 25. Code Reviews byL10n team Did our code reviews - Masha’s review rate was much higher than mine Code Reviews by L10n team helped us catch errors much early and iterate faster Every code review taught us best practices and raised the quality bar amongst the team
- 26. Decided on complexpatterns much earlier user.message={:type,map,MEMBER#Hello, {:value,name,full}|COMPANY#Hello, {:value}|DEFAULT_TEXT#Hello, {:user_login}}
- 27. Avoid XSS At everystep ensure that you don’t insert broken HTML and take special care of quotes Do it before security finds it
- 28. Write tons oftests 80 UITF tests for EN ~400 Tests for Xmessage 40 tests for new i18n backend Added 80 for each of the languages which SlideShare supports
- 29. Be Available Most ofthe queries resolved on slack Most of the discussions done on slack
- 30. Resolve issues assoon as they come Most of the issues resolved within 1-2 days to maintain the pace
- 31.
- 32.