W3C mailing list search service

Search among 2,298,714 messages in the W3C mailing list archives:

This is page 1, displaying results 1-17 of 17

Closed: [i18n-activity] i18n-ISSUE-359: Drop ruby-merge in favour of a specific jukugo value (#98)

Date
Tue, 28 Nov 2023 20:59:00 +0000
Author
Addison Phillips via GitHub <sysbot+gh@w3.org>

aphillips closed this issue. See https://github.com/w3c/i18n-activity/issues/98 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Re: [i18n-activity] i18n-ISSUE-359: Drop ruby-merge in favour of a specific jukugo value (#98)

Date
Fri, 05 Feb 2021 17:43:39 +0000
Author
r12a via GitHub <sysbot+gh@w3.org>

Some clarifications were made, which i think leave me happy. Ok to close ? -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/9

Re: Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value

Date
Fri, 2 Oct 2015 17:01:59 +0100
Author
Richard Ishida <ishida@w3.org>

presented as mono ruby with the phonetics centered per character, or as word-based ruby where the phonetics are centered per word. presumably this would only work if you considered that eventuality i

Re: Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value

Date
Fri, 2 Oct 2015 17:01:59 +0100
Author
Richard Ishida <ishida@w3.org>

presented as mono ruby with the phonetics centered per character, or as word-based ruby where the phonetics are centered per word. presumably this would only work if you considered that eventuality i

Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value

Date
Thu, 1 Oct 2015 18:38:14 -0700
Author
"Tab Atkins Jr." <jackalmage@gmail.com>

Hmm, I see. I was under the impression that jukugo was the "word" mode; I didn't realize it was actually "mono, but allow overlap if necessary". I definitely see how the "word" mode is necessary for

Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value

Date
Thu, 1 Oct 2015 18:38:14 -0700
Author
"Tab Atkins Jr." <jackalmage@gmail.com>

Hmm, I see. I was under the impression that jukugo was the "word" mode; I didn't realize it was actually "mono, but allow overlap if necessary". I definitely see how the "word" mode is necessary for

Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value

Date
Thu, 1 Oct 2015 13:36:34 -0400
Author
fantasai <fantasai.lists@inkedblade.net>

It's not, see Koji's reply. Jukugo and the sort of collapsing I'm describing for Latin phonetics are not the same. We basically need three values, in order of priority, for ruby-merge: 1. syllable ru

Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value

Date
Thu, 1 Oct 2015 13:36:34 -0400
Author
fantasai <fantasai.lists@inkedblade.net>

It's not, see Koji's reply. Jukugo and the sort of collapsing I'm describing for Latin phonetics are not the same. We basically need three values, in order of priority, for ruby-merge: 1. syllable ru

Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value

Date
Thu, 1 Oct 2015 19:05:21 +0900
Author
Koji Ishii <kojiishi@gmail.com>

I'm ok with deferring as Richard suggested, or limit to Jukugo only as Tab suggested. One clarification about Jukugo-ruby; we can informatively reference JLREQ, but I'm not positive to make the logic

Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value

Date
Thu, 1 Oct 2015 19:05:21 +0900
Author
Koji Ishii <kojiishi@gmail.com>

I'm ok with deferring as Richard suggested, or limit to Jukugo only as Tab suggested. One clarification about Jukugo-ruby; we can informatively reference JLREQ, but I'm not positive to make the logic

Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value

Date
Wed, 30 Sep 2015 17:06:39 -0700
Author
"Tab Atkins Jr." <jackalmage@gmail.com>

Yeah, "mono" and "group" ruby are both covered under "ruby-merge: separate", meaning "each base lays out with its individual ruby text". That seems to be well-handled by marking up each word as a sep

Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value

Date
Wed, 30 Sep 2015 17:06:39 -0700
Author
"Tab Atkins Jr." <jackalmage@gmail.com>

Yeah, "mono" and "group" ruby are both covered under "ruby-merge: separate", meaning "each base lays out with its individual ruby text". That seems to be well-handled by marking up each word as a sep

Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value

Date
Tue, 29 Sep 2015 21:02:43 -0400
Author
fantasai <fantasai.lists@inkedblade.net>

"Group ruby" is not the same -- it a term used for a ruby annotation which has multi-character base text, and there is no smaller mapping. E.g. mapping “San Francisco” to 旧金山 or “あし

Re: i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value

Date
Tue, 29 Sep 2015 21:02:43 -0400
Author
fantasai <fantasai.lists@inkedblade.net>

"Group ruby" is not the same -- it a term used for a ruby annotation which has multi-character base text, and there is no smaller mapping. E.g. mapping “San Francisco” to 旧金山 or “あし

i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value

Date
Thu, 24 Sep 2015 17:51:37 +0100
Author
Richard Ishida <ishida@w3.org>

http://www.w3.org/TR/css-ruby-1/#collapsed-ruby 4.2 Sharing Annotation Space: the ruby-merge property I think the new ruby-merge property in the editor's draft is overthinking the task. If people wan

i18n-ISSUE-359: [css-ruby] Drop ruby-merge in favour of a specific jukugo value

Date
Thu, 24 Sep 2015 17:51:37 +0100
Author
Richard Ishida <ishida@w3.org>

http://www.w3.org/TR/css-ruby-1/#collapsed-ruby 4.2 Sharing Annotation Space: the ruby-merge property I think the new ruby-merge property in the editor's draft is overthinking the task. If people wan

I18N-ISSUE-359: Drop ruby-merge in favour of a specific jukugo value [css-ruby]

Date
Fri, 04 Jul 2014 11:53:28 +0000
Author
"Internationalization Working Group Issue Tracker" <sysbot+tracker@w3.org>

I18N-ISSUE-359: Drop ruby-merge in favour of a specific jukugo value [css-ruby] http://www.w3.org/International/track/issues/359 Raised by: Richard Ishida On product: css-ruby I think the new ruby-me

Help and hints for using this service

W3C Member? Check the Member-only interface. W3C staff? Use the Team-only interface.