Options:
- # Session Start: Sun Jun 10 00:00:01 2012
- # Session Ident: #css
- # [01:16] * Joins: shepazu (shepazu@128.30.52.169)
- # [03:10] * Joins: tantek_ (tantek@50.0.92.247)
- # [03:10] * Quits: tantek (tantek@50.0.92.247) (Connection reset by peer)
- # [03:10] * tantek_ is now known as tantek
- # [03:49] * Quits: tantek (tantek@50.0.92.247) (Ping timeout)
- # [03:56] * Joins: tantek (tantek@50.0.92.247)
- # [06:13] * Joins: koji (koji@222.158.227.129)
- # [06:41] * Quits: koji (koji@222.158.227.129) (Quit: Leaving...)
- # [06:43] * Joins: koji (koji@222.158.227.129)
- # [06:43] <koji> fantasai: ping
- # [06:56] <fantasai> koji: pong
- # [06:57] <fantasai> koji: So, I think we could use some data on whether single or double quotes are more common in Chinese
- # [06:57] * Quits: tantek (tantek@50.0.92.247) (Quit: tantek)
- # [06:57] <fantasai> koji: If single quotes are less common, then maybe it's ok to make them sideways
- # [06:58] <fantasai> koji: And that handles apostrophes
- # [06:58] <koji> fantasai: let me see some PDFs I have
- # [07:00] <fantasai> maybe i should make another trip to Chinatown :)
- # [07:00] <koji> I like that :)
- # [07:00] <koji> I searched for MacFan 2011/3
- # [07:01] <koji> 5 or 6 U+2019 found, all in horizontal flow only
- # [07:02] <koji> Maybe girl's magazine could use more apostrophe for French names etc., but I don't have such PDF :|
- # [07:03] <fantasai> lol
- # [07:03] <fantasai> It's not even just French, English uses 's for the possessive
- # [07:03] <koji> I'm leaning to make single/double to Tu
- # [07:04] <koji> and I don't care the rest but I understand people wants consistent, so probably all to Tu
- # [07:04] <koji> Also wondering if we have any other data we can investigate within a day or less...
- # [07:06] <koji> I suspect
- # [07:06] <koji> The guy who attended EPUB mtg at Taiwan and came to CSS F2F once
- # [07:06] <koji> were working digital archive library in EPUB
- # [07:07] <koji> ...thought they already rely on Tu behavior but that's too qiuck
- # [07:07] <koji> because today's webkit sets R
- # [07:08] <fantasai> right..
- # [07:11] <koji> Maybe I'm biased to Tu for my wish, I'm trying not to think about that but
- # [07:12] <koji> I can't think saying Chinese that they should markup with upright because Japanese fonts are broken is PC
- # [07:12] <fantasai> heh
- # [07:13] <fantasai> well, from Unicode perspective they're supposed to be using different codepoints
- # [07:15] <koji> I'm ok to follow policies if there were any good workaround
- # [07:16] <koji> Possibly by the time Chinese market emerges, @text-transform is ready
- # [07:16] * fantasai switches the browser's language headers to zh-TW and looks for conent
- # [07:16] <fantasai> koji: that would be handy :)
- # [07:16] <koji> Oh, that sounds good
- # [07:23] <koji> Both usages exist in wiki: http://zh.wikipedia.org/wiki/%E5%BC%95%E5%8F%B7
- # [07:23] <koji> Both I mean, native and Latin
- # [07:23] <fantasai> I'm seeing mostly quotes like 「基民」
- # [07:25] <fantasai> I found some double quotes
- # [07:25] <fantasai> no single quotes yet
- # [07:26] <koji> It needs to be quotes within quotes, if the rule is the same as Japanese
- # [07:26] <koji> ...is it same in Latin?
- # [07:26] <fantasai> depends
- # [07:26] <fantasai> Some traditions use single quotes inside double quotes
- # [07:27] <fantasai> other tradition use double qoutes inside single quotes
- # [07:27] <fantasai> (so single quotes is the default)
- # [07:27] <koji> Interesting
- # [07:27] <koji> Example 2 of wiki has nested quotes, but you want the real example?
- # [07:27] <fantasai> Xinhua uses double quotes
- # [07:28] <fantasai> If single quotes is only used for quotes within quotes
- # [07:28] <fantasai> then it's pretty uncommon
- # [07:28] * fantasai notes Xinhua is the PRC newspaper
- # [07:28] <koji> ah
- # [07:29] <fantasai> tw.yahoo.com uses 「
- # [07:29] <fantasai> 」
- # [07:29] * fantasai looks at news.google.com.tw
- # [07:30] <fantasai> Chinatimes.com uses same
- # [07:31] <koji> Newspaper tends to follow more in tradition, and its source are likely to be in vertical
- # [07:31] <koji> Same at www.yomiuri.co.jp
- # [07:31] <fantasai> yeah
- # [07:31] <fantasai> cnyes.com also uses the same
- # [07:31] <fantasai> and also BBC
- # [07:32] <fantasai> And they're using the correct codepoints
- # [07:33] <koji> double quotes at http://3c.msn.com.tw/View.aspx?ArticleID=66474
- # [07:34] <koji> which uses brackets in the same article, when to use quotes and when to brackets isn't clear
- # [07:34] <fantasai> both styles , actually :)
- # [07:34] <fantasai> yeah
- # [07:35] <fantasai> Given Taiwanese sources seem to be comfortable using the correct codepoints
- # [07:35] <koji> I wish search engines don't normalize punctuation :)
- # [07:36] <fantasai> Seems like we don't need to worry about them depending on double quotes transforming into bracket quotes
- # [07:36] <fantasai> via font substitution
- # [07:37] <koji> by "correct codepoints" what do you mean?
- # [07:37] <fantasai> U+300C
- # [07:38] <koji> ah, yeah, but things we can find on the web is supposed to be read in horizontal, right?
- # [07:38] <fantasai> yes
- # [07:38] <fantasai> which makes it *more* likely that they'd be using double quotes!
- # [07:38] <fantasai> but we're not seeing it much
- # [07:38] <koji> I see your points
- # [07:39] <koji> Maybe blogs are different from these professional writings
- # [07:39] <fantasai> maybe
- # [07:39] * fantasai wonders how to find them
- # [07:39] <koji> Quotes are imported one, professional editors don't use much in Japan too
- # [07:39] <koji> yeah
- # [07:41] <koji> "網誌" in Google is blog search
- # [07:43] <koji> ...most of them are talking about shell, javascript, php :)
- # [07:47] <koji> Google translation to Japanese doesn't make much sense but can't find how to translate to English: http://blog.sina.com.cn/s/blog_77f02c450101533q.html
- # [07:49] <fantasai> /me used babelfish
- # [07:50] <fantasai> sounds like it's complaining about ascii quotes being ambiguous
- # [07:50] <koji> yeah, don't use and replace before you publish?
- # [07:50] * Joins: tantek (tantek@208.54.5.171)
- # [07:50] <fantasai> yeah
- # [07:51] <koji> "pair" is probably talking about Word's feature--English Word determines direction by existence of space
- # [07:51] <koji> But EA Word changed the logic to look for pairs because EA scripts don't use spaces
- # [07:51] <koji> So odd occurance in a paragraph is automatically changed to open
- # [07:52] <koji> and even to close
- # [07:52] <koji> but can't read in what case it can cause problems to Chinese
- # [07:54] * Quits: tantek (tantek@208.54.5.171) (Connection reset by peer)
- # [07:54] <koji> Maybe too quick but blogs tend to use quotes than brackets? no? http://hi.baidu.com/xingyuhann/blog/item/f945aaf8565fdd5e252df2ad.html
- # [07:55] <koji> Can't find single, but several doubles http://snake88888888.blog.163.com/blog/static/128766735200994112349224/
- # [07:56] <koji> The above one uses quites-in-quotes but use double for both
- # [08:04] <fantasai> interesting
- # [08:05] <fantasai> I'm still thinking double=T, single=R is the best option
- # [08:06] <koji> Yeah
- # [08:06] <koji> double=Tu I agree, I see more usage than expected in native context
- # [08:07] <koji> and less worried about single, so I'm fine to follow you, bu
- # [08:07] <koji> woun't someone say they should be consistent?
- # [08:10] <koji> can't find any use of single
- # [08:12] <fantasai> It's inconsistent, because apos makes it inconsistent
- # [08:12] <koji> Yeah, I understand that
- # [08:13] <koji> I don't know if we can convince everyone because I don't agree with them...
- # [08:13] <fantasai> heh
- # [08:14] <koji> and more importantly, no idea what Eric and Laurentiau would think
- # [08:14] <fantasai> well, we can present the data and try
- # [08:14] <fantasai> yes, we need to hear back from MS on this
- # [08:14] * Quits: glenn (gadams@174.16.80.45) (Client exited)
- # [08:15] <koji> But I need to finalize data tonight...
- # [08:18] <koji> They set to Tr originally, with their understanding of Tr,
- # [08:18] <koji> which probably change orientation by fonts,
- # [08:18] <koji> so Tu with vert, and R without
- # [08:18] <koji> Probably the same understanding as Murakami-san had
- # [08:18] <koji> If such "switch by fonts" is not possible,
- # [08:18] <koji> They have to make a hard trade-offs
- # [08:18] <koji> Which isn't easy to predict
- # [08:20] <koji> hm. for people who wants consistency,
- # [08:20] <fantasai> (sorry, just got back home)
- # [08:20] <koji> all of them want consitent and R
- # [08:20] <koji> ok
- # [08:20] <fantasai> I'm ok with R
- # [08:20] <koji> I know :)
- # [08:21] <fantasai> So
- # [08:21] <fantasai> for tonight
- # [08:21] <fantasai> the question is
- # [08:21] <fantasai> What's safest?
- # [08:21] <koji> I mean, they'd complain if we make double Tu too
- # [08:21] <koji> that's the question, and is tough
- # [08:21] <fantasai> R is most consistent
- # [08:22] <fantasai> But if people depend on it and we change, how bad is that?
- # [08:22] <koji> yeah
- # [08:22] <fantasai> Tu is less consistent
- # [08:22] <fantasai> If people depend on it and we change, how bad is that?
- # [08:22] <koji> well
- # [08:22] <fantasai> Which choice will leave fewest people broken if it changes?
- # [08:22] <koji> all quotes in muti-lingual usage will be broken, right?
- # [08:22] <fantasai> Maybe that's the best choice for now.
- # [08:23] <koji> ahhh
- # [08:23] <fantasai> My understanding is that quotation marks belong to the language doing the quoting, not the language of the quotation.
- # [08:23] <koji> small vs small again :)
- # [08:23] <fantasai> So if Chinese is quoting English, quotes should be Chinese
- # [08:23] <fantasai> Quotes inside quotes are rare
- # [08:23] <fantasai> but apostrophes inside Latin are not
- # [08:24] <fantasai> If we go with Tu, they'll be broken in Japanese fonts, because they don't have vert
- # [08:24] <fantasai> but will work better for Chinese, because they have vert
- # [08:24] <koji> yeah
- # [08:25] <fantasai> bbiab
- # [08:26] * fantasai has to set someone up with stuff they need
- # [08:26] <koji> ok
- # [08:29] <fantasai> seems to me for Japanese market...
- # [08:29] <fantasai> if we set T, then it's broken, and people will use text-orientation: sideways
- # [08:29] <fantasai> if it changes to R later, then it still works
- # [08:30] <koji> yeah
- # [08:30] <fantasai> if we set to R, people might depend on it
- # [08:30] <fantasai> Opposite happens in Chinese market
- # [08:30] <fantasai> if we set T, then it works perfect
- # [08:30] <fantasai> and people won't use text-orientation: upright
- # [08:30] <fantasai> if it changes to R later, then it breaks
- # [08:30] <koji> yeah
- # [08:31] <koji> I'm leaning to your idea
- # [08:31] <koji> I guess
- # [08:31] <koji> Both Eric and Laurentiu are working on real-market enough that
- # [08:31] <koji> The real usage wins over theoritical consistency
- # [08:32] <koji> and I like such way to think too
- # [08:33] <koji> U+2018-201B to R, and U+201C-201F to Tu
- # [08:36] <koji> and 301D-301F Tu (we agreed, but UTR is still Tr, we can ignore for now though)
- # [08:38] <fantasai> They're both U in our tables anyway
- # [08:38] <fantasai> if we go with simplified version
- # [08:38] <fantasai> So that won't count as a difference
- # [08:39] <fantasai> I do agree with Murakami-san that if you're going to do a fallback in the case of missing vert, that R is better
- # [08:39] <fantasai> But we don't have that distinction in the classifications yet
- # [08:40] <koji> Yeah
- # [08:40] <koji> I agree too
- # [08:41] <koji> But I don't think Mozilla or WebKit can implement font-dependent orientations
- # [08:42] <koji> You remember that I had strong wish to make it font dependent, don't you
- # [08:42] <fantasai> yes
- # [08:43] <fantasai> ok, so should I draft an email to Addison about this?
- # [08:43] <koji> So you're ok with above?
- # [08:43] <koji> U+2018-201B to R, and U+201C-201F to Tu
- # [08:44] <fantasai> yes
- # [08:44] <koji> ok, let's go that way
- # [08:44] <koji> and for small parenthesis
- # [08:44] <koji> I confirmed they're just rotation
- # [08:44] <koji> so R would probably safer
- # [08:45] <fantasai> how reliable are Chinese fonts in having glyphs?
- # [08:45] <koji> vert glyphs?
- # [08:45] <fantasai> yeah
- # [08:45] <fantasai> for small
- # [08:46] <koji> HVH
- # [08:46] <fantasai> ok, sounds like R is the way to go..
- # [08:47] <koji> wonderful, we resolved all, right?
- # [08:47] <fantasai> I think so...
- # [08:47] <fantasai> Other than Meroitic Egyptian maybe :P
- # [08:47] <koji> ha ha
- # [08:48] <koji> I can warn you when content holders starts creating such documents
- # [08:48] <fantasai> heheh :)
- # [08:48] <koji> and I think we can resolve them at UTC before worrying
- # [08:49] <fantasai> I agree
- # [08:49] <koji> good, so much thank you for making time for me
- # [08:50] <fantasai> thank you for making time for *us* :)
- # [08:50] <koji> :)
- # [08:51] <koji> are you tired? ok?
- # [08:51] <fantasai> btw, did Eric's notes include the Pc changes we agreed to with MS?
- # [08:51] <fantasai> no, I'm good
- # [08:51] * Joins: Ms2ger (Ms2ger@91.181.79.165)
- # [08:51] * fantasai spent the entire day helping a friend debug wireless routers, so working on UTR50 is a relief
- # [08:51] <koji> ah...which Pc?
- # [08:52] <koji> FF3F is left after applying all changes recorded in minutes http://wiki.csswg.org/spec/utr50/diff20120609#pc
- # [08:52] <fantasai> ah, right
- # [08:52] <fantasai> I have no idea what to do with FF3F!
- # [08:53] <koji> all fonts except one (MS JhengHei, TC) have vert for FF3F
- # [08:53] <fantasai> what does vert look like?
- # [08:53] <koji> rotated
- # [08:54] <fantasai> ok
- # [08:54] <fantasai> I think what's in UTR50 is okay
- # [08:54] <fantasai> we could consider making R, but doesn't seem critical
- # [08:55] <koji> Yeah
- # [08:56] <koji> I have to run in 10mins
- # [08:56] <koji> and will work on data after I'm back
- # [08:56] <fantasai> ok
- # [08:56] <koji> Thank you a lot again!
- # [08:56] <fantasai> do you want me to send you a draft of my email first?
- # [08:56] <fantasai> you can check it over
- # [08:56] <koji> No, fine, you can just send
- # [08:57] <fantasai> ok
- # [08:57] <fantasai> I'll CC you
- # [08:57] <koji> Great, thank you
- # [08:58] <koji> I'll CC you when sending data when ready
- # [08:58] <fantasai> ok
- # [08:58] <koji> talk to you later!
- # [08:58] <fantasai> ja ne!
- # [09:12] * Joins: glenn (gadams@174.16.80.45)
- # [09:35] * Quits: glenn (gadams@174.16.80.45) (Client exited)
- # [09:56] <fantasai> koji: sent
- # [10:33] * Joins: heycam|away (cam@203.98.73.35)
- # [10:39] * heycam|away is now known as heycam|away|away
- # [11:12] * Joins: drublic (drublic@77.2.133.124)
- # [13:24] * Quits: dglazkov (u4270@88.198.6.68) (Ping timeout)
- # [13:30] * Joins: dglazkov (u4270@88.198.6.68)
- # [13:44] * Quits: jdaggett (jdaggett@180.235.8.216) (Quit: jdaggett)
- # [16:17] * Joins: glenn (gadams@174.16.80.45)
- # [16:48] * Joins: Ms2ger` (Ms2ger@157.193.2.229)
- # [16:49] * Quits: Ms2ger (Ms2ger@91.181.79.165) (Connection reset by peer)
- # [16:49] * Joins: Ms2ger`` (Ms2ger@91.181.79.165)
- # [16:52] * Quits: Ms2ger` (Ms2ger@157.193.2.229) (Ping timeout)
- # [16:57] * Quits: drublic (drublic@77.2.133.124) (Client exited)
- # [16:58] * Joins: drublic (drublic@77.2.133.124)
- # [17:47] * Quits: Ms2ger`` (Ms2ger@91.181.79.165) (Quit: Leaving)
- # [17:48] * Joins: Ms2ger (Ms2ger@91.181.79.165)
- # [18:50] * Joins: jet (jet@67.169.43.128)
- # [19:57] * Joins: tantek (tantek@66.108.178.122)
- # [20:19] * Quits: jet (jet@67.169.43.128) (Quit: jet)
- # [20:22] * Quits: tantek (tantek@66.108.178.122) (Quit: tantek)
- # [21:16] * Joins: jarek (jarek@83.27.244.145)
- # [21:37] * Quits: Ms2ger (Ms2ger@91.181.79.165) (Quit: nn)
- # [22:01] * Joins: jet (jet@67.169.43.128)
- # [22:01] * Quits: jet (jet@67.169.43.128) (Client exited)
- # [22:05] * Joins: tantek (tantek@66.108.178.122)
- # [22:05] * Joins: dbaron (dbaron@70.36.140.110)
- # [22:54] * Quits: jarek (jarek@83.27.244.145) (Quit: jarek)
- # Session Close: Mon Jun 11 00:00:00 2012
The end :)