public-i18n-cjk@w3.org from July to September 2012 by subject

[Bug 13113] Parsing algorithm should not preclude Complex Ruby

[Bug 17967] New: Parsing algorithm should not preclude Complex Ruby

[Bug 17967] Parsing algorithm should not preclude Complex Ruby

[css3-text] Better wording than "known to be language X" (was line-break questions/comments

[css3-text] Break opportunity between two different line-break values (was line-break questions/comments

[css3-text] Korean should be added to enable additional line breaking rule sets

[css3-text] line-break questions/comments

[css3-text] require UAX#14 for line breaks in CSS? (was line-break questions/comments

[css3-writing-modes] before/after terminology alternative?

[css3-writing-modes] column progression direction

Fwd: First Public Working Draft published: Use Cases & Exploratory Approaches for Ruby Markup

Katakana/hiragana list lettering

Last message date: Wednesday, 26 September 2012 11:00:00 UTC