W3C home > Mailing lists > Public > public-i18n-core@w3.org > April to June 2011

RE: [css3-lists] Remaining feedback on the module

From: Koji Ishii <kojiishi@gluesoft.co.jp>
Date: Wed, 20 Apr 2011 22:02:23 -0400
To: Tab Atkins Jr. <jackalmage@gmail.com>
CC: www-style list <www-style@w3.org>, WWW International <www-international@w3.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-ID: <A592E245B36A8949BDB0A302B375FB4E0AC2874D76@MAILR001.mail.lan>
> That said, the fact that OOXML and ODF use U+3007 makes me want to
> switch it over.

Great. Thanks.


> >> > * Are we dropping "cjk-ideographic" which was in CSS 2.0?
> >> It would be ideal if the value
> >> can map to "*-informal" depending on language tag.
> >>
> >> Yes; the only purpose of that type seemed to be to host the cjk
> >> algorithm.  Since the three languages all actually have slightly
> >> *different* algorithms, it didn't make sense to keep it.
> >
> > Thanks, I'll take this to Japanese ML, as both Mozilla and WebKit have implemented this
> value, although I'm not sure if they're interoperable or used widely.
> 
> Fantasai informs me that 'cjk-ideographic' was defined in CSS2, so I
> shouldn't drop it.  >_<  I'll just map it to chinese-informal or
> something.

I agree that chinese-informal would be a good choice. I checked Mozilla and WebKit quickly up to 1100. It looks like both implementations use chinese-informal.


> > Ah, ok, so if I understand correctly, "japanese-informal" for instance is a predefined
> counter style that cannot be expressed by @counter-style rule, correct? I thought all
> predefined styles can be expressed by @counter-style rule and they're in Appendix A.
> 
> Yes, correct.  There are 4 or 5 subtly different algorithms used here
> for the different languages and formal/informal.  I don't think it's
> worthwhile to define a @counter-style type for it when there's only
> one or two types of list that would ever use it.  This is similar to
> the current situation with 'hebrew' and 'ethiopian-numeric' - they use
> algorithms that can't be easily generalized, so rather than making a
> one-shot 'type' value, I just define them explicitly.

Thank you for the confirmation. Then, can you add suffix to use for each predefined counter style?


> You can mess with the suffix yourself by using 'content' and the
> counter() function, as you demonstrated in your example.  The
> predefined suffix is only used by the automatic ::marker content
> creation.
> 
> You can't use 'content' to set the negative sign.

Ok. Suffixes are often customized. As long as it can be customized, I can live without being able to create my own counter style.

I was thinking how much I want to customize negative signs, and concluded not too much as long as its usage is list-style-type and counter() function where we don't expect using negative numbers.


Regards,
Koji
Received on Thursday, 21 April 2011 02:07:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 21 April 2011 02:07:50 GMT