From owner-freebsd-java@FreeBSD.ORG Fri Feb 27 18:02:05 2009 Return-Path: Delivered-To: java@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 3734410656C5; Fri, 27 Feb 2009 18:02:05 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-java@freebsd.org Date: Fri, 27 Feb 2009 13:01:31 -0500 User-Agent: KMail/1.6.2 References: <49A77F4A.2080508@ongs.co.jp> <200902271159.15176.jkim@FreeBSD.org> In-Reply-To: <200902271159.15176.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200902271301.57014.jkim@FreeBSD.org> Cc: NAKATA Maho , Daichi GOTO , java@freebsd.org, glewis@freebsd.org, SAITOU Toshihide , =?utf-8?q?=E8=91=89=E4=BD=B3=E5=A8=81_Jiawei_Ye?= Subject: Re: Japanese font conf for JDK16 to use IPA font X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2009 18:02:06 -0000 On Friday 27 February 2009 11:59 am, Jung-uk Kim wrote: > On Friday 27 February 2009 12:51 am, Daichi GOTO wrote: > > Hi greg :) > > > > How about to deploy or integrate included fontconfig.properties > > file to /usr/local/jdk1.6.0/jre/lib/fontconfig.properties or > > /usr/local/jdk1.6.0/jre/lib/fontconfig.properties.src. > > > > I have known some Japanese java developers have been giving up to > > use FreeBSD and Java as their default development environment > > because FreeBSD JDK16 default configurations lacks of proper > > Japanese font setting. > > > > Right now, IPA font(japanese/ipa-ttfonts) is proper high quality > > font as Japanese font. To enable that font as default font makes > > a lot of sense. > > > > I have checked included one with JDK16 and OpenJDK6, that looks > > like working well. > > I have been using the attached properties for korean fonts for many > years, which uses korean/unfonts-ttf. Baekmuk fonts in your > properties are unmaintained and obsolete. Un-series fonts are de > facto standard for korean FOSS projects these days. One of the > reasons is it works pretty well with Freetype2. I believe many > FOSS projects still use Baekmuk because Redhat does. :-( > > https://bugzilla.redhat.com/show_bug.cgi?id=112877 It is little OT but I found Fedora project approved Un-series fonts as the next default korean fonts: http://fedoraproject.org/wiki/UN_fonts "Fontconfig has been changed upstream to use UN as default Korean font set instead of Baekmuk (current Fedora Korean font)." Yeah! Jung-uk Kim