myDSL Extensions (deprecated) :: Has anyone built an msttcorefonts.dsl?
kopsis, ke4nt1:
Thanks for the latest suggestions. I will give them a try today and let you know.
sci_fiHello kopsis, ke4nt1:
Thank you both for the suggestions. I am making some progress.
I installed the XF86 extension and made the modifications explained in the instructions. I use the VESA version of XF86Config-4 from the samples provided. Seems to work better than anything else.
I have the msttfonts.dsl file set up to load via MyDSL at boot. I have added "sudo xset +fp /opt/msttcorefonts/TrueType" to /opt/bootlocal.shell
Here are the results:
1. The MSfonts seem to load fine via MyDSL.
2. When the xset command executes from bootlocal.sh, a message saying "xset could not open display" appears, but the boot proceeds.
3. A lot of warnings and error messages relating to font paths appear briefly (can be viewed during shutdown procedure).
3. The boot appears to complete normally.
4. At this point, OpenOffice does not have the MS fonts.
5. Running "xset +fp /opt/msttcorefonts/TrueType" manually works without error and OO can now see the MS fonts.
6. FireFox does not see the fonts at all, ever. I am using FF 1.0.4 via GTK extension and have not tested with the earlier FF version that is standard in DSL. It certainly appears that FF handles fonts differently. I need to investigate this.
I am very puzzled that xset does not work from bootlocal.sh. I do not know if the modifed file /home/dsl/.xserverrc" is functioning properly or not. (this was per the instructions for installing the XF86 extension). I will be poking around FF trying to determine where it looks for fonts.
Any thoughts?
Thanks.
sci_fiIf I am correct, the GTK2 versions of most of our extensions use the defoma package for font management..
After a succesful xset + command, try rerunning the "Update to Gtk2" command, and see if it updates the defoma cache.
and the xset command needs an X environment to operate with. Try adding the line to your .xinitrc file, BEFORE the last 'enhance' line in the file. This will run the command AFTER x has started.
73 ke4nt
Quote (sci_fi @ Aug. 03 2005,14:46)
I have the msttfonts.dsl file set up to load via MyDSL at boot. I have added "sudo xset +fp /opt/msttcorefonts/TrueType" to /opt/bootlocal.shell
Take the "sudo" off. Your X session is owned by the "dsl" user. You'd have to do an "xhost + ..." command to give "root" permission to run xset against "dsl's" X session.
You shouldn't need root priviledges to do the xset.Hi ke4nt1 and kopsis:
Yes, I realized I didn't need the "sudo" on the xset and had already removed it. Forgot to mention. Sorry.
Slowly making progress. Not quite there yet.
1. I moved "xset +fp /opt/msttcorefonts/TrueType" to .xinitrc
I re-booted.
Immediately after boot-up OpenOffice now sees the new fonts. Hurrah!
Firefox does not see the fonts.
Exited FF. I ran the Update_to_GTK2 command from the myDSL drop-down menu. Run FF again.
I examined the error messages appearing during boot up. They appear to be related to the XF86Config-4 file (IMHO only). Messages of apparent relevance:
Could not init font path element unix /:7100, removing from list
Couldn't load XKB keymap, falling back to pre-XKB keymap (I noticed that cntl-alt-delete and my power buttom don't seem to be seen)
[EE] Mouse(2) no protocol specified [EE] PreInit failed for input device "Mouse(2)"
Perhaps the above font path element error is the culprit. What to do? I will change over to a different XF86Config-4 file as an experiment and let you know.