4 ms·

Huh. Localize.js sounds really cool. Fantastic idea. Can you explain your example a little more? What would translators see in this case for Arabic; would t

Huh. Localize.js sounds really cool. Fantastic idea. Can you explain your example a little more? What would translators see in this case for Arabic; would they need to provide three translations? And if there were two variables, nine translations? "Localization" also implies a lot more than just translation. Does Localize.js handle work like culture-specific number and date formatting? Different collation of records for different languages? How does it identify application-generated text versus user data (eg. on a blog, does it translate blog comments entered by readers, or just text like "Please enter a comment below")?

cj 12y ago
> What would translators see in this case for Arabic The Arabic translator would have to provide 6 different translations, one translation for each plural form. > And if there were two variables, nine translations? We currently only allow for pluralization based on one variable per phrase. We're hoping address this soon. > Does Localize.js handle work like culture-specific number and date formatting? We usually recommend libraries like moment.js to handle date localization. They do a fantastic job at localizing dates. > How does it identify application-generated text versus user data We provide a set of HTML markers that you can use to indicate to Localize.js that certain text should be translated. For example... <div class="blog-comments" notranslate> [...] </div> https://localizejs.com/docs/usage/variables https://localizejs.com/docs/usage/variables