Geeko Magazine: A Technical Magazine on openSUSE, edited on openSUSE
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Takeyama, Fuminobu
Japan openSUSE User Group publishes a technical magazine every half year. The title of the magazine is Geeko Magazine. It consists of technical articles on openSUSE and applications running on openSUSE. For example, the latest issue of the magazine contains articles like "Launching Kubernetes Cluster with Kubic in 10 minutes", "Accessing to Google Drive from openSUSE", and "How to enable HTTPS with Let's Encrypt." Since 2014, we have published 9 issues of Geeko Magazine. In this talk, after explaining the culture of self-publishing in Japan, I will talk about the process from calling articles from the user group until distributing Geeko Magazine. Another topic is our challenge: editing the magazine on openSUSE. Thereby, we cannot use popular desktop publishing (DTP) applications like Adobe InDesign. Instead of such applications, we have been using Scribus, an OSS DTP application to edit Geeko Magazine. It supports CMYK color and DTP data such as trim marks and bleed areas, required by print shops. However, in 2014, Scribus was not adequate for writing a Japanese document. This is because typesetting rules are much different from English etc. To publish Geeko Magazine, we went OSS way; we have improved Scribus one by one at every issue of the magazine in cooperation with the upstream community. I will talk about a brief summary of those problems we have resolved.
 Okay, good afternoon everyone. Thank you for coming. Today I'm talking about Giko Magazine, which is a series of technical magazines about open souser and it's published by the Japan Open-Souser group. So before starting, let me introduce myself. I'm Fumino Mutakiyama. My open souser ID is Etake and maybe you've already noticed I'm from Japan. And I'm one of the organizers of Japan Open-Souser user group, which is a local, so, Linux user group. And so I often attend local conferences and have a booth and talk about open souser. And so, also since 2014, I'm a member of Open-Souser Asia Summit Organizing Committee. And in 2017, we had Open-Souser Asia Summit in Tokyo, Japan. And as a conference, I was the chair. And so here's today for the interesting next Open-Souser Asia Summit. So next Open-Souser Asia Summit is held in Bali, Indonesia. So the important thing is the Koroko paper is open until next month. So Bali is a very good place to visit because it's a tropical resort area and many historical places. And also, important thing is, this photo is taken in 2016, the last time Open-Souser Asia Summit was held in Indonesia. So there in Indonesia, there is a big community. So as a conference, 500 people come to the Asia Summit. And so committee guys are very enthusiastic and very hot and friendly. So yeah, I recommend to visit Indonesia and have a talk at the conference. So then I'm a package maintainer of Open-Souser's MS-70N project and maintaining some input methods or a package related to points. And by the way, so I'm not working for Souser. I'm a community developer. And so my daily job is working as a house of their consultant in Japanese civilian infrastructure platform products company. So today's topic is Gikomagazine. So is there anyone who knows about Gikomagazine? Thank you very much. So Gikomagazine is a technical magazine or Open-Souser. So it contains many technical articles related to Open-Souser. And also it have some contents like Novels, which is not non-technical, but Novels is related to Open-Souser. Yeah, it's very fun. So here is one copy of Gikomagazine. Gikomagazine is so B5 size. B5 Japanese, we use the Japanese special size, but it's between A5 and A4. And it have about this issue. We have 44 pages and we are selling this book in 500 yen. It's approximately 4 euro. So why do we publish Gikomagazine by ourselves? One reason is commercial publishing, so technical commercial magazine does not mention Open-Souser. They tend to write about many CentOS and Ubuntu, so they don't write articles about Open-Souser. So we decided to make our own magazine, which have many Open-Souser articles. Of course, it's fun to make magazine by ourselves. So please look at this picture. There are many covers of past Gikomagazines. So on the covers, we can usually find personified, so human-like chameleons, or some stuffed chameleon toys. So why are there two types of covers? The reason is very simple. So we cannot find a good painter of those years. In such case, I take photo of my Giko toys and put it on the cover. So what contents of Gikomagazine like? This is one page of Gikomagazine 2018 winter. The title of this article is Building Kubernetes Cluster Using Cubic in 10 Minutes. This one written by Ashiota-san. And he will talk about Cubic and software-defined storage after this session. This one is Let's Start High-Speed Packet Processing with DPDK. Yeah, very crazy. Tenron, this article is written by Imaxel. He's a very young guy. And he loves packet processing. So every time he write about some articles about packet processing. So this is of this article about packet processing is very popular among readers. And the last one is how to use Google Drive. A promo for this. This one is written by Rippon-san. Maybe you know, we have several approaches to use Google Drive. For example, one approach is using KDE integration or GNOME integration to access Google Drive. So this article explains such ways to access Google Drive and compare them one by one. And he also write about OneDrive before this issue. At that time, so many people say that, why you introduce OneDrive? Why not Google Drive? So he decided to write about Google Drive. As I mentioned, Gecko Magazine is not commercial magazine, but self-published magazine. So it is distributed by not by publishers, by ourselves. So let me explain about self-publishing culture in Japan. So in Japan, there are many groups or individuals who are doing self-publishing. For such people, there is an event called Comiket. Also, Comiket is in short, full name is Comiket. One knows about Comiket here. Comiket is a huge kind of festival. At Comiket, we can find some comic events, so we can make comics. And also some novels and music, many kinds of stuff. And so Comiket is held every half year, August and December. And it's very huge. And every time, half million people come together to the biggest event hall in Japan in three days. And we have a booth at Comiket. So this is the picture of our booth. The booth is not so big because the space is very limited. And there are about five groups around us, also writing technical books about some source applications. So the market of self-publishing is now growing in Japan. In 2016, another event called Takebook Fest just started. So this Takebook Fest, for this Takebook Fest, 470 groups, or individuals writing technical books, come together. And 1,000 visitors come to buy self-published books. And Japan booths have a booth twice at the Takebook Fest, but it is now difficult to get a booth because too many groups want it to get a booth at the Takebook Fest. So far, I talk about Gigo Magazine and Japanese self-publishing culture. So from now on, I talk about how to make Gigo Magazine. The first step to make Gigo Magazine is call for articles. The articles on Gigo Magazine is written by three or four members of Japan Opsu the user group. To collect articles two months before comicate, I post a message, a simple message to our mailing list to call articles. It's like if you have some topics for next Gigo Magazine, please reply title and expected number of pages to me. This is just, this is all I write for call for articles. And by the way, what is return to authors? The only return is the authors can get copy of Gigo Magazine after comicate. So authors cannot get money, for example. So it's like contributing to open the week or something like that. So second step, then each author start to write the articles and first, so first they start to write a draft. We have a template for template in open document format, so they use library for writing draft. The drafts are reviewed by all the authors, by each other. So this picture is a screenshot of draft. I sometimes write many comments or ask them to fix. So this article has many comments. So yellow box is comment feature, from comment feature of library office writer. So the author can fix. So if the author, even if the author are not familiar with writing technical articles, but they can get some other prices from other authors than me. And maybe so he can challenge to write technical articles. So after reviewing, the third step is design and making pages. So this is my job. And from now on, I don't use library office. I now use Scribas. Scribas is a publishing application. And I mentioned it in detail later. So I copy text and images from library office and place them onto the page of Scribas. So this is important because this allows to keep the design consistent and consistent among all the articles. So finally, so step four is printing of magazine. So to print our book, I send PDF data to generated by Scribas to a print shop. So to print the magazine, it costs about 300 euros for 150 copies of 48 pages book. And it takes about two weeks to print. So we print the book directly to communicate booth. So we just receive then at the booth at Comiquet. So from now on, I talk about technical some more detail how to make Gikko magazine. So our challenge is to edit Gikko magazine with free library open source software running on open source. So we don't use, for example, popular products like Adobe InDesign or Illustrator. So firstly, we use open source fonts. And then we use open source applications such as Krita and Scribas. So today I will talk mainly about Scribas. So the first component in the fonts, we need some fonts to write, to make a book, of course. However, in 2014, when we made the first issue of Gikko magazine, there was no choice among Japanese open source fonts, open source, so cellophane, so sans fonts, with enough quality. But it was IPA EXMintro for cellophane and Mplus fonts for sans fonts. So this is because Japanese letters, so maybe it's very complex characters. So Japanese font tends to be expensive. And this IPA EXMintro is font distributed in open source license, but actually it's not developed in open source way. It's provided by government. And Mplus font is developed in open source way. And now this situation is getting better. And now we have Advisors Hansel fonts and also known as Google Not Cjk font series, which is high quality open source fonts with much weight. So from the last issue, we are using not cellophane font and Mplus font. So then we use Scribath instead of Adobe InDesign. Scribath is a powerful desktop publishing software. And of course, it is open source. We are now using 1.5X SVM head for Gikko magazine. So what is special and different from applications such as Libreos writer? Firstly, Scribath supports CMYK color, which is necessary for offset printing. And then it can export PDFX format, which is a strict version of PDF. And it is also necessary to send our data to print shop. And finally, it supports TrimMax and Bleed. Those are also important, but I'll explain in detail this slide. So look at this picture explaining TrimMax and Bleed. And Bleed is earlier printed but trimmed out. It's necessary when we place an image at the edges of a page. And on Scribath, the area outside of this red line is Bleed. And TrimMax is a mark indicating where is Bleed. So when writing a PDF data from Scribath, Scribath automatically adds these three marks onto PDF pages. So as shown in the third picture, after printing, Bleed is trimmed out. So however, the first time I tried Scribath, it only provides very limited Japanese support. So it's because Japanese is quite different from languages, for example, in Europe. So supporting Japanese is very difficult. So even Microsoft Word and LibreOffice Writer does not fully support Japanese text layout thing. So if you're interested in Japanese type setting, there is a very huge document from W3C. And so what we did, so we went on open source way. We improved Scribath together with upstream community. We are very lucky because after we started this Gigo magazine, in Scribath project, there is a sub-project of Scribath, CTL project, just started. CTL project is aimed to improve and rewrite Scribath score engine to support complex text layout, such as right to left languages used in Arabic, and also they aim to improve CJK support. I helped to improve CJK support and send many feedbacks and wrote only a few code. So since we had a very excellent committer from maybe he's Arabic native, so yeah, I just, so it was okay to send, just send feedbacks. He wrote many code for me. What is difficult in implementing Japanese and so CJK, Chinese, Japanese, Korean support? One major difference is text justification. So text justification is a feature to align text at the end of time, so which is necessary for writing books. One major difference in CJK and the European language is there's no space between words. So Scribath cannot adjust the end of line by extending spaces. So what we have to do for CJK text layout is Scribath insert implicit spaces, so in other, so all spacing between every character of, every CJK characters. And then, so the end of line is now aligned. So Scribath 1.4, which is a stable branch, does not support this CJK so justification. So first time I made Gecko magazine, I put some patches from 1.5 branch and applied to 1.4.4. Now we are using a screen head, so containing, so it's okay because those fixes are already merged. In this side I want to introduce another improvement, which is spacing between CJK and Latin letters. So to keep a clearance, we usually add a quarter space between CJK characters and Latin characters. So this one is a screenshot of first implementation. So in this implementation there is a space after E of open-sensor and Japanese letter 1. Yeah, it's okay. And second line, there is a space between Japanese character and colon. So we don't need automatic space here. So the problem is the rule is not correct or well defined. So we defined a list of characters which need space around between CJK and Latin letters. And after that improvement, now we don't have implicit space between Japanese character and colon. So the patch is very simple like this. There is a giant if and so, or sign. So maybe, so condition indicating the range of characters and they are connected with or sign. So but sometimes I think what happens with K-lib letters? I mentioned there is adding space between Latin and CJK characters. So in this implementation, K-lib characters are not supported. So maybe we still need to extend the rule for more, so, longer support. So there are the problems not resolved. There are many, but I will introduce two. The first one is Japanese input from keyboard. Fortunately, Scribath does not work correctly with Scribath main window. So we cannot enter directly from keyboard. So I usually copy text from library or other editors. And the other one is timing of some Japanese type setting rules. For example, we sometimes turn on a spacing feature I mentioned, previous slide for writing so program code onto articles because if so Scribath is adding implicit spaces onto program code, the column not aligned every characters. So we still need my improvement. And I want to fix some bugs by the next issue of Kiko magazine. So the remaining time is limited. Let's conclude my talk. But yeah, yeah, the quickly answered questions. And I'm pretty asked for a question. So, will you translate to our Giko magazine into other languages? The answer is no by us. But we are planning to release our Giko magazine, so archive version of our Giko magazine under creative common license. So after that, maybe everyone can translate it, but they have to understand some Japanese. So here is summary of this talk. Giko magazine is written by Japan OpenSusus group and it's self-published technical magazine and so self-publishing of technical magazine, technical books in Japan is growing. So we are maybe so riding that way. And Scribath is a powerful open source desktop publishing applications and we have improved. It improves Scribath for better Japanese support for our Giko magazine. So thank you for listening. That's all. So, yeah. Two questions. I'm planning to release archive version of Scribath file, source of our Giko magazine in creative common license. But one problem is there's no compatibility between old and current Scribath file. So that's why we choose archive version. So I will convert all version, all Scribath file to new version. For the first question, so when? The combating is not finished. So yeah, I now cannot answer when. But yeah, if I make time, I will so combat it and as soon as possible, so I will release the combat version as soon as possible. We will talk. So articles are written in English. Yeah, maybe I will. So English articles onto something. So yeah, yeah, we are welcome to come in. Japanese. It's very much. I don't know either. Maybe people, so I think when the leader of Gikomagase can understand some English articles, I believe. So yeah, maybe English articles are all fine. That's an idea, which you may be writing. Maybe it will be interesting to let people who are not that know what to speak to know about the articles. Like the word for article is to make something more open so people know what to speak to and what to do. So it means for the people that speak, the people that speak, it's open for people to understand. I don't know, so you said you write about, you will write an interview with the publisher, but I don't know, let's say you wonder how to use OBS and anybody in the producer will know about it. So you could make a list of topics you don't know much about, so other people can ask you to write about it and you publish that interview. So we will send the talk of papers to the, not only to the managers, but to the managers. So maybe the topic that I'm appealing for the user. So yeah, maybe let's make a Gikomagase with kind of global community. Yeah, it's a nice idea, but maybe editing, so yeah, editor will be very busy, I think. But yeah, it's good idea to invite more, so contents from global community. Yeah. So. Hmm. Yeah. Yeah, I think next Gikomagase have a personified version. Yeah, there are these, so there's no stuffed version. I'm not sure how it will be because yeah, I don't have so draft cover work. How long does it take from the first draft to the final magazine to work? What's the timeline? Ah. So, about two weeks, two or three weeks. I need more than one week to make a page, so we're making a scripted state. So yeah. Right? Left or right? Yeah, yeah. So, scrimmage don't support vertical layout. And, Porticon Gikomagase, yeah, we usually use, so left to right. Because it's like scrimmage doesn't support it and you would have to use that right. Would you prefer your magazine from top to bottom? Yeah. So articles we usually use left to right because we use many, so English words. So, top to bottom, so pushing English letters, so top to bottom layout is really difficult. It can. I know one commercial magazine using vertical layout. Yeah, to me it's too difficult to edit, I think. I never thought about the Japanese and Japanese and Japanese, but I never thought about it. Yeah, that works for it. So, it's Japanese support is maybe best among open source applications, I think. But, so using that tip, we sometimes use magazine like layout, so putting images at the edge of pages. So we use corner pages. But using the tech, it's a bit difficult because we need to know, so type native commands. Yeah, it's a bit difficult. I don't know if you know that, but I think that people would like to make it at the end, more of a term for it. And you know, like the final style between changing the style of the photo. Yeah, many people in Japan, software writing, technical articles, use Ratek. I think it's a very serious problem, but I won't think that, because that opens the possibility to translate your magazine to other languages without writing. Yeah, so, yeah, we sort of set it with, so, but maybe so they have to adjust some layout. Thank you.
 Okay, good afternoon everyone.  Thank you for coming.  Today I'm talking about Giko Magazine, which is a series of technical magazines about open  souser and it's published by the Japan Open-Souser group.  So before starting, let me introduce myself.  I'm Fumino Mutakiyama.  My open souser ID is Etake and maybe you've already noticed I'm from Japan.  And I'm one of the organizers of Japan Open-Souser user group, which is a local, so, Linux user  group.  And so I often attend local conferences and have a booth and talk about open souser.  And so, also since 2014, I'm a member of Open-Souser Asia Summit Organizing Committee.  And in 2017, we had Open-Souser Asia Summit in Tokyo, Japan.  And as a conference, I was the chair.  And so here's today for the interesting next Open-Souser Asia Summit.  So next Open-Souser Asia Summit is held in Bali, Indonesia.  So the important thing is the Koroko paper is open until next month.  So Bali is a very good place to visit because it's a tropical resort area and many historical  places.  And also, important thing is, this photo is taken in 2016, the last time Open-Souser Asia  Summit was held in Indonesia.  So there in Indonesia, there is a big community.  So as a conference, 500 people come to the Asia Summit.  And so committee guys are very enthusiastic and very hot and friendly.  So yeah, I recommend to visit Indonesia and have a talk at the conference.  So then I'm a package maintainer of Open-Souser's MS-70N project and maintaining some input  methods or a package related to points.  And by the way, so I'm not working for Souser.  I'm a community developer.  And so my daily job is working as a house of their consultant in Japanese civilian infrastructure  platform products company.  So today's topic is Gikomagazine.  So is there anyone who knows about Gikomagazine?  Thank you very much.  So Gikomagazine is a technical magazine or Open-Souser.  So it contains many technical articles related to Open-Souser.  And also it have some contents like Novels, which is not non-technical, but Novels is  related to Open-Souser.  Yeah, it's very fun.  So here is one copy of Gikomagazine.  Gikomagazine is so B5 size.  B5 Japanese, we use the Japanese special size, but it's between A5 and A4.  And it have about this issue.  We have 44 pages and we are selling this book in 500 yen.  It's approximately 4 euro.  So why do we publish Gikomagazine by ourselves?  One reason is commercial publishing, so technical commercial magazine does not mention Open-Souser.  They tend to write about many CentOS and Ubuntu, so they don't write articles about Open-Souser.  So we decided to make our own magazine, which have many Open-Souser articles.  Of course, it's fun to make magazine by ourselves.  So please look at this picture.  There are many covers of past Gikomagazines.  So on the covers, we can usually find personified, so human-like chameleons, or some stuffed chameleon  toys.  So why are there two types of covers?  The reason is very simple.  So we cannot find a good painter of those years.  In such case, I take photo of my Giko toys and put it on the cover.  So what contents of Gikomagazine like?  This is one page of Gikomagazine 2018 winter.  The title of this article is Building Kubernetes Cluster Using Cubic in 10 Minutes.  This one written by Ashiota-san.  And he will talk about Cubic and software-defined storage after this session.  This one is Let's Start High-Speed Packet Processing with DPDK.  Yeah, very crazy.  Tenron, this article is written by Imaxel.  He's a very young guy.  And he loves packet processing.  So every time he write about some articles about packet processing.  So this is of this article about packet processing is very popular among readers.  And the last one is how to use Google Drive.  A promo for this.  This one is written by Rippon-san.  Maybe you know, we have several approaches to use Google Drive.  For example, one approach is using KDE integration or GNOME integration to access Google Drive.  So this article explains such ways to access Google Drive and compare them one by one.  And he also write about OneDrive before this issue.  At that time, so many people say that, why you introduce OneDrive?  Why not Google Drive?  So he decided to write about Google Drive.  As I mentioned, Gecko Magazine is not commercial magazine, but self-published magazine.  So it is distributed by not by publishers, by ourselves.  So let me explain about self-publishing culture in Japan.  So in Japan, there are many groups or individuals who are doing self-publishing.  For such people, there is an event called Comiket.  Also, Comiket is in short, full name is Comiket.  One knows about Comiket here.  Comiket is a huge kind of festival.  At Comiket, we can find some comic events, so we can make comics.  And also some novels and music, many kinds of stuff.  And so Comiket is held every half year, August and December.  And it's very huge.  And every time, half million people come together to the biggest event hall in Japan in three  days.  And we have a booth at Comiket.  So this is the picture of our booth.  The booth is not so big because the space is very limited.  And there are about five groups around us, also writing technical books about some source  applications.  So the market of self-publishing is now growing in Japan.  In 2016, another event called Takebook Fest just started.  So this Takebook Fest, for this Takebook Fest, 470 groups, or individuals writing technical  books, come together.  And 1,000 visitors come to buy self-published books.  And Japan booths have a booth twice at the Takebook Fest, but it is now difficult to  get a booth because too many groups want it to get a booth at the Takebook Fest.  So far, I talk about Gigo Magazine and Japanese self-publishing culture.  So from now on, I talk about how to make Gigo Magazine.  The first step to make Gigo Magazine is call for articles.  The articles on Gigo Magazine is written by three or four members of Japan Opsu the user  group.  To collect articles two months before comicate, I post a message, a simple message to our  mailing list to call articles.  It's like if you have some topics for next Gigo Magazine, please reply title and expected  number of pages to me.  This is just, this is all I write for call for articles.  And by the way, what is return to authors?  The only return is the authors can get copy of Gigo Magazine after comicate.  So authors cannot get money, for example.  So it's like contributing to open the week or something like that.  So second step, then each author start to write the articles and first, so first they  start to write a draft.  We have a template for template in open document format, so they use library for writing draft.  The drafts are reviewed by all the authors, by each other.  So this picture is a screenshot of draft.  I sometimes write many comments or ask them to fix.  So this article has many comments.  So yellow box is comment feature, from comment feature of library office writer.  So the author can fix.  So if the author, even if the author are not familiar with writing technical articles,  but they can get some other prices from other authors than me.  And maybe so he can challenge to write technical articles.  So after reviewing, the third step is design and making pages.  So this is my job.  And from now on, I don't use library office.  I now use Scribas.  Scribas is a publishing application.  And I mentioned it in detail later.  So I copy text and images from library office and place them onto the page of Scribas.  So this is important because this allows to keep the design consistent and consistent  among all the articles.  So finally, so step four is printing of magazine.  So to print our book, I send PDF data to generated by Scribas to a print shop.  So to print the magazine, it costs about 300 euros for 150 copies of 48 pages book.  And it takes about two weeks to print.  So we print the book directly to communicate booth.  So we just receive then at the booth at Comiquet.  So from now on, I talk about technical some more detail how to make Gikko magazine.  So our challenge is to edit Gikko magazine with free library open source software running  on open source.  So we don't use, for example, popular products like Adobe InDesign or Illustrator.  So firstly, we use open source fonts.  And then we use open source applications such as Krita and Scribas.  So today I will talk mainly about Scribas.  So the first component in the fonts, we need some fonts to write, to make a book, of course.  However, in 2014, when we made the first issue of Gikko magazine, there was no choice among  Japanese open source fonts, open source, so cellophane, so sans fonts, with enough quality.  But it was IPA EXMintro for cellophane and Mplus fonts for sans fonts.  So this is because Japanese letters, so maybe it's very complex characters.  So Japanese font tends to be expensive.  And this IPA EXMintro is font distributed in open source license, but actually it's  not developed in open source way.  It's provided by government.  And Mplus font is developed in open source way.  And now this situation is getting better.  And now we have Advisors Hansel fonts and also known as Google Not Cjk font series,  which is high quality open source fonts with much weight.  So from the last issue, we are using not cellophane font and Mplus font.  So then we use Scribath instead of Adobe InDesign.  Scribath is a powerful desktop publishing software.  And of course, it is open source.  We are now using 1.5X SVM head for Gikko magazine.  So what is special and different from applications such as Libreos writer?  Firstly, Scribath supports CMYK color, which is necessary for offset printing.  And then it can export PDFX format, which is a strict version of PDF.  And it is also necessary to send our data to print shop.  And finally, it supports TrimMax and Bleed.  Those are also important, but I'll explain in detail this slide.  So look at this picture explaining TrimMax and Bleed.  And Bleed is earlier printed but trimmed out.  It's necessary when we place an image at the edges of a page.  And on Scribath, the area outside of this red line is Bleed.  And TrimMax is a mark indicating where is Bleed.  So when writing a PDF data from Scribath, Scribath automatically adds these three marks  onto PDF pages.  So as shown in the third picture, after printing, Bleed is trimmed out.  So however, the first time I tried Scribath, it only provides very limited Japanese support.  So it's because Japanese is quite different from languages, for example, in Europe.  So supporting Japanese is very difficult.  So even Microsoft Word and LibreOffice Writer does not fully support Japanese text layout  thing.  So if you're interested in Japanese type setting, there is a very huge document from W3C.  And so what we did, so we went on open source way.  We improved Scribath together with upstream community.  We are very lucky because after we started this Gigo magazine, in Scribath project, there  is a sub-project of Scribath, CTL project, just started.  CTL project is aimed to improve and rewrite Scribath score engine to support complex text  layout, such as right to left languages used in Arabic, and also they aim to improve CJK  support.  I helped to improve CJK support and send many feedbacks and wrote only a few code.  So since we had a very excellent committer from maybe he's Arabic native, so yeah, I  just, so it was okay to send, just send feedbacks.  He wrote many code for me.  What is difficult in implementing Japanese and so CJK, Chinese, Japanese, Korean support?  One major difference is text justification.  So text justification is a feature to align text at the end of time, so which is necessary  for writing books.  One major difference in CJK and the European language is there's no space between words.  So Scribath cannot adjust the end of line by extending spaces.  So what we have to do for CJK text layout is Scribath insert implicit spaces, so in  other, so all spacing between every character of, every CJK characters.  And then, so the end of line is now aligned.  So Scribath 1.4, which is a stable branch, does not support this CJK so justification.  So first time I made Gecko magazine, I put some patches from 1.5 branch and applied to  1.4.4.  Now we are using a screen head, so containing, so it's okay because those fixes are already  merged.  In this side I want to introduce another improvement, which is spacing between CJK and Latin letters.  So to keep a clearance, we usually add a quarter space between CJK characters and Latin characters.  So this one is a screenshot of first implementation.  So in this implementation there is a space after E of open-sensor and Japanese letter 1.  Yeah, it's okay.  And second line, there is a space between Japanese character and colon.  So we don't need automatic space here.  So the problem is the rule is not correct or well defined.  So we defined a list of characters which need space around between CJK and Latin letters.  And after that improvement, now we don't have implicit space between Japanese character  and colon.  So the patch is very simple like this.  There is a giant if and so, or sign.  So maybe, so condition indicating the range of characters and they are connected with  or sign.  So but sometimes I think what happens with K-lib letters?  I mentioned there is adding space between Latin and CJK characters.  So in this implementation, K-lib characters are not supported.  So maybe we still need to extend the rule for more, so, longer support.  So there are the problems not resolved.  There are many, but I will introduce two.  The first one is Japanese input from keyboard.  Fortunately, Scribath does not work correctly with Scribath main window.  So we cannot enter directly from keyboard.  So I usually copy text from library or other editors.  And the other one is timing of some Japanese type setting rules.  For example, we sometimes turn on a spacing feature I mentioned, previous slide for writing  so program code onto articles because if so Scribath is adding implicit spaces onto program  code, the column not aligned every characters.  So we still need my improvement.  And I want to fix some bugs by the next issue of Kiko magazine.  So the remaining time is limited.  Let's conclude my talk.  But yeah, yeah, the quickly answered questions.  And I'm pretty asked for a question.  So, will you translate to our Giko magazine into other languages?  The answer is no by us.  But we are planning to release our Giko magazine, so archive version of our Giko magazine under  creative common license.  So after that, maybe everyone can translate it, but they have to understand some Japanese.  So here is summary of this talk.  Giko magazine is written by Japan OpenSusus group and it's self-published technical magazine  and so self-publishing of technical magazine, technical books in Japan is growing.  So we are maybe so riding that way.  And Scribath is a powerful open source desktop publishing applications and we have improved.  It improves Scribath for better Japanese support for our Giko magazine.  So thank you for listening.  That's all.  So, yeah.  Two questions.  I'm planning to release archive version of Scribath file, source of our Giko magazine  in creative common license.  But one problem is there's no compatibility between old and current Scribath file.  So that's why we choose archive version.  So I will convert all version, all Scribath file to new version.  For the first question, so when?  The combating is not finished.  So yeah, I now cannot answer when.  But yeah, if I make time, I will so combat it and as soon as possible, so I will release  the combat version as soon as possible.  We will talk.  So articles are written in English.  Yeah, maybe I will.  So English articles onto something.  So yeah, yeah, we are welcome to come in.  Japanese.  It's very much.  I don't know either.  Maybe people, so I think when the leader of Gikomagase can understand some English articles, I believe.  So yeah, maybe English articles are all fine.  That's an idea, which you may be writing.  Maybe it will be interesting to let people who are not that know what to speak to know about the articles.  Like the word for article is to make something more open so people know what to speak to and what to do.  So it means for the people that speak, the people that speak, it's open for people to understand.  I don't know, so you said you write about, you will write an interview with the publisher, but I don't know, let's say you wonder how to use OBS and anybody in the producer will know about it.  So you could make a list of topics you don't know much about, so other people can ask you to write about it and you publish that interview.  So we will send the talk of papers to the, not only to the managers, but to the managers.  So maybe the topic that I'm appealing for the user.  So yeah, maybe let's make a Gikomagase with kind of global community.  Yeah, it's a nice idea, but maybe editing, so yeah, editor will be very busy, I think.  But yeah, it's good idea to invite more, so contents from global community.  Yeah.  So.  Hmm.  Yeah.  Yeah, I think next Gikomagase have a personified version.  Yeah, there are these, so there's no stuffed version.  I'm not sure how it will be because yeah, I don't have so draft cover work.  How long does it take from the first draft to the final magazine to work?  What's the timeline?  Ah.  So, about two weeks, two or three weeks.  I need more than one week to make a page, so we're making a scripted state.  So yeah.  Right?  Left or right?  Yeah, yeah.  So, scrimmage don't support vertical layout.  And, Porticon Gikomagase, yeah, we usually use, so left to right.  Because it's like scrimmage doesn't support it and you would have to use that right.  Would you prefer your magazine from top to bottom?  Yeah.  So articles we usually use left to right because we use many, so English words.  So, top to bottom, so pushing English letters, so top to bottom layout is really difficult.  It can.  I know one commercial magazine using vertical layout.  Yeah, to me it's too difficult to edit, I think.  I never thought about the Japanese and Japanese and Japanese, but I never thought about it.  Yeah, that works for it.  So, it's Japanese support is maybe best among open source applications, I think.  But, so using that tip, we sometimes use magazine like layout, so putting images at the edge of pages.  So we use corner pages.  But using the tech, it's a bit difficult because we need to know, so type native commands.  Yeah, it's a bit difficult.  I don't know if you know that, but I think that people would like to make it at the end, more of a term for it.  And you know, like the final style between changing the style of the photo.  Yeah, many people in Japan, software writing, technical articles, use Ratek.  I think it's a very serious problem, but I won't think that, because that opens the possibility to translate your magazine to other languages without writing.  Yeah, so, yeah, we sort of set it with, so, but maybe so they have to adjust some layout.  Thank you.
openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_0_143.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_144_1559.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_1560_2087.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_2088_5975.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_5976_6071.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_6072_8099.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_8100_9467.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_9468_9611.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_9612_12827.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_12828_14039.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_14040_14135.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_14136_15863.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_15864_17543.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_17544_20519.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_20520_21299.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_21300_22103.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_22104_22163.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_22164_23639.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_23640_25247.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_25248_31943.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_31944_32951.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_32952_37991.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_37992_39695.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_39696_42455.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_42456_42599.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_42600_42719.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_42720_42923.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_42924_43583.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_43584_45719.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_45720_47807.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_47808_48695.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_48696_48791.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_48792_50951.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_50952_52667.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_52668_53603.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_53604_53831.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_53832_54095.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_54096_54155.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_54156_54347.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_54348_55211.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_55212_55343.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_55344_55451.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_55452_55883.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_55884_56003.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_56004_57791.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_57792_59471.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_59472_62603.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_62604_62975.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_62976_63839.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_63840_65087.png openSUSE_Conference_2019_-_Geeko_Magazine__A_Techn_VedBFH1FTx4_65088_65207.png