At Tue, 07 Jul 2009 23:16:37 +0900, Satoru Matsumoto wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Takashi Iwai wrote:
At Thu, 02 Jul 2009 18:55:54 +0800, Yu Feng wrote:
On Thu, 2009-07-02 at 12:18 +0200, Takashi Iwai wrote:
At Thu, 02 Jul 2009 18:14:47 +0800, Yu Feng wrote:
Thank you.
The package is built on api.suse.de: home:rainwoodman:ttf-wqy-zenhei
It is the snapshot in May. Not difficult to revert to the latest stable release though.
@Takashi: what shall I do next?
First off, create your package on OBS, not IBS. Then submit it to M17N repo via osc submitreq.
Submitted as request 13455.
Thanks, the request is accepted. For further development, please work on a branched package. That is,
% osc branch M17N:Devel/ttf-wqy-zenhei
change there, then simply run "osc sr", which will point to M17N:Devel automatically.
The packaging looks almost OK. But, create *.changes file for change logs. In SUSE Packages, the changes log are separately kept. Use "osc vc" to edit the changelog.
Also, it'd be nice to follow the beginning of spec file like others with SUSE comments. It'd be anyway overwritten once when it's on FACTORY, though.
I curiously installed ttf-wqy-zenhei and I've come to notice that default font setting for monospace has been changed to wqy-zenhei in my KDE 4.2 / Japanese desktop.
Although most of the chinese characters (Kanji) in wqy-zenhei are suitable for Japanese, some characters are weird for Japanese. Example: 編
The original font setting shouldn't be overwritten by installing wqy-zenhei, at least in Japanese environment.
Right. The problem is likely that the font config files included in wqy-zenhei override the SUSE default definitions of serif, sans-serif and monospace (found in /etc/fonts/suse-post-user.conf). This should be fixed. However, another underlying problem is that we have no way to generate the preferred font list dynamically. And, the list would depend likely on the language you use since some glyphs look different, as Matsumoto-san pointed in the above. If there is any $LANG or locale specific expression in font config files, it can be fixed with such a style. If not, it's not so trivial... thanks, Takashi -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-m17n+help@opensuse.org