/irc-logs / w3c / #css / 2009-03-04 / end

Options:

  1. # Session Start: Wed Mar 04 00:00:00 2009
  2. # Session Ident: #css
  3. # [00:05] * Quits: annevk (opera@114.48.150.179) (Ping timeout)
  4. # [00:13] * Joins: annevk (opera@114.48.22.145)
  5. # [00:37] * Quits: annevk (opera@114.48.22.145) (Quit: annevk)
  6. # [00:47] * Joins: jdaggett_ (jdaggett@202.221.217.77)
  7. # [00:48] * Quits: jdaggett_ (jdaggett@202.221.217.77) (Quit: jdaggett_)
  8. # [00:48] * Quits: jdaggett (jdaggett@202.221.217.78) (Quit: jdaggett)
  9. # [00:50] * Joins: jdaggett (jdaggett@202.221.217.77)
  10. # [00:52] * jdaggett where is everyone? 9am and not a even a mouse around...
  11. # [00:54] * jdaggett opens the meeting by proposing css 4d transforms with 5x5 matrices
  12. # [00:55] * jdaggett clearing defining cross-cluster selection in the space-time continuum
  13. # [00:55] * jdaggett all in favor say aye
  14. # [00:59] * jdaggett proposal passed! welcome to the new world...
  15. # [01:06] * Joins: dbaron (dbaron@202.221.217.77)
  16. # [01:07] * Joins: sylvaing (sylvaing@202.221.217.77)
  17. # [01:20] * Joins: anne (annevk@202.221.217.77)
  18. # [01:21] <jdaggett> http://www.w3.org/Style/Group/2009/Tokyo.html
  19. # [01:25] * Joins: MikeSmith (MikeSmith@mcclure.w3.org)
  20. # [01:26] * Joins: ChrisL (ChrisL@128.30.52.30)
  21. # [01:26] <ChrisL> rrsagent, here
  22. # [01:27] * Joins: howcome (howcome@202.221.217.77)
  23. # [01:27] * Joins: RRSAgent (rrs-loggee@128.30.52.30)
  24. # [01:27] <RRSAgent> logging to http://www.w3.org/2009/03/04-css-irc
  25. # [01:27] <dbaron> RRSAgent, make logs public
  26. # [01:27] <RRSAgent> I have made the request, dbaron
  27. # [01:27] <ChrisL> trackbot, start telcon
  28. # [01:27] * trackbot is starting a teleconference
  29. # [01:27] <trackbot> RRSAgent, make logs member
  30. # [01:27] <RRSAgent> I have made the request, trackbot
  31. # [01:27] * Joins: Zakim (rrs-bridgg@128.30.52.30)
  32. # [01:27] <trackbot> Zakim, this will be Style_CSS FP
  33. # [01:27] <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
  34. # [01:27] <trackbot> Meeting: Cascading Style Sheets (CSS) Working Group Teleconference
  35. # [01:27] <trackbot> Date: 03 March 2009
  36. # [01:27] <dbaron> RRSAgent, make logs public
  37. # [01:27] <RRSAgent> I have made the request, dbaron
  38. # [01:27] <ChrisL> zakim, remind us in 8 hours to go home
  39. # [01:27] <Zakim> ok, ChrisL
  40. # [01:28] <jdaggett> http://www.w3.org/Style/Group/2009/Tokyo.html
  41. # [01:33] <ChrisL> Topic: Media Queries
  42. # [01:33] <ChrisL> Scribe: Hakon
  43. # [01:34] <ChrisL> scribenick: howcome
  44. # [01:36] * Joins: szilles (chatzilla@202.32.93.230)
  45. # [01:38] <howcome> Chris: specific MQ issues?
  46. # [01:38] <MikeSmith> RRSAgent, make minutes
  47. # [01:38] <RRSAgent> I have made the request to generate http://www.w3.org/2009/03/04-css-minutes.html MikeSmith
  48. # [01:38] <howcome> Anne: several comments have been made
  49. # [01:39] <howcome> Anne: Dean Jackson has proposed changes in aspect-ratio syntax
  50. # [01:39] <ChrisL> Dan Jackson asked for syntax changes in some queries
  51. # [01:39] <anne> http://lists.w3.org/Archives/Public/www-style/2008Dec/0019.html
  52. # [01:39] <anne> http://lists.w3.org/Archives/Public/www-style/2008Oct/0328.html
  53. # [01:40] <howcome> howcome: aren't we dropping these
  54. # [01:40] <howcome> Anne: they're marked at risk
  55. # [01:41] <howcome> Anne: I would be fine dropping the features at risk, and keep orientation unchanged
  56. # [01:41] * Joins: shinyu (shinyu@124.26.216.70)
  57. # [01:41] * Quits: shinyu (shinyu@124.26.216.70) (Connection reset by peer)
  58. # [01:42] * Joins: shinyu (shinyu@124.26.216.70)
  59. # [01:42] <howcome> Anne: the use case is to have a DOM interface to the orientation
  60. # [01:42] * Joins: masayuki (mnakano@202.221.217.77)
  61. # [01:43] <ChrisL> portrait or landscape is much more useful
  62. # [01:44] <howcome> steve: is there a square pixel issue involved?
  63. # [01:44] <howcome> dbaron: 3.1 supports aspect-ration
  64. # [01:45] <howcome> s/ration/ratio/
  65. # [01:45] <fantasai> Anne: s/the use case/the use case for degrees/
  66. # [01:45] <fantasai> Chris: If you're using it for games and things, then you also want to know the tilt, the acceleration, etc. Just make another API
  67. # [01:45] <howcome> dbaron: the use case for device-aspect-ration is weak
  68. # [01:45] <fantasai> Steve: In that case you'd want landscape/portrait in addition to the orientation angle
  69. # [01:46] <fantasai> dbaron: the use case for device-* is weak
  70. # [01:46] <howcome> dbaron: but we implement both aspect-ratio and device-aspect-ratio
  71. # [01:46] <dbaron> s/device-aspect-ration/device-*/
  72. # [01:47] <ChrisL> I could see a stylesheht that gave 4 columns for a 16:9 landscape and 3 for 4:3
  73. # [01:47] <ChrisL> s/shet/sheet/
  74. # [01:48] <howcome> fantasai: one use case is having more columns if the display is wide
  75. # [01:48] <ChrisL> s/sheht/sheet/
  76. # [01:49] <fantasai> anne: in that case you care about the width
  77. # [01:49] <fantasai> fantasai: Not if you're doing a presentation that scales to fill the space
  78. # [01:49] <howcome> steve: if I have several images, I could select the right one to fill the sceen
  79. # [01:50] <howcome> steve: I thought we went through this in great detail, why are we discussin this?
  80. # [01:50] <howcome> annevk: apple has proposed a syntax change
  81. # [01:51] <howcome> dbaron: given that we now support exact matching, we should stick to our current syntax
  82. # [01:51] <ChrisL> yes, trying to match on a float is liable to error
  83. # [01:54] <fantasai> howcome is skeptical that aspect-ratio is useful
  84. # [01:54] <fantasai> fantasai: you can use it to select a different video, widescreen vs fullscreen
  85. # [01:55] <fantasai> anne: device-aspect-ratio would be useful for videos too
  86. # [01:55] <jdaggett> shinyu: http://krijnhoetmer.nl/irc-logs/
  87. # [01:56] <fantasai> fantasai: Media queries are used for more than just CSS
  88. # [01:56] <fantasai> Chris: Mozilla and Opera both implement it
  89. # [01:56] <ChrisL> common industry use is ratio - 16:9, 16:10, 4:3 not 1.623
  90. # [01:57] <ChrisL> so we have implementations in firefox, opera and webkit
  91. # [01:57] <howcome> resolved: no current changes
  92. # [01:58] <howcome> chrisl: any other comments?
  93. # [01:58] <fantasai> RESOLVED: Keep aspect-ratio and device-aspect-ratio, no changes to syntax
  94. # [01:58] <howcome> annevk: some editoral comments, some comments on tty
  95. # [01:59] <howcome> annevk: we don't clarify what px unit means for tty devices
  96. # [02:02] <howcome> annevk: that clarification should possibly go into the Values and Units draft
  97. # [02:03] <ChrisL> there was one about malformed queries
  98. # [02:03] <ChrisL> http://lists.w3.org/Archives/Public/www-style/2008Dec/0064.html
  99. # [02:04] <howcome> chrisl: is there as disposition of comments?
  100. # [02:04] <howcome> annevk: I can add the new issues to the previous disposition of comments
  101. # [02:05] <howcome> dbaron: what's the issue with the formal grammar
  102. # [02:05] <anne> http://www.w3.org/mid/Pine.LNX.4.63.0902242324240.6949@master.abisoft.spb.ru
  103. # [02:08] <howcome> howcome: so, it seems we currently can't take all grammars in all CSS specs, concatinate them and have something valid comes out
  104. # [02:08] <howcome> steve: the formal grammar is only a hint
  105. # [02:09] <howcome> jdaggett: there are things that cannot easily be expressed in formal grammars
  106. # [02:09] * Quits: plinss_ (peter.lins@15.243.169.69) (Quit: plinss_)
  107. # [02:09] <howcome> szilles: do we say anywhere what the goal of the formal grammars are?
  108. # [02:10] <howcome> howcome: HTML5 writes it out in prose
  109. # [02:10] <howcome> Mike: by desing
  110. # [02:10] <howcome> s/desing/design/
  111. # [02:13] * Quits: howcome (howcome@202.221.217.77) (Ping timeout)
  112. # [02:13] * Quits: szilles (chatzilla@202.32.93.230) (Ping timeout)
  113. # [02:14] * Quits: sylvaing (sylvaing@202.221.217.77) (Ping timeout)
  114. # [02:14] * Quits: dbaron (dbaron@202.221.217.77) (Ping timeout)
  115. # [02:14] * Quits: jdaggett (jdaggett@202.221.217.77) (Ping timeout)
  116. # [02:15] * Quits: masayuki (mnakano@202.221.217.77) (Ping timeout)
  117. # [02:15] * Quits: anne (annevk@202.221.217.77) (Ping timeout)
  118. # [02:17] * Quits: ChrisL (ChrisL@128.30.52.30) (Ping timeout)
  119. # [02:17] * Quits: MikeSmith (MikeSmith@mcclure.w3.org) (Ping timeout)
  120. # [02:22] * Joins: sylvaing (sylvaing@202.221.217.77)
  121. # [02:23] * Joins: jdaggett (jdaggett@202.221.217.77)
  122. # [02:23] * Joins: ChrisL (ChrisL@128.30.52.30)
  123. # [02:23] * Joins: szilles (chatzilla@202.221.217.77)
  124. # [02:23] * Joins: anne (annevk@202.221.217.77)
  125. # [02:23] <shinyu> hi
  126. # [02:23] <ChrisL> The spec could state that, due to grammar overrides in the prose, the grammar is not sufficient by itself for creating a parser
  127. # [02:23] <ChrisL> The snapshots could collect together the 2.1 grammar plus the patches defined in each odule, to goive a consistent grammar
  128. # [02:23] * Joins: dbaron (dbaron@202.221.217.77)
  129. # [02:23] * Joins: masayuki (mnakano@202.221.217.77)
  130. # [02:24] * Joins: howcome (howcome@202.221.217.77)
  131. # [02:24] <howcome> annevk: i agree with the comment that the css grammar is rather hacky
  132. # [02:24] <howcome> dbaron: if we think this is important, somebody should sit down and think about it
  133. # [02:24] <howcome> fantasai: the grammar could be described in a snapshot
  134. # [02:24] <howcome> annevk: the alterative is for MQ to define its own grammar, like the CSS selectors spec
  135. # [02:24] <howcome> steve: there are selveral pieces to this: all the bits are not meant to go into a grammar generator
  136. # [02:24] <ChrisL> rrsagent, here
  137. # [02:24] <RRSAgent> See http://www.w3.org/2009/03/04-css-irc#T01-22-08
  138. # [02:25] <ChrisL> Meeting: CSS WG f2f, Tokyo
  139. # [02:25] * Joins: szilles_ (chatzilla@202.32.93.230)
  140. # [02:25] <ChrisL> Chair: Chris
  141. # [02:26] * Joins: MikeSmith (MikeSmith@mcclure.w3.org)
  142. # [02:26] * Quits: szilles (chatzilla@202.221.217.77) (Ping timeout)
  143. # [02:26] * szilles_ is now known as szilles
  144. # [02:26] <howcome> fantasasi: the productions for one specific module is prefixed with an identifier specific to the module; if a production is intended to replace an existing one, this will be marked
  145. # [02:27] <ChrisL> s/ odule/ module/
  146. # [02:27] <fantasai> s/fantasasi/steve/
  147. # [02:27] <ChrisL> s/black/white/
  148. # [02:27] <ChrisL> s/good/bad/g
  149. # [02:29] <howcome> fantasai: anne can either define a grammar for MQ or resolve the differences with the global grammar.
  150. # [02:31] <howcome> chrisl: somebody has to sit down and propose a solution
  151. # [02:31] <howcome> RESOLVED: anne can choose to either define a grammar for MQ or resolve the differences with the global grammar
  152. # [02:33] <fantasai> I don't think we have anything to discuss with namespaces, just need implementation reports
  153. # [02:33] <fantasai> The test suite went through a very meticulous review process and has already been published.
  154. # [03:01] <fantasai> Topic: Paged Media
  155. # [03:01] <shinyu> http://lists.w3.org/Archives/Public/www-style/2009Mar/0005.html
  156. # [03:04] <ChrisL> So, its not possible to select the initial containing block and set its size (and then set the margins to be auto)
  157. # [03:05] <ChrisL> ee: can set the document root element to be a fixed width
  158. # [03:05] * MikeSmith finds http://blog.mozilla.com/webdev/2009/02/27/css3-awesome-test/
  159. # [03:16] * Quits: sylvaing (sylvaing@202.221.217.77) (Ping timeout)
  160. # [03:16] * Quits: anne (annevk@202.221.217.77) (Ping timeout)
  161. # [03:16] * Quits: szilles (chatzilla@202.32.93.230) (Ping timeout)
  162. # [03:17] * Quits: masayuki (mnakano@202.221.217.77) (Ping timeout)
  163. # [03:17] * Quits: jdaggett (jdaggett@202.221.217.77) (Ping timeout)
  164. # [03:17] * Quits: dbaron (dbaron@202.221.217.77) (Ping timeout)
  165. # [03:17] * Quits: MikeSmith (MikeSmith@mcclure.w3.org) (Client exited)
  166. # [03:17] * Quits: ChrisL (ChrisL@128.30.52.30) (Client exited)
  167. # [03:17] * Quits: howcome (howcome@202.221.217.77) (Ping timeout)
  168. # [03:17] * Joins: dbaron (dbaron@202.221.217.77)
  169. # [03:18] * Joins: jdaggett (jdaggett@202.221.217.77)
  170. # [03:18] * Joins: szilles (chatzilla@202.221.217.77)
  171. # [03:20] * Joins: anne (annevk@202.221.217.77)
  172. # [03:20] * Joins: MikeSmith (MikeSmith@mcclure.w3.org)
  173. # [03:21] * Joins: sylvaing (sylvaing@202.221.217.77)
  174. # [03:26] <MikeSmith> jdaggett: 基本半面 in Japanese?
  175. # [03:27] <jdaggett> hmmm
  176. # [03:27] <jdaggett> check jp version?
  177. # [03:28] * MikeSmith looks now.. trying to figure out what "はんめん" means... seems it's not 半面
  178. # [03:28] <jdaggett> http://lists.w3.org/Archives/Public/www-style/2009Mar/0005.html
  179. # [03:28] <MikeSmith> thanks
  180. # [03:28] <jdaggett> 基本版面
  181. # [03:29] <jdaggett> MikeSmith: ^
  182. # [03:29] <MikeSmith> hmm, OK
  183. # [03:29] <MikeSmith> thanks
  184. # [03:33] * Joins: ChrisL (ChrisL@128.30.52.30)
  185. # [03:34] <MikeSmith> so seems like it's 基本版 as as unit modifying 面 .. translates as "baseline page"
  186. # [03:36] <jdaggett> compound noun, no? 基本 + 版面
  187. # [03:37] <ChrisL> rrsagent, here
  188. # [03:37] <RRSAgent> See http://www.w3.org/2009/03/04-css-irc#T02-34-58
  189. # [03:40] <MikeSmith> jdaggett: I never seen the word 版面 ... trying to figure out what it might mean
  190. # [03:41] <jdaggett> http://ext.dictionary.goo.ne.jp/leaf/jn/160482/m0u/%E7%89%88%E9%9D%A2/
  191. # [03:42] * Joins: masayuki (mnakano@202.221.217.77)
  192. # [03:42] <MikeSmith> ah, template, I guess?
  193. # [03:43] <fantasai> Discussion of kohon hanmen and Japanese layout.
  194. # [03:43] <fantasai> Elike summarizes what is meant by "kihon hanmen".
  195. # [03:43] <fantasai> It refers to three things:
  196. # [03:43] <fantasai> 1. The box that is the equivalent of the page area,
  197. # [03:43] <fantasai> i.e. the box in which the content is laid out on
  198. # [03:43] <fantasai> the page.
  199. # [03:43] <fantasai> 2. The settings used to arrive at the size of this
  200. # [03:43] <fantasai> box, namely:
  201. # [03:43] <fantasai> - font-size
  202. # [03:43] <fantasai> - number of columns per page
  203. # [03:43] <fantasai> - column gap
  204. # [03:43] <fantasai> - width of column
  205. # [03:43] <fantasai> - line gap
  206. # [03:43] <fantasai> - number of lines per page
  207. # [03:43] <fantasai> 3. The grid formed by those settings ...
  208. # [03:43] <fantasai> Murakami-san writes:
  209. # [03:43] <fantasai> @page {
  210. # [03:43] <fantasai> margin: auto;
  211. # [03:43] <fantasai> width: 40em;
  212. # [03:43] <fantasai> height: calc(20*16pt);
  213. # [03:43] <fantasai> font-size: 10pt;
  214. # [03:43] <fantasai> line-height: 16pt;
  215. # [03:43] <fantasai> }
  216. # [03:44] <fantasai> Murakam-san explains that in Japanese layout, you start
  217. # [03:44] <fantasai> with the kihon hanmen, and then center it within the page,
  218. # [03:44] <fantasai> or specify one side of the margin and let the other margin
  219. # [03:44] <fantasai> be auto. Suggests a unit for line-height would be useful.
  220. # [03:44] <fantasai> fantasai suggests that allowing @page to accept width and
  221. # [03:44] <fantasai> height should be sufficient. The author (or authoring tool)
  222. # [03:44] <fantasai> may have to do so some math to get the width and height of
  223. # [03:44] <fantasai> the kihon hanmen from the settings, but then the margin
  224. # [03:44] <fantasai> auto positioning should work.
  225. # [03:44] <fantasai> dbaron suggests the rem unit might be useful here
  226. # [03:44] <fantasai> Discussion of whether font-size and line-height in @page
  227. # [03:44] <fantasai> should affect the root element. No, it should not.
  228. # [03:44] <fantasai> Should @page inherit from the root element?
  229. # [03:44] <fantasai> Murakami-san writes column-count, writing-mode, and column-width
  230. # [03:44] <fantasai> into the @page rule. Discussion of page-based templates.
  231. # [03:44] <fantasai> Chris: So the bit of consensus that I heard was that 'width' and 'height' can be used on @page
  232. # [03:44] <fantasai> Steve: Also inheritance is as before, the :root element is the top of the inheritance chain and does not inherit from anything else
  233. # [03:50] <fantasai> Discussion of copying values between @page and :root
  234. # [03:50] <fantasai> fantasai does not want inheritance from @page to :root
  235. # [03:50] <fantasai> fantasai suggests inheritance from :root to @page
  236. # [04:05] <fantasai> Lots of discussion about page templates and getting @page templates to match up with elements in the tree
  237. # [04:05] <fantasai> e.g. an Appendix template that matches up with <div class="appendix">
  238. # [04:06] <fantasai> Proposed resolutions:
  239. # [04:07] <fantasai> 1. Apply width and height to the page box, following rules in CSS2.1:10 wrt calculating margins
  240. # [04:07] <fantasai> 2. @page inherits from the root
  241. # [04:07] <fantasai> 3. Synchronization between named page templates and content deferred until later
  242. # [04:13] <fantasai> fantasai explains that because the print industry is relying on css3-page for their own standards, we may need to add loopholes that allow implementations to be conformant if they don't do the above
  243. # [04:15] <fantasai> RESOLVED: 'width' and 'height' apply to the page box, follow rules in CSS2.1:10 wrt calculating margins. This behavior is at-risk.
  244. # [04:16] <fantasai> RESOLVED: @page inherits from the root. B/c this was not defined in previous CR, conformant implementations may instead use the initial value
  245. # [04:18] <fantasai> s/Synchronization/Synchronization of property values/
  246. # [04:31] <fantasai> Murakami-san shows an example where different parts of the document have different kihon-hanmen
  247. # [04:31] <fantasai> fantasai writes up an example that uses just the new 'width' resolution and named pages to accomplish this use case
  248. # [04:32] <fantasai> Steve suggests adding fantasai's example to the spec
  249. # [04:32] <fantasai> Example is:
  250. # [04:32] <fantasai> <html>
  251. # [04:32] <fantasai> <style>
  252. # [04:32] <fantasai> .main { page: main; columns: 2; column-gap: 1em; } /* 2*30ch width +gap = 61em; */
  253. # [04:33] <fantasai> .index { page: index; columns: 3; column-gap: 1em; } /* 3*20ch width + gap = 62em; */
  254. # [04:33] <fantasai> </style>
  255. # [04:33] <fantasai> <div class="main"> ... </div>
  256. # [04:33] <fantasai> <div class="index"> ... </div>
  257. # [04:33] <fantasai> </html>
  258. # [04:33] <fantasai> @page { margin: auto; }
  259. # [04:33] <fantasai> @page main { width: 61em; }
  260. # [04:33] <fantasai> @page index { with: 62em; }
  261. # [04:34] <fantasai> ACTION: fantasai add this example to the spec
  262. # [04:34] * trackbot noticed an ACTION. Trying to create it.
  263. # [04:34] * RRSAgent records action 1
  264. # [04:34] <trackbot> Created ACTION-125 - Add this example to the spec [on Elika Etemad - due 2009-03-11].
  265. # [04:34] <fantasai> <br type="lunch"/>
  266. # [05:24] * Quits: jdaggett (jdaggett@202.221.217.77) (Ping timeout)
  267. # [05:24] * Quits: sylvaing (sylvaing@202.221.217.77) (Ping timeout)
  268. # [05:24] * Quits: szilles (chatzilla@202.221.217.77) (Ping timeout)
  269. # [05:25] * Quits: masayuki (mnakano@202.221.217.77) (Ping timeout)
  270. # [05:25] * Quits: anne (annevk@202.221.217.77) (Ping timeout)
  271. # [05:25] * Quits: dbaron (dbaron@202.221.217.77) (Ping timeout)
  272. # [05:28] * Quits: ChrisL (ChrisL@128.30.52.30) (Ping timeout)
  273. # [05:28] * Quits: MikeSmith (MikeSmith@mcclure.w3.org) (Ping timeout)
  274. # [05:29] * Joins: dbaron (dbaron@202.221.217.77)
  275. # [05:31] * Joins: sylvaing (sylvaing@202.221.217.77)
  276. # [05:31] * Joins: jdaggett (jdaggett@202.221.217.77)
  277. # [05:32] * Quits: dbaron (dbaron@202.221.217.77) (Ping timeout)
  278. # [05:33] * Joins: dbaron (dbaron@202.221.217.77)
  279. # [05:34] * Joins: ChrisL (ChrisL@128.30.52.30)
  280. # [05:38] <fantasai> Introductions
  281. # [05:40] <fantasai> Joined by
  282. # [05:40] <fantasai> Kobayashi-sensei
  283. # [05:40] <fantasai> Kobayashi-san
  284. # [05:40] <fantasai> Yasuhiro Anan-san
  285. # [05:40] <fantasai> Tatsuo Kobayashi-san, Justsystem, chair of JLTF
  286. # [05:41] <fantasai> Anan-san, Microsoft, will be translating for Kobayashi-sensei
  287. # [05:42] * Joins: szilles_ (chatzilla@202.221.217.77)
  288. # [05:45] <szilles_> EE: offers to discuss the specs that are relevant to the JLTF requirements
  289. # [05:45] * Joins: anne (annevk@202.221.217.77)
  290. # [05:45] <szilles_> EE: there are 3 relevant spects plus GCPM
  291. # [05:45] <dbaron> s/spects/specs/
  292. # [05:45] <szilles_> EE: the first spec is Paged Media that covers the description of the page, its margins, headers and footers, ...
  293. # [05:46] <szilles_> EE: there is a default page, plus pages forfirst, left and right pages and a set of named pages.
  294. # [05:47] <szilles_> EE: the content has to fit inside the page box else it gets clipped
  295. # [05:49] <szilles_> EE: the current Paged Media model does not have a concept of "spread" (that is two facing pages together), that is a topic for a future version.
  296. # [05:50] <szilles_> K-san: what about line-staking-strategy?
  297. # [05:51] <fantasai> Note to self: css3-page should not clip to the page area, but to the padding box of the page box
  298. # [05:53] <szilles_> DB: Some of the goals of the line box module are contradictory; e. g., since an author cannot really know what font (and other) resources will acctually be used.
  299. # [05:54] <szilles_> DB: the current line stacking rules are not ideal for Western topography and they certainly do not consider things like Rugy annotations.
  300. # [05:55] <fantasai> Discussion of line-stacking-strategy
  301. # [05:55] <fantasai> dbaron: The current rules aren't even ideal for Western typogrpahy
  302. # [05:56] <fantasai> dbaron: We might want different options for what gets considered
  303. # [05:57] <fantasai> Anan-san, Kobayashi-san: ruby above the first line spills outside the kihon hanmen
  304. # [05:57] <fantasai> Steve: Do we flag this as an issue to come back to later?
  305. # [05:58] <fantasai> fantasai: yes. We don't have anyone working on a module that involves this. Nobody will be able to fix it within the next 6 months
  306. # [05:59] <szilles_> K-san: figure 37 of the current JLTF draft shows the ruby outside the Kihonhanmen on the first line.
  307. # [06:03] <fantasai> dbaron asks if the ruby crosses the midline between two lines
  308. # [06:03] <fantasai> yes, it does
  309. # [06:03] <szilles_> The current JLTF draft is
  310. # [06:03] <szilles_> http://www.w3.org/2007/02/japanese-layout/docs/aligned/japanese-layout-requirements-en.html
  311. # [06:03] <fantasai> Kobayashi-san: The line gap is usually smaller than the line width, e.g. 2/3
  312. # [06:04] <fantasai> Kobayashi-san: Ruby is usually 1/2 the size of the font size
  313. # [06:05] <szilles_> K-san and K-sensei: the ruby chars are set without and "leading" between the base characters and the ruby characters; this assumes internal leading in the fonts.
  314. # [06:05] <fantasai> Anan-san: The current MSFT implementations grow the line-height to accommodate ruby, but this is not correct
  315. # [06:06] <fantasai> Anan-san: the ruby characters should fit within the line-gap
  316. # [06:06] * Joins: masayuki (mnakano@202.221.217.77)
  317. # [06:10] <szilles_> SZ: One reason that line-stacking-strategy was created was to allow a user to specify whether he wanted to guarantee that no overlap (the CSS rule) or he wanted to guarantee consistent spacing between lines
  318. # [06:11] <szilles_> SZ: Since CSS tries to guarantee no overlap of lines, it would be reasonable to have the Ruby chars taken into account in determining the actual line height.
  319. # [06:12] <szilles_> EE: CSS3 Page module covers margin boxes, their position, their content
  320. # [06:12] <szilles_> EE: for styling the boxes the many of the normal CSS properties can be used.
  321. # [06:12] <szilles_> EE: page numbers can be inserted
  322. # [06:13] <szilles_> EE: various paper sizes can be selected
  323. # [06:14] <szilles_> EE: the current rules in Paged Media select the paper size, and determine the page area by setting values for the margins. This does not guarantee a specified numbers o lines or line lengths
  324. # [06:16] <szilles_> EE: this morning we proposed that Paged Media would allow explicit setting of the Width and Height using the rules of CSS2.1 section 10
  325. # [06:18] <szilles_> EE: this allows explicit setting of the Kihonhanmen size in EMs and centering the resultant area on the paper.
  326. # [06:19] <szilles_> EE: named pages provide a kind of styling template that can be applied to different sections of the content (using selectors)
  327. # [06:20] <szilles_> EE: The second document is CSS Text which is, itself, not a complete module (it is an extract of a prior module.
  328. # [06:21] <szilles_> EE: it covers wihite space control, line breaking and word boundaries.
  329. # [06:22] <szilles_> EE: We know that Japanese has its own line breaking rules which are different than western text rules.
  330. # [06:22] <szilles_> EE: There are some named rules for controlling line breaking
  331. # [06:25] <szilles_> Anan-san: Appendix 3 of the JLTF document has an explicit description of line-breaking for Japanese based on character classes
  332. # [06:28] <szilles_> Anan-san: There are at least two sets of rules for line breaking: basic ones such as the Unicode line breaking rules
  333. # [06:29] <szilles_> Anan-san: and stricter rules that cover a more complete set of cases, such as those in Appendix 3 of the JLTF report
  334. # [06:30] <szilles_> Anan-san: for example, Firefox does a better job of handling rules than some other implementations
  335. # [06:31] <szilles_> Anan-san: Microsoft Word adopted an earlier version of the rules in JIS4051 and, therefore, allows some breaks that would not be expected.
  336. # [06:33] <szilles_> EE: for western text, there are 2 options, break where allowed by the language and break anywhere (including inside a word)
  337. # [06:35] <szilles_> EE: for japanese, there are also two options: loose and strict, with strict being the default. Specifying what these mean, however, is a problem.
  338. # [06:36] <szilles_> Murasaki-san: breaking before small kana is fairly common in Japanese
  339. # [06:39] * Quits: szilles_ (chatzilla@202.221.217.77) (Ping timeout)
  340. # [06:40] * Quits: jdaggett (jdaggett@202.221.217.77) (Ping timeout)
  341. # [06:40] * Quits: masayuki (mnakano@202.221.217.77) (Ping timeout)
  342. # [06:40] * Quits: sylvaing (sylvaing@202.221.217.77) (Ping timeout)
  343. # [06:40] * Quits: anne (annevk@202.221.217.77) (Ping timeout)
  344. # [06:40] * Quits: dbaron (dbaron@202.221.217.77) (Ping timeout)
  345. # [06:40] * Quits: ChrisL (ChrisL@128.30.52.30) (Ping timeout)
  346. # [06:41] * Joins: szilles (chatzilla@202.221.217.77)
  347. # [06:41] <fantasai> Kobayashi-san: There are three levels: newspaper level, magazine level, book level
  348. # [06:41] <szilles> There are 3 levels: newspaper level, magazine level and book level
  349. # [06:41] <fantasai> Murakami-san: Many books use normal level, not strict level
  350. # [06:41] * Joins: jdaggett (jdaggett@202.221.217.77)
  351. # [06:41] * Joins: dbaron (dbaron@202.221.217.77)
  352. # [06:42] * Joins: masayuki (mnakano@202.221.217.77)
  353. # [06:42] <fantasai> Kobayashi-san discusses house rules
  354. # [06:42] <szilles> There are also "house rules" used by a particular publication house
  355. # [06:42] <dbaron> Perfect line breaking rules for English probably don't exist either. Consider finding the allowed breaks in bis(4-chlorophenyl)-1,1,1-trichloroethane
  356. # [06:42] <szilles> K-san: we do not, however, need to have rules at that level of detail
  357. # [06:42] <fantasai> Kobayashi-san: Although some implementations use house rules, we can still define some base levels
  358. # [06:43] <fantasai> Murakami-san writes: loose, normal, strict
  359. # [06:45] <szilles> K-sensei: there are 4 options: loose, normal, strict and very-strict
  360. # [06:45] * Joins: sylvaing (sylvaing@202.221.217.77)
  361. # [06:47] <szilles> very-strict forbids breaks before small-kana, the sound lengthen mark and decoration marks.
  362. # [06:48] <szilles> K-san: almost all publications do not not use very-strict
  363. # [06:48] <szilles> From now on we will use levels 1,2,3 and 4 where 4 is most strict and 1 is least strict
  364. # [06:49] <szilles> level 4 is not often used.
  365. # [06:51] <szilles> K-san agrees that the JLTF will define the rules for the 4 classes of line-breaking rules.
  366. # [06:52] <szilles> EE: could we also get a textual summary of the rules that would give an author an sense of what to expect without tracing thru the table?
  367. # [06:53] <szilles> EE: which level is the default level?
  368. # [06:53] <szilles> K-san/K-sensei: level 3 is the default
  369. # [06:58] <szilles> EE: do these breaking rules also cover numbers and foreign language text?
  370. # [07:00] <szilles> EE: for example, there is a property value that applies to latin text that allows breaking anywhere within a word. This occurs, for example, in Korean usage.
  371. # [07:01] <szilles> K-san/K-sensei: Japanese link-breaking does not allow line-breaking inside a word.
  372. # [07:22] * Quits: dbaron (dbaron@202.221.217.77) (Ping timeout)
  373. # [07:22] * Quits: jdaggett (jdaggett@202.221.217.77) (Ping timeout)
  374. # [07:22] * Quits: szilles (chatzilla@202.221.217.77) (Ping timeout)
  375. # [07:23] * Quits: masayuki (mnakano@202.221.217.77) (Ping timeout)
  376. # [07:23] * Quits: sylvaing (sylvaing@202.221.217.77) (Ping timeout)
  377. # [07:25] * Joins: jdaggett (jdaggett@202.221.217.78)
  378. # [07:26] * Quits: jdaggett (jdaggett@202.221.217.78) (Connection reset by peer)
  379. # [07:27] * Joins: jdaggett (jdaggett@202.221.217.78)
  380. # [07:27] * Quits: jdaggett (jdaggett@202.221.217.78) (Client exited)
  381. # [07:27] * Joins: jdaggett (jdaggett@202.221.217.78)
  382. # [07:28] * Quits: jdaggett (jdaggett@202.221.217.78) (Client exited)
  383. # [07:28] * Joins: jdaggett (jdaggett@202.221.217.78)
  384. # [07:32] * Joins: szilles_ (chatzilla@202.221.217.78)
  385. # [07:33] * Joins: masayuki (mnakano@202.221.217.78)
  386. # [07:35] * Joins: anne (annevk@202.221.217.78)
  387. # [07:37] <szilles_> Resuming after a break
  388. # [07:37] * Joins: ChrisL (ChrisL@128.30.52.30)
  389. # [07:37] * Joins: dbaron (dbaron@202.221.217.78)
  390. # [07:37] <szilles_> EE: The WG thanks the JLTF for agreeing to provide us guidance on line breaking
  391. # [07:37] <dbaron> We also need to keep the line-breaking compatible with English. :-)
  392. # [07:38] <szilles_> EE: text-wrap gives control over chuncks of text beyond the word level
  393. # [07:38] <ChrisL> dictionary-based English hyphenation ftw!
  394. # [07:39] <szilles_> EE: Alignment (horizontal) controls aligning to start, end, center, justify and control over last line as well
  395. # [07:40] * Joins: jdaggett_ (jdaggett@202.221.217.78)
  396. # [07:40] * Quits: jdaggett (jdaggett@202.221.217.78) (Connection reset by peer)
  397. # [07:42] <szilles_> Anan-san/K-sensei: there are cases in Japanese in which a single line is justified.
  398. # [07:42] <szilles_> EE: in CSS, a single line is also a last line.
  399. # [07:43] * Joins: jdaggett (jdaggett@202.221.217.78)
  400. # [07:43] * Quits: jdaggett_ (jdaggett@202.221.217.78) (Ping timeout)
  401. # [07:44] <szilles_> EE: because a window can always be resized, one cannot guarantee that a "single line" will fit within the window so ti would be justified in two or more lines unless wrapping is forbidden
  402. # [07:46] * Joins: glazou (glazou@82.247.96.19)
  403. # [07:46] * glazou waves
  404. # [07:46] <fantasai> Issue: text-align-last: justify center;
  405. # [07:46] * trackbot noticed an ISSUE. Trying to create it.
  406. # [07:46] <trackbot> Created ISSUE-97 - Text-align-last: justify center; ; please complete additional details at http://www.w3.org/Style/CSS/Tracker/issues/97/edit .
  407. # [07:46] <szilles_> Murakami-san: if there is only one character on the last line where is it placed with Justtify?
  408. # [07:49] <szilles_> EE: there is control over which space adjustments are used for justification:
  409. # [07:53] <szilles_> Anan-san: How does "inter-graphemic" apply to east asian languages?
  410. # [07:54] <szilles_> Many: it is there primarily for scripts like indic scripts that have grapheme clusters.
  411. # [07:55] <szilles_> Anan-san: Japanese characters with diacrictics for voicing do form a grapheme
  412. # [07:57] * Joins: sylvaing (sylvaing@202.221.217.78)
  413. # [07:58] <szilles_> Issue: If the same about of extra space that is being used between full width characters (for justification) is also put between half width characters, then the alignment of two half width characters with one full width character will be broken.
  414. # [07:58] * trackbot noticed an ISSUE. Trying to create it.
  415. # [07:58] <trackbot> Created ISSUE-98 - If the same about of extra space that is being used between full width characters (for justification) is also put between half width characters, then the alignment of two half width characters with one full width character will be broken. ; please complete additional details at http://www.w3.org/Style/CSS/Tracker/issues/98/edit .
  416. # [07:59] <dbaron> (I asked a few minutes ago what happens with halfwidth characters and justification.)
  417. # [07:59] <fantasai> ISSUE: make sure justification allows not justifying between various bits of punctuation
  418. # [07:59] * trackbot noticed an ISSUE. Trying to create it.
  419. # [07:59] <trackbot> Created ISSUE-99 - Make sure justification allows not justifying between various bits of punctuation ; please complete additional details at http://www.w3.org/Style/CSS/Tracker/issues/99/edit .
  420. # [07:59] <szilles_> Anan-san: the vertical kana repeat mark upper half should not be split from the lower half mark during justification
  421. # [08:03] <szilles_> JD: In implementation that use the typographic data in a font should not be considered non-conforming
  422. # [08:03] <szilles_> s/implementation/implementations/
  423. # [08:04] <szilles_> s/In i/I/
  424. # [08:04] <szilles_> EE: there is spacing that does "tracking"
  425. # [08:05] <szilles_> EE: Word spacing does not (should not) apply to the Ideographic Space.
  426. # [08:07] <szilles_> Anan-san: Tsumegumi controls the reduction of spaces between characters up to the collision of the glyphs
  427. # [08:09] <szilles_> JD: letter spacing is problematic becuase when kerning is involved you want a multiplicative property rather than a adative one.
  428. # [08:09] <szilles_> EE: the current design has a percentage of the letter space; what is wanted?
  429. # [08:11] <szilles_> JD: what is desired for letter spacing is to add/subtract a percentage of the character advance rather than a fixed amount between all characters.
  430. # [08:11] <fantasai> Issue: percentage should be wrt character advance, (before or after kerning?)
  431. # [08:11] * trackbot noticed an ISSUE. Trying to create it.
  432. # [08:11] <trackbot> Created ISSUE-100 - Percentage should be wrt character advance, (before or after kerning?) ; please complete additional details at http://www.w3.org/Style/CSS/Tracker/issues/100/edit .
  433. # [08:11] <szilles_> Note that kerning changes the advance between certain characters
  434. # [08:12] <fantasai> Steve says after kerning
  435. # [08:14] * glazou brb's, daddy duty
  436. # [08:15] <fantasai> fantasai: that would create uneven spacing in, e.g. "filling"
  437. # [08:15] <fantasai> "milling"
  438. # [08:15] <ChrisL> "Anyone who would letterspace blackletter would steal sheep."
  439. # [08:16] <szilles_> SZ: the specification of these properties should not require the implementation of bad typography; it should allow an implementation to do "better than a minimum level"
  440. # [08:16] <dbaron> fantasai, so why are you introducing a new feature (% letter spacing) if you don't think it does something reasonable?
  441. # [08:17] <szilles_> EE: with evenly spaced tsumegumi, how do measure the space added or subtracted?
  442. # [08:18] <fantasai> fantasai, we're missing a measurement that accounts for the character advance width
  443. # [08:18] <szilles_> discussion: the tracking value is not applied to the full character advance, but (in an as yet undefined way) to the space between characters after kerning is done
  444. # [08:19] <fantasai> fantasai, so I picked a way to reference the advance with of a space character
  445. # [08:19] * glazou is back
  446. # [08:19] <fantasai> s/fantasai,/dbaron,/
  447. # [08:19] <fantasai> dbaron, right now you can reference ems
  448. # [08:19] <fantasai> dbaron, but that gives weird results if you compare a narrowly-designed font with a widely-designed one
  449. # [08:20] <szilles_> a;nan-san/K-sensei: the tsumegumi can be specified in ems because the amount is typically a percent of the font size.
  450. # [08:21] <fantasai> anan-san: the letter-spacing applied to cjk would usually be too much for latin
  451. # [08:21] <fantasai> anan-san: so you may need a way to separate
  452. # [08:22] <szilles_> Anan-san/K-sensei: when a line has mixed latin and ideographic text the space adjustments are not uniform across the line but are different for the different kinds of text
  453. # [08:24] * Quits: arronei (arronei@131.107.0.71) (Ping timeout)
  454. # [08:25] <szilles_> CL: rather than have different letter spacing values for each language, it would be better to markup each section of text with its language and use selectros to apply differn letter spacing values to the different spans
  455. # [08:28] <szilles_> K-san: I like CL's solution because it also handles cases where in a span things liek the font-size is changed and the letter spacing needs to change.
  456. # [08:29] <szilles_> EE: but, there will be cases where the foreign text is not marked up and there needs to be a way to deal with those cases.
  457. # [08:30] * Joins: arronei (arronei@131.107.0.71)
  458. # [08:31] <fantasai> K-san: tsumegumi like this is usually only used for short bits of text in large fonts, such as headings
  459. # [08:31] <fantasai> K-san: so this solution should be sufficient
  460. # [08:31] <szilles_> EE: trying to use Unicode ranges to control the letter-spacing is not a good idea because it does not deal with punctuation characters
  461. # [08:33] <fantasai> EE shows definition for punctuation-trim
  462. # [08:34] <fantasai> jdaggett: is this in addition to or instead of kerning?
  463. # [08:35] * Quits: szilles_ (chatzilla@202.221.217.78) (Ping timeout)
  464. # [08:36] <fantasai> jdaggett: if the font is already doing this kerning, we can't tell
  465. # [08:36] <fantasai> anan-san: Also, the same Unicode code-point is different depending on what language the font was designed for
  466. # [08:40] <fantasai> k-san: Three issues interrelated: where to break the line, where to position characters by default, where to adjust (justify) the line
  467. # [08:42] * Joins: szilles_ (chatzilla@202.221.217.78)
  468. # [08:42] <fantasai> k-san: There are several places to solve the issue. The CSS level, the font level, ...
  469. # [08:43] <fantasai> k-san: Justsystem and MSFT, between ours the handling of parentheses is slightly different
  470. # [08:43] <fantasai> s/.../OS-level/
  471. # [08:43] <fantasai> k-san: CSS should explicitly define its position, this will be helpful to other parties
  472. # [08:44] <fantasai> anan-san: Technically we can define the pairs at the font level, but once you put the characters in the line you may want different results
  473. # [08:44] <szilles_> earlier lost data:
  474. # [08:44] <szilles_> EE: punctuation-trim property - this handles the conversion of full width punctuation to half width
  475. # [08:44] <szilles_> JD: asks how this interacts with information in kerning tables in the fonts
  476. # [08:45] <szilles_> It is really hard to know if such kerning data is in the font which makes it difficult to tell whether the lower level enging (e.g. Uniscribe) will do the xform or not.
  477. # [08:45] * Joins: melinda (melinda.gr@67.47.246.6)
  478. # [08:46] <fantasai> EE: so do we assume the font is wide or not?
  479. # [08:48] <fantasai> no real answer
  480. # [08:48] <fantasai> Murakami-san: Antenna House implements punctuation-trim
  481. # [08:48] <fantasai> Murakami-san: It applies only to CJK fonts
  482. # [08:48] <fantasai> Murakami-san: That have fixed-em width
  483. # [08:48] <fantasai> Murakami-san: full-width brackets only
  484. # [08:48] <fantasai> Murakami-san: Not applied to narrow punctuation
  485. # [08:49] <fantasai> Murakami-san: Interaction with kerning is not a problem.
  486. # [08:49] <fantasai> EE: how do you know if it's full-width?
  487. # [08:49] <fantasai> Murakami-san: MS Mincho has full-width fixed-width glyphs for punctuation
  488. # [08:49] <fantasai> Murakami-san: But MS P Mincho has narrower glyphs for Japanese punctuation
  489. # [08:50] <fantasai> Murakami-san: Antenna House punctuation-trim controls MS Mincho, but not MS P Mincho
  490. # [08:50] <fantasai> jdaggett: With a proportional font, the "half-width" characters are proportionally spaced
  491. # [08:50] <fantasai> jdaggett: whereas in a full-width font they are not (end of summary of P vs not P)
  492. # [08:51] <fantasai> K-san: In Unicode, fullwidth punctuation marks usually have half-width default size
  493. # [08:51] <fantasai> K-san: in the JLTF document
  494. # [08:52] <fantasai> K-san: In Japanese typsetting tradition, especially hot-metal era, usually the punctuation marks are 1/2 em size
  495. # [08:52] <fantasai> K-san: So when the punctuation mark need to be 1em we add 1/2em space
  496. # [08:52] <fantasai> K-san: Steve and us made 6 hours discussion on this at the last meeting
  497. # [08:52] <fantasai> K-san: And we decided to describe every punctuation mark as 1/2 width size as a default
  498. # [08:53] <fantasai> K-san: And with some other half-width space added
  499. # [08:53] <fantasai> K-san: Our document is based on such an agreement
  500. # [08:53] <fantasai> Steve: The reason that the discussion took 6 hours was primarily because there were several kinds of terminology being used in different parts of the document
  501. # [08:54] <fantasai> Steve: this contributed confusion on the part of the non-Japanese speakers who were tyring to read the document and weren't sure how many different principles were used
  502. # [08:54] <fantasai> Steve: So we picked one that made sense to the ppl writing the document and use that consistently
  503. # [08:55] <fantasai> jdagget: Fonts, and OpenType especially, have many ways of doing the same thing. E.g. kerning
  504. # [08:55] * Quits: Lachy (Lachlan@85.196.122.246) (Quit: Leaving)
  505. # [08:58] * Joins: Lachy (Lachlan@85.196.122.246)
  506. # [09:04] <fantasai> Murakami-san: professional Japanese fonts use fullwidth pucntuation
  507. # [09:05] <fantasai> discussion of P Gothic black magic
  508. # [09:06] <fantasai> Anan-san: You can do pairs kerning in Uniscribe, but it's performance-expensive
  509. # [09:06] <fantasai> Anan-san: ...
  510. # [09:07] <fantasai> jdaggett: FF uses Uniscribe for a lot of text rendering
  511. # [09:07] <fantasai> jdaggett: for desktop, it's ok
  512. # [09:07] <fantasai> jdaggett: for mobile device, ehhh
  513. # [09:07] <fantasai> Murakami-san: Meiryo also has fixed full-width punctuation
  514. # [09:08] <fantasai> Murakami-san: even though Latin is proportional
  515. # [09:12] <szilles_> K-san: the JLTF is willing to consider having levels w.r.t the punctiuation-trim as will be done for line-breaking
  516. # [09:13] <szilles_> EE: the CSS WG has to explain the requirements for punctuation-trim in a way that implementers can implement it.
  517. # [09:14] <szilles_> EE: underline position does not really support Japanese because the convention in Japanese is to use underlines on horizontal text and before-edge lines in vertical text
  518. # [09:17] <szilles_> K-san: the spacing of the "underline" relative to the character box is up to the implementation; they may or may not be useful information for this in the font.
  519. # [09:18] <szilles_> K-sensei: Kendots should be used only for vertical text
  520. # [09:21] <szilles_> K-san: there are two code point for the dots; it is the context of usage, horiz or vert, that determines which glyph is used, independently of which code point is used to represent the dots
  521. # [09:21] <szilles_> Note, also, that the "dots" do not occur in the content, they are generated by CSS UA.
  522. # [09:22] * glazou goes to his office and will rejoin from there
  523. # [09:22] * glazou bbiab
  524. # [09:22] * Quits: glazou (glazou@82.247.96.19) (Quit: glazou)
  525. # [09:27] <Zakim> ChrisL, you asked to be reminded at this time to go home
  526. # [09:29] <anne> good idea
  527. # [09:30] <szilles_> K-san/K-sensei: w.r.t. middle dot or the accent character, the normal size of the full width character is used, but 1/4 em is trimmed off the top and bottom of the character in a dot above the character or from the left and right of the character in a dot on the before edge.
  528. # [09:33] <szilles_> K-sensei: Ruby and dots will not be used together; therefore dots should be ignored (for Japanese) if specified with ruby.
  529. # [09:35] <szilles_> K-sensei: if text with Ruby annotation is to be emphasized, it can be done by using brackets before and after the emphasized text
  530. # [09:35] <szilles_> EE: Hanging Punctuation has 3 values
  531. # [09:36] <shinyu> http://lists.w3.org/Archives/Public/www-style/2007Oct/0204.html
  532. # [09:36] <szilles_> Start allows the bracket to occur prior to where the first non-punctuation character is to occur
  533. # [09:36] <szilles_> End does the same for the last line
  534. # [09:37] <fantasai> Murakami-san presents his proposal
  535. # [09:37] <szilles_> end-edge allows hanging on end of every line
  536. # [09:39] <szilles_> CL: is there a use case for "start-edge" in analogy to "end-edge"
  537. # [09:40] <szilles_> EE: if there is an indent of the first line, then hanging means into the indent space, not the content area.
  538. # [09:41] <szilles_> EE: what punctuation characters are allowed to hang with "end-edge"?
  539. # [09:42] * Zakim excuses himself; his presence no longer seems to be needed
  540. # [09:42] * Parts: Zakim (rrs-bridgg@128.30.52.30)
  541. # [09:43] <szilles_> Murakami-san/K-sensei: only 4 characters (stop, ideographic stop, comma and ideographic comma) can hang with "end-edge"
  542. # [09:46] <szilles_> Murakami-san/EE: for "start" the punctuation that hangs are opening brackets and quotes; for "end" they are ending brackets and quotes.
  543. # [09:47] <szilles_> It was ageed that there is no Japanese use case for "start-edge".
  544. # [09:52] <fantasai> end should have end-auto functionality
  545. # [09:53] <fantasai> forcing the punctuation to hang should be 'force-end'
  546. # [09:53] <szilles_> K-sensei: there is a requirement for a "forced-end" value which forces the final stop to be hanging and then justifies the chararacters that remain on the line.
  547. # [09:59] <szilles_> EE and Murakami-san: In the above discussion, replace "end-edge" with "end"; replace "start" with "first" and "end" with "last"
  548. # [10:00] * Joins: glazou (glazou@80.118.184.70)
  549. # [10:01] <szilles_> This renaming leaves "forced-end" meaning that the hang is forced on any line that ends with one of the four punctuation symbols that can hang with "end"
  550. # [10:04] * Joins: MikeSmith (MikeSmith@mcclure.w3.org)
  551. # [10:05] <fantasai> Murakami-san suggests maybe 'end' might be confusing with 'forced-end' for Western typographers
  552. # [10:05] <fantasai> Western typography typically only hangs the hyphen, and it's not common
  553. # [10:06] <fantasai> Suggestion: 'allow-end' 'forced-end'
  554. # [10:06] <fantasai> Other suggestion, need 'hypens' value? since Japanese doesn't hang hyphens
  555. # [10:07] <fantasai> Meeting closed
  556. # [10:08] <szilles_> EE: suggests that "end" be called "allow-end" to make it relationship to "force-end" to be more clear.
  557. # [10:08] <szilles_> At 6:10, the meeting adjourned for the day.
  558. # [10:08] * Quits: ChrisL (ChrisL@128.30.52.30) (Client exited)
  559. # [10:10] * Quits: jdaggett (jdaggett@202.221.217.78) (Quit: jdaggett)
  560. # [10:11] * Quits: sylvaing (sylvaing@202.221.217.78) (Ping timeout)
  561. # [10:11] <MikeSmith> RRSAgent, make minutes
  562. # [10:11] <RRSAgent> I have made the request to generate http://www.w3.org/2009/03/04-css-minutes.html MikeSmith
  563. # [10:12] * Quits: shinyu (shinyu@124.26.216.70) (Quit: See you...)
  564. # [10:12] <glazou> have a nice evening
  565. # [10:12] * Quits: glazou (glazou@80.118.184.70) (Quit: glazou)
  566. # [10:12] <MikeSmith> RRSAgent, make logs public
  567. # [10:12] <RRSAgent> I have made the request, MikeSmith
  568. # [10:13] * Quits: szilles_ (chatzilla@202.221.217.78) (Ping timeout)
  569. # [10:15] * Quits: dbaron (dbaron@202.221.217.78) (Quit: 8403864 bytes have been tenured, next gc will be global.)
  570. # [10:17] * Quits: masayuki (mnakano@202.221.217.78) (Ping timeout)
  571. # [10:18] * Parts: anne (annevk@202.221.217.78)
  572. # [10:20] * Quits: MikeSmith (MikeSmith@mcclure.w3.org) (Quit: Tomorrow to fresh woods, and pastures new.)
  573. # [10:24] * Joins: masayuki (mnakano@202.221.217.78)
  574. # [11:12] * Joins: A (A@85.185.37.200)
  575. # [11:19] * Quits: A (A@85.185.37.200) (Quit: used MtvIRC 2.1)
  576. # [11:59] * Joins: myakura (myakura@122.29.116.63)
  577. # [13:13] * Joins: dbaron (dbaron@222.151.83.100)
  578. # [13:35] * Joins: szilles (chatzilla@124.155.113.142)
  579. # [13:41] * Joins: szilles__ (chatzilla@202.32.93.230)
  580. # [13:41] * Quits: szilles (chatzilla@124.155.113.142) (Ping timeout)
  581. # [13:41] * szilles__ is now known as szilles
  582. # [13:47] * Quits: masayuki (mnakano@202.221.217.78) (Quit: See you...)
  583. # [14:06] * Joins: sylvaing (sylvaing@210.188.139.188)
  584. # [14:13] * Quits: szilles (chatzilla@202.32.93.230) (Ping timeout)
  585. # [14:18] * Quits: sylvaing (sylvaing@210.188.139.188) (Ping timeout)
  586. # [14:39] * Joins: annevk (opera@114.48.227.62)
  587. # [14:42] * Quits: dbaron (dbaron@222.151.83.100) (Quit: 8403864 bytes have been tenured, next gc will be global.)
  588. # [16:11] * Quits: annevk (opera@114.48.227.62) (Quit: annevk)
  589. # [16:59] * RRSAgent excuses himself; his presence no longer seems to be needed
  590. # [16:59] * Parts: RRSAgent (rrs-loggee@128.30.52.30)
  591. # [18:23] * Joins: dsinger (dsinger@66.28.50.51)
  592. # [18:23] <dsinger> zakim, who is here?
  593. # [18:44] * Quits: dsinger (dsinger@66.28.50.51) (Quit: dsinger)
  594. # [19:22] * Quits: myakura (myakura@122.29.116.63) (Quit: Leaving...)
  595. # [19:35] * Quits: shepazu (schepers@128.30.52.30) (Ping timeout)
  596. # [19:49] * Joins: shepazu (schepers@128.30.52.30)
  597. # [20:46] * Quits: melinda (melinda.gr@67.47.246.6) (Connection reset by peer)
  598. # [20:47] * Quits: arronei (arronei@131.107.0.71) (Ping timeout)
  599. # [20:52] * Joins: arronei (arronei@131.107.0.71)
  600. # [22:32] * Joins: szilles_ (chatzilla@202.32.93.230)
  601. # [22:32] * szilles_ is now known as szilles
  602. # [22:49] * Quits: szilles (chatzilla@202.32.93.230) (Ping timeout)
  603. # [23:06] * Joins: sylvaing (sylvaing@210.188.139.162)
  604. # [23:45] * Quits: sylvaing (sylvaing@210.188.139.162) (Ping timeout)
  605. # [23:52] * Joins: annevk (opera@114.48.30.0)
  606. # Session Close: Thu Mar 05 00:00:00 2009

The end :)