ISSUE-404: Lang matching undefined

Lang matching undefined

Raised by:
Addison Phillips
Opened on:

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)?
Related Actions Items:
No related actions
Related emails:
  1. Weekly github digest (Tracker items) (from on 2019-11-06)
  2. Daily github digest (WG INTERNAL review issues) (from on 2019-11-01)
  3. Issues for review during tomorrow's telecon (from on 2017-10-04)
  4. Daily github digest (WG INTERNAL review issues) (from on 2017-09-26)
  5. FOR REVIEW: pending and close items for Thursday (from on 2017-09-25)
  6. Daily github digest (WG INTERNAL review issues) (from on 2017-09-23)
  7. [minutes] Internationalization telecon 2016-07-21 (from on 2016-07-21)
  8. Review list page improved (from on 2016-07-15)
  9. RE: [Packaging] language tag reference and language tag matching [I18N-ISSUE-404] (from on 2015-09-23)
  10. [minutes] Internationalization telecon 2015-09-17 (from on 2015-09-23)
  11. I18N-ISSUE-404: Lang matching undefined [web-packaging] (from on 2015-01-07)

Related notes:

Richard Ishida, 17 Mar 2016, 13:22:20

Display change log ATOM feed

Addison Phillips <>, Chair, Richard Ishida <>, Bert Bos <>, Fuqiao Xue <>, Atsushi Shimono <>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 404.html,v 1.1 2023/07/19 12:02:03 carcone Exp $