W3C mailing list search service
Search among 2,291,512 messages in the W3C mailing list archives:
Closed: [i18n-activity] i18n-ISSUE-316: Line breaking defaults (#91)
- Date
- Thu, 25 Jun 2020 13:56:42 +0000
- Author
- r12a via GitHub <sysbot+gh@w3.org>
Re: [i18n-activity] i18n-ISSUE-316: Line breaking defaults (#91)
- Date
- Fri, 05 Jun 2020 02:38:46 +0000
- Author
- Fuqiao Xue via GitHub <sysbot+gh@w3.org>
Re: [i18n-activity] i18n-ISSUE-316: Line breaking defaults (#91)
- Date
- Thu, 14 May 2020 16:18:50 +0000
- Author
- r12a via GitHub <sysbot+gh@w3.org>
Re: [i18n-activity] i18n-ISSUE-316: Line breaking defaults (#91)
- Date
- Thu, 14 May 2020 11:43:24 +0000
- Author
- r12a via GitHub <sysbot+gh@w3.org>
Re: [i18n-activity] i18n-ISSUE-316: Line breaking defaults (#91)
- Date
- Wed, 06 May 2020 05:00:14 +0000
- Author
- Fuqiao Xue via GitHub <sysbot+gh@w3.org>
Re: [i18n-activity] i18n-ISSUE-316: Line breaking defaults
- Date
- Fri, 23 Sep 2016 13:35:44 +0000
- Author
- r12a via GitHub <sysbot+gh@w3.org>
Re: [i18n-activity] i18n-ISSUE-316: Line breaking defaults
- List
- public-i18n-core
- Date
- Fri, 23 Sep 2016 13:35:44 +0000
- Author
- r12a via GitHub <sysbot+gh@w3.org>
I18N-ACTION-366: Identify categories non-controversial for line-breaking to support i18n-issue-316 in css3-text
- List
- public-i18n-core
- Date
- Fri, 31 Oct 2014 21:52:47 +0000
- Author
- Internationalization Working Group Issue Tracker <sysbot+tracker@w3.org>
I18N-ACTION-366: Identify categories non-controversial for line-breaking to support i18n-issue-316 in css3-text http://www.w3.org/International/track/actions/366 Assigned to: Richard Ishida
Re: [css-text] I18N-ISSUE-316: Line breaking defaults
- Date
- Thu, 23 Oct 2014 01:17:51 -0400
- Author
- fantasai <fantasai.lists@inkedblade.net>
I am unsure and don't have the time to solve this particular problem within the next 2 weeks. If you or the i18nwg would like to go through the entire list and annotate it over the next couple weeks,
Re: [css-text] I18N-ISSUE-316: Line breaking defaults
- List
- www-style
- Date
- Thu, 23 Oct 2014 01:17:51 -0400
- Author
- fantasai <fantasai.lists@inkedblade.net>
I am unsure and don't have the time to solve this particular problem within the next 2 weeks. If you or the i18nwg would like to go through the entire list and annotate it over the next couple weeks,
Re: [css-text] I18N-ISSUE-316: Line breaking defaults
- Date
- Wed, 22 Oct 2014 15:49:43 -0700
- Author
- Asmus Freytag <asmusf@ix.netcom.com>
BA Category 1 BA Category 2 Are there any other members of Category 2? Is the issue "generic" to all kinds of hyphens and slashes, or is it "specific" to special strings like dates, path names or ide
Re: [css-text] I18N-ISSUE-316: Line breaking defaults
- List
- www-style
- Date
- Wed, 22 Oct 2014 15:49:43 -0700
- Author
- Asmus Freytag <asmusf@ix.netcom.com>
BA Category 1 BA Category 2 Are there any other members of Category 2? Is the issue "generic" to all kinds of hyphens and slashes, or is it "specific" to special strings like dates, path names or ide
Re: [css-text] I18N-ISSUE-316: Line breaking defaults
- Date
- Wed, 22 Oct 2014 18:12:55 -0400
- Author
- fantasai <fantasai.lists@inkedblade.net>
It's not an issue of kana characters, those are actually normatively covered in the section on 'line-break'. It's also not an issue of the non-tailorable sets you are citing, since those are already
Re: [css-text] I18N-ISSUE-316: Line breaking defaults
- List
- www-style
- Date
- Wed, 22 Oct 2014 18:12:55 -0400
- Author
- fantasai <fantasai.lists@inkedblade.net>
It's not an issue of kana characters, those are actually normatively covered in the section on 'line-break'. It's also not an issue of the non-tailorable sets you are citing, since those are already
Re: [css-text] I18N-ISSUE-316: Line breaking defaults
- Date
- Wed, 22 Oct 2014 17:51:02 +0100
- Author
- Richard Ishida <ishida@w3.org>
The i18n WG discussed this at http://www.w3.org/2014/10/16-i18n-minutes.html#item06 and concluded that there should be normative wording to say that UAX14 SHOULD be followed except in those specific
Re: [css-text] I18N-ISSUE-316: Line breaking defaults
- List
- www-style
- Date
- Wed, 22 Oct 2014 17:51:02 +0100
- Author
- Richard Ishida <ishida@w3.org>
The i18n WG discussed this at http://www.w3.org/2014/10/16-i18n-minutes.html#item06 and concluded that there should be normative wording to say that UAX14 SHOULD be followed except in those specific
Re: [css-text] I18N-ISSUE-316: Line breaking defaults
- Date
- Wed, 08 Oct 2014 20:07:16 +0100
- Author
- Richard Ishida <ishida@w3.org>
But what we're asking for is that the spec recommend that UAX14 be used as the default, ie. in lieu of any other considerations - we're not asking that browsers conform to it rigidly. (We are also su
Re: [css-text] I18N-ISSUE-316: Line breaking defaults
- List
- www-style
- Date
- Wed, 08 Oct 2014 20:07:16 +0100
- Author
- Richard Ishida <ishida@w3.org>
But what we're asking for is that the spec recommend that UAX14 be used as the default, ie. in lieu of any other considerations - we're not asking that browsers conform to it rigidly. (We are also su
Re: [css-text] I18N-ISSUE-316: Line breaking defaults
- Date
- Fri, 25 Jul 2014 19:52:33 +0100
- Author
- fantasai <fantasai.lists@inkedblade.net>
Very nice summary, yes. :) One of the main problems is actually the handling of various punctuation like slashes. A lot of these breaks need some amount of prioritization in order to work correctly.
Re: [css-text] I18N-ISSUE-316: Line breaking defaults
- List
- www-style
- Date
- Fri, 25 Jul 2014 19:52:33 +0100
- Author
- fantasai <fantasai.lists@inkedblade.net>
Very nice summary, yes. :) One of the main problems is actually the handling of various punctuation like slashes. A lot of these breaks need some amount of prioritization in order to work correctly.
Help and hints for using this service
W3C Member? Check the Member-only interface. W3C staff? Use the Team-only interface.