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

bugzilla@jessica.w3.org

• [Bug 13113] Parsing algorithm should not preclude Complex Ruby (Friday, 21 September)
• [Bug 13113] Parsing algorithm should not preclude Complex Ruby (Friday, 14 September)
• [Bug 13113] Parsing algorithm should not preclude Complex Ruby (Thursday, 23 August)
• [Bug 17967] Parsing algorithm should not preclude Complex Ruby (Tuesday, 21 August)
• [Bug 17967] Parsing algorithm should not preclude Complex Ruby (Tuesday, 21 August)
• [Bug 17967] Parsing algorithm should not preclude Complex Ruby (Monday, 20 August)
• [Bug 17967] Parsing algorithm should not preclude Complex Ruby (Friday, 20 July)
• [Bug 17967] Parsing algorithm should not preclude Complex Ruby (Friday, 20 July)
• [Bug 17967] Parsing algorithm should not preclude Complex Ruby (Wednesday, 18 July)
• [Bug 13113] Parsing algorithm should not preclude Complex Ruby (Wednesday, 18 July)
• [Bug 17967] New: Parsing algorithm should not preclude Complex Ruby (Wednesday, 18 July)

David Singer

• Re: [css3-text] Better wording than "known to be language X" (was line-break questions/comments (Tuesday, 28 August)

fantasai

• Katakana/hiragana list lettering (Monday, 24 September)
• Re: [css3-text] Better wording than "known to be language X" (was line-break questions/comments (Wednesday, 29 August)
• Re: [css3-text] Break opportunity between two different line-break values (was line-break questions/comments (Monday, 27 August)

Florian Rivoal

• Re: [css3-writing-modes] before/after terminology alternative? (Monday, 24 September)

Glenn Adams

• Re: [css3-writing-modes] before/after terminology alternative? (Tuesday, 25 September)
• Re: [css3-writing-modes] before/after terminology alternative? (Monday, 24 September)
• Re: [css3-writing-modes] before/after terminology alternative? (Monday, 24 September)
• Re: [css3-writing-modes] before/after terminology alternative? (Sunday, 23 September)
• Re: [css3-writing-modes] before/after terminology alternative? (Sunday, 23 September)
• Re: [css3-writing-modes] before/after terminology alternative? (Sunday, 23 September)
• Re: [css3-text] Korean should be added to enable additional line breaking rule sets (Monday, 17 September)
• Re: [css3-text] Better wording than "known to be language X" (was line-break questions/comments (Wednesday, 29 August)
• Re: [css3-text] Better wording than "known to be language X" (was line-break questions/comments (Wednesday, 29 August)
• Re: [css3-text] Better wording than "known to be language X" (was line-break questions/comments (Wednesday, 29 August)
• Re: [css3-text] Better wording than "known to be language X" (was line-break questions/comments (Tuesday, 28 August)
• Re: [css3-text] Better wording than "known to be language X" (was line-break questions/comments (Tuesday, 28 August)
• Re: [css3-text] line-break questions/comments (Monday, 27 August)
• Re: [css3-text] require UAX#14 for line breaks in CSS? (was line-break questions/comments (Monday, 27 August)
• Re: [css3-text] line-break questions/comments (Monday, 27 August)
• Re: [css3-text] line-break questions/comments (Monday, 27 August)
• Re: [css3-text] line-break questions/comments (Monday, 27 August)

Kang-Hao (Kenny) Lu

• Re: Katakana/hiragana list lettering (Tuesday, 25 September)

koba

• Re: [css3-writing-modes] before/after terminology alternative? (Monday, 24 September)

Koji Ishii

• RE: Katakana/hiragana list lettering (Tuesday, 25 September)
• RE: [css3-writing-modes] before/after terminology alternative? (Sunday, 23 September)
• RE: [css3-writing-modes] before/after terminology alternative? (Sunday, 23 September)
• RE: [css3-writing-modes] before/after terminology alternative? (Sunday, 23 September)
• RE: [css3-writing-modes] before/after terminology alternative? (Sunday, 23 September)
• RE: [css3-text] Korean should be added to enable additional line breaking rule sets (Sunday, 16 September)
• [css3-text] Korean should be added to enable additional line breaking rule sets (Thursday, 6 September)
• RE: [css3-text] Better wording than "known to be language X" (was line-break questions/comments (Wednesday, 29 August)
• RE: [css3-text] Break opportunity between two different line-break values (was line-break questions/comments (Tuesday, 28 August)
• RE: [css3-text] Better wording than "known to be language X" (was line-break questions/comments (Tuesday, 28 August)
• [css3-text] Better wording than "known to be language X" (was line-break questions/comments (Monday, 27 August)
• RE: [css3-text] line-break questions/comments (Monday, 27 August)
• [css3-text] require UAX#14 for line breaks in CSS? (was line-break questions/comments (Monday, 27 August)
• RE: [css3-text] line-break questions/comments (Monday, 27 August)
• RE: [css3-text] line-break questions/comments (Monday, 27 August)
• RE: [css3-text] Break opportunity between two different line-break values (was line-break questions/comments (Monday, 27 August)
• [css3-text] Break opportunity between two different line-break values (was line-break questions/comments (Sunday, 26 August)
• RE: [css3-writing-modes] column progression direction (Saturday, 7 July)

Leif Halvard Silli

• RE: [css3-text] Better wording than "known to be language X" (was line-break questions/comments (Wednesday, 29 August)
• Re: [css3-text] Better wording than "known to be language X" (was line-break questions/comments (Tuesday, 28 August)
• Re: [css3-text] Better wording than "known to be language X" (was line-break questions/comments (Tuesday, 28 August)
• RE: [css3-text] line-break questions/comments (Monday, 27 August)

Liam R E Quin

• Re: [css3-writing-modes] before/after terminology alternative? (Tuesday, 25 September)

Martin J. Dürst

• Re: [css3-writing-modes] before/after terminology alternative? (Tuesday, 25 September)
• Re: [css3-writing-modes] before/after terminology alternative? (Monday, 24 September)

MURAKAMI Shinyu

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

Nat McCully

• Re: [css3-text] Better wording than "known to be language X" (was line-break questions/comments (Tuesday, 28 August)

Phillips, Addison

• RE: [css3-writing-modes] before/after terminology alternative? (Sunday, 23 September)

Richard Ishida

• Re: Katakana/hiragana list lettering (Wednesday, 26 September)
• Re: Katakana/hiragana list lettering (Wednesday, 26 September)
• Fwd: First Public Working Draft published: Use Cases & Exploratory Approaches for Ruby Markup (Tuesday, 10 July)

Stephen Zilles

• RE: [css3-text] Better wording than "known to be language X" (was line-break questions/comments (Wednesday, 29 August)

Tab Atkins Jr.

• Re: [css3-writing-modes] before/after terminology alternative? (Tuesday, 25 September)
• Re: Katakana/hiragana list lettering (Tuesday, 25 September)
• Re: [css3-writing-modes] before/after terminology alternative? (Monday, 24 September)
• Re: [css3-writing-modes] before/after terminology alternative? (Sunday, 23 September)
• Re: [css3-writing-modes] before/after terminology alternative? (Sunday, 23 September)

신정식

• Re: [css3-text] Korean should be added to enable additional line breaking rule sets (Tuesday, 18 September)

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