I apologize if this already exists. I tried to do a search but "font" seems to be a rather common word in posts.

What I am looking for is a source for fonts that work with slackware. I have installed OpenOffice hoping that it would have "Times New Roman" but did not see it.

I would also like to find some fonts that resemble old typewriters like Royal and Underwood.

Is there some type of program or procedure that can convert fonts designed for windows systems to be recognized by Linux systems?

I have a file of all my windows fonts (for reinstall if needed) and would really like to be able to instruct some program to batch convert all my windows fonts to something that works in Slackware.

Look for ttf-mscorefonts and how to install them.

Although I have no knowledge of Slackware, the following is an alternative solution to converting your Windows fonts if no other poster can help you:

http://www.slackware.com/~alien/slac...refonts/build/

See Alien Bob's note in this thread: http://www.linuxquestions.org/questi...e-13-a-789945/

I used slackware briefly once, although I do not recall the packaging system much beyond needing to be actual root to create packages from source to install with the package management system. Looks like pkgtool, installpkg, and other tools. If you did the standard install, most everything in the kitchen sink should have been installed by default. Otherwise check out slackbuilds.org for things not provided by the distro.

I tend towards debian where it's a matter of installing a package, which downloads the fonts in the case of msttcorefonts. And there's apt-file to look for files in packages if you don't know what package provides it. I would imagine that you could probably grab a debian package and use alien to convert it to a slackware package. Or grab and place the fonts manually from a windows install with a few extra steps. A variety of ways.

How about the one here? I had a look at the license once I downloaded it and it is free or personal and commercial use, although a donation is appreciated. Reproduction and redistribution is allowed (with some stipulations,) however, you cannot "rename, edit or create any derivative works."

If I remember correctly, my mother had an old Underwood from 1923 back when I was in middle school and high school. The thing weighed a ton but it was built like a tank!

Regards...

https://slackbuilds.org/system/webcore-fonts/

I'm not familiar with Royal or Underwood, but this is a good serif font:

https://slackbuilds.org/system/GentiumPlus/

There's nothing to convert. You put the font files (.ttf, .otf, etc) in this directory:

The normal place to put fonts on a single-user system, or for a single user, is in a .fonts directory in your home directory. Just run your file manager, create the .fonts folder and copy the fonts into it. You don't even need to run fc-cache, as the new fonts will be immediately recognised by software and fully indexed automatically at the next boot. As far as I know, Slackware is no different.

The Nimbus fonts include a very good typewriter, Nimbus mono, which is like Courier but more legible in small sizes. That's a Type 1, not a ttf. You may have it: most distros install it. Nimbus Roman looks very like Times.

My favourite is Linux Libertine. That's a ttf and has more variants than any other free font: regular, italic, bold, bold italic, small caps, and display (optimised for sizes over 18 points). It's well designed, too.

Thank you for all the input. I am going to leave this up for another day, in case there are other suggestions out there, and then mark it as solved.

As stated previously, the ~/.fonts/ is the usual place for many distros. Also, not that simple, when the contents of that path changes, you must run mkfontscale and mkfontdir to update things or they don't show up in various lists (fc-list / xlsfonts / xfontsel). Which implies unusable by various applications.

$ cd ~/.fonts/
$ mkfontscale
$ mkfontdir
$ cd ~/
$ fc-cache -f -v

But you only need mkfontscale and mkfontdir WHEN the contents of that directory changes. As in adding or removing fonts. Although you may need to run "fc-cache -f -v" every time that X starts (every boot / login). Or inside any X in X sessions via Xephyr, Xnest, Xdmx, and such.

$ xset fp+ /home/user/.fonts/
$ xset fp rehash
$ fc-cache -f -v

Are mkfontscale and mkfontdir still necessary for modern fonts? I have fonts.dir and fonts.scale in the directories of bitmap and Type 1 fonts, but I've never created them for the ttf ones and they all work perfectly.

If you install via the package management system, that generally takes care of that step for you. AKA distro supplied fonts ONLY. But in the case of custom fonts i.e. /home/user/.fonts/ the package management system doesn't manage that for you. Outside of the configs needed to not completely ignore that path when running fc-cache. You only "need" to run those when the contents "change". AKA if it's there and it doesn't show up in the lists, that's when mkfontscale and mkfontdir can save you. Sometimes you can get away without knowing that by re-installing various font packages that run them for you. If you use more distro expected locations like /usr/share/fonts/X11/misc/ and whatnot.

http://www.free-fonts-ttf.org/true-t...9-download.htm


Times New Roman Normal | Unicode | Q-T | TTF | >>> Free True


googled

times new roman ttf free download

then follow the instructions already give in prior post in here on installing it into your system.

No. mkfontscale, mkfontdir, xlsfonts and xfontsel aren't relevant to programs that use Fontconfig.

1 members found this post helpful.

I tend to do some black magic / vodoo. You will need to reconfigure fontconfig for bitmap fonts if you use those (I do). Doing so may crash your web browser (firefox). But I have an old affinity for those old bitmap fonts like vgarom.f14. It's a pattern recognition thing, plus making custom fonts out of them let's you scale them x3 so they scale in video form from 1920x1080 to 640x360 with pixel perfection. Plus you can read them on ridiculous 4k 11" screens (at x3). Plus pixels are either on or off so there's no eye strain there trying to interpret aliased-ness with less than perfect vision.