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

Re: Korean-specific CSS issues to be discussed

From: Sangwhan Moon <sangwhan.moon@hanmail.net>
Date: Tue, 25 Jan 2011 02:00:44 +0900
Cc: "Kang-Hao (Kenny) Lu" <kennyluck@w3.org>, HTML Korean Interest Group <public-html-ig-ko@w3.org>, ML public-i18n-core <public-i18n-core@w3.org>, fantasai <fantasai.lists@inkedblade.net>
Message-Id: <C97C261A-FA4E-4F94-88A0-45F33FE4750B@hanmail.net>
To: Koji Ishii <kojiishi@gluesoft.co.jp>
On 2011. Jan (1). 21, at 4:34 PM, Koji Ishii wrote:

>> 1. CSS vertical
>> Actually it has disappeared the Korean vertical typesetting since 1999. Now
>> there are only type setting from left to right in Korea. So I think Korea is
>> exceptional case from CJK.
> 
> Just from curiosity. When you want to publish old books written in vertical flow in EPUB, are you going to publish them in horizontal flow?

For archival purposes it would make very little sense to change the original flow of the publication.

On the other hand, documents that have significant archival value do require more than just vertical notation - for one example to replicate the exact transcript of [1][2] Hunminjeongeum Eonhaebon, I would suspect that additional notes might be needed in the specification for this particular use case, as per the Ruby Annotation spec there are only two places to position ruby text in a vertical context - left and right.

Not being a historian (nor a linguist) myself, I'm unable to say much about the actual value of such a use case though apart from that it would be "nice to have".

[1] http://net.segye.com/9932
[2] http://en.wikipedia.org/wiki/Hunminjeongeum
[3] http://www.w3.org/TR/jlreq/

Best regards,
Sangwhan
Received on Monday, 24 January 2011 17:05:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 24 January 2011 17:05:36 GMT