Internationaliz(s)ation m(p)ain pointsАрхитектуры, масштабируемость
Open source-minded web developer with a strong belief in openness of the web in addition to 10+ year experience in software development.
Developing Adblock Plus Full-Time, working on my own projects the rest of the time.
Github: https://github.com/Manvel
Gitlab: https://gitlab.com/saroyanm
https://twitter.com/saroyanm
https://www.linkedin.com/in/saroyanm/
When it comes to the Multilingual websites or project creation, the lack of complete standards for Internationalization(i18n) implementation makes Framework, CMS and/or tools choice not a trivial task. Managing translations might become pain in the ass if you won’t make it right from the beginning.
Avoiding common localization(l10n) issues when developing Multilingual websites will lead into huge growth opportunities for your project, understanding crucial l10n and i18n details, will help you choose the right architecture solution for your project and understand why most of the existing solutions are "not a go" for your project.
My background.
I'm experienced in developing project(s) that does support more than 80 different languages and I’m deeply involved in defining translations management process for that project (which is active on more than 100 million devices), so I'm ready to share with you all the main and pain points of #i18n, #l10n and #a11y.
