IRC log of css on 2011-06-01

Timestamps are in UTC.

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