SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Happy Holidays Daedra, Dugan,
Thanks much for all your work on fonts. Have gone thru this thread alot, keep going over Dugans Page and googling.
First attempt @ Fonts running slackware13.38.6 x86_64, Xfce DM.
Started trying to follow Dugan's Optimizing Fonts and got stuck at few junctures:
Do I change Lilo UTF8=0 to =1?
Edited /etc/profile.d/lang.sh and changing the LANG variable from en_US to en_US.UTF-8.
But-> Changes & Hints - suggests SCIM be started first? Also "maybe you should leave root with a non-UTF-8 locale because you don't want root's commands to be misinterpreted.
You can add the following line to your
~/.profile file to enable UTF-8 just for yourself:
export LANG=en_US.UTF-8"
-> Tried but ~/.profile would not set export LANG=en_US.UTF-8 - Locally ???
?Tried to create a ~/.profile & tried adding local user option to ~/.bashrc - it did not work... Seems you have to use DM Login to make it work and I runlevel 3? When folks say try this or do that - A description of how to do such things would make configuring options achievable tasks instead of week long research projects. Experienced & technically inclined folks under estimate their own expertise, assuming the common reader will know what they are referring too. Weeks googling and re-reading to do one thing is rough.
? Have rxvt-unicode.-2.7.10-x86_64-4 installed as part of current slackware system, so do I use SlackBuild rxvt-unicode-9.12.tar.bz2 to upgrade the installed package or uninstall older pkg. and install the new pkg that goes with libAfterImage?
??export LANG=en_US.UTF-8 in /etc/profile.d changes some characters in man pages?
?Where do i unpack ucs-fonts.tar.gz -> unpacked in /home/build. Did the little cat quickbrown.txt test. Now what do i do with the unpacked package? Do I simply create a ucs
Created /usr/local/share/fonts & local.conf
How do I specifically put fonts directly into /usr/local/share/fonts?
Download and unpkg or build pkg? Use install to the directory or unpkg, or build and then move (like cut and paste) to the /usr/local/share/fonts? Apologize my questions are so basic, I can follow the instructions but it's no good if i don't understand what I am doing.
I've learned much from this thread and Dugan's Site but the easiest questions are the hardest to find answers for. Thank you everyone.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Does someone have a slackbuild for the latest Infinality release? I tried to modify it from 13.37's default slackbuild but it didn't seem to work as now KDE doesn't even start anymore. I haven't made many of those earlier so there's probably just some error on my SlackBuild.
KDE seems to work again when I reinstalled default freetype.
How do I specifically put fonts directly into /usr/local/share/fonts?
If you got the fonts as part of a package or SlackBuild, then just install the package or SlackBuild.
If (and only if) a package or SlackBuild is not available, then you just copy the font files (e.g. with copy and paste in a graphical file manager) into /usr/local/share/fonts. I would just use cp or mv.
Quote:
Where do i unpack ucs-fonts.tar.gz -> unpacked in /home/build. Did the little cat quickbrown.txt test. Now what do i do with the unpacked package
You're finished with it. Delete it.
Quote:
? Have rxvt-unicode.-2.7.10-x86_64-4 installed as part of current slackware system, so do I use SlackBuild rxvt-unicode-9.12.tar.bz2 to upgrade the installed package or uninstall older pkg. and install the new pkg that goes with libAfterImage?
You're asking whether it's worth upgrading from version 2 to version 9? Gee, that question answers itself, doesn't it? Do keep in mind that the current SBo SlackBuild does not build rxvt-unicode with libAfterImage support; it's not something that you need.
You use the SlackBuild to build the package and then you use upgradepkg to replace the old package with the new one.
I'll look into the issue with the characters in man pages.
Quote:
Does someone have a slackbuild for the latest Infinality release?
Thank you Dugan, for such a quick response.
Is UTF8 required for Font enhancement? Is a local UTF8 option available? I will initiate en_US.UTF-8 again and will report back any issues.
Right on cp & mv, copy/paste is just very clear concept.
Quote:
You're asking whether it's worth upgrading from version 2 to version 9?
Noo.. Question was if the installed slackware rxvt the same as rxvt -unicode9 except of the version... if its the same upgrade is fine. Installed libAfterImage, just needed clarification on rxvt part.
Slackware comes with rxvt, not rxvt-unicode. They are different completely different programs, and Slackware's packaging tools (including slackpkg and upgradepkg) will recognize them as such. You install rxvt-unicode alongside rxvt.
And no, you don't need UTF-8 if you don't need to display non ASCII-characters.
Great, thank you Dugan, maybe on your homepage u can write a little about how you use these two tools.
Finally upgraded Fonts with Daedra's packages, looks really crisp & clean. Thanks Daedra
FYI: Changing /etc/profile.d/lang.sh from en_us to export LANG=en_US.UTF-8 adds distorts pkgtool on 13.38.7 current. Uninstalled libAfterImage & rxvt-unicode since, currently know no use for it. Would be helpful to know how to setup en-UTF-8 as a local environment since it helps display different languages Thanks again
Next logical Font question, looking at my printed pages from Xfce hurts. Font types look like an old typewriter stroke. Don't want to use kde or gnome, been dealing with printer "Stdin" header over a year. Print to:Brother HL-2170W, w/brhl217wlpr-2.0.2-1 + cupswrapper for HL2170W. Pretty Printing Option does nothing, how do control what pages look like? Printer GUI setup no printing options other than running it? Searched CUPs Fonts and googled, been looking at possible printer conf files but don't understand them? Thank you
I have always had this problem with firefox, printed pages always come out looking really crappy, I have never found a fix for this, however I have never really looked into that much.
Thanks, for responding. I am interested in graphics using slackware, currently looking into printing font configuration options, will post what I find.
lol Firefox prints well here. Printing from mouse pad is horrible - with STDIN header. Prints better from terminal using lp filename. Kate Notepad provided decent font control but i removed all things KDE. Still looking for a way to create font options from xfce print manager.
Does someone have a slackbuild for the latest Infinality release? I tried to modify it from 13.37's default slackbuild but it didn't seem to work as now KDE doesn't even start anymore. I haven't made many of those earlier so there's probably just some error on my SlackBuild.
KDE seems to work again when I reinstalled default freetype.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.