If you are commenting out lines in font.properties and getting a different font than you would usually get, I'd imagine you are commenting out too many lines.
If you don't want to modify font.properties, require that the fonts being complained about are installed on the machine running the Java application. ----- Original Message ----- From: "Vella, John" <[EMAIL PROTECTED]> To: "Advanced-Swing (E-mail)" <[EMAIL PROTECTED]> Sent: Monday, April 29, 2002 4:38 AM Subject: FW: PLEASE HELP: Need best technique to avoid "missing font" warnings > Is there anyone on this list that can help with this? > > -----Original Message----- > From: Vella, John > Sent: Friday, April 26, 2002 4:46 PM > To: [EMAIL PROTECTED] > Subject: PLEASE HELP: Need best technique to avoid "missing font" > warnings > > > My 1.3.1_02 product will be shipping soon and I'm faced with figuring out the best way to avoid those darned "missing font" warnings that usually happen when executing on Solaris and remote displaying(especially when using a PC X server). > > Does anyone know a fairly "rock solid" technique to work around this? Just commenting out the offending line in the font.properties file doesn't help because the font that ends up getting used turns out to be REALLY large(at least it does on my eXceed PC X server). I would even be willing to modify our JRE's rt.jar file to include a "patched" class file that suppresses the warning(although I don't which .class file the warning is coming from). > > Thanks for any help you guys can provide, > > John > _______________________________________________ > Swing mailing list > [EMAIL PROTECTED] > http://eos.dk/mailman/listinfo/swing > _______________________________________________ > Advanced-swing mailing list > [EMAIL PROTECTED] > http://eos.dk/mailman/listinfo/advanced-swing > _______________________________________________ Advanced-swing mailing list [EMAIL PROTECTED] http://eos.dk/mailman/listinfo/advanced-swing
