W3C home > Mailing lists > Public > www-international@w3.org > April to June 2015

Re: [manifest] i18n: No localization model; [I18N-ISSUE-412]

From: Marcos Caceres via GitHub <sysbot+gh@w3.org>
Date: Fri, 15 May 2015 15:48:57 +0000
To: www-international@w3.org
Message-ID: <issue_comment.created-102442930-1431704936-sysbot+gh@w3.org>
> @marcoscaceres I don't know that it ended in sadness and confusion, 
but the model Widgets uses was somewhat complex (more so because there
 were actually TWO models--one in the configuration file and other 
that used directory structure)

Oh, what I meant to say was that the "mix and matching" (some could be
 lolcalized, some could not) of the element localization model became 
confusing. Overall, I think the model was awesome. The mistake was 
just not making everything localizable. I also think the directory 
localization model was great. 

> I don't care for the "solution" of generating multiple manifests 
because there doesn't seem to be a mechanism in place for finding out 
about which manifests are available and selecting the "right" one for 
the job (aka "language negotiation")... and I note that in my day job 
I have apps that are localized into several languages and don't have a
 different start_url for each language.

Agree. This is also what I'm worried about. I'm working with Mozilla's
 content services team, who currently targets 26 languages with their 
products, and they also just localize using geoip on the server (not 
great, but good enough in most cases).   

GitHub Notif of comment by marcoscaceres
See https://github.com/w3c/manifest/issues/338#issuecomment-102442930
Received on Friday, 15 May 2015 15:48:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:39 UTC