for review & agenda+: An Introduction to Multilingual Web Addresses
some progress on [I18N-ACTION-445] (font subsetting)
Wiki page for language/direction metadata proposal [I18N-ACTION-448]
"sticky" language negotiation article
[Bug 16166] i18n-ISSUE-138: Make lang and xml:lang synonyms in HTML5
I18N-ACTION-450: Ask dom to change settings to notify of all traffic on our issues via email
I18N-ACTION-449: Remind wg membership to read and be ready to discuss http://r12a.github.io/docs/bidi-plain-text/index.html
I18N-ACTION-448: Write a proposal to the working group for options in handling language and direction metadata in cases such as mediastream labels
I18N-ACTION-447: Publish updated version of klreq
[Bug 16970] i18n-ISSUE-105: compatibility caseless matching
[Bug 16966] i18n-ISSUE-98: 13 month calendar support
[Bug 16965] i18n-ISSUE-97: Allowing a page to request a given locale (4.10.7.2 normativity)
[Bug 16963] i18n-ISSUE-94: Allowing culturally specific week rules
[Bug 18162] IDN email addresses should be converted to Punycode before validating them
[Bug 16979] i18n-ISSUE-119: provide example of language detection fallback
[Bug 16960] i18n-ISSUE-89: Time zones and local dates and times
[Bug 16959] i18n-ISSUE-88: local/floating date terminology
[Bug 17864] i18n-ISSUE-118: explicitly undefined language
[Bug 16978] i18n-ISSUE-118: explicitly undefined language
[Bug 16166] i18n-ISSUE-138: Make lang and xml:lang synonyms in HTML5
I18N-ISSUE-479: Marking tables as right-to-left in the media type [tabular-data-model]
[Bug 16166] i18n-ISSUE-138: Make lang and xml:lang synonyms in HTML5
[Bug 18162] IDN email addresses should be converted to Punycode before validating them
I18N-ISSUE-478: determining cell text direction [tabular-data-model]
I18N-ISSUE-477: default value of direction [tabular-data-model]
RE: Advice on MediastreamTrack.label
I18N-ACTION-446: Ask ivan about his experience with using github issues and best practices and report back
I18N-ACTION-445: Check out using a subsetting web font for example chars
I18N-ISSUE-476: International taxation and delivery rates/times [web-payments-use-cases]
I18N-ACTION-444: Write to w3 parties requesting that the publication tool be updated to support note track documents after richard identifiers who to ping
Review of Track Issues for Best Practices (Part VII)
Not the editor's copy of charmod updated
I18N-ISSUE-475: Do Unicode Strings get normalized when placed into RDF â?? [tabular-data-rdf]
I18N-ISSUE-474: What are the rules for string equality when column names are matched with annotations â?? [tabular-data-rdf]
I18N-ISSUE-473: Can RDF data be generated from non UTF-8 encoded CSV data â?? [tabular-data-rdf]
I18N-ISSUE-472: geographic variation of terms or availability â?? [web-payments-use-cases]
I18N-ISSUE-471: identify time zone dependent vs. independent cases [web-payments-use-cases]
[Media Capture] Human readable message not localizable? [I18N-ISSUE-465]
[Media Capture] 'label' needs direction and language metadata [I18N-ISSUE-464]
I18N-ISSUE-470: Cashback processing [web-payments-use-cases]
I18N-ISSUE-469: More multicultural examples [web-payments-use-cases]
I18N-ACTION-443: Contact interested parties about starting an arabic script layout task force
I18N-ACTION-442: Remind working group to read new process document for adoption voting at next week's teleconference
I18N-ACTION-441: Write back to fantasai/csswg and propose a way to organize layout information
I18N-ACTION-440: Follow up with daniel about ethiopic information
I18N-ISSUE-468: Do Unicode Strings get normalized when placed into JSON data â?? [tabular-data-json]
I18N-ISSUE-467: What are the rules for string equality when column names are matched with annotations â?? [tabular-data-json]
I18N-ISSUE-466: Can JSON data be generated from non UTF-8 encoded CSV data â?? [tabular-data-json]
FYI: First Public Working Draft of Web Payments Use Cases
I18N-ISSUE-465: Human readable message not localizable? â?? [media-capture-and-streams]
I18N-ISSUE-464: 'label' needs direction and language metadata [media-capture-and-streams]
I18N-ISSUE-463: Language metadata elsewhere than for columns [tabular-data-model]
I18N-ISSUE-462: Human readable formats for numeric percentages â?? [tabular-data-model]
I18N-ACTION-439: Send message to member list polling for document priority so we can schedule actions
I18N-ACTION-438: Edit grc documents, create a github in your account, add top material, and bring to wg for review
I18N-ACTION-437: Create article about the time zone proposal
Review of track issues for best practices (Part VI)
I18N-ACTION-436: Send richard flat version of ltli for publication
I18N-ACTION-435: Publish new wd of ltli
I18N-ACTION-434: Write to klreq editors seeking response on current edits and possible future participation
Review of tracker issues for best practices (Part V)
I18N-ACTION-433: Send ltli to richard for adding to github
I18N-ACTION-432: Amend our tpac wbs to request a room for tpac
I18N-ACTION-431: Send new message to www-international looking for a name for our counter styles note
I18N-ACTION-430: Contact editors of klreq for comments and seeking additional support
I18N-ACTION-429: Publish new wd of korean layout requirements
I18N-ISSUE-461: Wrong caption? [klreq]
I18N-ISSUE-460: 4.3.7 Inter-char restrictions typo [klreq]
Comments on: W3C Process2015
- RE: Comments on: W3C Process2015
- Re: Comments on: W3C Process2015
- RE: Comments on: W3C Process2015
- Announcing FPWD pubs on p-review-announce [Was: Re: Comments on: W3C Process2015]
- Re: Announcing FPWD pubs on p-review-announce [Was: Re: Comments on: W3C Process2015]
- Re: Announcing FPWD pubs on p-review-announce [Was: Re: Comments on: W3C Process2015]
- RE: Announcing FPWD pubs on p-review-announce [Was: Re: Comments on: W3C Process2015]
- Re: Announcing FPWD pubs on p-review-announce [Was: Re: Comments on: W3C Process2015]
- RE: Announcing FPWD pubs on p-review-announce [Was: Re: Comments on: W3C Process2015]
- RE: Announcing FPWD pubs on p-review-announce [Was: Re: Comments on: W3C Process2015]
- Re: Announcing FPWD pubs on p-review-announce [Was: Re: Comments on: W3C Process2015]
- RE: Announcing FPWD pubs on p-review-announce [Was: Re: Comments on: W3C Process2015]
- Re: Announcing FPWD pubs on p-review-announce [Was: Re: Comments on: W3C Process2015]
- Re: Announcing FPWD pubs on p-review-announce [Was: Re: Comments on: W3C Process2015]
- Announcing FPWD pubs on p-review-announce [Was: Re: Comments on: W3C Process2015]