Thanks Tony, this investigation is very valuable not just for GPII, but also for various other i18n concerns for Infusion-related projects. Great writeup.
From: Architecture <[email protected]<mailto:[email protected]>> on behalf of Tony Atkins <[email protected]<mailto:[email protected]>> Date: Friday, July 28, 2017 at 10:00 AM To: "[email protected]<mailto:[email protected]> Architecture" <[email protected]<mailto:[email protected]>> Subject: Re: [Architecture] Technology Evaluation: Supporting i18n in Javascript.... Hi, All: As we agreed, I investigated two candidates for handling internationalising strings in Infusion components and wrote up the results in a technology evaluation on the wiki: https://wiki.gpii.net/w/Technology_Evaluation_-_Internationalising_and_Localising_UI_strings I hope to discuss this at the next architecture meeting and/or PCP meeting depending on the level of interest. Please review and comment. Cheers, Tony On Fri, Jul 21, 2017 at 12:23 PM, Tony Atkins <[email protected]<mailto:[email protected]>> wrote: Hi, All: Just to follow up, in yesterday's PCP meeting, we agreed that I would create a simple demonstration of the top candidates in the Technology Evaluation shared earlier. In starting work on this today, I realised that although "counterpart" claimed browser support, they meant via browserify<http://browserify.org>, which I missed in my initial review. IMO that adds enough complexity to take them off the short list of candidates. I will proceed to flesh out a demo comparing the following: 1. Infusion 2. i18next<https://github.com/i18next/i18next> 3. intl.js<http://github.com/andyearnshaw/Intl.js> I plan to write something up next week for us to review on the list, and in the next PCP meeting. Cheers, Tony On Thu, Jul 20, 2017 at 1:31 PM, Tony Atkins <[email protected]<mailto:[email protected]>> wrote: Hi, All: As part of the discussions around the PCP API, we have had a few side discussions about how best to support internationalisation, specifically displaying different strings in the UI depending on the user's preferred language. In the JIRA ticket<https://issues.gpii.net/browse/GPII-2444> related to adding i18n support to gpii-handlebars, Steve asked that we look around for existing approaches. With that in mind, I took a few minutes today to review as many options as I could find, and wrote a new Technology Evaluation on the wiki<https://wiki.gpii.net/w/Technology_Evaluation_-_Internationalising_and_Localising_UI_strings>. I would like to discuss the list at least briefly in tonight's PCP meeting, but whether or not you're attending, you are more than welcome to review and comment. I want to confirm that we have good set of requirements and candidates to evaluate before proceeding further. Thanks in advance for your help. Cheers, Tony
_______________________________________________ Architecture mailing list [email protected] http://lists.gpii.net/mailman/listinfo/architecture
