Opened 12 years ago

Closed 11 years ago

#113 closed design (fixed)

language tag matching (Accept-Language) vs RFC4647

Reported by: julian.reschke@… Owned by: julian.reschke@…
Priority: Milestone: 04
Component: p3-payload Severity: Active WG Document
Keywords: Cc:

Description

Matching of language tags is defined in RFC4647.

Should the definition of "Accept-Language" just delegate to that specification?

Attachments (2)

i113.diff​ (3.0 KB) - added by julian.reschke@… 11 years ago.
Proposed patch.
i113.2.diff​ (3.2 KB) - added by julian.reschke@… 11 years ago.
Updated proposal.

Download all attachments as: .zip

Change History (5)

comment:1 Changed 11 years ago by julian.reschke@…

  • Milestone changed from unassigned to 04
  • Owner set to julian.reschke@…

See <​http://lists.w3.org/Archives/Public/ietf-http-wg/2008JulSep/0167.html>.

comment:2 Changed 11 years ago by fielding@…

It can delegate by specifying a particular matching algorithm defined by RFC4647.

Changed 11 years ago by julian.reschke@…

Proposed patch.

Changed 11 years ago by julian.reschke@…

Updated proposal.

comment:3 Changed 11 years ago by julian.reschke@…

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in [303]:

Resolve #113: refer to RFC4647 for definition of language ranges and matching (closes #113).

Note: See TracTickets for help on using tickets.