Path: csiph.com!usenet.pasdenom.info!news.albasani.net!newsfeed.freenet.ag!news2.euro.net!xlned.com!feeder1.xlned.com!193.166.3.22.MISMATCH!newsfeed3.funet.fi!newsfeeds.funet.fi!feeder2.news.elisa.fi!fi.sn.net!newsfeed2.tdcnet.fi!news.song.fi!not-for-mail From: Jukka Lahtinen Newsgroups: comp.lang.java.programmer Subject: Re: need help with javadocs Organization: none References: X-no-archive: yes Content-Type: text/plain;charset="iso-8859-1";format=flowed Content-Transfer-Encoding: 8bit Date: Sun, 29 Apr 2012 12:00:14 +0300 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) Cancel-Lock: sha1:CLElaSkZWgqa4cF3+m3KRtWh3xI= MIME-Version: 1.0 Lines: 12 NNTP-Posting-Host: 81.17.207.67 X-Trace: 1335690013 news.tdc.fi 2764 81.17.207.67:49578 X-Complaints-To: abuse@tdcnet.fi Xref: csiph.com comp.lang.java.programmer:14014 Lew writes: > If you want to play with physical fonts you'll need some means of what's > called "discovery" - a way for the software to read the system or some > configuration to find out what's there. ..and when you (the OP) read the javadoc documentation of the constructor Font(String, int, int) you should find there a "See also" link that tells you how to do that. -- Jukka Lahtinen