Hi Thomas, > Yes, as far as I remember, italic/bold is unusual in Japanese > typography, isn't it?
Surely it was unusual in the past. But now frequently used; I think computing culture makes it usual (HTML tags, word processing softwares etc.). > It may be worth to branch the original ipa-fonts package from > M17N:fonts and submit your changes back. That way, we have it in _one_ > package and it's in an official repository. Ok, I'll try. On Thu, 19 Apr 2012 16:02:57 +0200 Thomas Schraitle <t...@suse.de> wrote: > Hi Yasuhiko Kamata, > > > > > Finally we have completed translations of openSUSE-manual to Japanese > > (already uploaded to opensuse-doc SVN). > > So I want them to be distributed via opensuse official repository and > > make them available online (doc.opensuse.org). > > Thanks for your efforts! Regarding translation, Karl already answered > that part. > > > > Anyway, some tweaks needed for Japanese PDF (not neededed for HTML); > > 1. Need italic/bold fonts. > > > > Since FOP cannot generate italic(oblique)/bold style from existing > > fonts (and all existing Japanese fonts does not contain them), > > I've decided to generate them (by fontforge scripting) before > > making PDFs. > > Cool! > Yes, as far as I remember, italic/bold is unusual in Japanese > typography, isn't it? > > > > These fonts are packaged with name IPAGothic_BoldItalic > > in OBS home project (OBS > Projects > home:belphegor_belbel). > > (This package's publish flag is now off, because this package is > > not essential one.) > > It may be worth to branch the original ipa-fonts package from > M17N:fonts and submit your changes back. That way, we have it in _one_ > package and it's in an official repository. > > > > 2. Special FOP configs. > > > > For Japanese fonts, special configs are needed for FOP (even if > > normal (not bold/italic) font). This config is now located at > > opensuse-doc SVN > > (/svn/opensuse-doc/trunk/documents/distribution/ja/fop-suse-ja.xml). > > DC-* and ENV-* files were adjusted accordingly. > > Our latest daps version contains a bugfix which lets you set the FOP > config file. However, this is not available in the current released daps > package. > > The latest version supports the FOP_CONFIG_FILE environment variable. > Move your FOP configuration file to your SVN working copy and set the > above variable to your file, (re)build the book and it will use the > correct file. > > If you are unsure, you can check the value, if you use daps with this > options: > > $ daps -d YOUR_DC_FILE showvariable VARIABLE=FOP_CONFIG_FILE > > We will release a new package soon which supports this feature. > > > -- > Gruß/Regards, > Thomas Schraitle > > ---------------------------------------------------------------------- > SUSE LINUX Products GmbH (o< > Maxfeldstrasse 5 /\\ Documentation Specialist > 90409 Nuernberg, Germany _\_v http://www.suse.com > http://lizards.opensuse.org/author/thomas-schraitle/ > SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, > Felix Imendörffer, HRB 21284 (AG Nürnberg) > -- > To unsubscribe, e-mail: opensuse-doc+unsubscr...@opensuse.org > To contact the owner, e-mail: opensuse-doc+ow...@opensuse.org > Thanks, -- Yasuhiko Kamata <belphe...@belbel.or.jp> -- To unsubscribe, e-mail: opensuse-doc+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-doc+ow...@opensuse.org
