Re: Blackdown JDK vs Sun/Inprise
On Mon, Dec 20, 1999 at 05:55:52PM -0800, noisebrain wrote: > > Aren't we forgetting something in this discussion? > > Average PC has 64M, you want to write an application that runs > on this PC, your dev environment (JBuilder or whatever) > has, in addition to the application, a compiler, the IDE, a debugger... > > ...your development environment is probably going to need more than 64m. > This would be as true of a C/C++ ide. True, in general a developement machine is bigger and faster than the one required for the application developed. Just ask John Carmak if he uses a 64Mb PC to write Quake III. I don't think so :) -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
segmentation violation when invoking JVM
Hi,
I'm using the code below to invoke the JVM. The code compiles and links Ok. When I
try to run the code, the CallStaticVoidMethod(cls,mid) returns an error (segmentation
violation).
I'm using JDK1.1.7 version 3 and Linux 6.1 (SUSE).
Does anybody know what causes this error ???
Thanks !!
E-Mail : [EMAIL PROTECTED]
#include
#include
JavaVM *jvm;
JNIEnv *env;
JDK1_1InitArgs vm_args;
void main(int argc, char **argv)
{
printf("Creating the Java VM\n");
JNI_GetDefaultJavaVMInitArgs(&vm_args);
vm_args.classpath="/usr/jdk117_v3/lib/classes.zip:/home/test";
JNI_CreateJavaVM(&jvm, &env, &vm_args);
jclass cls = env->FindClass("Main");
jmethodID mid = env->GetStaticMethodID(cls, "main", "()V");
env->CallStaticVoidMethod(cls, mid);
if (env->ExceptionOccurred() != NULL) env->ExceptionDescribe();
jvm->DestroyJavaVM();
}
public class Main
{
public static void main(String[] args)
{
System.out.println("Running Java ...");
}
}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
can't be instantiated.
Hello, When I run swing/applet program on browser, it show "can't be instantiated". But when I run on appletviewer, it works fine. Why is the cause? How can I run this app on browser as well? Regards, Penn.
SRC for COLIN PLUMBS package
[jdk1.2 pre v2 LINUX] Hi, We are into indepth analysis of cryptix.org and java.security. following the code we landed at BigInteger.java where there is a reference to the native code [ plumbGeneratePrime ] which was found in ./jre/lib/i386/libmath.so. This is Colin Plumbs big +ve integer package. java is open source and we are required to give source to depth of ocean bed for our security application. can i get the source file for libmath.so ? or can any one shed more light on this. -- __ | S.Suresh | SoftWare Engineer | Technology Communication Systems ( I ) Pvt Ltd | Usha Bhavan, A-41, MCIE, Delhi Mathura Road, | New Delhi 110 044 |_I N D I A___ | Tel (91) 11 -6959 200, 6959 300, 6959 194 | Fax (91) 11- 6959 090 |_ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: segmentation violation when invoking JVM
>
> jclass cls = env->FindClass("Main");
> jmethodID mid = env->GetStaticMethodID(cls, "main", "()V");
>
I'm no expert, but your problem appears to be right
above. You are trying to locate a main method that
takes no args, but your main method in your java program
takes an array of strings as args. Try removing the
String[] args from your java method.
In any case, you probably want to check that you
actually found the method you were looking for.
ie :
if ( mid == 0 ) {
fprintf(stderr, "unable to locate method");
exit(1);
}
ditto for FindClass.
One other thing. In the demo code for the java
tutorial at javasoft, they have the following
two lines of code at the beginning:
/* IMPORTANT: specify vm_args version # if you use JDK1.1.2 and beyond
*/
vm_args.version = 0x00010001;
Since you are using 1.1.7, and they claim it's important,
you might want to add the above in before you do anything.
later
jp
>
> public class Main
> {
> public static void main(String[] args)
> {
> System.out.println("Running Java ...");
> }
> }
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
I wasn't able to run the Blackdown JDK 1.2.2 (or at least the JRE) with glibc 2.1.1, but installing glibc 2.1.2 did the trick. Still having annoying font problems, though... John André Dahlqvist wrote: > > Hi > > I noted in Blackdowns README file that glibc 2.1.2 is required, and read > in Sun's README file that glic 2.1 is required for their version. Does > anyone know if they mean that any 2.1.x version works? > > // André -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
problems with JNI
I use RedHat 6.1 and JDK1.2.2 RC1
I have 2 kind of problemes with the JNI.
First I get an exception with the following code.
Exception in thread "main" java.lang.UnsatisfiedLinkError: Hello
at Native.main(Native.java:14)
// Here is Native.java
public class Native {
static {
System.loadLibrary("Native");
}
public Native() {
}
public native void Hello();
public static void main(String [] args) {
Native n = new Native();
n.Afficher();
}
}
// Here is Native.c
#include
#include
JNIEXPORT
void
JNICALL
Java_Native_Hello (JNIEnv * env, jobject object)
{
cout << "Hello World !" << endl;
}
Second, I get a segmentation fault on the JNI_CreateJavaVM call of the
following code.
Am i missing something ?
// Here is Invoke.cpp
#include
#include
#include
int main(int argc, char **argv)
{
JavaVM * jvm;
JNIEnv * env;
JavaVMInitArgs vm_args;
JNI_GetDefaultJavaVMInitArgs ( &vm_args );
jint res = JNI_CreateJavaVM(&jvm, (void **)&env, &vm_args);
if (res < 0)
{
cerr << "Can't start JavaVM" << endl;
exit(1);
}
cout << "Java VM Started" << endl;
jvm->DestroyJavaVM();
}
Pierre
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: can't be instantiated.
Hi, if you mean something like "system event queue can't be instantiated", it's due to security restrictions, but doesn't hurt most Swing applications. Matthias > Siriphen Wikaisuksakul wrote: > > Hello, > > When I run swing/applet program on browser, it show "can't be > instantiated". > But when I run on appletviewer, it works fine. > Why is the cause? How can I run this app on browser as well? > > Regards, > Penn. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
On Tue, Dec 21, 1999 at 12:31:17AM +0100, André Dahlqvist wrote: > I noted in Blackdowns README file that glibc 2.1.2 is required, and read > in Sun's README file that glic 2.1 is required for their version. Does > anyone know if they mean that any 2.1.x version works? The Sun/Inprise JKD has been tested with glibc 2.1.1. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems with JNI
Pierre HÊroux wrote: > I use RedHat 6.1 and JDK1.2.2 RC1 > I have 2 kind of problemes with the JNI. > > First I get an exception with the following code. > Exception in thread "main" java.lang.UnsatisfiedLinkError: Hello > at Native.main(Native.java:14) I had the same error on my RedHat 6.1 jdk 1.1.7 v3 You should set LD_LIBRARY_PATH variable matching the path to your library (lib***.so file). E.g.: export LD_LIBRARY_PATH=/my/program > Second, I get a segmentation fault on the JNI_CreateJavaVM call of the > following code. > You should try to compile library with -shared option. After that all worked on my system. If not there are some other ways, described in the conference archive. Try to search it for SIGSEGV. -- Regards, Anthony G. Starovojtov, System Administrator of IMS Department, Kharkov State Technical University of Radioelectronics, pr. Lenina,14, room 254, Kharkov, 61726, Ukraine Phone +380 572 409451 (Work), +380 572 648863 (Home) E-mail: [EMAIL PROTECTED], [EMAIL PROTECTED] ICQ: 32572820; Yahoo Messenger ID: starovojtov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SRC for COLIN PLUMBS package
Hi, well, Java isn't open source (see the recent story around blackdown). But the Sun Community Source License (SCSL) at least allows you to look at the code, including the native one. You can download it from Sun's web pages (25 MB); follow the links on Community Program or something like that. By the way, I noticed that in 1.3beta the BigInteger class no longer uses native methods. Instead, all seams to be implemented in java. For your convenience, I'll send you the native code of interest in a private mail. Matthias Suresh wrote: > > [jdk1.2 pre v2 LINUX] > > Hi, > We are into indepth analysis of cryptix.org and java.security. > following the code we landed at > BigInteger.java where there is a reference to the native code [ > plumbGeneratePrime ] which was found in ./jre/lib/i386/libmath.so. > > This is Colin Plumbs big +ve integer package. > > java is open source and we are required to give source to depth of ocean > bed for our security application. > > can i get the source file for libmath.so ? or can any one shed > more light on this. > > -- > __ > | S.Suresh > | SoftWare Engineer > | Technology Communication Systems ( I ) Pvt Ltd > | Usha Bhavan, A-41, MCIE, Delhi Mathura Road, > | New Delhi 110 044 > |_I N D I A___ > | Tel (91) 11 -6959 200, 6959 300, 6959 194 > | Fax (91) 11- 6959 090 > |_ > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
John Hartman wrote: > > I wasn't able to run the Blackdown JDK 1.2.2 (or at least the JRE) with > glibc 2.1.1, but installing glibc 2.1.2 did the trick. Still having > annoying font problems, though... > > John > > André Dahlqvist wrote: > > > > Hi > > > > I noted in Blackdowns README file that glibc 2.1.2 is required, and read > > in Sun's README file that glic 2.1 is required for their version. Does > > anyone know if they mean that any 2.1.x version works? > > > > // André > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] I spent about a day trying to solve font problems with Blackdown JDK 1.2.2 RC3. I improved the overall font situation with my RH6.0 system, but could not get rid of the many warning messages about zapf fonts. This problem vanished when I switched to Inprise JDK 1.2.2 RC1. Alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
On Tue, Dec 21, 1999 at 08:51:03AM -0800, Paolo Ciccone wrote: > The Sun/Inprise JKD has been tested with glibc 2.1.1. Does anybody know whether it is possible to install the glibc 2.1.2 as a secondary libc (having glibc 2.0.7 as primary libc)? I´d like to do this in order to use JBuilder together with the JDK 1.2.2. TIA. bye, Thomas > > -- > Paolo Ciccone > JBuilder dev.team -- If there are two or more ways to do something, and one of those ways can result in a catastrophe, then someone will do it. (Murphy's Law) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
> Alan Westhagen writes: Alan> I spent about a day trying to solve font problems with Alan> Blackdown JDK 1.2.2 RC3. I improved the overall font Alan> situation with my RH6.0 system, but could not get rid of the Alan> many warning messages about zapf fonts. This problem Alan> vanished when I switched to Inprise JDK 1.2.2 RC1. No big surprise, they've commented out the relevant entries in the font.properties file. I'll do the same for the next Blackdown release as people think that it is a bug, but it isn't. Try to display dingbats characters (0x2701 - 0x27be) on an AWT component with the Inprise JDK, you'll get no warnings but the component only will show question marks: ''. The warnings from the Blackdown JDK just tell you immediately that something might not work correctly. Juergen -- Juergen Kreileder, Blackdown Java-Linux Team http://www.blackdown.org/java-linux.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
On Tue, Dec 21, 1999 at 11:22:03PM +0100, Juergen Kreileder wrote: > No big surprise, they've commented out the relevant entries in the > font.properties file. I'll do the same for the next Blackdown release > as people think that it is a bug, but it isn't. > > Try to display dingbats characters (0x2701 - 0x27be) on an AWT > component with the Inprise JDK, you'll get no warnings but the > component only will show question marks: ''. The warnings from > the Blackdown JDK just tell you immediately that something might not > work correctly. Does anybody know if installing the URW fonts fixes the problem ? If yes, than it could be a requirement for the JDk and it just could be mentioned in the README. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
> Paolo Ciccone writes: Paolo> On Tue, Dec 21, 1999 at 11:22:03PM +0100, Juergen Kreileder wrote: >> No big surprise, they've commented out the relevant entries in >> the font.properties file. I'll do the same for the next >> Blackdown release as people think that it is a bug, but it >> isn't. >> >> Try to display dingbats characters (0x2701 - 0x27be) on an AWT >> component with the Inprise JDK, you'll get no warnings but the >> component only will show question marks: ''. The warnings >> from the Blackdown JDK just tells you immediately that >> something might not work correctly. Paolo> Does anybody know if installing the URW fonts fixes the Paolo> problem ? Yes, but you have to restore the original '.1' entries in font.properties too. Juergen -- Juergen Kreileder, Blackdown Java-Linux Team http://www.blackdown.org/java-linux.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
jni + rmi = NoClassDefFoundError + consternation
I eventually found a "solution" to this problem. I never could get it to work under linux jdk1.1.7, however, when I upgraded java to 1.1.8 ( and to glibc2.1.2 ) the NoClassDefFoundError problem went away. Thanks to all who had suggestions. regards jp Jean-Pierre Fournier wrote: > > Hi, > > linux 2.0.38 > java 1.1.7B > > I am trying to get a handle to a remote > object from C. In my C program, I create > a VM, find the class I want, find the method > and then call CallStaticIntMethod(). It > appears that Naming.lookup() is the cause > of my NoClassDefFoundError, since if I > comment this line out in the java code > things seem to work. > > Digging around on the JDC the only similar > problem I found involved applets in browsers. > In this case the conclusion was that the > browser didn't support rmi. > > Does anyone know of any limitations on VMs > created via JNI_CreateJavaVM()? > > I will append some code below, in case I am > doing something obviously wrong. > > thanks, > > jp > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
Paolo Ciccone wrote: > > On Tue, Dec 21, 1999 at 11:22:03PM +0100, Juergen Kreileder wrote: > > No big surprise, they've commented out the relevant entries in the > > font.properties file. I'll do the same for the next Blackdown release > > as people think that it is a bug, but it isn't. > > > > Try to display dingbats characters (0x2701 - 0x27be) on an AWT > > component with the Inprise JDK, you'll get no warnings but the > > component only will show question marks: ''. The warnings from > > the Blackdown JDK just tell you immediately that something might not > > work correctly. > > Does anybody know if installing the URW fonts fixes the problem ? If yes, > than it could be a requirement for the JDk and it just could be mentioned in > the README. Yes, if the font.properties file is changed accordingly and the fonts are made available in one of two possible ways: 1) Added to the X server's font path. 2) Added to the AWT's font path with the JAVA_FONTS environment variable. The advantage of the latter approach is that font rendering is performed by the AWT instead of X, and the Graphics2D manipulations work. If you use JAVA_FONTS, you need to specify a path containing all directories from with the AWT gets scalable fonts, including the directory containing the default fonts shipped with the JDK. Nathan > -- > Paolo Ciccone > JBuilder dev.team > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
> Nathan Meyers writes: Nathan> Paolo Ciccone wrote: >> >> On Tue, Dec 21, 1999 at 11:22:03PM +0100, Juergen Kreileder wrote: >> > No big surprise, they've commented out the relevant entries in the >> > font.properties file. I'll do the same for the next Blackdown release >> > as people think that it is a bug, but it isn't. >> > >> > Try to display dingbats characters (0x2701 - 0x27be) on an AWT >> > component with the Inprise JDK, you'll get no warnings but the >> > component only will show question marks: ''. The warnings from >> > the Blackdown JDK just tell you immediately that something might not >> > work correctly. >> >> Does anybody know if installing the URW fonts fixes the problem >> ? If yes, than it could be a requirement for the JDk and it >> just could be mentioned in the README. Nathan> Yes, if the font.properties file is changed accordingly Nathan> and the fonts are made available in one of two possible Nathan> ways: Nathan> 1) Added to the X server's font path. Nathan> 2) Added to the AWT's font path with the JAVA_FONTS environment Nathan> variable. Nathan> The advantage of the latter approach is that font Nathan> rendering is performed by the AWT instead of X, and the RC3 should do that in case 1 too. Nathan> Graphics2D manipulations work. If you use JAVA_FONTS, you Nathan> need to specify a path containing all directories from Nathan> with the AWT gets scalable fonts, including the directory Nathan> containing the default fonts shipped with the JDK. Juergen -- Juergen Kreileder, Blackdown Java-Linux Team http://www.blackdown.org/java-linux.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
On Wed, Dec 22, 1999 at 01:57:01AM +0100, Juergen Kreileder wrote: > Paolo> Does anybody know if installing the URW fonts fixes the > Paolo> problem ? > > Yes, but you have to restore the original '.1' entries in > font.properties too. I believe this is the best solution. Any reason for not doing it ? I mean, the URW fonts are free and come bundled with several distros, I think it would be reasonable to list it as a requirement. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
Juergen Kreileder wrote: > > > Nathan Meyers writes: > > Nathan> Paolo Ciccone wrote: > >> > >> On Tue, Dec 21, 1999 at 11:22:03PM +0100, Juergen Kreileder wrote: > >> > No big surprise, they've commented out the relevant entries in the > >> > font.properties file. I'll do the same for the next Blackdown release > >> > as people think that it is a bug, but it isn't. > >> > > >> > Try to display dingbats characters (0x2701 - 0x27be) on an AWT > >> > component with the Inprise JDK, you'll get no warnings but the > >> > component only will show question marks: ''. The warnings from > >> > the Blackdown JDK just tell you immediately that something might not > >> > work correctly. > >> > >> Does anybody know if installing the URW fonts fixes the problem > >> ? If yes, than it could be a requirement for the JDk and it > >> just could be mentioned in the README. > > Nathan> Yes, if the font.properties file is changed accordingly > Nathan> and the fonts are made available in one of two possible > Nathan> ways: > > Nathan> 1) Added to the X server's font path. > > Nathan> 2) Added to the AWT's font path with the JAVA_FONTS environment > Nathan> variable. > > Nathan> The advantage of the latter approach is that font > Nathan> rendering is performed by the AWT instead of X, and the > > RC3 should do that in case 1 too. > > Nathan> Graphics2D manipulations work. If you use JAVA_FONTS, you > Nathan> need to specify a path containing all directories from > Nathan> with the AWT gets scalable fonts, including the directory > Nathan> containing the default fonts shipped with the JDK. > > Juergen > > -- > Juergen Kreileder, Blackdown Java-Linux Team > http://www.blackdown.org/java-linux.html > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] I tried to get this to work with blackdown jdk1.2.2-RC3. I already had URW fonts. Some of the documentation seemed to point towards installing Microsoft truetype fonts, as well. Since I am running RH6.0, which has the xfs font server, I did that. I edited the config file for xfs so that it contains the path of the URW fonts and the truetype fonts, as well as all of the usual fonts in the XF86 configuration. The repetitive warnings about missing dingbat fonts did not, unfortunately, go away. I would bet that a lot of the developers using linux/jdk are running RH6.x. It would be very useful if someone who really understands this font problem could document a solution to this problem, which does not involve removing dingbat fonts, or any other fonts for that matter, from availability. It seems that commenting entries out of font.properties will at some point cause cross-platform incompatibilities. -- Alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
Juergen Kreileder wrote: > > No big surprise, they've commented out the relevant entries in the > font.properties file. I'll do the same for the next Blackdown release > as people think that it is a bug, but it isn't. > Exactly, it just means that a font package isn't installed on the host system. I seem to remember seeing something some time back about the specific font package to install, but I don't remember what it was... > Try to display dingbats characters (0x2701 - 0x27be) on an AWT > component with the Inprise JDK, you'll get no warnings but the > component only will show question marks: ''. The warnings from > the Blackdown JDK just tell you immediately that something might not > work correctly. > This is, in my opinion, the correct way to handle it - let the user know right away that something may not work right instead of making them guess. -- Jeff Galyan http://www.anamorphic.com http://www.sun.com jeffrey dot galyan at sun dot com talisman at anamorphic dot com Sun Certified Java(TM) Programmer == Linus Torvalds on Microsoft and software development: "... if it's a hobby for me and a job for you, why are you doing such a shoddy job of it?" The views expressed herein do not necessarily reflect those of my employer. Sun Microsystems, Inc., has no connection to my involvement with the Mozilla Organization. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
Juergen Kreileder wrote: > > > Nathan Meyers writes: > > Nathan> Paolo Ciccone wrote: > >> > >> On Tue, Dec 21, 1999 at 11:22:03PM +0100, Juergen Kreileder wrote: > >> > No big surprise, they've commented out the relevant entries in the > >> > font.properties file. I'll do the same for the next Blackdown release > >> > as people think that it is a bug, but it isn't. > >> > > >> > Try to display dingbats characters (0x2701 - 0x27be) on an AWT > >> > component with the Inprise JDK, you'll get no warnings but the > >> > component only will show question marks: ''. The warnings from > >> > the Blackdown JDK just tell you immediately that something might not > >> > work correctly. > >> > >> Does anybody know if installing the URW fonts fixes the problem > >> ? If yes, than it could be a requirement for the JDk and it > >> just could be mentioned in the README. > > Nathan> Yes, if the font.properties file is changed accordingly > Nathan> and the fonts are made available in one of two possible > Nathan> ways: > > Nathan> 1) Added to the X server's font path. > > Nathan> 2) Added to the AWT's font path with the JAVA_FONTS environment > Nathan> variable. > > Nathan> The advantage of the latter approach is that font > Nathan> rendering is performed by the AWT instead of X, and the > > RC3 should do that in case 1 too. Partially. The AWT does the best job it can with fonts rasterized by the X server, but it is stuck doing that job with bitonal bitmaps. When it can get to the scalable font files directly (case 2), it can do a much better job. Some Graphics2D capabilities, such as anti-aliased font rendering, are not available in case 1. I don't see anything different in RC3 w.r.t. those behaviors, but I've only tried a few tests. Has something about font rendering changed? Nathan > > Nathan> Graphics2D manipulations work. If you use JAVA_FONTS, you > Nathan> need to specify a path containing all directories from > Nathan> with the AWT gets scalable fonts, including the directory > Nathan> containing the default fonts shipped with the JDK. > > Juergen > > -- > Juergen Kreileder, Blackdown Java-Linux Team > http://www.blackdown.org/java-linux.html > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
