/irc-logs / w3c / #css / 2011-06-01 / end

Options:

# Session Start: Wed Jun 01 00:00:00 2011
# Session Ident: #css
# [00:10] * Quits: arno (arno@192.150.10.200) (Quit: Leaving.)
# [00:12] * Joins: arno (arno@192.150.10.201)
# [00:22] * Quits: arronei (arron.eich@131.107.0.117) (Quit: arronei)
# [00:26] * Joins: arronei (arron.eich@131.107.0.91)
# [00:39] * Quits: dbaron (dbaron@222.151.136.131) (Quit: 8403864 bytes have been tenured, next gc will be global.)
# [00:40] * Joins: arronei_ (arron.eich@131.107.0.84)
# [00:41] * Quits: arronei (arron.eich@131.107.0.91) (Ping timeout)
# [00:42] * Joins: arronei (arron.eich@131.107.0.71)
# [00:43] * Quits: arronei_ (arron.eich@131.107.0.84) (Ping timeout)
# [00:56] * Quits: arronei (arron.eich@131.107.0.71) (Quit: arronei)
# [01:07] * Joins: arronei (arron.eich@131.107.0.73)
# [01:49] * Quits: arronei (arron.eich@131.107.0.73) (Quit: arronei)
# [01:52] * Joins: arronei (arron.eich@131.107.0.81)
# [01:56] * Joins: dbaron (dbaron@125.207.177.35)
# [01:56] * Quits: fantasai (fantasai@69.162.163.148) (Ping timeout)
# [02:00] * Quits: dbaron (dbaron@125.207.177.35) (Quit: 8403864 bytes have been tenured, next gc will be global.)
# [02:00] * Quits: arronei (arron.eich@131.107.0.81) (Quit: arronei)
# [02:04] * Joins: arronei (arron.eich@131.107.0.73)
# [02:18] * Joins: dbaron (dbaron@125.207.177.35)
# [02:26] * Joins: fantasai (fantasai@69.162.163.148)
# [02:50] * Joins: plinss (plinss@125.207.177.35)
# [02:58] * Joins: RRSAgent (rrs-loggee@128.30.52.169)
# [02:58] <RRSAgent> logging to http://www.w3.org/2011/06/01-css-irc
# [02:58] <fantasai> Nat McCully (Adobe)
# [02:58] <fantasai> Nat talks about line layout, and how the model in CSS differs from that in InDesign
# [02:58] <fantasai> Nat: Core concept of ideographic embox
# [02:58] * hober thanks fantasai for scribing this! :)
# [02:59] * Joins: szilles (chatzilla@125.207.177.35)
# [02:59] <fantasai> Nat: In 1998, most fonts don't have this. Each product had to do calculations for it.
# [02:59] <fantasai> Nat: ...
# [02:59] <fantasai> Nat: Once you have ideographic embox built into line layout engine, you can support other concepts
# [02:59] <fantasai> Nat: e.g. leading direction -- whether leading is forwards or backwards wrt line
# [03:00] <fantasai> Nat: If you have two lines and you set leading, which one will move?
# [03:00] <fantasai> Nat: Leading measurement points, or baselines, is from where in the line do you measure from
# [03:01] <fantasai> Nat: When you have multiple font sizes in a line, changing this reference point changes the spacing between lines
# [03:01] <fantasai> Nat: Lastly, if we have time I can talk about Mojikumi spacing. Refers to adjustment of space around punctuation to achieve good full justification.
# [03:02] <fantasai> Nat: So, when laying text out on the screen, you generally have margins, that you decide, and in both CSS layout and InDesign you decide the LTRB margins
# [03:02] <fantasai> Nat: within which you want to layout a text line.
# [03:02] <fantasai> Nat: So each line box gets laid out within the margin area
# [03:02] <fantasai> Nat's screen shows a white box with purple rectangles representing line boxes
# [03:02] <fantasai> Nat: Vertical layout is similar
# [03:03] <fantasai> Nat's screen shows the same, but with the line boxes oriented vertically
# [03:03] * Quits: szilles (chatzilla@125.207.177.35) (Ping timeout)
# [03:03] <fantasai> Nat: But there are some differences between CSS and traditional line layout
# [03:03] <fantasai> Nat: Within the line box, we have a calculated line height
# [03:03] <fantasai> Nat: In CSS this is equal to the leading.
# [03:03] <fantasai> Nat: For example, if you have this text (shows some text in English)
# [03:03] <fantasai> Nat: You get the ascent and descent from the font metrics to calculate the text height
# [03:04] <fantasai> Nat: And you place it somewhere within that line height
# [03:04] <fantasai> Nat: So, let's depart a bit from CSs and talk about InDesign Roman Composition.
# [03:04] <fantasai> Nat: Within the first line's line height, we place the text like this
# [03:04] <fantasai> Nat shows a purple box covering the ascent.
# [03:04] <fantasai> Nat: The second line box looks like this, and the text is placed thus
# [03:04] <fantasai> Nat shows the second line box extending from alphabetic baseline of first line to alphabetic baseline of second line
# [03:05] <fantasai> Nat: So the first line has the same height as the ascent
# [03:05] <fantasai> Nat: Second line uses 100% of the leading *of the second line*.
# [03:05] <fantasai> Nat: So the line leading direciton is upwards in this case.
# [03:05] <fantasai> Nat: Notice that each line's y position in the frame is equal to the Roman baseline.
# [03:06] <fantasai> Nat: You can see that the descender of the second line is hanging outside the linebox.
# [03:06] <fantasai> Nat: So, how did I change this for Japanese?
# [03:06] <fantasai> Nat: In Japanese composition, you need to do some different hings.
# [03:06] <fantasai> Nat: You have your line box.
# [03:06] <fantasai> Nat: And you have text placed within that line box
# [03:06] <fantasai> Nat: And then you have your second line with its line box, and then text inside that one
# [03:06] <fantasai> Nat: The first line offset is set to the embox height
# [03:07] <fantasai> Nat: OpenType fonts have an 'ideo' baseline.
# [03:07] <fantasai> Nat: This was added so that the font designer can tell us where the Roman baseline is wrt the embox
# [03:07] <fantasai> Nat: The second line offset is the embox height of the second line plus the previous line gap.
# [03:07] <fantasai> Nat: The line gap is placed downward
# [03:08] <fantasai> Nat's screen shows a purple box the height of the Japanese text, a gap, and then the next purple box
# [03:08] <fantasai> Nat: The default behavior in InDesign is to measure from the embox top to the next embox top
# [03:08] <fantasai> Nat: when setting leading
# [03:08] <fantasai> Nat: So in developing the EPUB layout engine, I've been working with experts at adobe to tell me how conventions are followed in CSS.
# [03:08] <fantasai> Nat: And so when placing text within the line, we first get the metrics fo the font
# [03:09] <fantasai> Nat: and then we divide the line gap in half, and place half above the text and half below
# [03:09] <fantasai> Nat's screen shows a diagram of this
# [03:09] <fantasai> Nat: I'm told this is in order to make it easier for browsers to avoid text lines writing on top of each other, and ot give enough space above and below the text for ascenders and descenders.
# [03:09] <fantasai> Nat: When I first saw this, I thought, what a problematic way to do text layout
# [03:10] <fantasai> Nat: because you cannot predict where the text will be within the line box
# [03:10] <fantasai> Nat: This is especially true when you have different font sizes
# [03:10] <fantasai> Nat: So the line y position for the layout engine is at the baseline, because when you're drawing text you need to place the pen at the roman baseline
# [03:10] <fantasai> Nat: So, suppose we have some different-sized text within the line
# [03:11] <fantasai> Nat: We have our line box, and each line's metrics
# [03:11] <fantasai> Nat's screen shows two text boxes aligned by baseline
# [03:11] <fantasai> Nat: Then you add the line gap.
# [03:11] <fantasai> Nat: The line height increases as you add text.
# [03:11] <fantasai> Nat: The baseline moves down, but the calculation is not straightforward if you want to get an exact pixel position on the screen.
# [03:12] <fantasai> Nat: In InDesign, when you have different point sizes, such as in this Japanese run
# [03:12] <fantasai> Nat: We get the text metrics as before
# [03:12] <fantasai> Nat: ...
# [03:12] <fantasai> Nat: The Japanese text has a particular relation to the roman baseline
# [03:13] <fantasai> Nat: As far as the user is concerned, they don't have to worry about the calculations. Their text is centered within the line box
# [03:13] <fantasai> Nat's screen shows large Japanes text next to small Japanese text within the purple line box
# [03:13] <fantasai> The roman baselines are not aligned -- the ideographic emboxes are centered within the purple line box
# [03:14] <fantasai> Nat: In CSS, there have been controls added for choosing baselines.
# [03:14] <fantasai> Nat: The main problem I have right now is leading being added above and below
# [03:14] <fantasai> Nat: I have a proposal to solve it, but it has some drawbacks.
# [03:15] <fantasai> Nat: In Japanese two major baslines used are embox center baseline and embox bottom baseline
# [03:15] <fantasai> Nat: When measuring leading, you measure from top of embox to top of next embox
# [03:15] <fantasai> Nat shows a diagram. Gap between lines is labeld as aki -- line gap
# [03:15] <fantasai> Nat: Why do we need grids?
# [03:16] <fantasai> Nat: In InDesign we have two different grids.
# [03:16] <fantasai> Nat: First is the Roman baseline grid.
# [03:16] <fantasai> Nat: This grid is in both Japanese and Roman InDesign.
# [03:16] <fantasai> Nat: In Japanese InDesign we added a different grid.
# [03:16] <fantasai> Nat: This is what a Japanese grid looks like.
# [03:17] <fantasai> Nat shows example with long rectangles representing the lines, separated by gaps
# [03:17] <fantasai> Most lines are that size, and fit within that grid
# [03:17] <fantasai> Three lines are in a bigger font size: they are centered within the bounding box of four line grid boxes.
# [03:18] <fantasai> Nat: In the Japanese grid, we can center wrt the grid
# [03:18] <fantasai> Nat shows an example where there is small text, then large text, then small text in one line
# [03:18] <fantasai> Nat: The big bold text is centered within the two grid boxes
# [03:18] <fantasai> Nat: The first run is bottom-aligned to the centered text. The second small run is top-aligned wrt the centered (bold) text.
# [03:19] <fantasai> Nat: When the text is placed wrt the grid, it makes for a more pleasant reading experience.
# [03:19] <fantasai> Nat: So to summarize, the Japanese grid has seeral purposes
# [03:19] <fantasai> 1) Sets the frame size to fit the grid
# [03:20] <fantasai> 2) Positions lines in the frame rgardless of font size to fit the grid (snaps like bsaelines e.g. embox centers)
# [03:20] <fantasai> The baseline grid:
# [03:20] <fantasai> 1) Allows lines in the paragrpah to "snap" to the grid, aligning to "snapped" line sin any other frame on the page
# [03:21] <fantasai> 2) Supports any single baseline (embox or Roman) per paragraph
# [03:21] * Joins: alexmog (qw3birc@128.30.52.28)
# [03:21] <fantasai> Nat: The baseline grid is drawn over the whole page.
# [03:21] <fantasai> Nat: When you place frames on that page, the text within those frames is moved to snap to the grid.
# [03:21] <fantasai> Nat: what that accomplishes is that across different frames
# [03:22] <fantasai> Nat: The text matches position
# [03:22] <fantasai> Nat: For example in multiple paragraphs, depending on whether you have titles or pictures or something embedded within those columns,
# [03:22] <fantasai> Nat: The body text in the left column will be snapped to the same lines as the body text in the right coumn
# [03:22] <fantasai> Nat: so that overall the layout on the page will be very clean.
# [03:22] <fantasai> Nat: The snapping behavior to the grid is a paragraph setting
# [03:23] <fantasai> Nat: When you set that, you can have a choice of snapping the first line of the paragraph to the grid, or all lines of the paragraph to the grid.
# [03:23] <fantasai> Nat: Within that, you choose which baseline to snap to
# [03:23] <fantasai> Nat: You can choose embox bottom, embox top
# [03:23] <fantasai> Nat: It snaps to the grid
# [03:23] <fantasai> Nat: So I see that we're almost out of time
# [03:23] <fantasai> Nat: So I will leave it at that and hope we have fruitful discussion about grids and any other thing.
# [03:25] <fantasai> RRSAgent: make logs public
# [03:25] <RRSAgent> I have made the request, fantasai
# [03:25] <fantasai> Koji: I will talk about the Tokyo session and ideas and opinions presented there.
# [03:25] <fantasai> Koji (via translater): We had 5 sessions in Tokyo, and today I will present the results of each of the sessions.
# [03:26] <fantasai> Koji: Firstly, an EPUB session, we had presentation Hiratsukashi
# [03:26] <fantasai> Koji: City of Hiratsukashi has been distributing PR brochure in EPUB since March
# [03:26] <fantasai> Koji: In Hiratsuka in order to reduce file size, they are using CSS3 properties such as border-radius
# [03:26] <fantasai> Koji: And also they are hoping to be able to change the layout depending on the device/orientation
# [03:27] <fantasai> Koji: They're not using Ruby because it was unstable on some terminals, so they are using brackets
# [03:27] <fantasai> Koji: Next panelist we had was person from Toppan printing company.
# [03:27] * Joins: szilles (chatzilla@125.207.177.35)
# [03:27] <fantasai> Koji: One of the first requests that Toppan person made was that they wanted to define box sizing by number of characters and number of lines
# [03:28] <fantasai> Koji: Also, in terms of line-breaking rules in CSS3 Text, they want to specifically designate certain characters for line breaking rules (by codepoint)
# [03:28] * Joins: murakami (murakami@118.154.209.3)
# [03:28] <fantasai> Koji: We also discussed line notes (warichu)
# [03:29] <fantasai> Koji: The comment they raised is how are we going to treat these in Web and ePublishing
# [03:29] <fantasai> Koji: The request comes from the fact that some people would like to publish things like this in electronic formats
# [03:29] <fantasai> Koji: Question is whether something like this can be done in electronic format
# [03:29] <fantasai> Koji: Also, Toppan Printing made comments about so-caled private characters.
# [03:30] <fantasai> Koji: Unicode is so well-spread today. They found 1200 chars in Ko-jien dictionary that are not in Unicode.
# [03:30] <fantasai> Koji: They searched 800 books, 1400 chars (0.6%) are not in Unicode
# [03:31] <fantasai> Koji: So they also said that in archaeologists excavate, every year discover about 30 new characters.
# [03:31] <fantasai> Koji: For EPUB we use WOFF/OpenType, but according to Toppan SVG fonts are easier to create. They suggest supporting SVG, too.
# [03:32] <fantasai> Koji: Discussions about font and private characters will be covered deeper in session 4.
# [03:32] <fantasai> Koji: A person from company Voyager was a panelist
# [03:32] <fantasai> Koji: As you probably aware, they developed ebook reader and marketing it since 1993
# [03:33] <fantasai> Koji: Voyager person made a point that in general Japanese literature you can often see mixed writing modes.
# [03:33] <fantasai> Koji: This is a cover page.
# [03:33] <fantasai> Koji: Then the table of contents follows
# [03:33] <fantasai> Koji: And next is section heading, typically vertical writing to
# [03:33] <fantasai> Koji: Main text is normally all vertical
# [03:33] <fantasai> Koji: And back matter is normally horizontal.
# [03:33] <fantasai> (cover page was also horizontal)
# [03:34] <fantasai> Koji: They raised some questions.
# [03:34] <fantasai> Koji: One was whether mixed mode can be used in EPUB
# [03:34] <fantasai> Koji: Whether change in progresion is possible for section heading
# [03:34] <fantasai> Koji: Other point the Voyager person made was that we may need to review some line-breaking rules
# [03:35] <fantasai> Koji: One of the resons for this is because we are going to enable reflow, or differences in resolution, we may need different line-breaking rules than rules in the paper world.
# [03:35] <fantasai> Koji: In fact, Voyager person said they implemented different line-breaking rules than the one sin JIS, wrt inseparable characters and also some other elements such as grouping (?)
# [03:36] <fantasai> Koji: And some comments were made about possibly user-switchable text-flow.
# [03:36] <fantasai> Koji: Voyager's readers have always supported vertical/horizontal switching by the user.
# [03:36] <fantasai> Koji: concern that this will increase cost of content development.
# [03:37] <fantasai> Koji: In Tokyo discussion, general consensus was that depending on the content we may enable this kind of switching for the user, although it may increase production cost.
# [03:37] <murakami> Voyager readers can break group ruby.
# [03:37] <fantasai> Koji: But we may also implement some mechanism that allows the creator to prevent users from switching.
# [03:37] <fantasai> Koji: Also the other point was made that we may need to allow this kind of switching from accessibility point of view. But this is a different discussion.
# [03:38] <fantasai> Koji: The other request that Voyager made was about old chinese writing (kanbun)
# [03:38] <fantasai> Koji: Their understanding is that kanbun writings are often included in textbooks, so they should be supported.
# [03:38] <fantasai> Koji: In terms of how to support this in CSS/EPUB, needs further discussion.
# [03:38] <fantasai> Koji: Next panelist we heard from was from Impress R&D
# [03:39] <fantasai> Koji: They publish a magazine called [??]
# [03:39] <fantasai> Koji: They're publishing on Web, printing, and ebook.
# [03:39] <fantasai> Koji: They're separate in production, on an experimental basis
# [03:39] <fantasai> Koji: Basically the question is, when they have one set of contents, how can they change the style and layout for different formats.
# [03:40] <fantasai> Koji: They also made a point that in carrying out such experiments, they discovered that some implementations are behind.
# [03:40] <fantasai> Koji: In terms of logic, it sounds correct, but in reality did not work.
# [03:40] <fantasai> Koji: One particular example was that SVG and MathML and fonts in vertical writing did not work well
# [03:40] <fantasai> Koji: Mainichi Communications spoke too.
# [03:40] <fantasai> Koji: In their company they're publishing in PDF.
# [03:41] <fantasai> Koji: One of the benefits of using PDF is that they can use the content with paper printing, so the production cost will be low
# [03:41] <fantasai> Koji: But it is hard to read, especially on small devices.
# [03:42] <fantasai> Koji: Their understanding is that if we really want a full-scale launch of ebook, we have to break down components of paper publishing and redesign for ebook publishing.
# [03:42] <fantasai> Koji: Their two requests that they made in terms of publishing future and for the web
# [03:42] <fantasai> Koji: One point they made is was that, especially in fee-pay services, we need high quality layout, fonts, use of private characters, etc. (Although may not be as good quality as paper)
# [03:42] <fantasai> Koji: They're particularly concerned about color
# [03:43] <fantasai> Koji: Especially when the publish things like photo albums.
# [03:43] <fantasai> Koji: Asahi Newspaper
# [03:43] <fantasai> Koji: They started browsers/iPad/Android services in May
# [03:43] <fantasai> Koji: Technically speaking, such services are based on HTML5/CSS3
# [03:43] <fantasai> Koji: One of the greatest reasons for using HTML5/CSS3 is that they are compatible with video and multi-column layout
# [03:44] <fantasai> Koji: Because there are some old PC browsers that aren't using HTMl5, they aren't using HTML5 for PC
# [03:44] <fantasai> Koji: In terms of design, they are using totally different design tha tnon-prepaying Asahi.com
# [03:44] <fantasai> Koji: One thing that they hope to do is make this fee-paying service much more like real newspapers
# [03:44] <fantasai> Koji: using boxes and multi-column layout
# [03:45] <fantasai> Koji: Also if we look at conventional news websites, because the text is so small, they are very hard to tap with fingers
# [03:45] <fantasai> Koji: These are actual screenshots
# [03:45] <fantasai> Koj: Right hand side is fee-paying service; left hand side is web page
# [03:45] <fantasai> Koji: Asahi Newspaper said they gave up using Ruby because some browsers cannot maintain vertical rhythms
# [03:46] <fantasai> Koji: What they also hope to do in the future, they attach particular importance to their own fonts.
# [03:46] <fantasai> Koji: But the file sizes are too large for users to download
# [03:46] <fantasai> Koji: In terms of Gaiji or private characters, what purposes do we need private characters?
# [03:46] <fantasai> Koji: Obviously proper nounds such as people and place names
# [03:47] <fantasai> Koji: Also the other great source of need is political parties, making iconic-square ligature (kumimoji)
# [03:47] <fantasai> Koji: that's it for reports from Tokyo session.
# [03:47] <fantasai> Koji: Do you have any questions or comments?
# [03:49] <fantasai> Ashimura of W3C: I asked same question day before,
# [03:49] <fantasai> Ashimura: EPUB is combination of CSS and HTML as a package
# [03:49] <fantasai> Ashimura: Asahi said that validation is very difficult. Validation itself is not difficult, but fixing errors is difficult.
# [03:50] <fantasai> Ashimura: Do others have a need to make these functions easier?
# [03:50] <fantasai> Ashimura: Comments from audience?
# [03:50] <fantasai> Koji: How many are creating content in EPUB?
# [03:50] <fantasai> several raise their hands
# [03:50] <fantasai> Koji: How many use EPUB validation tool?
# [03:50] <dbaron> 2 raise their hands
# [03:52] <fantasai> Mitsubishi, involved in JAGAT
# [03:52] <fantasai> Mitsubishi: I don't see any problems with validation. I also work on PDF, and for PDF2 we need validation to check compatibility with printing
# [03:53] <fantasai> Mitsubishi: For EPUB, it's just started now. We don't need anything right now, but in the future there will be many mroe validation tools.
# [03:53] <fantasai> Koji: Any more questions?
# [03:54] <fantasai> ?: My name is Hagimura, and I work in Web Publishing.
# [03:54] <fantasai> Hagimura: Printing and Newspaper companies are trying to achieve same quality as paper printing?
# [03:54] <fantasai> Koji: My understanding is that they don't necessarily require same quality standards for epublishign and paper. We need to establish different standards for elctronic publishing.
# [03:55] <fantasai> Koji: But as Asahi and ?machi person said, the current standards of CSS publishing is not good enough for fee-charging services.
# [03:55] <fantasai> Koji: I'd like to hear your opinion, too, ifyou'd like
# [03:56] <fantasai> Hagimura: As someone working on Web, I'm fed up with discussion that we have to be same as the paper.
# [03:57] <fantasai> Hagimura: In terms of what you said, wrt quality are they requiring better quality wrt layout or general general ? or content wrt fee-charging services
# [03:58] <fantasai> Koji: As I recall, what ? perosn aid, if we are going to publish some kind of graphic services we need better color calibration. Also in temrs of general view, fonts and line-breaking etc, will need to optimize to the new environment.
# [03:58] <fantasai> Nat: I don't think anyone thinks that we need to reproduce the same layout that we get on paper on the Web.
# [03:58] <fantasai> Nat: We have PDF for that.
# [03:58] <fantasai> Nat++ :)
# [03:59] <fantasai> Nat: We need the UA to be able to control where things go on the screen, so that the author can place content predictably on the screen.
# [03:59] * fantasai also appreciates that he's speaking slowly and it small segments
# [03:59] <fantasai> Nat: One of the problems we keep hearing over and over is that ruby increases the line height.
# [04:00] <fantasai> Nat: The consensus was to add a boolean to choose which behavior you wanted.
# [04:00] <fantasai> Nat: What this does is that it adds compexity to the API and the markup. But I think that it's possible to honor the conventions that existed in print
# [04:00] * Quits: arno (arno@192.150.10.201) (Quit: Leaving.)
# [04:01] <fantasai> Nat: The conventions existed for a reasons, they existed because legibility and beauty of design has become refined on paper.
# [04:01] <fantasai> Nat: We can take that refinement and adapt it to the Web.
# [04:01] <fantasai> Nat: That's why we're requesting these kinds of controls, so that the UA can give these controls to the user.
# [04:02] <fantasai> jdaggett: I think there's a tension in CSS between giving the designer control over the design, and assuring that the user actually sees a result that's visible.
# [04:02] <fantasai> jdaggett: I guess it seems like a counter to some o the stuff you're saying.
# [04:02] <fantasai> jdaggett: Fixed line heights are great, but gives the author opportunity to shoot themselves in the foot and make line heights that collide
# [04:02] <fantasai> jdaggett: I'd like to hear if you think that's something to consider.
# [04:04] <fantasai> Nat: I think that many of these topics that we're going to talk about, font fallback, the beginnings of the rendering side of the Internet technology had different browsers giving completely different layout for the same markup.
# [04:04] <fantasai> Nat: So this problem is I think extremely important for the Web, and less so for print.
# [04:04] <fantasai> Nat: Although in print we had similar problems in the early days
# [04:04] <fantasai> Nat: Layout was unpredictable depending on fonts.
# [04:05] <fantasai> Nat: So I think that right now CSS errs in the direction of providing layout with the lowest common denominator, and as a result we get really ugly layout.
# [04:05] <fantasai> Nat: And unfortunately, there is no way for the so-called correct browser to display the correct layout because the controls don't exit yet, just starting to come together now.
# [04:06] <fantasai> Nat: I think things will improve greatly when more and more platforms support a single browser technology, or at least the browser technologies agree on exactly what is supposed to happen.
# [04:06] <fantasai> Nat: CSS3 Text leaves too much up to the UA.
# [04:06] <fantasai> Nat: But your quesiton makes me feel very positive about the outlook and I think we can definitely work on it.
# [04:07] <fantasai> Koji closes, everybody claps.
# [04:11] * Joins: myakura (d2e8220d@78.129.202.38)
# [04:16] <fantasai> Masaki Yamabe CTO/Designer ??
# [04:16] <fantasai> Yamabe: I'm from Alliance Port. We design and produce websites. I'm invited by ? from W3C. Today I'm going to share with you what we have done so far in Japanese typesetting.
# [04:17] <fantasai> Yamabe: Let me introduce what we do at our company. In addition to web designing we do .. DTP /logo
# [04:17] <fantasai> Yamabe: We work with both analog and digital.
# [04:18] <fantasai> Yamabe: As we discussed in first session, one of our challenges is how we make beauty of Japanese layout into web site.
# [04:18] <fantasai> Yamabe: Now I'm going to share with you wnat we have done.
# [04:18] <fantasai> Yamabe: 5 years ago in 2006, here is an example of vertical typesetting for Japanese layout.
# [04:19] <fantasai> Yamabe: If you look back 5 years ago, there's almost no existing vertical typesetting implementation.
# [04:19] <fantasai> Yamabe: We went through trial and error process, finally implemented vertical typesetting.
# [04:19] <fantasai> Yamabe: What we did in 2006 was website for traditional Japanese inn.
# [04:20] <fantasai> Yamabe: And please look at the screen on your left. On the top to the right is the vertical Flash.
# [04:20] <fantasai> Yamabe: Flash is used on the top to the right.
# [04:20] <fantasai> Yamabe: What we did for vertical typesetting you can se eon the bottom.
# [04:20] <fantasai> Yamabe: Simply describing the website, this a blog for Japanese and traditional inn
# [04:20] <fantasai> Yamabe: First the managers or owners of the inn write the blog contents using the CMS Moveable Type
# [04:21] <fantasai> Yamabe: The CMS text is converted to XML, which is set vertically with JavaScript
# [04:21] <fantasai> Yamabe: This is how it looks like
# [04:21] <fantasai> slide shows horizontal text in the text box
# [04:21] <fantasai> converted to XML format <item>, <published>, <description>, etc.
# [04:21] <fantasai> Yamabe: After that it's arranged vertically with Javascript
# [04:22] <fantasai> bottom of slide shows vertical text.
# [04:22] <fantasai> Yamabe: If you look at hte subject, we impelmented the typeface to make some expression.
# [04:22] <fantasai> Yamabe: I fyou look at XML version and the JavaScript version, you can see that the numerals are converted to Chinese numerals
# [04:22] <fantasai> (date is converted
# [04:22] <fantasai> )
# [04:22] <fantasai> (and formatted, started out as iso, now in CJK)
# [04:23] <fantasai> Yamabe: As I explained before, the CMS Moveable Type is used.
# [04:23] <fantasai> Yamabe: The horizontal text from the CMS is rearranged vertically with JavaScript
# [04:23] <fantasai> Yamabe: Let me explain how we rearrange.
# [04:23] <fantasai> slide:
# [04:23] <fantasai> Not using CSS rotation but using <div> for each character
# [04:24] <fantasai> slide shows tons of divs with style attributes, classes, one per character
# [04:24] <fantasai> letterspacing done with margin-top
# [04:25] <fantasai> each line of text is inside a <div class="lb">
# [04:25] <fantasai> Lines are arranged vertically using float
# [04:25] <fantasai> Typeset processing
# [04:25] <fantasai> * applying line break not only lining up characters vertically
# [04:25] <fantasai> * adjusting punctuation marks to correct position
# [04:25] <fantasai> *replacing to vertical characters
# [04:26] <fantasai> *replacing Arabic numbers ot Chinese numerals automatically
# [04:26] <fantasai> Yamabe: Implementing line-breaking rules
# [04:26] <fantasai> Yamabe: Need to replace characters e.g. for vertical brackets
# [04:27] <fantasai> Yamabe: Also need to adjust punctuation mark position using position: relative
# [04:28] <fantasai> Yamabe: For the numerals we developed source code that converted the numerals
# [04:28] <fantasai> s/numerals/numbers/
# [04:28] <fantasai> e.g. 11 -> 十一
# [04:29] <fantasai> Yamabe: Let me do some demonstration.
# [04:29] <fantasai> Yamabe shows slide with demo of tategumi.js
# [04:30] <fantasai> Yamabe: We disclosed the information on how we implemented this, if you're interested ask me.
# [04:30] <fantasai> Yamabe: This is where the vertical script islaid out
# [04:30] <fantasai> Yamabe: Here we have markup in HTML.
# [04:31] <fantasai> Yamabe: We classified text into different categories, e.g. heading, main body, etc.
# [04:31] <fantasai> Yamabe: We assigned an ID when we want to convert from horizontal to vertical
# [04:31] <fantasai> Yamabe: Let me show you how we make this website
# [04:31] <fantasai> Yamabe shows JS
# [04:31] <fantasai> Yamabe: First you specify id of what you wnat to convert
# [04:32] <fantasai> Yamabe: Then we assign parameters, using selectors
# [04:32] <fantasai> Yamabe: For example if I delete an ID, then it's going to go back to horizontal layout like this
# [04:32] <fantasai> Yamabe: These are the parameters that we can set
# [04:32] <fantasai> Yamabe: First font-size by pixel
# [04:32] <fantasai> Yamabe: glyphs per line
# [04:32] <fantasai> Yamabe: line margin
# [04:33] <fantasai> Yamabe: space between letters (glyphMargin)
# [04:33] <fantasai> Yamabe: Also block Margin, will explain in detail later
# [04:33] <fantasai> Yamabe: And you assign either true or falso whether you wnat to activate or deactivate kinsoku
# [04:33] <fantasai> Yamabe: So by setting these parameters, you change expressions in the vertical layout
# [04:33] <fantasai> Yamabe: For example, if I change from 16 to 20
# [04:34] <fantasai> Yamabe: you can really change the font size
# [04:34] <fantasai> Yamabe: Here is an example, between first line and second line the line-breaking rules are applied.
# [04:35] <fantasai> Yamabe: But if you set it to false, they will lay out without the line breaking rules (period can start a line)
# [04:35] <fantasai> Yamabe: Here is just one line-breaking rules.
# [04:35] <fantasai> Yamabe: You can specify which letters are subject to the line-breaking rules.
# [04:36] <fantasai> Yamabe: Here I will copy a large amount of text into honmon area.
# [04:36] <fantasai> Yamabe: It will make columns.
# [04:37] <fantasai> Yamabe: Readers can simply scroll down.
# [04:37] <fantasai> Yamabe: Margin between different columns are set here.
# [04:37] <fantasai> Yamabe: Here we have 100px blockMargin, which will be applied between columns.
# [04:38] <fantasai> Yamabe: Regarding font type and sizes, you can set them using the style sheet.
# [04:38] <fantasai> Yamabe: This script is available in github
# [04:38] <fantasai> http://github.com/allianceport/tategumi.js
# [04:38] <fantasai> Yamabe: MIT license
# [04:38] <fantasai> Yamabe returns to presentation slides
# [04:39] <fantasai> Yamabe: Our objective for this project was to do in browsers what we do in the editors
# [04:40] <fantasai> Yamabe: not using Flash
# [04:40] <fantasai> Yamabe: Through this project, we felt that we were able to do a lot of things in parameters using a combination of XML, HTML, JavaScript, and CSS.
# [04:41] <fantasai> Yamabe: For example in 2008, we developed a script that enabled multi-columns. At that time CSS multicol was not available
# [04:42] <fantasai> Yamabe: If you look at the source code, it's just one block, but once it goes thorugh the JS, it is separated into two columns like this.
# [04:42] <fantasai> Yamabe: We're using our automatic layout to develop a newspaper block, where we implemented vertical layout as well as the multi-column layout
# [04:43] <fantasai> Yamabe: In this website once they write their text, the XML is then laid out as for a newspaper
# [04:44] <fantasai> Yamabe: You have a vertical text heading, and multi-columns for the text.
# [04:44] <fantasai> Yamabe: Regarding pictures, once the users upload the pictures
# [04:44] <fantasai> Yamabe: The text flows around the pictures
# [04:45] <fantasai> Yamabe: User can choose whether they want to place the picture on the right or the left
# [04:45] <fantasai> Slide shows box of text in 2 columns. Top of 2ncd column is taken by picture. It is floated; the sentence from the bottom of the column continues after the picture.
# [04:45] <fantasai> (the picture is exactly the width of the column)
# [04:46] <fantasai> Yamabe: Users can choose the size of the papers -- A4 or A3
# [04:46] <fantasai> Yamabe: They can print them out into A4 papars
# [04:47] <fantasai> Yamabe: Columns are common in DTP, but it was very difficult ot implement in JavaScript
# [04:47] <fantasai> Yamabe: If you're interested in this newspaper blog
# [04:47] <fantasai> http://www.allianceport.jp/shinbunblog/demo/
# [04:48] <fantasai> Typeset Engine for Newspaper Blog slide:
# [04:48] <fantasai> * In case of Japanese, character area is calculated by numbers of characters and number of characters are calculated by character area
# [04:48] <fantasai> * Wrapping around automatically
# [04:48] <fantasai> * Making newspaper name vertically
# [04:49] <fantasai> Yamabe: When it comes to the newspaper blog, you have defined areas you can put text into
# [04:49] <fantasai> Yamabe: You are given a number of characters which you can enter into the newspaper.
# [04:50] <fantasai> Yamabe: When the overflow happens, we have a magnifying glass so you can read the overflowing contents (???)
# [04:50] <fantasai> Yamabe: We didn't want users to write a special language, therefore we try to do almost everything by this automatic layout engine so that users can simply input what they want to say, like writing a blog
# [04:50] <fantasai> Yamabe: It is then presented like a newspaper
# [04:51] <fantasai> Yamabe: What we wanted to provide with this newspaper blog, we didn't want the users to write in a special language
# [04:51] <fantasai> Yamabe: We just want users to make a blog, like a regular blog. The automatic engine converts their input
# [04:52] <fantasai> Yamabe: We follow the progress on CSS development, but also enhance our own layout engine.
# [04:52] <fantasai> Yamabe: Even though CSS3 is there, some browsers do not support.
# [04:53] <fantasai> Yamabe: We will continue using both our own engine as well as CSS.
# [04:53] <fantasai> Yamabe: Our objective is to make something enjoyable, like the layouts we showed you.
# [04:54] <fantasai> Yamabe: ...
# [04:54] <fantasai> Yamabe: Random typography, Fractal typography
# [04:54] <fantasai> Yamabe: Here I'd like to share with you ...
# [04:54] * Quits: szilles (chatzilla@125.207.177.35) (Ping timeout)
# [04:55] <fantasai> Yamabe: One of them is random typography. It was used for Design Language 2.0
# [04:55] <fantasai> Yamabe: The cover of this book is done with random typography
# [04:55] <fantasai> Yamabe shows photo of a book cover where a block of text is set in random font sizes and styles (per character)
# [04:56] <fantasai> Yamabe: This cover contains the names of the authors as well as a summary of the book. This is randomly laid out using JavaScript
# [04:56] <fantasai> Yamabe shows an example of this in the browser.
# [04:56] <fantasai> Clicking reload changes the typography
# [04:56] <fantasai> Yamabe: You see random type sizes, styles, and margins
# [04:57] <fantasai> Yamabe: This is possible because we use the Web tehcnology, with paper-based design we couldn't do this. People liked this idea, that's why they took this idea.
# [04:57] <fantasai> Yamabe: This design on the cover is done by Yasuhito Magahara. He used our technology
# [04:58] <fantasai> Yamabe: Before closing I would like to share with you anothe rone, which is Fractal Typography
# [04:58] <fantasai> Yamabe: This is artwork, which we exhibited at ? Newspaper Building
# [04:58] <fantasai> Yamabe: I will show you a tape
# [04:59] <fantasai> Yamabe: So we have this using plasma display with Google Chrome fullscreen
# [04:59] <fantasai> Showas an exmaple
# [04:59] <fantasai> on the screen
# [05:00] <fantasai> the characters are placed one-by-one, large, small, filling in gaps etc.
# [05:00] <fantasai> minute-taker can't tell how one is supposed to read any of it
# [05:01] <fantasai> as the placement seems pretty random
# [05:01] <fantasai> and in some cases overlapping
# [05:01] <fantasai> Yamabe: We are inspired by typography works where they laid out .. metal
# [05:02] <fantasai> Yamabe: We tried to mimic that technology by using our own technology
# [05:03] <fantasai> Yamabe: Each letter is sandwiched with <div>s
# [05:03] <fantasai> Yamabe: From aesthetic perspective, it's not so good. But the program runs very smoothly
# [05:03] <fantasai> Yamabe: They are not necessarily readable, but we accept that.
# [05:04] <fantasai> Yamabe: Japanese language is unique in that you can write both horizontally and vertically.
# [05:05] <fantasai> Yamabe: When we created this work, it is enjoyable even if it's not readable.
# [05:05] <fantasai> Yamabe: This is actually accepted by the audience as well.
# [05:05] <fantasai> Yamabe: We used the ? newspaper typeface since we exhibited at the ? newspaper building.
# [05:06] <fantasai> Yamabe: As for fractal typography, we expose the script, so if you're interested please ask me.
# [05:06] <fantasai> Yamabe: Thank you very much.
# [05:07] <fantasai> Yamabe: Any questions?
# [05:07] <fantasai> Nat asks to see the newspaper blog again.
# [05:07] <fantasai> Nat: My comment is about last quesiton in the session, do we need to recreate what's on paper.
# [05:07] <fantasai> Nat: This argument goes back and forth.
# [05:08] <fantasai> Nat: As you can see, this layout is very nicely representing what normally we can see on a newspaper.
# [05:08] <fantasai> Nat: But when I see this, as someone who is rather detail-oriented, I see that the picture has caused the text in the second column to move up a couple pictures
# [05:09] <fantasai> Nat: And the top of the text does not align on the top of the picture.
# [05:09] <fantasai> Nat: These types of details, it looks ok.
# [05:09] <fantasai> Nat: If you can support puting this on the character grid
# [05:09] <fantasai> Nat: And have the pictures be put relative to the character face.
# [05:09] <fantasai> Nat: Even if the users can't tell you what they're looking at, they can appreciate the quality.
# [05:10] <fantasai> Nat: The comments we get is that they won't pay for this.
# [05:10] <fantasai> Nat: It's revolutionary technology to make this Shinbun blog. But wouldn't it be nice to go a little bit futher.
# [05:10] <fantasai> s/futher/further/
# [05:10] <dbaron> the example is http://www.allianceport.jp/shinbunblog/demo/portal/cat4/05/post_1.html
# [05:11] <dbaron> discussing in particular alignment of text in the columns under the heading "新人が入社しました" due to the image
# [05:11] * myakura re "? newspaper" that's probably NIkkei
# [05:11] * fantasai sounds right
# [05:12] <fantasai> Yamabe: We don't believe it's necessary to reproduce what's on paper, but it's necessary to recreate paper.
# [05:13] <fantasai> Yamabe: ...
# [05:14] <fantasai> Yamabe: Users that can't use InDesign can enjoy a newspaper-like blog.
# [05:14] <fantasai> Yamabe:
# [05:15] <fantasai> Yamabe: Let me share with use use case for this blog.
# [05:15] <fantasai> Yamabe: In their class, they divided into smaller groups in one class.
# [05:15] <fantasai> Yamabe: And they made investigation of ? products
# [05:15] <fantasai> Yamabe: The Ministry of ?and Forestry
# [05:16] <fantasai> Yamabe: ... based on this campaign by the ministry, the schoolkids were sent out to make investigation of their local foods
# [05:16] <fantasai> Yamabe: They went out to the field and looked for local products, like fish or crops
# [05:16] <fantasai> Yamabe: They put tohse information into blog
# [05:16] <fantasai> Yamabe: They are laid out like newspapers.
# [05:17] <dbaron> s/?and Forestry/Agriculture and Forestry/
# [05:18] <fantasai> Yamabe: Question was dealing with fonts sizes and window sizes etc. for multicol
# [05:18] <fantasai> Yamabe: We don't actually convert XML to HTML, we use regular markup
# [05:18] <fantasai> Yamabe: And using scripts convert the horizontal layout to vertical layout.
# [05:19] <fantasai> Yamabe: So once you access the information I provided to you, the source code and demonstration
# [05:19] <fantasai> http://www.kumihan.org/
# [05:19] <fantasai> Question on how to render vertical glyphs
# [05:19] <fantasai> Yamabe shows source code, which converts to vertical presentaiton forms
# [05:21] <fantasai> Question was about the katakana prolongation mark
# [05:21] <fantasai> For vertical text they use a vertical line
# [05:22] <fantasai> Question was about use of the script. Answer is, it's under MIT license, and you can use it within scope of that license.
# [05:22] <fantasai> Yamabe: I will stay in this program to the end, so if you have further questions please ask later.
# [05:23] <fantasai> <br type="lunch">
# [05:23] * myakura Fractal Typography: http://fairground-mag.com/fractal-type/ demo: http://fairground-mag.com/fractaltype/kusamakura_small.html
# [05:24] * myakura is not sure about this is what Yamabe-san presented since he's in Tokyo :p
# [05:26] * Quits: dbaron (dbaron@125.207.177.35) (Quit: 8403864 bytes have been tenured, next gc will be global.)
# [05:27] * Quits: plinss (plinss@125.207.177.35) (Quit: plinss)
# [06:10] * Quits: myakura (d2e8220d@78.129.202.38) (Quit: http://www.mibbit.com ajax IRC Client)
# [06:30] * Quits: alexmog (qw3birc@128.30.52.28) (Ping timeout)
# [06:42] * Joins: plinss (plinss@125.207.177.35)
# [06:47] * Joins: dbaron (dbaron@125.207.177.35)
# [06:48] <dbaron> </br>
# [06:49] <dbaron> The next session is session 3. Approach to the e-book Business. Keitaro Hanada, Sharp Corporation.
# [06:50] <fantasai> Hanada: First I'd like to cover our company history. Over past 10 years we've been involved in e-expressions. Also review what kind of contents we have been dealing with
# [06:50] <fantasai> Hanada: First, an introduction of our company shop
# [06:51] <fantasai> Hanada: Sharp entered ebook business in 2001. Actually we had been working in ebook business before, but not stated publishing yet
# [06:51] <fantasai> Hanada: Our company originally has nothing to do with books or publishing. We develop electronic devices and mobiles
# [06:52] <fantasai> Hanada: In that way, as the mobile phone tterminals evolved, our ebook business has evolved accordingly.
# [06:52] * Joins: sylvaing (sylvaing@125.207.177.35)
# [06:52] <fantasai> Hanada: When we started to provide services, we had PDA and also notebook PCs
# [06:52] <fantasai> Hanada: First we started to deal with text, books and other literature
# [06:53] <fantasai> Hanada: Around 2006, XMDF 2.* we started targetting mobile phones, too
# [06:53] <fantasai> Hanada: PDA is mainly aimed at business customers. As you know, mobile phones are targetted at many more people, particularly young people.
# [06:53] <fantasai> Hanada: As a result our targetted publications change from regular text to more comic books
# [06:54] <fantasai> Hanada: initially, people wondered whether it would be possible to read manga on mobile phones.
# [06:54] <fantasai> Hanada: of course not possible to display the whole page, but can show frame by frame and young people did not mind
# [06:54] <fantasai> Hanada: Much of what we publish today is comics
# [06:55] <fantasai> Hanada: Also, the tablets' function and performance have advanced, and we've started to see emergence of tablets
# [06:55] <fantasai> Hanada: So our business started to focus on more high-perf terminals that can display e.g. magazine media
# [06:55] <fantasai> Hanada: In 2010 we started to develop terminals specifically for book formats
# [06:56] <fantasai> Hanada: One of the main pillars of our technology is XMDF -- ever-eXtending Mobile Document Format
# [06:56] <fantasai> Hanada: XMDF technology is based on XML
# [06:57] <fantasai> Hanada: As I said before, it's focused on mobile so we needed technology that functions well in an environment with smaller resources, but still has high speed, high-performance with small amount of memory
# [06:57] <fantasai> Hanada: As for XMDF, there's a distribution format and execution format
# [06:58] <fantasai> Hanada: Description format is standardized by IEC
# [06:58] <fantasai> Hanada: One of the features of XMDF format, it has support for Japanese-specifi features such as vertical writing, line breaking rules, and ruby
# [06:59] <fantasai> Hanada: JP language support functions are not very special, not going to cover all of them
# [06:59] <fantasai> Hanada: One thing I will talk about is float graphics.
# [07:00] <fantasai> Hanada: We became compatible with horizontal/vertical switching from an early point in time.
# [07:00] <fantasai> Hanada: So users are able to choose vertical or horizontal mode, and either way it provides a decent view.
# [07:00] <fantasai> Hanada: Some functions presented here, e.g. bg image, bg music, conrol over page advance
# [07:01] <fantasai> Hanada: Also has a jump function, used in e.g. dictionary or choose-your-own-adventure story
# [07:01] <fantasai> Hanada: Next is a comic function
# [07:02] <fantasai> Hanada: As I said, you can't see the entire page at once on a mobile device, so how we show the frames is important
# [07:02] <fantasai> Hanada: For example, here we have a vertically-long frame so you can't display the whole frame in one screen.
# [07:02] <fantasai> Hanada: It shows the top first, and then automatically scrolls to show the whole frame.
# [07:03] <fantasai> Hanada: Also, cartoon creators tend to use various expression. For example, the example on the right shows starting on the right, scrolling to the left, then coming back to the middle.
# [07:03] <fantasai> Hanada: Also we have functions implemented in our terminals
# [07:04] <fantasai> Hanada: When you change from one frame to next frame, we can set some special effects such as vibration.
# [07:04] <fantasai> Hanada: We have also been involved in electronic dictionary. XMDF can be used for this kind of e-dictionary
# [07:04] <fantasai> Hanada: Dictionaries are one of the electronic contents that can be marketed
# [07:05] * Joins: szilles (chatzilla@125.207.177.35)
# [07:05] <fantasai> Hanada: Functions I have been explaining here were realized even before 2-3 years ago
# [07:05] <fantasai> Hanada: Last year we extended our format to accommodate other content suhc as newspapers and magazines
# [07:06] <fantasai> Hanada: So we moved from the conventional format such as text media or comics to magazines
# [07:06] <fantasai> Hanada: There's a wider range of formats in magazine layouts, so we needed a format that can almost copy roughly what we can do in paper format.
# [07:06] <fantasai> Hanada: Also we wanted to enable dynamic format that's also possible in electronic media
# [07:06] <fantasai> s/also/only/
# [07:07] <fantasai> Hanada: We've added 3 different type of formats
# [07:07] * Joins: r12a (rishida@128.30.52.169)
# [07:07] <fantasai> Hanada: First one is image format. This is straight scanning and copy of paper media into a bitmap format
# [07:08] <fantasai> Hanada: Benefit of this format is that users can access layout image that they are accustomed to in printed media
# [07:08] <fantasai> Hanada: You can drag around the image to see parts of it and also zoom in and out
# [07:08] <fantasai> Hanada: Magazine format is relatively free, but for user it's hard to read the text because you constantly have to scroll up and down, left and right to read the text.
# [07:09] * Quits: szilles (chatzilla@125.207.177.35) (No route to host)
# [07:09] <fantasai> Hanada: That's why we added the next format, that we call the hybrid format.
# [07:09] <fantasai> Hanada: It's still an image format, but there is text inserted into the format.
# [07:09] * Joins: szilles (chatzilla@125.207.177.35)
# [07:09] <fantasai> Hanada: Basically what the user can do is first they look at the entire image and layout and photos. If they want to read parts of the text, they can go to text-only mode and read the text.
# [07:10] <fantasai> Hanada: The third one, multi-layout format. This is specifically an electronic format and the text does reflow.
# [07:10] * Quits: szilles (chatzilla@125.207.177.35) (Connection reset by peer)
# [07:10] * Joins: szilles (chatzilla@125.207.177.35)
# [07:10] <fantasai> Hanada: Because we are assuming this format will be viewed by different kinds of terminals, it's compatible with multi-layout, such as portrait vs. layout, vertical writing, horizontal
# [07:11] <fantasai> Hanada: It changes layout depending on screen sizes as well.
# [07:11] <fantasai> Hanada: This is an example of multi-layout
# [07:11] <fantasai> Hanada: As you can see on the screen, you can increas the text size without changing the layout.
# [07:11] <fantasai> or the pictures.
# [07:12] <fantasai> Hanada: This table shows different patterns of multi-layout that this format can do.
# [07:12] <fantasai> Hanada: For example you can have 10in screen or 5.5in screen
# [07:12] <fantasai> Hanada: You can select vertical flow or horizontal flow, portrait or landscape.
# [07:13] <fantasai> Hanada: Of course you don't have to create content to fit all these different patterns. You can create content for one format, and somehow the terminal will cope with it and display the contents.
# [07:13] <fantasai> Hanada: We have these different settings to meet the demands of the publishers.
# [07:14] <fantasai> Hanada: Some publishers want to have completely different layout for 10in vs 5in, etc.
# [07:14] <fantasai> Hanada: We create a format and sell terminals that provide a viewer.
# [07:14] <fantasai> Hanada: We also make content-creation tools as well.
# [07:14] * Quits: szilles (chatzilla@125.207.177.35) (No route to host)
# [07:14] <fantasai> Hanada: These are the 3 patterns we have
# [07:15] <fantasai> Hanada: ...
# [07:15] <fantasai> Hanada: There's actually one layout format not included in this slide.
# [07:15] * Joins: szilles (chatzilla@125.207.177.35)
# [07:15] <fantasai> Hanada: That's what we call HTML View. It imports HTML as-is and displays as-is.
# [07:15] <fantasai> Hanada: This is actually one of the formats that we strongly recommend.
# [07:16] <fantasai> Hanada: Many customers will tell us that XMDF is complicated, and we already have a lot of content in HTML.
# [07:16] <fantasai> Hanada: You might wonder why we didn't put that format in this slide, will touch on that later.
# [07:16] <fantasai> Hanada: In our first format, image and hybrid
# [07:17] <fantasai> Hanada: Publishers already have the contents in paper, so such images and text can be automatically converted to this format.
# [07:17] * Joins: SteveZ2 (chatzilla@125.207.177.35)
# [07:17] * Quits: szilles (chatzilla@125.207.177.35) (No route to host)
# [07:17] * SteveZ2 is now known as szilles
# [07:17] <fantasai> Hanada: The third format, multi-layout format, we're talking about publishers using a creation tool to make the layout.
# [07:18] <fantasai> Hanada: This is the overview of the workflow.
# [07:18] <fantasai> Slide:
# [07:18] <fantasai> Input Material
# [07:18] <fantasai> Edit the Body Text
# [07:18] <fantasai> Edit the Page Layout
# [07:18] <fantasai> Confirm the output
# [07:18] <fantasai> Publish
# [07:18] <fantasai> Input formats: Adobe InDesign IDML format
# [07:18] <fantasai> plan text
# [07:18] <fantasai> HTML
# [07:18] <fantasai> TTX
# [07:18] <fantasai> XMDF Description Format
# [07:18] * Joins: SteveZ2 (chatzilla@125.207.177.35)
# [07:18] * Quits: szilles (chatzilla@125.207.177.35) (Connection reset by peer)
# [07:18] <fantasai> Hanada: One challege for e-publishing is that e-publishing alone is not going to make financial support
# [07:18] * SteveZ2 is now known as szilles
# [07:19] <fantasai> Hanada: They're still a paper-based business, and e-publishing is on the side.
# [07:19] <fantasai> Hanada: I think that will change soon, but right now there is a need to reduce the cost of e-publishing for such publishers.
# [07:19] * Quits: szilles (chatzilla@125.207.177.35) (No route to host)
# [07:19] * Joins: szilles (chatzilla@125.207.177.35)
# [07:19] <fantasai> Hanada: The key challenge that we face is how to minimize specific processes that are only required for e-publishing.
# [07:20] <fantasai> Hanada: Basically we don't want to add many complex processes just for electronic format.
# [07:20] * Quits: szilles (chatzilla@125.207.177.35) (Connection reset by peer)
# [07:20] <fantasai> Hanada: One of the most important things is of course to be compatible with various content data formats, for example InDesign's format.
# [07:20] * Joins: szilles (chatzilla@125.207.177.35)
# [07:20] * r12a is very happy to find this minute stream, because the interpreter cannot be heard clearly all the time (speakers are very clear though)
# [07:21] <fantasai> Hanada: And one work that it's speficially required for electronic publishing is the page layout, or multipe-page layout assuming it will be published to multipel terminal types.
# [07:21] * Quits: szilles (chatzilla@125.207.177.35) (Connection reset by peer)
# [07:21] * hober thinks the jet lag may be hitting dbaron
# [07:21] * Joins: szilles (chatzilla@125.207.177.35)
# [07:21] <fantasai> Hanada: The other thing that publishers .. is the proofreading of the contents.
# [07:21] <fantasai> Hanada: Of course this proof-reading process is time consuming
# [07:21] * hober apologies to dbaron, I didn't know your computer would beep on mention
# [07:21] <fantasai> Hanada: especially if you have to proof read for various terminals
# [07:22] <fantasai> Hanada: The proof-reading is a lot of work, and costs a lot.
# [07:22] <fantasai> Hanada: It will be impossible for publisher to buy all the terminal sto test.
# [07:22] <fantasai> Hanada: So tools that emulate terminals can be used to check.
# [07:22] <fantasai> Hanada: The other challenge is related to the private characters.
# [07:23] <fantasai> Hanada: PC environment has the same problem, but moreso in mobile fonts due to limited fonts they can carry.
# [07:23] <fantasai> Hanada: Usually such devices are only compatible with JIS level 1 and level 2
# [07:23] <fantasai> Hanada: In our creation tool, we compatible with Adobe 1.6 fonts
# [07:24] <fantasai> Hanada: As long as fonts are within this collection, it creates a bitmap graphic and inserts within text
# [07:24] * fantasai thinks some thing was missing from that sentence
# [07:24] * dbaron wonders what JIS level 1, 2, and 3 are
# [07:24] * fantasai character collections
# [07:24] <fantasai> Hanada: Some people wonder why not insert and use real fonts.
# [07:24] <fantasai> Hanada: But due to limitations of mobile devices, we think at this point this is the best option.
# [07:24] * r12a JIS levels are the various standardised character repertoires
# [07:25] <fantasai> Hanada: Now I have been talking mainly about XMDF format that is our ebook
# [07:25] * Quits: szilles (chatzilla@125.207.177.35) (Ping timeout)
# [07:25] <fantasai> Hanada: Now I'd like to switch subject.
# [07:25] <fantasai> Hanada: These slides are from the Tokyo forum and panel discussion
# [07:25] <fantasai> Hanada: Going to talk about challenges we see in the future of CSS.
# [07:25] * Joins: szilles (chatzilla@125.207.177.35)
# [07:26] <fantasai> Hanada: As we enter this ebook business, in the past we have taken care of large portion of this value chain of ebook business.
# [07:26] <fantasai> Slide: Production, Deliver, View
# [07:26] <fantasai> Hanada: This is an old business model. In new model, there are standards and different players play different roles.
# [07:26] <fantasai> Hanada: We recognize that and try to change our role.
# [07:27] <fantasai> s/role/business model/
# [07:27] <fantasai> Hanada: What we feel is that in order to tackle challenges in ebook business, we have to keep in mind entire picture of this value chain.
# [07:27] * Quits: szilles (chatzilla@125.207.177.35) (Connection reset by peer)
# [07:27] * Joins: SteveZ2 (chatzilla@125.207.177.35)
# [07:27] <fantasai> Hanada: Specifically, the first challenge as we see is display layout setting.
# [07:28] <fantasai> Hanada: So content builders can configure the settings, and users can change the settings. How are we going to balance these two?
# [07:28] * Quits: SteveZ2 (chatzilla@125.207.177.35) (Connection reset by peer)
# [07:28] * Joins: szilles (chatzilla@125.207.177.35)
# [07:28] <fantasai> Hanada: In the past, mostly the publisher or creator side dictated the layout. They had certain views or layouts in mind that they wanted the user to see and created that.
# [07:28] <fantasai> Hanada: But recently we are starting to see that users are wanting to choose how they see the screen.
# [07:29] * Quits: szilles (chatzilla@125.207.177.35) (No route to host)
# [07:29] * Joins: szilles (chatzilla@125.207.177.35)
# [07:29] <fantasai> Hanada: Also in terms of contents there is more .. type of content that high quality and layout really matter, and other where it's just information really
# [07:29] <fantasai> Hanada: So rather than the layout, ...
# [07:30] <fantasai> Hanada: In terms of our implementation, we make it possible to choose vertical reading and horizontal reading.
# [07:30] <fantasai> Hanada: So there are 3 possible types of settings for character direciton.
# [07:30] <fantasai> Hanada: First one is not specified, which means user can choose whether to read vertically or horizontally.
# [07:31] * Quits: szilles (chatzilla@125.207.177.35) (No route to host)
# [07:31] <fantasai> Hanada: Second choice is a set value, the author sets the preferred value but the user can change it.
# [07:31] <fantasai> Hanada: The third one is enforced.
# [07:31] * Joins: szilles (chatzilla@125.207.177.35)
# [07:31] <fantasai> Hanada: The publisher says "this is for vertical only", then the user cannot change it.
# [07:31] <fantasai> Hanada: So basically in terms of our hardware we're making all possible to set these different types of settings
# [07:32] <fantasai> Hanada: Which one is chosen depends on the character and nature of the contents.
# [07:32] <fantasai> Hanada: In the case of JP people, they tend to like reading things vertically.
# [07:32] <fantasai> Hanada: So they tend to choose reading vertically.
# [07:32] <fantasai> Hanada: Also we have notification functions, on the content-builder functions.
# [07:33] <fantasai> Hanada: They can say there'll be maintenance outage tomorrow, etc.
# [07:33] * Quits: szilles (chatzilla@125.207.177.35) (No route to host)
# [07:33] * Joins: szilles (chatzilla@125.207.177.35)
# [07:33] <fantasai> Hanada: As you can imagine the speed and timing is key for such messages, so usually composed in horizontal format. If displayed in vertical will look strange.
# [07:34] <fantasai> Hanada: Second is foreground / background color.
# [07:34] <fantasai> Hanada: Basically in terms of color spettings, if publisher doesn't set anything, then the user can choose the colors.
# [07:34] <fantasai> Hanada: If the publisher sets colors, then the user cannot change anything.
# [07:35] <fantasai> Hanada: Because as you'd image in font color and bg color are too similar, in some cases it will be hard to set the color of the text.
# [07:35] <fantasai> Hanada: So in most cases either the publisher will dictate, or the user will chose the colors at their own responsibility.
# [07:35] * Joins: SteveZ2 (chatzilla@125.207.177.35)
# [07:35] <fantasai> Hanada: There's a fine line in terms of how much we allow users to change. There's question of accessibility, and also some users have strong preferences.
# [07:36] <fantasai> Hanada: ... difficult decision to make.
# [07:36] <fantasai> Hanada: We can also specify line break rules, which characters are in scope, character spacing, and hanging punctuation
# [07:36] * Quits: szilles (chatzilla@125.207.177.35) (Ping timeout)
# [07:36] * fantasai the pauses for translation make this easier to minute ;)
# [07:37] <fantasai> Hanada: For this implementation, we only allow content builder to change these settings because some publishers really want to control these, but users hardly wnat to control these elemtns.
# [07:37] <fantasai> s/mtns/ments/
# [07:37] <fantasai> Hanada: As for Ruby, there are two types of ???
# [07:37] * r12a the interpreter's voice trails off at the end of every intervention, so it's very difficult to follow without your minutes elika !
# [07:37] <fantasai> Hanada: One usage is when Kanji is very difficult to read.
# [07:37] <r12a> s/???/issue/
# [07:38] * dbaron thinks the problem is the interpreter moving his head relative to the microphone
# [07:38] <fantasai> Hanada: So the publisher might put Ruby in because they think the kanji is difficult.
# [07:38] * Quits: SteveZ2 (chatzilla@125.207.177.35) (Ping timeout)
# [07:38] <fantasai> Hanada: But we allow the user to turn that off, if they can read every kanji.
# [07:39] <fantasai> Hanada: But there are some other special cases where publishers put ruby to force the pronunciation of characters in an unusual way.
# [07:39] <fantasai> Hanada: In those cases we don't allow the user to turn the ruby off.
# [07:39] <fantasai> Hanada: Here are examples of some control settings. I'm sure there are other things publishers want to control and users want to control.
# [07:40] <fantasai> Hanada: Theoretically-speaking we could enable all controls on both sides, but by doing so usability will decrease rather than increase.
# [07:40] <fantasai> Hanada: If the user understands what they are changing, then it's ok. But if not then usability is reduced.
# [07:41] <fantasai> Hanada: There are some cases where contents are intended for vertical layout, and the user changed to horizontal layout, and didn't like the way it looked and complained.
# [07:41] <fantasai> Hanada: Users are kinder than you think. They gave us lot of advice.
# [07:41] <fantasai> Hanada: They continue to give us lots of advice, or, complain to us.
# [07:41] <fantasai> Hanada: It's difficult for us to turn around and say it's your settings, it's your fault.
# [07:41] <fantasai> Hanada: So we try to make it safer.
# [07:42] <fantasai> Hanada: As a result, we create terminals and we tend to get opinions that say our terminals are very boring. We cannot set anything, we cannot customize, they are very boring machines.
# [07:42] <fantasai> Hanada: There's another major issue that is display by different viewers.
# [07:43] <fantasai> Hanada: As I've been explaining, we create the format and distribute the format and manufacture terminals as well.
# [07:43] <fantasai> Hanada: It's an old business model.
# [07:43] <fantasai> Hanada: In our business if the customer complains, then we take responsibility.
# [07:43] <fantasai> Hanada: Now, as a result of standardization format, the format became free.
# [07:43] <fantasai> Hanada: Anyone can create content and distribution, and I think that's a very welcome change.
# [07:44] <fantasai> Hanada: I think there'll be some challeng eas we discussed in the morning session.
# [07:44] <fantasai> Hanada: Ok, we have standardized format, but there'll be variations in implementation.
# [07:44] <fantasai> Hanada: because of differing interpretation of the format by different vendors.
# [07:45] <fantasai> Hanada: The classic example is the different viewing experience problem with the web browsers, which is not entirely resolved.
# [07:45] <fantasai> Hanada: People create contents base don the stnadard, but when displayed in one web browser looks ok but displayed in another browser doesn't work
# [07:46] <fantasai> Hanada: We are starting to see similar problems again with different terminals.
# [07:46] <fantasai> Hanada: As for mobile phones, especially for Android, we already have WebKit and that's a de-facto standard.
# [07:46] <fantasai> Hanada: So we have expectations that this WebKit will create standards for e-publishing.
# [07:47] <fantasai> Hanada: I actually spoke about HTML input function, and we are faced with problem that if we use this function, even on the same smartphone terminals the view looks slightly different.
# [07:47] <fantasai> s/terminals/terminals category/
# [07:47] <fantasai> Hanada: This is due to sometimes different versions of webKit, and sometimes vendors have altered WebKit
# [07:48] <fantasai> Hanada: Technology advancing is a good thing, but at the same time we always continue to have terminals that are old and cannot be updated anymore
# [07:48] * Joins: myakura (d2e8220d@109.169.29.95)
# [07:48] <fantasai> Hanada: when these different versions exist we will continually face the problem of making things look the same in different terminals.
# [07:49] <fantasai> Hanada: This is one of the reasons why we cannot advertise more the HTML input function.
# [07:49] <fantasai> Hanada: This function is mostly ok, but for ebooks where exact reproduction is important, it's not adequate.
# [07:49] <fantasai> Hanada: That's why we aren't marketing this, we want to market it in a more controllable size and scale.
# [07:50] <fantasai> Hanada: .. exaclty reproduce wha twe were doing in paper, .. electronic is electronic so it can be different
# [07:50] <fantasai> Hanada: SO about this point I would like to hear your opinions too.
# [07:50] <fantasai> Hanada: This brings me to the end of this presentation.
# [07:50] <fantasai> s/SO/So/
# [07:51] <fantasai> jdaggett: My name is John Daggett from Mozilla.
# [07:52] <fantasai> jdaggett: You said there were some issues with the display of fonts, what exactly were the issues.
# [07:52] * Joins: szilles (chatzilla@125.207.177.35)
# [07:52] <fantasai> Hanada: I think you're probably talking about when I mentioned there is only limited numbers of fonts that can be installed in mobile phones.
# [07:53] <fantasai> Hanada: I say this is a problem because every time a private character comes in it creates a bitmap. It would be best to use a real font, but because of the limitaitons of the mobile phone we haven't arrived at that yet.
# [07:55] <fantasai> Ashimura: My quesiton not directly related to layout, my question is related to copyright issues.
# [07:55] <fantasai> Ashimura: When we deal with comics, also can be text materials, but particularly comics.
# [07:55] <fantasai> Ashimura: Youre technology can change dynamically the presentation of the content, setting vibrations, turning ruby on and off.
# [07:55] <fantasai> Ashimura: I'm wondering if changing such things is a problem for copyright.
# [07:56] <fantasai> Hanada: Apart from the legal issues, I'm not sure of the legal issues, but frankly if we had such effects as we explain, the publishers will tell us off.
# [07:57] <fantasai> Hanada: We ask the publisher and display per their instructions. We never change anything.
# [07:57] <fantasai> Hanada: this isn't a quesiton of what is good or bad, and environment will change in the future.
# [07:58] <fantasai> Hanada: Google started audio reading of the text, and it was very controversial and they had to stop it
# [07:58] <fantasai> Hanada: ...
# [07:58] <fantasai> Hanada: Thank you very much. We are out of time. If you have further questions, come to the secreteriat and ask the question through the secretariat
# [07:59] <fantasai> <br duration="10m">
# [07:59] * Joins: glazou (glazou@82.247.96.19)
# [07:59] * fantasai waves to glazou
# [07:59] <glazou> hello !
# [07:59] <fantasai> RRSAgent: pointer
# [07:59] <RRSAgent> See http://www.w3.org/2011/06/01-css-irc#T05-55-53
# [07:59] <glazou> everything ok in Kyoto ?
# [07:59] <fantasai> glazou: afaict, yep
# [07:59] <fantasai> glazou: minutes up there *points*
# [07:59] <fantasai> glazou: we're on break for 10m
# [07:59] * fantasai is glad of this
# [07:59] <glazou> ok
# [07:59] * r12a wonders whether someone can have a word with the interpreter during the break about mic usage ?
# [07:59] <glazou> beginning of day here
# [08:00] * fantasai I think we're switching interpreters now
# [08:00] * r12a gambatte kudasai, fantasai !
# [08:00] <fantasai> ^_^
# [08:00] <r12a> wow! how do you do that ?
# [08:02] <glazou> do what ?
# [08:02] * r12a sees how in the irc log
# [08:02] * r12a gets a picture of fantasai when she types ^_^ in irc ;-0
# [08:02] <glazou> not here
# [08:02] * r12a figures it's down to his client
# [08:03] <glazou> yep
# [08:03] <glazou> what's your irc client ?
# [08:03] <r12a> colloquy
# [08:03] <glazou> hmm
# [08:03] <glazou> me too but I get the usual smiley
# [08:03] <r12a> hmm, interesting
# [08:03] <glazou> could depend on the theme you use
# [08:04] <glazou> Preferences > Appearance
# [08:04] * r12a notes that it's not *really* a picture of elika, but it looks like a cartoon version of her
# [08:04] * r12a default style: Standard
# [08:04] * r12a emoticons: Standard
# [08:05] <glazou> aaah wait I don't have last version
# [08:05] <glazou> you have probably 2.3
# [08:06] * r12a yep
# [08:06] <glazou> let me upgrade right now :-)
# [08:07] * Quits: glazou (glazou@82.247.96.19) (Quit: glazou)
# [08:07] * Joins: glazou (glazou@82.247.96.19)
# [08:07] <glazou> back in 2.3
# [08:07] <glazou> test :-)
# [08:07] * r12a test ^_^
# [08:07] <glazou> nothing :-)
# [08:07] <r12a> nothing for ^_^ either ?
# [08:08] * r12a sees a smily face for glazou's test
# [08:09] <glazou> hmmm
# [08:10] <glazou> retest
# [08:10] <glazou> :)
# [08:10] <glazou> sigh
# [08:10] <glazou> aaaaah
# [08:10] * r12a wonders how to spell smily/smilie
# [08:10] * r12a smiley ?
# [08:10] <glazou> it's the emoticons "standard" style
# [08:10] <glazou> I was in iChat style
# [08:10] <r12a> yep, standard
# [08:10] <glazou> yeah I see a girl's face
# [08:11] <r12a> heh
# [08:11] <glazou> ;-)
# [08:11] <r12a> ;-)
# [08:11] <glazou> so emoticons in Colloquy have gender ? :-D
# [08:12] <fantasai> </br>
# [08:12] <dbaron> Taichi Kawabata (川幡太一), NTT Corp.
# [08:12] * fantasai thanks dbaron
# [08:13] * glazou waves
# [08:13] <dbaron> s/Kawabata/KAWABATA/
# [08:13] <fantasai> Kawabata: Because of my involvement in standardization process for IVD, I've been invited to speak here.
# [08:13] <fantasai> Kawabata: I'm going to explain character and font-related topics that may affect standardization of CSS3.
# [08:14] <fantasai> Kawabata: Let me apologize because I prepared my presentation for 1 hour, but since we have simult translation I might run out of time.
# [08:14] <fantasai> Kawabata: Let me explain current status of private characters in fonts.
# [08:14] <dbaron> Topic: Private Characters and Font Formats
# [08:14] <fantasai> Slide: Unicode does not encode idiosyncratic, personal, novel, or private-use characters nor logos nor graphics.
# [08:15] <fantasai> Unicode reserves 6400 codepoints in BMP for private-use, and also another 130000 are available outside BMP
# [08:15] <fantasai> Slide: Private Characters
# [08:16] <fantasai> Logos, emoticons, etc.
# [08:16] <dbaron> "Note, however, that the Unicode Standard does not encode idiosyncratic, personal, novel, or private-use characters, nor does it encode logos or graphics. Graphologies unrelated to text, such as dance notations, are likewise outside the scope of the Unicode Standard. Font variants are explicitly not encoded. The Unicode Standard reserves 6,400 code points in the BMP for private use, which may be used to assign codes to characters not included in the repertoire
# [08:16] <dbaron> of the Unicode Standard. Another 131,068 private-use code points are available outside the BMP, should 6,400 prove insufficient for particular applications." (Unicode, 1.1)
# [08:16] <fantasai> Kawabata: In books, special symbols are sometimes used to convey the complex or abstract idea in a simpler manner.
# [08:16] <fantasai> Kawabata: Also emoticons used in Japanese mobile phones are not encoded yet.
# [08:17] <dbaron> [image of book of john in Greek, with lots of annotations]
# [08:17] <fantasai> Kawabata: Regarding Kanji characters, already 75,000+ are encoded under the Unification rules
# [08:17] * Joins: kojiishi (kojiishi@222.158.227.129)
# [08:17] <fantasai> Kawabata: However if you look at dictionaries or some scientific papers, there are still more that are not yet encoded.
# [08:17] * Quits: kojiishi (kojiishi@222.158.227.129) (Quit: Leaving...)
# [08:17] <fantasai> Kawabata: There are reasons for those characters not to be encoded, e.g.
# [08:17] <fantasai> * misdescribed
# [08:17] <fantasai> * invented
# [08:17] <fantasai> * (very) local
# [08:18] <fantasai> * historic/short-lived
# [08:18] * dbaron is amazed that "misdescribed" is one character in Japanese
# [08:18] * Joins: kojiishi (kojiishi@222.158.227.129)
# [08:18] <fantasai> Kawabata: Kanji characters are often invented. If invented by a famous author they might be encoded, but are otherwise not encoded.
# [08:19] * Quits: kojiishi (kojiishi@222.158.227.129) (Quit: Leaving...)
# [08:19] <fantasai> Kawabata: Here is a book from late 19th century. The government in Japan issued a dictionary with vocabulary of new introduced legal terminology
# [08:19] <fantasai> Kawabata: They introduced several hundred new kanji for those vocabulary
# [08:19] * Joins: kojiishi (kojiishi@222.158.227.129)
# [08:19] * Quits: kojiishi (kojiishi@222.158.227.129) (Quit: Leaving...)
# [08:19] <fantasai> Kawabata: However those new introduced characters have never been used.
# [08:19] <fantasai> Kawabata: In other cases we have other characters not in use
# [08:20] <fantasai> Kawabata: Regarding private characters, there have been discussions of how to render those characters in HTML.
# [08:20] <fantasai> Kawabata: Based on discussions we have this week, there are five issues.
# [08:20] * Joins: kojiishi (kojiishi@125.207.177.35)
# [08:21] <fantasai> Kawabata: These are the classifications of those five emthods to render private characters. Each has different profiles, whether they have ? or not, whether they are searchable or not, how many available, etc.
# [08:21] <fantasai> Kawabata: In order to utilize private character, must think about font format for private characters.
# [08:21] <fantasai> Kawabata: With HTML and CSS3 you can include the font files
# [08:22] <fantasai> Kawabata: There are three formats which can be implemented or embedded into HTML.
# [08:22] <fantasai> Kawabata: OpenType, WOFF, SVG
# [08:22] * dbaron thinks the Japanese version of that slide has a lot more info than the English version
# [08:22] <fantasai> Kawabata: Each font format has pros and cons.
# [08:22] <fantasai> Kawabata: OpenType is most popular, but has large size.
# [08:23] <fantasai> Kawabata: WOFF has smaller size, tailored for Web use
# [08:23] * r12a finds this interpreter even harder to understand :(
# [08:23] <fantasai> Kawabata: The SVG is different to other types. You can convert SVG into a font.
# [08:23] <fantasai> Kawabata: SVG is different in that it's possible to use gradation, color, animation.
# [08:23] <fantasai> Kawabata: Also SVG font can be embedded into HTML and can also inherit CSS
# [08:24] <fantasai> Kawabata: However the SVG is not supported by all browsers
# [08:24] <fantasai> Kawabata: And EPUB ??
# [08:24] <fantasai> Kawabata: When it comes to how to render those private characters, I'm going to show you a solution.
# [08:24] <dbaron> slide shows http://glyphwiki.org/wiki/u26f97
# [08:24] <fantasai> Kawabata: What I'd like to show you is the glyphwiki project.
# [08:24] <fantasai> Kawabata: Everyone can register his or her own characters.
# [08:25] <fantasai> Kawabata: Once you create a new page and put that glyph, then the font will be automatically created from the glyph
# [08:25] <fantasai> Kawabata: Nearly 100,000 characters are registered
# [08:25] <fantasai> Kawabata: And base don this, about 1 month ago Hanazon-Mincho, a new font became available
# [08:25] * glazou goes to his office and will rejoin from there ; bbl
# [08:25] * Quits: glazou (glazou@82.247.96.19) (Quit: glazou)
# [08:25] <fantasai> Kawabata: This is only one free font that can .. all UCS/AJ1 ideographs
# [08:26] <dbaron> s/Hanazon-Mincho/Hanazono-Mincho/
# [08:26] <fantasai> Kawabata: This one on the right is the glyph created for UCS
# [08:26] <fantasai> Kawabata: With private characters ther eis a challenge of how to deal with vertical layout
# [08:27] <fantasai> Kawabata: When it comes to vertical layout, whether you rotate the charater or you rearrange vertically based on ... gsub
# [08:27] <fantasai> Kawabata: When text-orientation is vertical-right, set characters upright (using vertical font settings ) unles sotherwise specified above.
# [08:27] <fantasai> Kawabata: In OpenType (quoting from spec here) ...
# [08:28] <fantasai> Kawabata: Now go over IVS and font selection
# [08:28] <fantasai> Kawabata: IVS stands for Ideographic Variation Selector
# [08:28] <r12a> s/Selector/Sequence/
# [08:28] <fantasai> Kawabata: IVS enables to display ideographic variance by ...
# [08:29] <r12a> s/Sequence/Selector/
# [08:29] <fantasai> Kawabata: In the past Unicode only specifies the abstract character, however IVS can specify concrete glyphs
# [08:29] <fantasai> Kawabata: In order to use IVS you need to register IVS into IVD
# [08:29] <fantasai> Kawabata: Regarding the way to register IVD, that is specified UTS 37
# [08:30] <fantasai> Kawabata: If a registrant wants to register a variant into a registrar, which is currently the Unicode Consortium, first you need to register your collection
# [08:30] <fantasai> Kawabata: Once you register collection, then you can register glyphs ... as many times as you wish
# [08:30] <fantasai> Kawabata: ...
# [08:31] <fantasai> Kawabata: In the IVD_Collections.txt, ... register into IVD_Sequences.txt
# [08:31] <fantasai> Kawabata: Currently two colections are registered: Adobe-Japan1 and Hanyo-Denshi
# [08:31] <r12a> s/Selector/Sequence/
# [08:32] <fantasai> Kawabata: These tow collections are implemented in some fonts
# [08:32] <fantasai> Kawabata: However these two collections do not match always necessarily
# [08:32] <dbaron> shows image from http://d.hatena.ne.jp/NAOI/20100406/1270550459
# [08:32] <fantasai> Kawabata: This is one example where the collections don't match
# [08:32] <fantasai> Kawabata: I've taken this information from ?'s website
# [08:32] <fantasai> Kawabata: Blue boxes are from AJ1 and red one are from Hanyo-Denshi
# [08:33] <fantasai> Kawabata: This is one specific chinese character. As you see, some of them match, but they don't always match
# [08:33] <fantasai> Kawabata: How are people using an IVS? There are two main usages
# [08:33] * Joins: nmccully (nmccully@125.207.177.35)
# [08:33] <fantasai> Kawabata: One usage could to show a archaic style
# [08:34] <fantasai> Kawabata: Another purpose for IVS is to correctly display proper names
# [08:34] <fantasai> Kawabata: Let me explain using an example.
# [08:34] <fantasai> Kawabata: For example if you have this kind of older text
# [08:34] <fantasai> Kawabata: And if you apply an IVS, you can make a little bit more traditional
# [08:34] <fantasai> Kawabata: So if you compare the characters you can see differences
# [08:35] <fantasai> Kawabata: If you have a font that supports the IVSes, you can convert the document into a classical look
# [08:35] * r12a just realised that there's a demo going on on the japanese screen that he can't see
# [08:36] <fantasai> Kawabata: Here's an example where IVS is used for proper names
# [08:36] * dbaron emacs!
# [08:36] <fantasai> Kawabata: These for example are all different names using Chinese characters that can be pronounced the same
# [08:36] <fantasai> Kawabata: But if you look at the chinese characters, they are a little bit different.
# [08:36] <fantasai> Kawabata: ... small differences in a person's name
# [08:37] <fantasai> Kawabata: Another case for example, Katsudaku City and Katsudaku Ward (sp?)
# [08:37] <fantasai> Kawabata: Although pronounced the same, their Chinese characters are different.
# [08:37] <fantasai> Kawabata: If you press delete key to delete the IVS (in emacs) then you see the character conert
# [08:37] <fantasai> Kawabat: Now a different topic, CSS has the font-matching algorithm.
# [08:37] * dbaron oh well
# [08:37] <fantasai> Kawabata: For example if you specify 3 fonts in font-family value
# [08:37] * hober dbaron: yeah, but he's using the X11 build, even on OSX. Quick, someone point him to http://emacsformacosx.com/
# [08:38] <fantasai> Side: font-family: font-A, font-B, font-C
# [08:38] <fantasai> Kawabata: And you have a sequence like this
# [08:38] <fantasai> Slide: C1 C2 C3 C4 C55
# [08:38] <fantasai> Kawabata: The best font will be picked in the font-family in thes order
# [08:38] <fantasai> Kawabata: Here there are two different text decorations.
# [08:39] <fantasai> Kawabata: One decoration is done by CSS, for example converting this character into bold face
# [08:39] <fantasai> Kawabata: Other time if you use IVS you can convert same characters into it svariant.
# [08:39] <fantasai> s/it sv/its v/
# [08:39] <fantasai> Kawabata: If you want to show the character that is not supported by IVS, you have to go through font fallback
# [08:40] <fantasai> Kawabata: By combining CSS and IVS can you make it boldface for variant, or does it change the character?
# [08:40] <fantasai> Kawabata: IVS and font-selections, there are various arguments.
# [08:40] <fantasai> Kawabata: Now I'm going to go into a technical deep discussion.
# [08:40] <fantasai> Slide:
# [08:40] <fantasai> font-family: font-A, font-B, font-C;
# [08:40] <fantasai> font-A supports only base characters
# [08:40] <fantasai> font-B supports IVCx
# [08:40] <fantasai> font-C supports IVCy
# [08:41] <fantasai> Consider sequence
# [08:41] <fantasai> C1 IVSx (3IVCx) IVSy (3IVCy) Cy
# [08:41] * fantasai somebody convert those 3s to element-of?
# [08:41] <fantasai> Kawabata: In which font family should the ... render in the web browser?
# [08:42] <fantasai> Kawabata: Option A is to render all those characters using the base characters
# [08:42] <dbaron> s/3IVC/∈IVC/g
# [08:42] <fantasai> Kawabata: Option 2 is to prioritize characters which are specified in the IVSx or IVSy
# [08:42] <fantasai> Kawabata: These two options have pros and cons
# [08:42] * dbaron doesn't understand how many glyphs are in that example
# [08:43] * dbaron is it trying to use two variation selectors on one base?
# [08:43] <fantasai> s/2/B/
# [08:43] <fantasai> Option A:
# [08:43] <fantasai> Pro - whole text has a consistent font-fmaily
# [08:43] <fantasai> Con - multiple IVC fonts can not be supported
# [08:43] <fantasai> Option B
# [08:43] <fantasai> Pro - each IVS will be rendered with a supporting font
# [08:44] <fantasai> Con - Text may be displayed in inconsistent font
# [08:44] <fantasai> Kawabata: If you choose option 1, it is difficult for user to display each IVS , font family must be specified in eac IVS
# [08:44] <r12a> s/C1 IVSx (3IVCx) IVSy (3IVCy) Cy/C1 IVSx (∈IVCx) IVSy (∈IVCy) Cy/
# [08:44] <fantasai> Kawabata: Under option B, it is easy for user to dsiplay only base character -- just remove VS characters
# [08:45] * sylvaing dbaron, yes, I don't get the use-case either
# [08:45] <dbaron> Topic: Normalization
# [08:46] * r12a redialling via skype - connection lost :(
# [08:47] * hober ObMarkpLink: http://diveintomark.org/archives/2004/07/06/nfc
# [08:47] <Bert> Kawabata: [explains NFD/NFC/NFKC/NFKD normalization]
# [08:47] * r12a back on skype
# [08:48] * fantasai is skipping the Unicode Normalization Primer section of this prsentation
# [08:48] * dbaron thought KNFC/KNFD removed the squared/circled stuff
# [08:48] * dbaron er, NFKC/NFKD
# [08:48] * fantasai I think he means it converts circled 1 to 1
# [08:48] * fantasai the characters aren't /removed/
# [08:48] * fantasai the circles are just stripped, iirc
# [08:49] * dbaron yeah, but seems like he's saying it decomposes to a combining circle
# [08:49] * Quits: szilles (chatzilla@125.207.177.35) (Ping timeout)
# [08:49] * Joins: SteveZ2 (chatzilla@125.207.177.35)
# [08:49] * SteveZ2 is now known as szilles
# [08:50] * dbaron thinks the examples are most fun in Tiếng Việt
# [08:51] * Quits: kojiishi (kojiishi@125.207.177.35) (Quit: Leaving...)
# [08:51] * Joins: kojiishi (kojiishi@125.207.177.35)
# [08:51] <fantasai> Kawabata: Once you have normalization, then you can compare character strings
# [08:52] <fantasai> Kawabata: Especially for CSS and HTML, the name of class ...
# [08:52] <fantasai> Kawabata: And actually normalization has some challenges
# [08:52] <fantasai> Kawabata: For example, implementation is very combersome, especially NFC
# [08:53] <fantasai> Kawabata: Actually tried to implement NFC, but I have difficult time to do that.
# [08:53] <fantasai> Kawabata: Another issue for normalization is the singleton decomposition
# [08:53] <fantasai> Kawabata: This means different characters sometimes folded to the same character
# [08:54] <fantasai> Kawabata: For example, Angstrom (U+212B / JIS X 0208) normalizes to A with ring above (U+00C5 / ISO8859-1 )
# [08:54] <fantasai> Kawabata: Another issue with normalization is compatibility ideographs
# [08:54] <fantasai> Kawabata: All compatibility ideographs will be transforme dto corresponding unified ideographs
# [08:55] <fantasai> Kawabata: Apple in HFS file, they do not normalize compability ideographs
# [08:55] <fantasai> Kawabata: 10 years ago Apple proposed to Unicode to exclude the compatibility characters
# [08:55] <fantasai> Kawabata: However this proposal was not accepted
# [08:56] <fantasai> Kawabata: Ideographs are unified by unification rules specified in ISO/IEC 10646 Annex S
# [08:56] <fantasai> Kawabata: However there are some exceptions.
# [08:56] <fantasai> Kawabata: Before 1992, there were some separately encoded
# [08:56] * dbaron the example on slide 27/26 didn't translate properly to English
# [08:56] <fantasai> e.g. U+98F2 and U+98EE
# [08:57] <fantasai> Kawabata: These two are different characters meaning the same thing. But they were encoded before 1992, that's why they are separated
# [08:57] <fantasai> Kawabata: ...
# [08:57] * Joins: futhark (rune@213.236.208.22)
# [08:57] <fantasai> Kawabata: Japanese Compatibility ideographs include name ideographs, shown in the bottom of the slide
# [08:58] <fantasai> Kawabata's slide shows characters that are variants of each other -- on is a compatibility ideograph
# [08:58] <fantasai> Kawabata: Another issue is when and where normalization should be implemented.
# [08:58] <fantasai> Kawabata: In 2005 draft version of charmod 1.0
# [08:59] <fantasai> Kawabata: Early Unicode Normalization was suggested
# [08:59] <fantasai> Kawabata: It was suggested to put this in HTML
# [08:59] <fantasai> Kawabata: But if you implement this, we might lose the specific Chinese characters, e.g. for a person's name.
# [08:59] * dbaron wonders if normalization to NFD or NFC loses that information
# [08:59] <fantasai> Kawabata: Such an issue understood by many people
# [08:59] * fantasai both
# [09:00] <r12a> http://rishida.net/scripts/uniview/?charlist=%E9%A3%B2%E9%A3%AE click on characters to see large
# [09:00] <fantasai> Kawabata: I personally hope that EUN will not be adopted for HTML
# [09:00] * dbaron really... I thought the idea was that only NF*K*C/NF*K*D would lose information.
# [09:00] <fantasai> Kawabata: But I'm not against all normalization for HTML
# [09:00] <fantasai> Kawabata: I suggest normalization for ID, class, and URL for example
# [09:00] <fantasai> Kawabata: But this is an example from XML appendix J
# [09:01] <fantasai> Kawabata: Many types of values can be normalized
# [09:01] * Joins: glazou (glazou@80.118.184.70)
# [09:01] <fantasai> Kawabata: Given difficulty of implementation, e.g. NFC, it's not a good idea to normalize those values like ? attribute
# [09:02] * Joins: Ms2ger (Ms2ger@91.181.154.155)
# [09:02] <fantasai> Kawabata: My personal opinion is that for web browsers, NFKC is more useful
# [09:02] <fantasai> Kawabata: By having this normalization, you can search single-byte katakan by using double-byte katakana
# [09:02] <fantasai> Kawabata: Or even you can search .. characters by separating characters
# [09:03] * Quits: nmccully (nmccully@125.207.177.35) (Quit: Colloquy for iPad - http://colloquy.mobi)
# [09:03] <fantasai> (example of searching Liter ligature with Liter)
# [09:03] * r12a notes that maybe search and comparison of ids-classnames-selectors are different types of operation - perhaps you shoudn't be using characters that decompose using NFKC/D for the latter
# [09:03] <fantasai> Kawabata: ... for example you can't search old Kanji charaters by using newer Chinese characters
# [09:03] <fantasai> Kawabata: So we need a new method to make searching for old and new characters
# [09:04] <fantasai> Kawabata: Ok, that is my end of presentation.
# [09:04] <fantasai> Kawabata: Thank you very much.
# [09:04] * fantasai that was the idea. But it's just an idea.
# [09:04] <fantasai> jdaggett: You showed a slide that was very complicaed
# [09:05] * Ms2ger shares http://diveintomark.org/archives/2004/07/06/nfc
# [09:05] <fantasai> jdaggett: That used IVSx IVSy
# [09:05] <fantasai> jdaggett: This is not a problem that any author should ever have to deal with.
# [09:05] <fantasai> jdaggett: This is a problem because of the way the Hanyo-Denshi was registered.
# [09:05] <fantasai> jdaggett: You have two selectors that specify the same glyph
# [09:05] <fantasai> jdaggett: And you have fonts that support only the Hanyo-Denshi selectors and not the AJ1 selectors.
# [09:06] <fantasai> jdaggett: There is *no reason* the author should *ever* have to insert two selectors because there's a problem in the font.
# [09:06] <fantasai> jdaggett: Also a problem for implementers. I just want to ask the font if it has the right glyph and get the right answer.
# [09:06] <dbaron> (AJ1 == Adobe-Japan1)
# [09:07] <fantasai> Kawabata: Idea of 37 was that different groups want their own collection, their own set of variatns. So there's a concept of collections.
# [09:07] <fantasai> jdaggett: For the same glyph, why do you need two selectors.
# [09:08] <fantasai> Kawabata: It's very difficult to see if the glyphs are really the same or different
# [09:08] <fantasai> jdaggett: But it's very hard for authors, too.
# [09:09] <fantasai> Kawabata argues that it's a lot of work to check if the glyphs are the same or different
# [09:09] <fantasai> Nat: I would never support all these different collections. As a developer I will only pick one, and I'll pick the one that's easiest to support.
# [09:09] <fantasai> Nat: It's not easy for me to have knowledge of your database.
# [09:09] <fantasai> Nat: my renderer should have no need to understand you rdatabase
# [09:09] <fantasai> Nat: And content creators should need to have even less understanding of your database
# [09:10] <fantasai> Nat: If you don't do this, then font fallback will fail, and you run into all kinds of problems.
# [09:10] <fantasai> Nat: And it ties to the politics of the font vendor and the registrant, and all of those issues are being foisted on the content creators.
# [09:11] <fantasai> jdaggett: This feels a lot like going back to encoding problems of the 80s in Japan, where Hitachi has their own vendor codes and Fujitsu has their own vendor codes, where if Fujitsu made it then Hitachi can't support it.
# [09:13] * fantasai gives her own rant on the topic and concludes by noting that this particular problem is out-of-scope for CSS
# [09:13] <fantasai> Nat: The compatibility characters are an obsolete way of handling the same problem that IVS solves much more elegantly.
# [09:13] * Ms2ger fantasai++
# [09:14] <fantasai> Nat: I'm very confused by the normalization discussion, because normalization is by nature something that is a lossy converion.
# [09:14] <fantasai> Nat: Why do they think that they're losing something?
# [09:14] <fantasai> Nat: If you're destroying data by normalizing, then that's a bug.
# [09:15] <fantasai> Kawabata: Normalized data should be used only for comparison, not for circulation. That makes for data loss.
# [09:15] * Quits: szilles (chatzilla@125.207.177.35) (Ping timeout)
# [09:16] <fantasai> Yamamoto from Adobe: I agree with the last part of what ? said, normalization itself has no bad thing, but how to use it needs careful attention. If there is misuse or abuse of normalization it's wrong.
# [09:17] <fantasai> Yamamoto: I agree that IVS is a better approach and we should use it.
# [09:18] <fantasai> Yamamoto: For this reason, compatibility characters should only be used for guaranteeing round-tripping with a particular national standard. Other usage is strongly discouraged.
# [09:19] <fantasai> Yamamoto: Two points that Nat mentioned: wrt compatibility characters, he told the history and value
# [09:19] <fantasai> Yamamoto: On the other hand the stnadard 10646 for this reason compatibility characters should only be used for guaranteeing rount-tripping
# [09:19] * Joins: glazou_ (glazou@80.118.184.70)
# [09:20] * Quits: glazou (glazou@80.118.184.70) (Quit: glazou)
# [09:20] * glazou_ is now known as glazou
# [09:20] <fantasai> Yamamoto: ... multiple IVSes from multiple IVCs, tries to keep .. where one single IVD collection completely works, but even if there are other collections he doesn't seme to care about the interoperability of multiple IVSes from multiple IVD collections.
# [09:20] <fantasai> Yamamoto: Similarly he is trying to keep this closed world where compatibility ideographs are perpetually represented by ? systems
# [09:20] <fantasai> Yamamoto: There is always the other world of Unicode where we have attached importance to keep the interoperability of text communication worldwide.
# [09:21] <fantasai> Kawabata: let me share my thoughts on those issues
# [09:21] <fantasai> Kawabata: One comment wrt compat characters, he said that I am focusing on the round trip and that's only in closed word, not open to outside world, that's his comment.
# [09:22] <fantasai> Kawabata: Well I myself, Unicode is one big platform where text communication is conducted
# [09:22] <fantasai> Kawabata: Therefore within this big platform that's also contain the regional standard, therefore text communication is possible based on regional standard as well
# [09:22] * Joins: szilles (chatzilla@125.207.177.35)
# [09:23] <fantasai> Kawabata: And therefore by using Unicode as a ? ppl communicated by using regional standard or subset by agreeing each other themselves (?)
# [09:23] <fantasai> Kawabata: So well what I'm thinking is that we should not do something .. of those ppl who already have text communication based on regional standard subset.
# [09:23] <fantasai> Kawabata: Another point wrt IVD , it's been pointed that characters registered in different collections that would be costly.
# [09:24] * Joins: nmccully (nmccully@125.207.177.35)
# [09:24] <fantasai> Kawabata: Now we only two collections, but looking ahead there might be various people who want to register their collecitons for specific usage.
# [09:24] <fantasai> Kawabata: Of course ther's an argumen that if you have the same wrods registered in different colleciton they must be unified
# [09:25] <fantasai> Kawabata: Our concern is that .. people who want to register a new colleciton must search all the existing collections
# [09:25] <fantasai> Yamamoto: There are IVD collections by national Japanese, others for local governments.. similar situations.
# [09:26] <fantasai> Yamamoto: The registrant's intention doesn't matter. look at the glyphs. If they look shareable, after some research, maybe we can agree that a pair of glyphs can be shared, then those glyphs should be shared.
# [09:27] <fantasai> [bunch of discussion in Japanese]
# [09:28] * Quits: szilles (chatzilla@125.207.177.35) (Ping timeout)
# [09:30] <fantasai> ?: I've received requests from Buddhist texts for example, so I can't say that we should unify the whole collections.
# [09:31] <fantasai> <br duration="7m">
# [09:31] * Joins: Macnmm (qw3birc@128.30.52.28)
# [09:32] * r12a getting no answer when dialling in via skype - will try again in 5 mins
# [09:35] * Joins: szilles (chatzilla@125.207.177.35)
# [09:38] * Quits: nmccully (nmccully@125.207.177.35) (Quit: Colloquy for iPad - http://colloquy.mobi)
# [09:41] * fantasai changes topic to 'logged at http://krijnhoetmer.nl/irc-logs/'
# [09:41] * Joins: nmccully (nmccully@125.207.177.35)
# [09:41] * Quits: Macnmm (qw3birc@128.30.52.28) (Quit: Page closed)
# [09:42] <fantasai> i/Nat McCully (Adobe)/ScribeNicK: fantasai/
# [09:42] * dbaron r12a better now?
# [09:42] <fantasai> RRSAgent: make minutes
# [09:42] <RRSAgent> I have made the request to generate http://www.w3.org/2011/06/01-css-minutes.html fantasai
# [09:42] <r12a> ok, i'll dial in
# [09:43] <fantasai> RRSAgent: make logs public
# [09:43] <RRSAgent> I have made the request, fantasai
# [09:43] * Quits: szilles (chatzilla@125.207.177.35) (Ping timeout)
# [09:44] <fantasai> Ashimura: ...
# [09:44] <fantasai> Ashimura: W3C is an industry consortium created by Tim Berners-Lee
# [09:44] * r12a could someone turn on the video for my skype connection please?
# [09:45] <fantasai> Ashimura: W3C has 3 hosts: MIT, ERCIM, Keio University
# [09:45] * r12a thanks !
# [09:45] * dbaron sure
# [09:45] * dbaron sorry, didn't occur to me that was another step :-)
# [09:46] * r12a np :-)
# [09:46] <fantasai> Ashimura: One Web! That means global, accessible, implementable.
# [09:46] <fantasai> nmccully: Natasha Indik <tindik@Princeton.EDU>
# [09:46] <fantasai> er
# [09:46] <fantasai> Natasha Indik <tindik@Princeton.EDU>
# [09:46] <fantasai> http://www.w3.org/2011/06/01-css-minutes.html
# [09:46] <fantasai> THere we go
# [09:47] <fantasai> s/Natasha Indik <tindik@Princeton.EDU>//g;
# [09:47] * Joins: vhardy (vhardy@125.207.177.35)
# [09:47] * Joins: alexmog (qw3birc@128.30.52.28)
# [09:48] * fantasai nmccully I figure that's more easy to read
# [09:48] <fantasai> Ashimura gives an intro to W3C
# [09:48] <fantasai> Ashimura: Feedback from Tokyo Forum
# [09:48] <fantasai> Ashimura:e-standards is complicated and controversial
# [09:48] <fantasai> Ashimura: We need to start with actual use cases, I think
# [09:48] <fantasai> Ashimura: In Tokyo we asked e-Publishing stakeholders for requirements and use cases
# [09:50] <fantasai> Ashimura: The theme of the session in Tokyo was, What is needed for Japanese text layout on Web browsers and e-Books
# [09:50] <fantasai> Ashimura: Each panelist introduced their own products and services. The process of their products and services were discussed.
# [09:50] <fantasai> Ashimura: Discussed what was needed, what do we want to do using Web technology?
# [09:51] <fantasai> Ashimura: Feedback from browser vendors, for example Access, the Japanese vendor,
# [09:51] <fantasai> Ashimura: EPUB(HTMl+CSS) is a platform for publishing
# [09:52] <fantasai> Ashimura: Current latest specs already let us use a certain level of epub documents with Japanese layout.
# [09:52] <fantasai> Ashimura: However there is no free stable implementation for the latest specs
# [09:52] <fantasai> Ashimura: So they are making an implementation based on WebKit and Google Chrome source code
# [09:52] <fantasai> Ashimura: But it has some issues, especially wrt Ruby and so on
# [09:53] * r12a david i lost connection and reconnected - could you hit the video button again for me please?
# [09:53] <fantasai> Ashimura: Next, from signage viewpoint, this viewpoint was provided by [Kata?]san, Newphoria
# [09:54] <fantasai> Ashimura: Very big fonts are needed for advertizing etc.
# [09:54] <fantasai> Ashimura: Restriction based on hardware: number of characters, resolution, display size, etc.
# [09:54] <fantasai> Ashimura: Difficulty of Japanese text layout on big display is difficult,
# [09:54] <fantasai> Ashimura: e.g. 12 displays concatenated as a huge display
# [09:54] <fantasai> Ashimura: That kind of concatenation or linkage between displays is important
# [09:55] * r12a dbaron i lost connection and reconnected - could you hit the video button again for me please?
# [09:55] * r12a thanks
# [09:56] <fantasai> Ashimura: From Web designing viewpoint, including various text provided by customers
# [09:56] <fantasai> Ashimura: It's very difficult to justify the start/end point of characters nicely
# [09:57] <fantasai> Ashimura: Sankei Digital ^
# [09:57] <fantasai> Ashimura: Actual style depends on device resolution
# [09:58] <fantasai> Ashimura: Toppan generates magazines, novels, picture books, dictionaries
# [09:58] <fantasai> Ashimura: They have issues with quality of text layout and fonts.
# [09:58] <fantasai> Ashimura: They said they would like even more beautify layout
# [09:59] * fantasai RRSAgent make minutes
# [09:59] <kojiishi> Ashimura san's slides available at http://www.w3.org/2011/Talks/0601-web-and-japanese-layout-ka/
# [09:59] * fantasai RRSAgent: make minutes
# [09:59] * fantasai meh
# [09:59] <fantasai> Ashimura: Feedback from Audience
# [09:59] <fantasai> Slide:
# [09:59] <fantasai> * Important to consider spacing, inter-character/inter-line
# [09:59] <fantasai> * Ruby for pairs of kanji (jukugo) is important
# [10:00] <fantasai> * Dealing with text layout space is important
# [10:00] <fantasai> * stronger collaboration with SVG would be useful, e.g. SVG fonts and animation
# [10:01] * r12a would like to know how how much support there is for the need for jukugo ruby support as important
# [10:01] <fantasai> Ashimura: Today we're holding a dedicated forum on CSS
# [10:01] <fantasai> Ashimura shows a flowchart
# [10:02] <fantasai> Start box is JP, China, Korea, Taiwan, etc. Points with 'Use Cases & Requirements" to box labelled "This Forum"
# [10:02] <fantasai> "This Forum" branches into CSSWG, SVGWG, HTMLWG, I18NWG
# [10:02] <fantasai> "Japanese Layout Task Force" stretches across all of them and generates "Requirements for Japanese Text Layout", which feeds back into those WGs
# [10:03] <fantasai> The WG's each generate specs
# [10:03] <fantasai> CSSWG -> CSS specs, etc.
# [10:03] <r12a> diagram is here: http://www.w3.org/2011/Talks/0601-web-and-japanese-layout-ka/#[15]
# [10:03] <fantasai> Ashimura: Next steps should be bringing these requirements and the JLREQ requirements into working groups, including CSSWG
# [10:04] <fantasai> Ashimura: They will discuss how to implement (or not implement) those requirements.
# [10:04] <fantasai> Ashimura shows slide "Please join W3C!"
# [10:04] <fantasai> and encourages participation
# [10:08] <fantasai> Ashimura: I'd like to ask you all about this main theme: what is needed for Japanese Text Layout for the Web and e-Books?
# [10:09] <fantasai> [Commenting on slides in Japanese]
# [10:11] <fantasai> Tada: I haven't organized my thoughts yet, but looking at morning sessions especially Access's presentation
# [10:11] <fantasai> Tada: I thought some of those layouts would be useful for signage
# [10:14] <fantasai> Tada: Tada: ... larger fonts and display could be used for other purposes, and wondeirng if CSS can be used .
# [10:14] <fantasai> Tada: We are creating engines, can we use them for other effects.
# [10:14] <fantasai> Tada: For CSS, can we set up standards in a way that are extendable so that it can be used for various purposes
# [10:14] * r12a isn't clear what is the issue wrt large fonts
# [10:14] <fantasai> Tada: We were showing that presentation wondering if that could be used for other purposes
# [10:15] <fantasai> actually, I'm not sure who that was that was being translated
# [10:15] <fantasai> Maybe it was someone else..
# [10:16] <fantasai> Ashimura: Question for the audience: We received an opinion from Ichijo of Sankei that it's very difficult to display Japanese fonts in a ? way
# [10:16] <fantasai> Ashimura: So I think this question covers the issue of fonts, and also issues wrt spacing
# [10:16] <fantasai> Ashimura: And I have English on the side, maybe this because I'm not English speaker, but for some reason this English looks better to me
# [10:17] <fantasai> Ashimura: From native English speaker's POV, can't tell if English looks better than the Japanese
# [10:17] <fantasai> Nat: Neither is good.
# [10:17] <Bert> (I think that "someone" from above introduced himself as Yamamoto (sp?) from Alliance.)
# [10:17] <fantasai> Nat: In the case of Roman composition, unless it's a very fine composition.. in this resolution it looks ok.
# [10:17] <fantasai> Nat: For example, the end ... are not using proper ellipsis
# [10:18] * r12a dbaron am i missing something visual? (video is off again)
# [10:18] <fantasai> Nat: On the Japanese, the brackets and dots are not good at all.
# [10:18] * Quits: vhardy (vhardy@125.207.177.35) (Quit: vhardy)
# [10:19] <fantasai> Ashimura: The reason I ask this question to Nat-san, is Ichijo-san says Japanese layout does not look good.
# [10:19] <fantasai> Ashimura: Sounds like English native-speaker's POV this doesn't look good either.
# [10:19] <fantasai> Ashimura: It's an issue of making things look good on the Web.
# [10:21] * r12a thanks
# [10:22] <fantasai> Yamamoto says a lot of stuff.
# [10:22] * dbaron thinks the ugliest thing on the slides is the alignment of the square bullets
# [10:23] * hober dbaron: indeed
# [10:23] * fantasai the spacing in the Japanese is pretty off, too, though
# [10:23] * fantasai Japanese really needs a line-length that's a multiple of an em
# [10:23] * fantasai and the punctuation kerning there sucks
# [10:23] * fantasai I blame the font for that
# [10:24] * dbaron notes the version on the right (printed to PDF) is a mess (e.g., the "ffi")
# [10:24] <fantasai> Yamamoto: Even in Japanese, large headers or and advertisement, you usually use hand-kerning or proportional spacing (OpenType)
# [10:27] * dbaron wonders whether to comment on the English-in-Japanese-font now on the right screen
# [10:27] <fantasai> fantasai: Japanese needs measures that are a multiple of an em, otherwise justification results in very loose lines
# [10:28] <fantasai> fantasai: For CSS, that might mean being able to make the the width snap to a multiple of some length.
# [10:28] <fantasai> Nat: That reminds me of something I said in the Tokyo forum.
# [10:28] <fantasai> Nat: [Something] is not as important as [something else]
# [10:28] <dbaron> Nat: the placement of ... is not as important as the placement of the lines within the frame
# [10:28] <fantasai> Nat: In InDesign, the Japanese grid helps with the width of the line
# [10:29] <fantasai> Nat: If you use a frame grid, which is what we call the Japanese grid, to create the frame for the text
# [10:29] <fantasai> Nat: Then you will have an even number of ems
# [10:29] <fantasai> Nat: However inside the text, there will be times when you have text that doesn't exactly fit inside the grid.
# [10:29] <fantasai> Nat: And then you need to adjust the spacing.
# [10:29] <fantasai> Nat: When we did research early-on in InDesign's development cycle
# [10:29] * Joins: mg (mg@88.131.66.114)
# [10:30] <fantasai> Nat: We found that in Chinese text, there was a desire to return the grid as soon as possible as soon as you had got off the grid.
# [10:30] <fantasai> Nat: For example, if there was Chinese text then roman text then Chinese text, you would make spacing decisions to return to the grid as soon as possible.
# [10:30] * Quits: myakura (d2e8220d@109.169.29.95) (Quit: http://www.mibbit.com ajax IRC Client)
# [10:31] <fantasai> Nat: We found that in the early phototypesetting systems in Japan, we found that there were some house rules or conventions whereby they would have within the last few characters they would be on the grid
# [10:31] <fantasai> Nat: However, most of the users thought that that made it look like very old 1960s-style publication
# [10:31] <fantasai> Nat: However, my personal opinion was, I was very excited to hear this and wanted to make this happen in InDesign
# [10:31] <fantasai> Nat: But I'm the only one. :)
# [10:32] <fantasai> Nat: Instead what we did was, we decided the adjustment in the line between the two edges of the line would follow a more sophisticated spacing rule
# [10:32] <fantasai> Nat: And it should be the same whether or not there was a grid.
# [10:32] <fantasai> Nat: Therefore the grid in InDesign is used mostly to position the y-position of the line
# [10:33] * r12a would like someone to ask about grids as defined in CSS - are they important?
# [10:35] <r12a> s/defined in CSS/defined in CSS3/
# [10:35] <fantasai> Yamamoto: The role of the gird is to specify the lenght of the line and also the inter-line space
# [10:35] <fantasai> Yamamoto: What happens within the line is a separate discussion.
# [10:35] <fantasai> Yamamoto: For example if we have 32 characters per line
# [10:35] <fantasai> Yamamoto: We might have Japanese proportional setting to set the alignment
# [10:35] <fantasai> Yamamoto: But you can still revert to no spacing.
# [10:36] <fantasai> Yamamoto: As long as you revert the proportional setting, you can go back to solid setting
# [10:36] <fantasai> Yamamoto: When you specify proportional, each character has its own width. Uses font's alternate metrics
# [10:36] <fantasai> Yamamoto: So Japanese characters look like Roman characters. But even in that case we should use em-based grid to define the line lenght so that we can restore the original solid, non-proportional setting of the type group.
# [10:38] <fantasai> Ashimura: Now I'd like to ask your opinion. Nat discussed this from Adobe point of view. Now I'd like to ask web browser point of view
# [10:39] <fantasai> jdaggett: I'm not as knowledgeable as Nat, so I can't answer your question in a very knowledgeable way. But one thing
# [10:40] <fantasai> jdaggett: In conventional Web browser technologies, we don't really use OpenType data.
# [10:40] <fantasai> jdaggett: We use WebKit because we like to display things quickly.
# [10:40] <fantasai> jdaggett: But not good for quality
# [10:40] * fantasai jdaggett I think the translation missed something there
# [10:41] * dbaron notes jdaggett is not on irc
# [10:41] <fantasai> szilles: There's a number of cases where the quality of typography we see on the screen is perfectly adequate for that use case.
# [10:41] * sylvaing I'm totally quoting him on it regardless
# [10:41] <fantasai> szilles: But there are also use cases, particularly in advertising, where the quality of the image being projected is important
# [10:41] * dbaron is also amused to hear jdaggett being translated from Japanese to English
# [10:42] <fantasai> szilles: So the average user is not required to specify in great detail the typographic constraints
# [10:42] <fantasai> szilles: But the controls are there that someone looking for higher quality typography can get that by specifying additional properties
# [10:43] * Joins: myakura (d2e8220d@64.62.228.82)
# [10:43] <fantasai> Iksei: I've been involved in Web and printing for many years
# [10:44] <fantasai> Ikusei: Is it possible to have shashoku and shaken apart from CSS or in addition to CSS?
# [10:45] <r12a> what are shaken and sashoku ?
# [10:45] <fantasai> some discussion that doesn't really make sense without any context
# [10:45] * fantasai hasn't a clue
# [10:45] <fantasai> Ashimura: There are activities that use XML and ? to use things that are similar quality as paper printing
# [10:46] <fantasai> Nat: In talking about something other than CSS, it's useful to make the distinction between the rendering technology and the market that technology consumes
# [10:46] <fantasai> Nat: For example we have quite a nice text engine in Flash Player
# [10:46] <fantasai> Nat: Flash Player uses something totally different from CSS and HTML.
# [10:46] <fantasai> Nat: You can tell it to render text and animate it with ActionScript
# [10:47] <fantasai> Nat: The mojikumi in that string can be controlled much more precisely than with HTML and CSS
# [10:47] <fantasai> Nat: However, the point of evolving the standard, CSS and HTML, to improve their support for this kind of high-end typography is so that everyone can make use of it in more open technologies like the various browsers.
# [10:48] <fantasai> Nat: So, as to your question, I assume that you're talking about the rendering side rather than the markup side.
# [10:49] <fantasai> Ashimura: Unfortunately we have to close the session. I recommend that you come and join W3C directly to continue the conversation.
# [10:49] * Quits: sylvaing (sylvaing@125.207.177.35) (Quit: sylvaing)
# [10:49] <r12a> elika, how many people in the room ?
# [10:49] <fantasai> 4*7*3+~7
# [10:49] <fantasai> About 110?
# [10:49] <r12a> wow
# [10:49] <fantasai> Closing remarks.
# [10:50] * dbaron thinks a little less
# [10:50] <myakura> r12a, iirc shashoku means phototypesetting and Shaken is a shashoku system vendor
# [10:50] <fantasai> 3 per table, 28 tables
# [10:50] <fantasai> plus some standing
# [10:50] <r12a> doumo arigatou, myakura-san
# [10:50] <fantasai> or in the front
# [10:50] <dbaron> but a bunch of empty seats too
# [10:50] <fantasai> oh, they're all behind *you*
# [10:51] <fantasai> yeah, about 100
# [10:51] <fantasai> Koji: Using this forum as a starting point, we would like ot have more opportunities to learn from you
# [10:52] <fantasai> Forum closed.
# [10:52] <r12a> thanks for the panorama
# [10:52] <r12a> hello to all
# [10:52] <r12a> wishing i was there !
# [10:52] * Quits: kojiishi (kojiishi@125.207.177.35) (Quit: Leaving...)
# [10:52] * Quits: plinss (plinss@125.207.177.35) (Quit: plinss)
# [10:53] <r12a> dbaron, i just turned my video on
# [10:54] <dbaron> r12a, ah
# [10:54] <dbaron> anyway, 'later
# [10:54] * Quits: dbaron (dbaron@125.207.177.35) (Quit: 8403864 bytes have been tenured, next gc will be global.)
# [10:56] * Quits: alexmog (qw3birc@128.30.52.28) (Ping timeout)
# [11:02] * Quits: nmccully (nmccully@125.207.177.35) (Ping timeout)
# [11:04] * myakura wishes he's there, too.
# [11:09] * Quits: mg (mg@88.131.66.114) (Ping timeout)
# [11:14] <fantasai> RRSAgent: make minutes
# [11:14] <RRSAgent> I have made the request to generate http://www.w3.org/2011/06/01-css-minutes.html fantasai
# [11:14] * Quits: myakura (d2e8220d@64.62.228.82) (Quit: http://www.mibbit.com ajax IRC Client)
# [11:15] <fantasai> Meeting: Kyoto Forum on the Future of CSS for Asian Text Layout
# [11:15] <fantasai> RRSAgent: make minutes
# [11:15] <RRSAgent> I have made the request to generate http://www.w3.org/2011/06/01-css-minutes.html fantasai
# [11:20] * Joins: mg (mg@88.131.66.114)
# [11:35] * Parts: futhark (rune@213.236.208.22)
# [11:54] * Quits: glazou (glazou@80.118.184.70) (Quit: glazou)
# [12:57] * Quits: karl (karlcow@128.30.54.58) (Quit: This computer has gone to sleep)
# [14:26] * RRSAgent excuses himself; his presence no longer seems to be needed
# [14:26] * Parts: RRSAgent (rrs-loggee@128.30.52.169)
# [15:09] * Quits: murakami (murakami@118.154.209.3) (Quit: Leaving...)
# [16:00] * Quits: mg (mg@88.131.66.114) (Ping timeout)
# [16:07] * Quits: CSSWG_LogBot (PircBot@173.230.149.95) (Ping timeout)
# [16:07] * Joins: ChrisL (ChrisL@128.30.52.169)
# [16:09] * Joins: CSSWG_LogBot (PircBot@74.207.249.169)
# [17:25] * Joins: myakura (myakura@118.111.219.27)
# [17:55] * Joins: karl (karlcow@128.30.54.58)
# [18:13] * Quits: myakura (myakura@118.111.219.27) (Client exited)
# [18:17] * Joins: arno (arno@192.150.10.201)
# [18:23] * Quits: ChrisL (ChrisL@128.30.52.169) (Quit: Fire on main board error, client combusted)
# [18:47] * Quits: karl (karlcow@128.30.54.58) (Ping timeout)
# [19:02] * Joins: arno1 (arno@192.150.10.200)
# [19:04] * Quits: arno (arno@192.150.10.201) (Ping timeout)
# [20:28] * Quits: arno1 (arno@192.150.10.200) (Quit: Leaving.)
# [20:30] * Joins: arno (arno@192.150.10.200)
# [20:30] * Joins: mg (mg@83.227.44.127)
# [21:07] * Joins: arno1 (arno@192.150.10.200)
# [21:08] * Quits: arno (arno@192.150.10.200) (Ping timeout)
# [21:15] * Joins: karl (karlcow@128.30.54.58)
# [21:36] * Quits: arno1 (arno@192.150.10.200) (Quit: Leaving.)
# [21:38] * Joins: arno (arno@192.150.10.201)
# [22:15] * Quits: Ms2ger (Ms2ger@91.181.154.155) (Quit: nn)
# [23:04] * Quits: arno (arno@192.150.10.201) (Quit: Leaving.)
# [23:06] * Joins: arno (arno@192.150.10.201)
# Session Close: Thu Jun 02 00:00:00 2011

The end :)