This document discusses internationalization (i18n) in software development. It explains that i18n involves abstracting text and formatting out of an application so it can be translated and localized for different languages and regions. The document provides advice on setting up i18n in a Rails application, including creating translation files for different languages and inserting translated text into views. It also compares different methods of setting the locale/language in application routes, recommending scoped routes that specify the locale in the URL path.

1. Welcome to the
Movember DRUG
Meetup!!!
Wifi Network: Neutron-Guest
Wifi Password: welcome2u

2. About me
My name is Katherine
Muedas.
I am from Peru.
Software developer - I love
ruby on rails.
Bachelor Degree in Business
Management.
Passion: Marketing, fashion
and coding.
Also, I love playing Ping Pong,
spending time with family and
traveling.

3. I18n

5. Who can explain why
internationalization is
abbreviated as I18n?

6. I N T E R N A T I O N A L I Z A T I O N
I 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 N

7. What is
Internationalization?

8. What is I18n?
The process of "internationalization" usually means
to abstract all strings and other locale specific bits
(such as date or currency formats) out of your
application. The process of "localization" means to
provide translations and localized formats for these
bits.

9. Why Use It?

10. Why Use It?
Better UX
For Translation… obviously
Makes your product or message more accessible
More customers == MOAR profits

11. Why Use It?
All your static text is in one spot.
Easy to maintain and change
Keep code DRY
Organization

12. Let’s Get Started
Empezemos!

13. Setting Up Your Translation File
/config/locale/en.yml
/config/locale/es.yml

14. In Your Views…
views/home/_header.haml

15. You can do more than just put
words or sentences in the
translation file…

16. Nest translations for organization
config/locale/en.yml
views/home/_about
.html.haml

17. You can change a photo based on
language
config/locale/en.yml
views/home/_header.haml

18. and for spanish…
config/locale/es.yml
views/home/_header.haml

19. You can put HTML inside
config/locale/en.yml

20. Loop through a list
config/locale/en.yml views/about/_about.haml

21. Interpolation
config/locale/es.yml
views/about/_about.haml
webpage

22. Setting the Locale/
Language in your
Routes!

23. Setting locale in your routes
By Sub Domain
en.mysite.com
es.mysite.com peru.mysite.com
Cons
Does not work on Heroku without a domain.
A wild card SSL certificate is more expensive then a single domain certificate
Pros
Supports localization by country or by language
Cookies can be shared across all locales.

24. Setting locale in your routes
By Top-Level Domain
mysite.com
Cons
mysite.pe mysite.ca
Expensive and time consuming to buy many domains.
Cookies cannot be shared across multiple locales
Not a good option for localizing by language
Can not different languages for different countries.
Pros
Supports localization by country.

25. Setting locale in your routes
By Params
mysite.com?locale=en
Params get lost when redirecting
Bad for SEO
Quick to implement
Could be used to store locale
Info in a user cookie
mysite.com?locale=es
Cons
Pros

26. Setting locale in your routes
By Scoping Routes
mysite.com/en/contact
mysite.com/es
Pros
Easy to set up for hosting.
Locale is set in the url route so it will not get lost when you are
navigating to different pages.
The locale is in a better position based on a architectural
standpoint.

27. How to setup scoped
routes ?

28. Application.rb
config/application.rb

29. Routes.rb
Optional language can be passed in
config/routes.rb
/admins/sign_in
/en/admins/sign_in
/es/admins/sign_in

30. Links to change language

31. Thank You!!