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

Katakana/hiragana list lettering fantasai (Monday, 24 September)

[Bug 13113] Parsing algorithm should not preclude Complex Ruby bugzilla@jessica.w3.org (Friday, 21 September)

Re: [css3-writing-modes] before/after terminology alternative? MURAKAMI Shinyu (Friday, 21 September)

RE: [css3-text] Korean should be added to enable additional line breaking rule sets Koji Ishii (Sunday, 16 September)

[Bug 13113] Parsing algorithm should not preclude Complex Ruby bugzilla@jessica.w3.org (Friday, 14 September)

[css3-text] Korean should be added to enable additional line breaking rule sets Koji Ishii (Thursday, 6 September)

[css3-text] Better wording than "known to be language X" (was line-break questions/comments Koji Ishii (Monday, 27 August)

[css3-text] require UAX#14 for line breaks in CSS? (was line-break questions/comments Koji Ishii (Monday, 27 August)

Re: [css3-text] line-break questions/comments Glenn Adams (Monday, 27 August)

[css3-text] Break opportunity between two different line-break values (was line-break questions/comments Koji Ishii (Sunday, 26 August)

[Bug 13113] Parsing algorithm should not preclude Complex Ruby bugzilla@jessica.w3.org (Thursday, 23 August)

[Bug 13113] Parsing algorithm should not preclude Complex Ruby bugzilla@jessica.w3.org (Wednesday, 18 July)

[Bug 17967] New: Parsing algorithm should not preclude Complex Ruby bugzilla@jessica.w3.org (Wednesday, 18 July)

Fwd: First Public Working Draft published: Use Cases & Exploratory Approaches for Ruby Markup Richard Ishida (Tuesday, 10 July)

RE: [css3-writing-modes] column progression direction Koji Ishii (Saturday, 7 July)

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