- From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
- Date: Thu, 01 Aug 2013 12:52:25 +0900
- To: Andrew Cunningham <lang.support@gmail.com>
- CC: Marcos Caceres <w3c@marcosc.com>, acunningham@slv.vic.gov.au, www-international@w3.org
On 2013/08/01 8:08, Andrew Cunningham wrote: > On 01/08/2013 4:26 AM, "Marcos Caceres"<w3c@marcosc.com> wrote: >> That's good feedback. I guess I'm wondering what the ideal is to cover > the 80% use case? Like I said, the content that is motivating Mozilla to > add this API rarely, if ever, get's localized beyond two sub tags (that's > not to say that it shouldn't, but that's just what we are seeing so far - > though the good news is that developers are localizing content, which is > great!). I'm going to check all the content that we have got so far just to > make sure. >> > > For the 80% mark the approach you've outlined would be sufficient. > > Although localisation takes infrastructure, skills, knowledge and resources > that many languages do not have. > > My main concern is that what is adopted is a mechanism with a certain > degree of future proofing. > > If built on what is done now, may not be compatible with needs of some > languages in future. > > In our own work we've steered away localisation projects in the languages > we work with, because localisation models in use, seem to be missing > components needed. Andrew - Can you say from what you seered away localization projects? For which languages? And what were the components that were missing? Regards, Martin.
Received on Thursday, 1 August 2013 03:53:21 UTC