www-international@w3.org from April to June 2016 by date

Tuesday, 28 June 2016

• [minutes] Arabic layout telecon 2016-06-28 ishida@w3.org
• [minutes] Arabic layout telecon 2016-06-21 ishida@w3.org

Thursday, 23 June 2016

• [minutes] Internationalization telecon 2016-06-23 ishida@w3.org

Tuesday, 21 June 2016

• [minutes] Internationalization telecon 2016-06-21 ishida@w3.org

Monday, 20 June 2016

• [csswg-drafts] Issue: [css-text-3] Line breaking opportunities at the boundary of a white-space:pre inline element marked as i18n r12a via GitHub
• Re: [presentation-api] list of displays: should it address display name, language, etc.? Tomoyuki Shimizu via GitHub

Friday, 17 June 2016

• For review: Time & date, Essential concepts ishida@w3.org
• Closed: [bp-i18n-specdev] Change the rule for assuming text direction from language r12a via GitHub
• Closed: [bp-i18n-specdev] Change rule to allow surrogates r12a via GitHub
• Closed: [bp-i18n-specdev] Possibly soften requirements related to logical order over visual order. r12a via GitHub
• Closed: [bp-i18n-specdev] Consider combining defining language value checklist rules r12a via GitHub

Thursday, 16 June 2016

• FOR REVIEW: Closing Web Annotation Model & Annotation Vocab tracker items ishida@w3.org
• [bp-i18n-specdev] mention the language subtag registry aphillips via GitHub
• [bp-i18n-specdev] improve description of BCP 47 aphillips via GitHub
• Closed: [bp-i18n-specdev] Spell out internationalization in place of 'i18n' aphillips via GitHub

Wednesday, 15 June 2016

• [bp-i18n-specdev] establish a glossary? aphillips via GitHub
• [bp-i18n-specdev] Change rule to allow surrogates stevenatkin via GitHub
• [bp-i18n-specdev] Consider creating a rule regarding rejecting invalid surrogate pairs stevenatkin via GitHub
• Closed: [browser-payment-api] Add section on internationalization Adrian Hope-Bailie via GitHub
• [bp-i18n-specdev] Possibly soften requirements related to logical order over visual order. stevenatkin via GitHub
• [bp-i18n-specdev] Change the rule for establishing base direction stevenatkin via GitHub
• [bp-i18n-specdev] Change the rule for assuming text direction from language stevenatkin via GitHub
• [bp-i18n-specdev] Consider combining defining language value checklist rules stevenatkin via GitHub
• [bp-i18n-specdev] Mention inheritance when defining default text processing language. stevenatkin via GitHub
• Closed: [html] why is "content language" pragma processing not equivalent to HTTP Content-Language? Arron Eicholz via GitHub

Tuesday, 14 June 2016

• Re: [presentation-api] list of displays: should it address display name, language, etc.? François Daoust via GitHub
• Re: [presentation-api] list of displays: should it address display name, language, etc.? aphillips via GitHub
• Re: [presentation-api] list of displays: should it address display name, language, etc.? François Daoust via GitHub

Monday, 13 June 2016

• [html] Issue: Remove the use of printable character from accessKey attribute. marked as accessibility chaals via GitHub

Thursday, 9 June 2016

• [minutes] Internationalization telecon 2016-06-09 ishida@w3.org
• Fwd: Social Web WG reviews ishida@w3.org
• [html] Issue: Define or remove the use of the term Plain Unicode String marked as i18n r12a via GitHub
• [html] Issue: datetime-local needs a health warning for floating to incremental time conversion (was I18N-ISSUE-89) marked as i18n chaals via GitHub
• [html] Issue: Allow a page to request a given locale (was bug 16965) marked as i18n chaals via GitHub

Tuesday, 7 June 2016

• [csswg-drafts] Issue: [css-text-decor-3] behavior of text-decoration + text-emphasis marked as i18n r12a via GitHub

Monday, 6 June 2016

• [html] Issue: Default <details> heading should be localized marked as i18n chaals via GitHub

Friday, 3 June 2016

• Closed: [web-annotation] Use of dc:language Rob Sanderson via GitHub
• Closed: [web-annotation] Normalisation of Text Quote Selector Rob Sanderson via GitHub
• Closed: [web-annotation] Model is defined in terms of IRIs; Protocol with URI Rob Sanderson via GitHub
• Closed: [web-annotation] Request header and language negotiation Rob Sanderson via GitHub
• Closed: [web-annotation] (model) have a note on logical and visual order of text for text quote selector implementations Rob Sanderson via GitHub
• Closed: [web-annotation] white space normalisation Rob Sanderson via GitHub
• Closed: [web-annotation] Base direction for annotations Rob Sanderson via GitHub
• Closed: [web-annotation] Remove "and so forth", clarify utf-8 encoding Rob Sanderson via GitHub
• Closed: [web-annotation] exactly 0 or 1 language(s) Rob Sanderson via GitHub
• Closed: [web-annotation] 'generated' and 'modified' should use UTC by default Rob Sanderson via GitHub
• Closed: [web-annotation] TimeState, generated, and modified should recommend all values use UTC Rob Sanderson via GitHub
• Closed: [web-annotation] (model) vague definition of character position for text position selector Rob Sanderson via GitHub

Thursday, 2 June 2016

• [html] Issue: Is input type=datetime implemented? marked as i18n r12a via GitHub
• [minutes] Internationalization telecon 2016-06-02 ishida@w3.org

Wednesday, 1 June 2016

• Closed: [html] value on button in submit state is translateable Philippe Le Hegaret via GitHub

Friday, 27 May 2016

• Closed: [html] Type attribute for ordered lists should be obsolete but conforming Léonie Watson via GitHub
• [web-annotation] Issue: Model is defined in terms of IRIs; Protocol with URI marked as i18n-review r12a via GitHub

Thursday, 26 May 2016

• Updated article: Changing an HTML page to Unicode ishida@w3.org
• [minutes] Internationalization telecon 2016-05-26 ishida@w3.org
• Closed: [predefined-counter-styles] Mixed content in chrome, respec fails r12a via GitHub

Wednesday, 25 May 2016

• [predefined-counter-styles] Mixed content in chrome, respec fails Tab Atkins Jr. via GitHub
• [predefined-counter-styles] Should we add more Latin counter styles? r12a via GitHub

Tuesday, 24 May 2016

• Request for review Phil Archer
• [html] Issue: Tighten up usages of "compatibilty caseless" comparisons used in the spec marked as i18n r12a via GitHub

Sunday, 22 May 2016

• Closed: [web-annotation] (model) update reference for language tags: BCP47 instead of RFC5646 Ivan Herman via GitHub

Saturday, 21 May 2016

• [web-annotation] Issue: Remove "and so forth", clarify utf-8 encoding marked as editor_action Rob Sanderson via GitHub

Friday, 20 May 2016

• [web-annotation] Issue: Reference to text encoding in spec perhaps not appropriate marked as i18n-review r12a via GitHub
• Reminder about following i18n issues ishida@w3.org

Thursday, 19 May 2016

• [web-annotation] Issue: Use of dc:language marked as vocab Rob Sanderson via GitHub

Wednesday, 18 May 2016

• RE: Gtihub disruptions Tex Texin
• Re: Gtihub disruptions ishida@w3.org
• Gtihub disruptions ishida@w3.org
• [csswg-drafts] Issue: [css-fonts] Specifying changes to parameters for fallback fonts marked as i18n r12a via GitHub
• [csswg-drafts] notifications coming ishida@w3.org
• Closed: [csswg-drafts] test r12a via GitHub
• [csswg-drafts] Issue: test marked as i18n r12a via GitHub
• Re: Code units or code points for text pointers? ishida@w3.org
• Closed: [web-annotation] (model) make definition of a character more precise Ivan Herman via GitHub
• Closed: [web-annotation] 'generated' and 'modified' date/time properties specific reference and format Ivan Herman via GitHub
• [web-annotation] Issue: Base direction for annotations marked as editor_action Ivan Herman via GitHub
• Code units or code points for text pointers? ishida@w3.org

Tuesday, 17 May 2016

• Re: The HTML q element can sometimes be useful. Discuss. Gunnar Bittersmann
• Closed: [web-annotation] Defaults for an Annotation Collection Ivan Herman via GitHub
• Closed: [web-annotation] String body must not have a language associated? Ivan Herman via GitHub
• Closed: [web-annotation] How is language assigned to an annotation? Ivan Herman via GitHub
• Closed: [web-annotation] (model) missing mechanism to express language preferences in the intendend audience field Ivan Herman via GitHub
• [web-annotation] Issue: String body must not have a language associated? marked as i18n-review r12a via GitHub
• [web-annotation] Issue: Normalisation of Text Quote Selector marked as i18n-review r12a via GitHub
• [web-annotation] Issue: white space normalisation marked as i18n-review r12a via GitHub
• [web-annotation] Issue: Request header and language negotiation marked as i18n-review r12a via GitHub
• [web-annotation] Issue: Defaults for an Annotation Collection marked as i18n-review r12a via GitHub
• [web-annotation] Issue: How is language assigned to an annotation? marked as i18n-review r12a via GitHub
• [web-annotation] Issue: 'generated' and 'modified' date/time properties specific reference and format marked as i18n-review r12a via GitHub
• [web-annotation] Issue: 'generated' and 'modified' should use UTC by default marked as i18n-review r12a via GitHub
• [web-annotation] Issue: TimeState, generated, and modified should recommend all values use UTC marked as i18n-review r12a via GitHub

Thursday, 12 May 2016

• [html] Issue: example of language detection fallback, no mention of pragma marked as i18n Arron Eicholz via GitHub

Wednesday, 11 May 2016

• RE: HTML5.1 review Léonie Watson
• Closed: [browser-payment-api] Should the merchant be able to request your email and recipient phone number Ade Bateman via GitHub
• [minutes] Internationalization telecon 2016-05-05 ishida@w3.org
• [minutes] Internationalization telecon 2016-04-28 ishida@w3.org
• [minutes] Internationalization telecon 2016-04-14 ishida@w3.org
• Re: The HTML q element can sometimes be useful. Discuss. Ivan Herman
• RE: HTML5.1 review Phillips, Addison
• Re: HTML5.1 review ishida@w3.org
• RE: HTML5.1 review Léonie Watson

Tuesday, 10 May 2016

• RE: HTML5.1 review Phillips, Addison
• HTML5.1 review Léonie Watson
• Re: The HTML q element can sometimes be useful. Discuss. Bert Bos

Monday, 9 May 2016

• For review: New issues in the tracker for Web Annotations ishida@w3.org
• Re: [web-annotation] Issue: exactly 0 or 1 language(s) marked as model John Cowan
• [web-annotation] Issue: exactly 0 or 1 language(s) marked as model r12a via GitHub
• [web-annotation] Issue: (model) missing mechanism to express language preferences in the intendend audience field marked as i18n-review Felix Sasaki via GitHub
• [web-annotation] Issue: (model) have a note on logical and visual order of text for text quote selector implementations marked as i18n-review Felix Sasaki via GitHub
• [web-annotation] Issue: (model) make definition of a character more precise marked as model Felix Sasaki via GitHub
• [web-annotation] Issue: (model) update reference for language tags: BCP47 instead of RFC5646 marked as model Felix Sasaki via GitHub
• [web-annotation] Issue: (model) vague definition of charactor position for text position selector marked as i18n-review r12a via GitHub

Saturday, 7 May 2016

• Re: faq suggestions ishida@w3.org

Friday, 6 May 2016

• RE: github and mailing lists (was: Re: The HTML q element can sometimes be useful. Discuss.) Tex Texin
• github and mailing lists (was: Re: The HTML q element can sometimes be useful. Discuss.) Martin J. Dürst

Thursday, 5 May 2016

• [html] Issue: Improve documentation of i18n issues with input type="number" marked as Editorial chaals via GitHub
• [Bug 26417] i18n-ISSUE-343: Type attribute on ol bugzilla@jessica.w3.org

Wednesday, 4 May 2016

• Closed: [html] html and head elements should not get new attributes Travis Leithead via GitHub
• [html] Issue: Type attribute for ordered lists should be obsolete but conforming marked as technical improvement chaals via GitHub

Tuesday, 3 May 2016

• Comments on the q element: change in notification behaviour ishida@w3.org
• [html] Issue: How to handle legacy Ruby content that may use <rbc> marked as i18n chaals via GitHub
• [browser-payment-api] Issue: Add section on internationalization marked as HR: i18n r12a via GitHub
• [html] Issue: add warning/advice about lang attribute use marked as i18n r12a via GitHub
• [html] Issue: make any element with an explicit lang attribute (and no dir attribute) bidi-isolated by default marked as i18n r12a via GitHub
• [html] Issue: value on button in submit state is translateable marked as i18n r12a via GitHub
• [html] Issue: why is "content language" pragma processing not equivalent to HTTP Content-Language? marked as i18n r12a via GitHub
• [html] Issue: Sort out issues with [inputmode] marked as i18n r12a via GitHub
• [html] Issue: html and head elements should not get new attributes marked as i18n r12a via GitHub
• [html] Issue: Default styling for q element marked as i18n r12a via GitHub

Saturday, 30 April 2016

• RE: The HTML q element can sometimes be useful. Discuss. Tex Texin
• Re: The HTML q element can sometimes be useful. Discuss. ishida@w3.org
• Re: The HTML q element can sometimes be useful. Discuss. Ivan Herman
• Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss. ishida@w3.org

Friday, 29 April 2016

• RE: The HTML q element can sometimes be useful. Discuss. Tex Texin
• Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss. John Cowan
• Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss. Tex Texin via GitHub
• Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss. Tex Texin via GitHub
• Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss. Asmus Freytag (c)
• Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss. r12a via GitHub
• RE: [i18n-discuss] The HTML q element can sometimes be useful. Discuss. Tex Texin
• Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss. undivaga via GitHub
• Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss. asmusf via GitHub
• Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss. undivaga via GitHub
• Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss. asmusf via GitHub
• Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss. johnwcowan via GitHub
• Re: [w3c/i18n-discuss] notification issues ishida@w3.org
• Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss. asmusf via GitHub
• Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss. r12a via GitHub
• Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss. asmusf via GitHub
• Re: The HTML q element can sometimes be useful. Discuss. ishida@w3.org

Thursday, 28 April 2016

• Re: Wiki summary of q element default styling issues ishida@w3.org
• [Bug 26641] Proposal to add a 'tz' attribute to support real time zones in HTML5.x bugzilla@jessica.w3.org
• Retiring the i18n topic list ishida@w3.org
• Re: The HTML q element can sometimes be useful. Discuss. John Cowan
• RE: The HTML q element can sometimes be useful. Discuss. Tex Texin
• RE: The HTML q element can sometimes be useful. Discuss. Rebeca Ruiz Sánchez
• Re: The HTML q element can sometimes be useful. Discuss. Florian Rivoal
• Re: The HTML q element can sometimes be useful. Discuss. Asmus Freytag (c)
• Re: The HTML q element can sometimes be useful. Discuss. John Cowan
• Re: The HTML q element can sometimes be useful. Discuss. Asmus Freytag (c)
• Re: The HTML q element can sometimes be useful. Discuss. Asmus Freytag (c)

Wednesday, 27 April 2016

• RE: The HTML q element can sometimes be useful. Discuss. Tex Texin
• RE: The HTML q element can sometimes be useful. Discuss. Rebeca Ruiz Sánchez
• RE: The HTML q element can sometimes be useful. Discuss. Tex Texin
• Re: The HTML q element can sometimes be useful. Discuss. Asmus Freytag (c)
• RE: The HTML q element can sometimes be useful. Discuss. Tex Texin
• Re: The HTML q element can sometimes be useful. Discuss. Asmus Freytag (c)
• RE: The HTML q element can sometimes be useful. Discuss. Tex Texin
• RE: The HTML q element can sometimes be useful. Discuss. Tex Texin
• Re: The HTML q element can sometimes be useful. Discuss. John Cowan
• Re: The HTML q element can sometimes be useful. Discuss. Asmus Freytag (c)
• Re: The HTML q element can sometimes be useful. Discuss. Florian Rivoal
• Re: The HTML q element can sometimes be useful. Discuss. Nick Barreto
• Re: The HTML q element can sometimes be useful. Discuss. Florian Rivoal

Tuesday, 26 April 2016

• Re: The HTML q element can sometimes be useful. Discuss. Asmus Freytag (c)
• Re: The HTML q element can sometimes be useful. Discuss. ishida@w3.org
• The HTML q element can sometimes be useful. Discuss. ishida@w3.org
• Re: Wiki summary of q element default styling issues Florian Rivoal
• Re: Wiki summary of q element default styling issues Florian Rivoal

Monday, 25 April 2016

• [Bug 22835] window.navigator.language should not return "en" for privacy protection bugzilla@jessica.w3.org
• RE: Wiki summary of q element default styling issues Tex Texin
• Re: Wiki summary of q element default styling issues John Cowan
• For review: Ruby Markup ishida@w3.org
• Re: Wiki summary of q element default styling issues ishida@w3.org
• Re: Wiki summary of q element default styling issues Asmus Freytag (c)
• Re: Wiki summary of q element default styling issues ishida@w3.org
• Re: Wiki summary of q element default styling issues Asmus Freytag (c)
• Re: Wiki summary of q element default styling issues John Cowan
• Re: Wiki summary of q element default styling issues Asmus Freytag (c)
• Re: Wiki summary of q element default styling issues Florian Rivoal
• Re: Wiki summary of q element default styling issues John Cowan
• Re: Wiki summary of q element default styling issues ishida@w3.org
• Re: Wiki summary of q element default styling issues ishida@w3.org

Thursday, 21 April 2016

• RE: Wiki summary of q element default styling issues Tex Texin
• Re: Wiki summary of q element default styling issues Kent Karlsson
• Re: Wiki summary of q element default styling issues John Cowan
• Re: Wiki summary of q element default styling issues Kent Karlsson
• Re: Wiki summary of q element default styling issues Kent Karlsson
• Closed: [presentation-api] Possibility for a character to be interpreted differently depending on locale Mark Foltz via GitHub
• Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale Mark Foltz via GitHub
• Re: Wiki summary of q element default styling issues John Cowan
• Re: Wiki summary of q element default styling issues ishida@w3.org
• Re: Wiki summary of q element default styling issues Asmus Freytag (c)
• Wiki summary of q element default styling issues ishida@w3.org

Wednesday, 20 April 2016

• Closed: [charmod-norm] String matching problem (Section 2 introduction) -- types of operations aphillips via GitHub
• Closed: [charmod-norm] Definition of "Syntactic content" (section 1.4) aphillips via GitHub
• Closed: [charmod-norm] XML use of DTD (Section 1.4, Example 1 in 2016-02-01 Editor's version) aphillips via GitHub
• Closed: [charmod-norm] Definition of "natural language content' (Section 1.4) aphillips via GitHub
• Closed: [charmod-norm] Section number references to Unicode Standard aphillips via GitHub
• Closed: [charmod-norm] Definition of "vocabulary", Section 1.2 aphillips via GitHub
• Closed: [charmod-norm] Arabic & Hebrew unique issues associated with sections 2.4 and 2.5 tomerm via GitHub

Tuesday, 19 April 2016

• Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale Mark Foltz via GitHub
• Closed: [charmod-norm] add section for other kinds of equivalence aphillips via GitHub
• Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale Tomoyuki Shimizu via GitHub

Monday, 18 April 2016

• Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale Mark Foltz via GitHub
• Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale Mark Foltz via GitHub

Sunday, 17 April 2016

• Re: Expected behaviour of quotation marks Florian Rivoal

Friday, 15 April 2016

• Re: Expected behaviour of quotation marks John Cowan
• Re: Expected behaviour of quotation marks ishida@w3.org
• Re: [manifest] i18n: No direction metadata for 'name'; [I18N-ISSUE-416] Mounir Lamouri via GitHub
• Re: [manifest] i18n: No direction metadata for 'name'; [I18N-ISSUE-416] Marcos Cáceres via GitHub

Tuesday, 12 April 2016

• [minutes] Internationalization telecon 2016-04-07 ishida@w3.org

Friday, 8 April 2016

• Re: Is <q> useful? [was Expected behaviour of quotation marks] Liam R. E. Quin
• Re: Expected behaviour of quotation marks fantasai
• RE: Is <q> useful? [was Expected behaviour of quotation marks] Tex Texin
• Re: Is <q> useful? [was Expected behaviour of quotation marks] John Cowan
• RE: Is <q> useful? [was Expected behaviour of quotation marks] Tex Texin
• Re: Is <q> useful? [was Expected behaviour of quotation marks] ishida@w3.org
• Re: Is <q> useful? [was Expected behaviour of quotation marks] John Cowan
• Re: Is <q> useful? [was Expected behaviour of quotation marks] Phillips, Addison
• Re: Is <q> useful? [was Expected behaviour of quotation marks] John Cowan
• Re: Expected behaviour of quotation marks Gunnar Bittersmann
• RE: Expected behaviour of quotation marks Siegman, Tzviya - Hoboken
• Re: Is <q> useful? [was Expected behaviour of quotation marks] ishida@w3.org
• Re: Expected behaviour of quotation marks ishida@w3.org
• Is <q> useful? [was Expected behaviour of quotation marks] ishida@w3.org
• Re: Expected behaviour of quotation marks ishida@w3.org
• Re: Expected behaviour of quotation marks Gunnar Bittersmann
• Re: Expected behaviour of quotation marks Gunnar Bittersmann

Thursday, 7 April 2016

• Re: Expected behaviour of quotation marks fantasai

Friday, 8 April 2016

• Re: Expected behaviour of quotation marks Florian Rivoal
• Re: Expected behaviour of quotation marks Florian Rivoal

Thursday, 7 April 2016

• RE: Expected behaviour of quotation marks Tex Texin
• RE: Expected behaviour of quotation marks Siegman, Tzviya - Hoboken
• Re: Expected behaviour of quotation marks ishida@w3.org
• Re: Expected behaviour of quotation marks AUDRAIN LUC
• Re: Expected behaviour of quotation marks John Cowan
• Re: Expected behaviour of quotation marks Asmus Freytag (c)
• Re: Expected behaviour of quotation marks ishida@w3.org
• Re: Expected behaviour of quotation marks Lina Kemmel
• Re: Expected behaviour of quotation marks Amir E. Aharoni
• Re: Expected behaviour of quotation marks Dave Cramer
• Closed: [charmod-norm] [ed] normalization forms r12a via GitHub
• Re: Expected behaviour of quotation marks John Cowan
• Re: Expected behaviour of quotation marks Florian Rivoal

Wednesday, 6 April 2016

• Re: Expected behaviour of quotation marks Asmus Freytag (c)
• Re: Expected behaviour of quotation marks Asmus Freytag (c)
• Re: Expected behaviour of quotation marks John Cowan
• Re: Expected behaviour of quotation marks Christopher R. Maden
• Expected behaviour of quotation marks ishida@w3.org
• [charmod-norm] Limitations of Normalization - Confusion klensin via GitHub
• [charmod-norm] Confusability vs string matching r12a via GitHub
• [charmod-norm] [ed] eliminating encoding variation r12a via GitHub
• [charmod-norm] Removing meaning r12a via GitHub
• [charmod-norm] [ed] normalization forms r12a via GitHub

Monday, 4 April 2016

• [charmod-norm] ❿ hasn't a compat equiv r12a via GitHub
• [charmod-norm] Arabic & Hebrew issues with 2.4 r12a via GitHub

Friday, 1 April 2016

• [minutes] Internationalization telecon 2016-03-31 ishida@w3.org

Last message date: Tuesday, 28 June 2016 19:15:22 UTC