- From: Internationalization Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Wed, 07 Jan 2015 18:12:05 +0000
- To: public-i18n-core@w3.org
I18N-ISSUE-404: Lang matching undefined [web-packaging] http://www.w3.org/International/track/issues/404 Raised by: Addison Phillips On product: web-packaging http://w3ctag.github.io/packaging-on-the-web/#fragment-identifiers In section 3.4, there is this text about the 'lang' identifier: -- If the lang parameter is specified, the candidate parts are further filtered down to only those that have a Content-Language header whose media type matches the language tag provided by the lang parameter. -- What "matches" means is undefined. An exact match may not be appropriate? See RFC 4647 in BCP 47 for more details. There also is no example provided and probably there should be one. For those reading only this Issue, the "Content-Language header" mentioned is part of the file format. The idea of language negotiation using fragments probably should be considered here. You might have a fragment with "lang=en" and several parts: Content-Language: en-US ... Content-Language: en-GB ... Content-Language: en-AU ... Are any or all selected? Should the fragment Id be expected to be more explicit (using Lookup style matching)?
Received on Wednesday, 7 January 2015 18:12:07 UTC