7
Locales and Language Tags meet Conversations in Prague… – Language tags are being locale identifiers anyway… – Not going to need a big new thing… – Just a few things to fix… … we can do this really fast

22
Problems Matching – Does en-US match en-Latn-US ? Tag Choices – Users have more to choose from. Implementations – More to do, more to think about – (easier to parse, process, support the good stuff)

23
Tag Matching Uses Language Ranges in a Language Priority List to select sets of content according to the language tag. Basically what we already had, but in one place. Three Schemes – Basic Filtering – Extended Filtering – Lookup

34
What Do I Do (Content Author)? Not much. – Existing tags are all still valid: tagging is mostly unchanged. – Resist temptation to (ab)use the private use subtags. If your language typically has script variations (or if you content exhibits it): – ONLY THEN tag content with script subtag(s) Script subtags only apply to a small number of languages: zh, sr, uz, az, mn, and a very small number of others.

35
What Do I Do (Programmer)? Check code for compliance with 4646 – Decide on well-formed or validating implementation (note requirements well) – Implement suppress-script – Change to using the registry – Bother infrastructure folks (Java, MS, Mozilla, etc) to implement the standard

36
What Do I Do (End-User)? Check and update your language ranges. Tag content wisely.