[opensuse-m17n] Takao Fonts - community developed derivatives of IPA Fonts - are available. - openSUSE M17n

newer
[opensuse-m17n] M17N:Devel cleaned...

[opensuse-m17n] Takao Fonts - community developed derivatives of IPA Fonts - are available.

Satoru Matsumoto

16 Feb 2010 16 Feb '10

14:55

Takao Fonts Maintainers, which is mainly made up of the members of Ubuntu Japanese Team, has recently released Takao Fonts, that are community developed derivatives of IPA Fonts (which are default fonts for Japanese in openSUSE distribution ATM). https://launchpad.net/takao-fonts Although IPA Fonts are high quality Japanese outline fonts, they are released under the IPA Font license which allow us to modify and redistribute them on the condition of avoiding to use the word "IPA" for derivatives' name and following some other restrictions. This restriction means that only IPA can modify and release the IPA Fonts and 3rd party communities are prohibited to apply any patch and release them with the name "IPA Font" even if we found bugs on them. Takao Fonts Maintainers aim to avoid this problem by changing the fonts names. I think Takao Fonts can be alternatives to IPA Fonts and have curiously built packages of these fonts on my home project in OBS, using examples from IPAPGothic.spec file in openSUSE:Factory repo. https://build.opensuse.org/package/show?package=takeo-fonts&project=home%3AHeliosReds Since I'm not sure whether I am doing this right or not, I would be thankful if someone will review the spec file that I used for Takao Fonts packages and point out my mistakes when there are some. And, if the fonts work well, I'd propose replacing IPA Fonts with these Takao Fonts in the future release of openSUSE. Best, -- _/_/ Satoru Matsumoto - openSUSE Member - Japan _/_/ _/_/ Marketing/Weekly News/openFATE Screening Team _/_/ _/_/ mail: helios_reds_at_gmx.net / irc: HeliosReds _/_/ _/_/ http://blog.geeko.jp/author/heliosreds _/_/ -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-m17n+help@opensuse.org

Show replies by date

Takashi Iwai

16 Feb 16 Feb

15:55

At Tue, 16 Feb 2010 23:55:23 +0900, Satoru Matsumoto wrote:

...

Takao Fonts Maintainers, which is mainly made up of the members of Ubuntu Japanese Team, has recently released Takao Fonts, that are community developed derivatives of IPA Fonts (which are default fonts for Japanese in openSUSE distribution ATM).

https://launchpad.net/takao-fonts

Although IPA Fonts are high quality Japanese outline fonts, they are released under the IPA Font license which allow us to modify and redistribute them on the condition of avoiding to use the word "IPA" for derivatives' name and following some other restrictions. This restriction means that only IPA can modify and release the IPA Fonts and 3rd party communities are prohibited to apply any patch and release them with the name "IPA Font" even if we found bugs on them.

Takao Fonts Maintainers aim to avoid this problem by changing the fonts names.

I think Takao Fonts can be alternatives to IPA Fonts and have curiously built packages of these fonts on my home project in OBS, using examples from IPAPGothic.spec file in openSUSE:Factory repo. https://build.opensuse.org/package/show?package=takeo-fonts&project=home%3AHeliosReds

The IPA font spec file is a bit outdate. You can clean up the spec file for new packages a bit. Namely, - Recent packages tend to omit "Authors" list in the package description - The conversion of *.txt via dos2unix is unlikely needed for this package - Better to use %{version} to Sources and %setup macro as much as possible Otherwise looks fine to me. Feel free to submit first to M17N repo. Then we can adjust fonts-config to put this as a preferred font, then eventually submit to openSUSE 11.3. There are a few places where IPA fonts are used statically, e.g. in the installation. These can be fixed once after this new font is merged. Thanks! Takashi -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-m17n+help@opensuse.org

Satoru Matsumoto

17 Feb 17 Feb

09:15

Thanks for your advice, Iwai-san. -------- Original Message -------- Subject: Re: [opensuse-m17n] Takao Fonts - community developed derivatives of IPA Fonts - are available. From: Takashi Iwai To: Satoru Matsumoto Date: Wed Feb 17 2010 00:55:21 GMT+0900 (JST)

...

The IPA font spec file is a bit outdate. You can clean up the spec file for new packages a bit. Namely,

- Recent packages tend to omit "Authors" list in the package description

I saw some spec files for reference, but still it isn't clear for me. Is this mean: - I should remove whole "Authors" block from each %description sections of the spec file ? - I should just put the authers names but not URLs ? - I should just put "Takao Fonts Maintainers Team" as Auther ? Best, -- _/_/ Satoru Matsumoto - openSUSE Member - Japan _/_/ _/_/ Marketing/Weekly News/openFATE Screening Team _/_/ _/_/ mail: helios_reds_at_gmx.net / irc: HeliosReds _/_/ _/_/ http://blog.geeko.jp/author/heliosreds _/_/ -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-m17n+help@opensuse.org

Takashi Iwai

09:22

At Wed, 17 Feb 2010 18:15:18 +0900, Satoru Matsumoto wrote:

...

Thanks for your advice, Iwai-san.

-------- Original Message -------- Subject: Re: [opensuse-m17n] Takao Fonts - community developed derivatives of IPA Fonts - are available. From: Takashi Iwai To: Satoru Matsumoto Date: Wed Feb 17 2010 00:55:21 GMT+0900 (JST)

...
The IPA font spec file is a bit outdate. You can clean up the spec file for new packages a bit. Namely,

- Recent packages tend to omit "Authors" list in the package description

I saw some spec files for reference, but still it isn't clear for me. Is this mean:

- I should remove whole "Authors" block from each %description sections of the spec file ?

This one. The authors information is often too outdated and incorrect, so we usually drop it nowadays. In the earlier distros, this block was recorded in PDB (package database) and mandatory. Takashi -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-m17n+help@opensuse.org

Satoru Matsumoto

20 Feb 20 Feb

15:04

-------- Original Message -------- Subject: Re: [opensuse-m17n] Takao Fonts - community developed derivatives of IPA Fonts - are available. From: Takashi Iwai To: Satoru Matsumoto Date: Wed Feb 17 2010 00:55:21 GMT+0900 (JST)

...

The IPA font spec file is a bit outdate. You can clean up the spec file for new packages a bit. Namely,

- Recent packages tend to omit "Authors" list in the package description - The conversion of *.txt via dos2unix is unlikely needed for this package - Better to use %{version} to Sources and %setup macro as much as possible

Otherwise looks fine to me. Feel free to submit first to M17N repo. Then we can adjust fonts-config to put this as a preferred font, then eventually submit to openSUSE 11.3.

There are a few places where IPA fonts are used statically, e.g. in the installation. These can be fixed once after this new font is merged.

I've followed the advices and revised some additional minor problems, including: - Changed the package name to 'takao-fonts' (former name was 'takeo- fonts' due to my typo :-P) - 2009 -> 2010 in Copyright description in spec file - Removed dos2unix from BuildRequires - Added README* and ChangeLog to each %doc sections https://build.opensuse.org/package/show?package=takao-fonts&project=home%3AHeliosReds One more thing I'm not sure is, whether it is OK or not, that I divided the package into 4 RPMs - TakaoGothic, TakaoMincho, TakaoPGothic and TakaoPMincho. That's because I referred to the spec file for IPAPGothic package. If there are no other problems by packaging, can I submit the package directly to M17N repo instead of M17N:Devel repo ? Best, -- _/_/ Satoru Matsumoto - openSUSE Member - Japan _/_/ _/_/ Marketing/Weekly News/openFATE Screening Team _/_/ _/_/ mail: helios_reds_at_gmx.net / irc: HeliosReds _/_/ _/_/ http://blog.geeko.jp/author/heliosreds _/_/ -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-m17n+help@opensuse.org

Takashi Iwai

21 Feb 21 Feb

16:04

At Sun, 21 Feb 2010 00:04:06 +0900, Satoru Matsumoto wrote:

...

-------- Original Message -------- Subject: Re: [opensuse-m17n] Takao Fonts - community developed derivatives of IPA Fonts - are available. From: Takashi Iwai To: Satoru Matsumoto Date: Wed Feb 17 2010 00:55:21 GMT+0900 (JST)

...
The IPA font spec file is a bit outdate. You can clean up the spec file for new packages a bit. Namely,

- Recent packages tend to omit "Authors" list in the package description - The conversion of *.txt via dos2unix is unlikely needed for this package - Better to use %{version} to Sources and %setup macro as much as possible

Otherwise looks fine to me. Feel free to submit first to M17N repo. Then we can adjust fonts-config to put this as a preferred font, then eventually submit to openSUSE 11.3.

There are a few places where IPA fonts are used statically, e.g. in the installation. These can be fixed once after this new font is merged.

I've followed the advices and revised some additional minor problems, including:

- Changed the package name to 'takao-fonts' (former name was 'takeo- fonts' due to my typo :-P) - 2009 -> 2010 in Copyright description in spec file - Removed dos2unix from BuildRequires - Added README* and ChangeLog to each %doc sections

https://build.opensuse.org/package/show?package=takao-fonts&project=home%3AHeliosReds

One more thing I'm not sure is, whether it is OK or not, that I divided the package into 4 RPMs - TakaoGothic, TakaoMincho, TakaoPGothic and TakaoPMincho. That's because I referred to the spec file for IPAPGothic package.

Thanks. This split is fine, especially if this font is supposed to replace IPA fonts. IPA and other fonts are split to each font style in the case you need only one style. For example, in the YaST installation, only IPAPGothic is loaded on the system to save the memory size.

...

If there are no other problems by packaging, can I submit the package directly to M17N repo instead of M17N:Devel repo ?

Yes, please go ahead. Takashi -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-m17n+help@opensuse.org

hitoht＠gmail.com

24 Feb 24 Feb

07:58

Hi, On Sun, 21 Feb 2010 00:04:06 +0900, wrote:

...

...
Otherwise looks fine to me. Feel free to submit first to M17N repo. Then we can adjust fonts-config to put this as a preferred font, then eventually submit to openSUSE 11.3.

Could you please rename *.otf to *.ttf? (This is our{Takao Font's mainteners} todo, but current stuffs are not collected) Because these are *not* real ".otf" (OpenType::Type1). # Yes, this is originator's bug. In this case/IMHO, font developer/maintener must use ".ttf" (extension for OpenType:TTF, and TTF files). Regards, -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-m17n+help@opensuse.org

Takashi Iwai

08:06

At Wed, 24 Feb 2010 16:58:15 +0900, wrote:

...

Hi,

On Sun, 21 Feb 2010 00:04:06 +0900, wrote:

...
...
Otherwise looks fine to me. Feel free to submit first to M17N repo. Then we can adjust fonts-config to put this as a preferred font, then eventually submit to openSUSE 11.3.

Could you please rename *.otf to *.ttf? (This is our{Takao Font's mainteners} todo, but current stuffs are not collected)

Because these are *not* real ".otf" (OpenType::Type1). # Yes, this is originator's bug.

Sounds logical. Matsumoto-san, care to fix this and submit?

...

In this case/IMHO, font developer/maintener must use ".ttf" (extension for OpenType:TTF, and TTF files).

Just wondering, any practical problems using .otf extensions? Or is it just the well-creased character of Japanese? ;-) thanks, Takashi -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-m17n+help@opensuse.org

hitoht＠gmail.com

10:14

On Wed, 24 Feb 2010 09:06:25 +0100, wrote:

...

...
In this case/IMHO, font developer/maintener must use ".ttf" (extension for OpenType:TTF, and TTF files).

...

Just wondering, any practical problems using .otf extensions?

Nothing:) Currently, we use FreeType2(or 1), that evade from this miss-named. In rare situation, we *can* hit problem, such as pathname accessing (e.g. find /usr/share -name '*ttf') . So, this rename is aesthetics problem ;) Regards, -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-m17n+help@opensuse.org

Satoru Matsumoto

25 Feb 25 Feb

02:35

Thank you for your suggestion, hito. Renaming *.otf to *.ttf is not difficult. However, the problem is, how I should deal with README* files included in the source package and the name of the source tar ball. In README, there's a mention of:

...

Available Fonts --------------- Font Name File Name based on =============--================--================ TakaoGothic TakaoGothic.otf IPAGothic Takao PGothic TakaoPGothic.otf IPA PGothic TakaoMincho TakaoMincho.otf IPAMincho Takao PMincho TakaoPMincho.otf IPA PMincho

...and the credit:

...

Takao Fonts 003.01.20100214.1 (c) 2010 Takao Fonts Maintainers Team

As I'm not a part of the Takao Fonts Maintainers Team (not yet, at least :-P), can I modify the README* files by myself? And ATM, the name of the source tar ball is takao-fonts-otf-003.01.20100214.1.tar.gz. If I rename *.otf to *.ttf, should I also rename the source tar ball to "takao-fonts-ttf-003.01.20100214.1.tar.gz"? Any good solutions? Or, considering that there is no practical problem by using .otf extensions (at least) on openSUSE, and if the source package will be updated by Takao Fonts Maintainers Team and this issue will be fixed soon, should I wait and update the package for openSUSE afterward? Best, -- _/_/ Satoru Matsumoto - openSUSE Member - Japan _/_/ _/_/ Marketing/Weekly News/openFATE Screening Team _/_/ _/_/ mail: helios_reds_at_gmx.net / irc: HeliosReds _/_/ _/_/ http://blog.geeko.jp/author/heliosreds _/_/ -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-m17n+help@opensuse.org

Takashi Iwai

07:44

At Thu, 25 Feb 2010 11:35:47 +0900, Satoru Matsumoto wrote:

...

Thank you for your suggestion, hito.

Renaming *.otf to *.ttf is not difficult. However, the problem is, how I should deal with README* files included in the source package and the name of the source tar ball.

You can add README.SUSE or such to mention about the changes.

...

In README, there's a mention of:

...
Available Fonts --------------- Font Name File Name based on =============--================--================ TakaoGothic TakaoGothic.otf IPAGothic Takao PGothic TakaoPGothic.otf IPA PGothic TakaoMincho TakaoMincho.otf IPAMincho Takao PMincho TakaoPMincho.otf IPA PMincho

...and the credit:

...
Takao Fonts 003.01.20100214.1 (c) 2010 Takao Fonts Maintainers Team

As I'm not a part of the Takao Fonts Maintainers Team (not yet, at least :-P), can I modify the README* files by myself?

And ATM, the name of the source tar ball is takao-fonts-otf-003.01.20100214.1.tar.gz. If I rename *.otf to *.ttf, should I also rename the source tar ball to "takao-fonts-ttf-003.01.20100214.1.tar.gz"?

Any good solutions?

Don't rename tarball unless needed. BTW, in general bz2 is preferred (as you are warned by the check script during build). (Don't ask me why it's no .xz :) thanks, Takashi -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-m17n+help@opensuse.org

Stefan Müller

16 Feb 16 Feb

16:23

New subject: [opensuse-m17n] Persian fonts with Mandarin Chinese and Hindi

Hi, We are doing multilingual graamr engenering here and I have a font problem. Currently I use MULE unicode together with GNU Emacs 22.3.1 (x86_64-suse-linux-gnu, X toolkit, Xaw3d scroll bars) of 2008-11-23 on build12. (when t (load "mucs") (setq default-input-method "chinese-py") (set-default-coding-systems 'utf-8)) ;; to get the Hindi composition of characters right `so' (when t (load "un-define") (push '(indian-is13194 . in-is13194-devanagari-post-read-conversion) un-define-post-read-conversion-charsets-alist)) (when t ; changes the default preference for Chinese instead of Japanese to get ni1 right. (un-define-change-charset-order '(ascii latin-iso8859-1 latin-iso8859-2 latin-iso8859-3 latin-iso8859-4 cyrillic-iso8859-5 greek-iso8859-7 hebrew-iso8859-8 latin-iso8859-9 latin-iso8859-14 latin-iso8859-15 ipa indian-is13194 chinese-gb2312 japanese-jisx0208 japanese-jisx0212 chinese-cns11643-1 chinese-cns11643-2 chinese-cns11643-3 chinese-cns11643-4 chinese-cns11643-5 chinese-cns11643-6 chinese-cns11643-7 chinese-big5-1 chinese-big5-2 korean-ksc5601 latin-jisx0201 katakana-jisx0201 thai-tis620 ethiopic chinese-sisheng lao vietnamese-viscii-lower vietnamese-viscii-upper mule-unicode-0100-24ff mule-unicode-2500-33ff mule-unicode-e000-ffff mule-ucs-unicode-multichar)) ) The following I got from a web page on emacs-bidi: ;; Arabic & Persian ;; (set-fontset-font "fontset-default" ;; (cons (decode-char 'ucs #x05b0) (decode-char 'ucs #x06ff)) "-m17n-*--20-*-iso10646-1") ;; (set-fontset-font "fontset-default" ;; (cons (decode-char 'ucs #xfb2a) (decode-char 'ucs #xfbff)) "-m17n-*--20-*-iso10646-1") ;; (set-fontset-font "fontset-default" ;; (cons (decode-char 'ucs #xfe70) (decode-char 'ucs #xfefc)) "-m17n-*--20-*-iso10646-1") ;; (set-fontset-font "fontset-default" ;; (cons (decode-char 'ucs #x200c) (decode-char 'ucs #x200f)) "-m17n-*--20-*-iso10646-1") It works in isolation, but not with the other specifications above. What I need is something that displays the fonts correctly and does the character composition. emacs bidi does that, but I do not need all the functionality. The character composition together with standard left to right display would be sufficient and even preferred for me. Is there something that gets this with standard emacs? The character composition should be there when I load the file, without having to do any command. Thank you very much! Best wishes Stefan -- Stefan Müller Tel: (+49) (+30) 838 52973 Fax: (+49) (030) 838 4 52973 Institut für Deutsche und Niederländische Philologie Deutsche Grammatik Habelschwerdter Allee 45 14 195 Berlin http://hpsg.fu-berlin.de/~stefan/ http://hpsg.fu-berlin.de/~stefan/Babel/Interaktiv/ -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-m17n+help@opensuse.org

5178

Age (days ago)

5187

Last active (days ago)

List overview

Download

11 comments

4 participants

participants (4)

hitoht＠gmail.com
Satoru Matsumoto
Stefan Müller
Takashi Iwai

[opensuse-m17n] Takao Fonts - community developed derivatives of IPA Fonts - are available.

tags

participants (4)