[minutes] Arabic layout telecon 2016-06-28
[minutes] Arabic layout telecon 2016-06-21
[minutes] Internationalization telecon 2016-06-23
[minutes] Internationalization telecon 2016-06-21
[csswg-drafts] Issue: [css-text-3] Line breaking opportunities at the boundary of a white-space:pre inline element marked as i18n
For review: Time & date, Essential concepts
FOR REVIEW: Closing Web Annotation Model & Annotation Vocab tracker items
[bp-i18n-specdev] mention the language subtag registry
[bp-i18n-specdev] improve description of BCP 47
Closed: [bp-i18n-specdev] Spell out internationalization in place of 'i18n'
[bp-i18n-specdev] establish a glossary?
[bp-i18n-specdev] Change rule to allow surrogates
[bp-i18n-specdev] Consider creating a rule regarding rejecting invalid surrogate pairs
Closed: [browser-payment-api] Add section on internationalization
[bp-i18n-specdev] Possibly soften requirements related to logical order over visual order.
[bp-i18n-specdev] Change the rule for establishing base direction
[bp-i18n-specdev] Change the rule for assuming text direction from language
[bp-i18n-specdev] Consider combining defining language value checklist rules
[bp-i18n-specdev] Mention inheritance when defining default text processing language.
Closed: [html] why is "content language" pragma processing not equivalent to HTTP Content-Language?
Re: [presentation-api] list of displays: should it address display name, language, etc.?
- Re: [presentation-api] list of displays: should it address display name, language, etc.?
- Re: [presentation-api] list of displays: should it address display name, language, etc.?
- Re: [presentation-api] list of displays: should it address display name, language, etc.?
[html] Issue: Remove the use of printable character from accessKey attribute. marked as accessibility
[minutes] Internationalization telecon 2016-06-09
Fwd: Social Web WG reviews
[html] Issue: Define or remove the use of the term Plain Unicode String marked as i18n
[html] Issue: datetime-local needs a health warning for floating to incremental time conversion (was I18N-ISSUE-89) marked as i18n
[html] Issue: Allow a page to request a given locale (was bug 16965) marked as i18n
[csswg-drafts] Issue: [css-text-decor-3] behavior of text-decoration + text-emphasis marked as i18n
[html] Issue: Default <details> heading should be localized marked as i18n
Closed: [web-annotation] Use of dc:language
Closed: [web-annotation] Normalisation of Text Quote Selector
Closed: [web-annotation] Model is defined in terms of IRIs; Protocol with URI
Closed: [web-annotation] Request header and language negotiation
Closed: [web-annotation] (model) have a note on logical and visual order of text for text quote selector implementations
Closed: [web-annotation] white space normalisation
Closed: [web-annotation] Base direction for annotations
Closed: [web-annotation] Remove "and so forth", clarify utf-8 encoding
Closed: [web-annotation] exactly 0 or 1 language(s)
Closed: [web-annotation] 'generated' and 'modified' should use UTC by default
Closed: [web-annotation] TimeState, generated, and modified should recommend all values use UTC
Closed: [web-annotation] (model) vague definition of character position for text position selector
[html] Issue: Is input type=datetime implemented? marked as i18n
[minutes] Internationalization telecon 2016-06-02
Closed: [html] value on button in submit state is translateable
Closed: [html] Type attribute for ordered lists should be obsolete but conforming
[web-annotation] Issue: Model is defined in terms of IRIs; Protocol with URI marked as i18n-review
Updated article: Changing an HTML page to Unicode
[minutes] Internationalization telecon 2016-05-26
[predefined-counter-styles] Mixed content in chrome, respec fails
[predefined-counter-styles] Should we add more Latin counter styles?
Request for review
[html] Issue: Tighten up usages of "compatibilty caseless" comparisons used in the spec marked as i18n
Closed: [web-annotation] (model) update reference for language tags: BCP47 instead of RFC5646
[web-annotation] Issue: Remove "and so forth", clarify utf-8 encoding marked as editor_action
[web-annotation] Issue: Reference to text encoding in spec perhaps not appropriate marked as i18n-review
Reminder about following i18n issues
[web-annotation] Issue: Use of dc:language marked as vocab
Gtihub disruptions
[csswg-drafts] Issue: [css-fonts] Specifying changes to parameters for fallback fonts marked as i18n
Closed: [csswg-drafts] test
[csswg-drafts] Issue: test marked as i18n
Closed: [web-annotation] (model) make definition of a character more precise
Closed: [web-annotation] 'generated' and 'modified' date/time properties specific reference and format
[web-annotation] Issue: Base direction for annotations marked as editor_action
Code units or code points for text pointers?
Closed: [web-annotation] Defaults for an Annotation Collection
Closed: [web-annotation] String body must not have a language associated?
Closed: [web-annotation] How is language assigned to an annotation?
Closed: [web-annotation] (model) missing mechanism to express language preferences in the intendend audience field
[web-annotation] Issue: String body must not have a language associated? marked as i18n-review
[web-annotation] Issue: Normalisation of Text Quote Selector marked as i18n-review
[web-annotation] Issue: white space normalisation marked as i18n-review
[web-annotation] Issue: Request header and language negotiation marked as i18n-review
[web-annotation] Issue: Defaults for an Annotation Collection marked as i18n-review
[web-annotation] Issue: How is language assigned to an annotation? marked as i18n-review
[web-annotation] Issue: 'generated' and 'modified' date/time properties specific reference and format marked as i18n-review
[web-annotation] Issue: 'generated' and 'modified' should use UTC by default marked as i18n-review
[web-annotation] Issue: TimeState, generated, and modified should recommend all values use UTC marked as i18n-review
[html] Issue: example of language detection fallback, no mention of pragma marked as i18n
Closed: [browser-payment-api] Should the merchant be able to request your email and recipient phone number
[minutes] Internationalization telecon 2016-05-05
[minutes] Internationalization telecon 2016-04-28
[minutes] Internationalization telecon 2016-04-14
HTML5.1 review
For review: New issues in the tracker for Web Annotations
[web-annotation] Issue: exactly 0 or 1 language(s) marked as model
[web-annotation] Issue: (model) missing mechanism to express language preferences in the intendend audience field marked as i18n-review
[web-annotation] Issue: (model) have a note on logical and visual order of text for text quote selector implementations marked as i18n-review
[web-annotation] Issue: (model) make definition of a character more precise marked as model
[web-annotation] Issue: (model) update reference for language tags: BCP47 instead of RFC5646 marked as model
[web-annotation] Issue: (model) vague definition of charactor position for text position selector marked as i18n-review
Re: faq suggestions
[html] Issue: Improve documentation of i18n issues with input type="number" marked as Editorial
[Bug 26417] i18n-ISSUE-343: Type attribute on ol
Closed: [html] html and head elements should not get new attributes
[html] Issue: Type attribute for ordered lists should be obsolete but conforming marked as technical improvement
Comments on the q element: change in notification behaviour
[html] Issue: How to handle legacy Ruby content that may use <rbc> marked as i18n
[browser-payment-api] Issue: Add section on internationalization marked as HR: i18n
[html] Issue: add warning/advice about lang attribute use marked as i18n
[html] Issue: make any element with an explicit lang attribute (and no dir attribute) bidi-isolated by default marked as i18n
[html] Issue: value on button in submit state is translateable marked as i18n
[html] Issue: why is "content language" pragma processing not equivalent to HTTP Content-Language? marked as i18n
[html] Issue: Sort out issues with [inputmode] marked as i18n
[html] Issue: html and head elements should not get new attributes marked as i18n
[html] Issue: Default styling for q element marked as i18n
Re: [w3c/i18n-discuss] notification issues
Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss.
- Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss.
- Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss.
- Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss.
- Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss.
- Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss.
- Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss.
- Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss.
- Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss.
- Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss.
- Re: [i18n-discuss] The HTML q element can sometimes be useful. Discuss.
[Bug 26641] Proposal to add a 'tz' attribute to support real time zones in HTML5.x
Retiring the i18n topic list
The HTML q element can sometimes be useful. Discuss.
- Re: The HTML q element can sometimes be useful. Discuss.
- Re: The HTML q element can sometimes be useful. Discuss.
- Re: The HTML q element can sometimes be useful. Discuss.
- Re: The HTML q element can sometimes be useful. Discuss.
- Re: The HTML q element can sometimes be useful. Discuss.
- Re: The HTML q element can sometimes be useful. Discuss.
[Bug 22835] window.navigator.language should not return "en" for privacy protection
For review: Ruby Markup
Closed: [presentation-api] Possibility for a character to be interpreted differently depending on locale
Wiki summary of q element default styling issues
- Re: Wiki summary of q element default styling issues
- Re: Wiki summary of q element default styling issues
- Re: Wiki summary of q element default styling issues
- Re: Wiki summary of q element default styling issues
Closed: [charmod-norm] String matching problem (Section 2 introduction) -- types of operations
Closed: [charmod-norm] Definition of "Syntactic content" (section 1.4)
Closed: [charmod-norm] XML use of DTD (Section 1.4, Example 1 in 2016-02-01 Editor's version)
Closed: [charmod-norm] Definition of "natural language content' (Section 1.4)
Closed: [charmod-norm] Section number references to Unicode Standard
Closed: [charmod-norm] Definition of "vocabulary", Section 1.2
Closed: [charmod-norm] Arabic & Hebrew unique issues associated with sections 2.4 and 2.5
Closed: [charmod-norm] add section for other kinds of equivalence
Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale
- Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale
- Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale
- Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale
- Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale
Re: [manifest] i18n: No direction metadata for 'name'; [I18N-ISSUE-416]
[minutes] Internationalization telecon 2016-04-07
Expected behaviour of quotation marks
- Re: Expected behaviour of quotation marks
- Re: Expected behaviour of quotation marks
- Re: Expected behaviour of quotation marks
- Re: Expected behaviour of quotation marks
- Re: Expected behaviour of quotation marks
- Re: Expected behaviour of quotation marks
- RE: Expected behaviour of quotation marks
- Is <q> useful? [was Expected behaviour of quotation marks]
- RE: Is <q> useful? [was Expected behaviour of quotation marks]
- Re: Is <q> useful? [was Expected behaviour of quotation marks]
- RE: Expected behaviour of quotation marks
- RE: Is <q> useful? [was Expected behaviour of quotation marks]
- Re: Expected behaviour of quotation marks
- Re: Expected behaviour of quotation marks