Applications: Browsers' Related Problems

Ben Rosenberg

You can use TTF's in Netscape 6.x/7.x, but not in 4.x as far as I know. You will have to edit /opt/browser/defaults/prefs/unix.js and specify the freetype lib and the directory of your TTF's. Then you restart Netscape or Mozilla..and they will use them. :)

This is what the section of my unix.js looks like. After you tell it what to use and where the freetype lib is ..you should have full access to your TTF's.

      ######
// TrueType
pref("font.FreeType2.enable", true);
pref("font.freetype2.shared-library", "libfreetype.so.6");
// if libfreetype was built without hinting compiled in
// it is best to leave hinting off
pref("font.FreeType2.autohinted", false);
pref("font.FreeType2.unhinted", true);
// below a certian pixel size anti-aliased fonts produce poor results
pref("font.antialias.min",        10);
pref("font.embedded_bitmaps.max", 1000000);
pref("font.scale.tt_bitmap.dark_text.min", 64);
pref("font.scale.tt_bitmap.dark_text.gain", "0.8");
// sample prefs for TrueType font dirs
//pref("font.directory.truetype.1", "/u/sam/tt_font");
//pref("font.directory.truetype.2", "/u/sam/tt_font2");
//pref("font.directory.truetype.3", "/u/sam/tt_font3");
pref("font.directory.truetype.1", "/usr/X11R6/lib/X11/fonts/truetype");
######
      

File->Print-> Properties Now change the print command.

Unfortunately mozilla-1.1 forgets its print configuration, so you have to adopt it each time you start Mozilla.

What happens is Mozilla saves the preferences it started up with. So what you need to do is close mozilla down, then go into

/mozilla/default/pref/unix.js
      

and add something like this to the entries:

pref("print.print_command", "lpr ${MOZ_PRINTER_NAME:+'-P'}${MOZ_PRINTER_NAME}"); 
pref("print.printer_list", "lp lp1 lp2 lp3 lp4 lp5 lp6 lp7"); // list of printers, seperarated by spaces
      

Then the next time you start mozilla you will get a list of printers. You leave the postscript part in there, because the postscript output will get sent to the ghostscript filter for each printer listed.

Ben Rosenberg

In 8.1 the Java plugin Mozilla downloaded would not work, because SuSEs Mozilla was compiled with GCC 3, and the plugin was compiled with GCC 2.95.

You can get around this without any trouble. Just go to this site to read about them...they put a very nice GCC 3.2 compiled package of JAVA 1.4.1 and it works just fine with Mozilla when it's compiled with GCC 3.2. :) http://www.blackdown.org

Or you can just ftp directly and get it... ftp://ftp.tux.org/pub/java/JDK-1.4.1/i386/01. The file you want is called j2re-1.4.1-01-linux-i586-gcc3.2.bin.

After downloading, just move it to /usr/lib and do this..

This will unpack it into /usr/lib/j2re1.4.1

You do not have to change the default settings for Java at all. Instead you just make a softlink from your /opt/mozilla/plugins directory to the plugins directory in /usr/lib/j2re1.4.1/ and it should look like this...

libjavaplugin_oji.so -> /usr/lib/j2re1.4.1/plugin/i386/mozilla/javaplugin_oji.so
      

After making this softlink then Java should work just fine with your GCC 3.2 compiled browser. :)

It's not the best solution but it's a hell of a lot better then waiting for Sun to pull the heads from where then Sun doesn't shine in order to get a GCC 3.2 compiled pkg from them. And blackdown's been around a long time. I've never heard complaints about them.

The help centre was broken in 7.2 for people who upgraded their KDE to 2.2.x (from the original 2.1.2 in 7.2).

The solution is simple...get the susehelpcenter rpm for *7.3* from SuSE's site (or use a mirror!). It's in series k2de1.

Upgrade it with rpm -U or Yast and you will find that the help centre works.