3 ms·
Shameless plug: I've been working on a i18n / localization SaaS for about a year now called Localize.js (https://localizejs.com https://localizejs.com), with th
by cj 12y ago
Shameless plug: I've been working on a i18n / localization SaaS for about a year now called Localize.js (https://localizejs.com https://localizejs.com), with the goal of automating the localization process. It works by scanning the DOM for translatable content, and injecting translations client side, on-the-fly (happens fast enough that the user never sees the text in the original language).
Internationalization is a notoriously difficult problem, and it's great to see some native API browser support. We definitely have a long way to go.
- spacefight 12y agoI might be a potential target of your SaaS for one of my not yet fully localized web based applications. But there is just no way that I can src="" your .js directly into my web application and therefore access to the DOM. Could I still use your service somehow?
- cj 12y agoLocalize.js requires adding our Javascript library to your page (like you do with Google Analytics, Optimizely, Mixpanel, etc). If you don't mind me asking, what is preventing you from adding a line of js code to your website?
- spacefight 12y agoSecurity guidelines to not have any 3rd party JS.
- chrisrogers 12y agoYou could audit the code yourself and self-host.
- spacefight 12y agoSure, if the license permits that.
- thomasfoster96 12y agoLocalize.js looks awesomely convenient. I've just spent much of the past 10 days trying to think of how to internationalise and translate a web app. I'd resorted to writing my own dodgy JS client side solution, backed by something on the server side, but I'll take a good look at your solution now that I've seen it!