We're updating the issue view to help you get more done. 

To complete BCP 47 support add API for well-formedness & validity

Description

For full RFC-3066bis support, we need APIs that determine

a) well-formedness
b) validity

For well-formedness, see the spec (currently at
http://www.inter-locale.com/ID/draft-phillips-langtags-08.html, but we don't
anticipate changes). It needs to match both the ABNF
(http://www.inter-locale.com/ID/draft-phillips-langtags-08.html#syntax) and some
additional rules.

The data in RFC-3066bis (currently at
http://users.adelphia.net/~dewell/lstreg.txt) can be used to assess validity.
May change somewhat before the RFC goes final, but the changes should be
limited.

It would be possible to determine validity at a point in time, not just for the
latest snapshot of the registry that we picked up in ICU. That would require
keeping one more piece of information per entry. This could be compacted into a
byte or two, however.

We will also want the variants that we use in ICU to get registered.

Environment

Status

Assignee

Mark Davis

Reporter

Mark Davis

Labels

Time Needed

Weeks

tracCc

emmons,mark,markus,pedberg,roubert,srl,yoshito

tracCreated

Nov 15, 2004, 3:14 AM

tracOwner

mark

tracProject

all

tracReporter

mark

tracResolution

fixed

tracReviewer

yoshito

tracStatus

closed

tracWeeks

2

Components

Fix versions

Priority

medium