Problems with fonts in Windows

Forum / NoMachine for Windows / Problems with fonts in Windows

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #13969
    giaco777
    Participant

    I use NoMachine on Windows 7 to transfer the display of a computer running CentOS 6.7. I also have the chance to use MobaXterm for this purpose. If I run xlsfonts in an xterm opened using MobaXterm, I get a listing with 2815 font entries. If I use a xterm, which I opened from within a NoMachine session, I get the listing shown below. As a consequence programs, which I run via NoMachine are limited to the ‘Fixed; fonts, whereas the same programs offer me the wealth of many fonts in the MobaXterm environment. Why is this?

    Note by keymaster. List was long and so has been attached as a separate file.

     

    Attachments:
    #13975
    graywolf
    Participant

    Check the font path with command xset q.

    You can change the font path with command xset fp= <comma separated set of strings> (notice the blank after “=”). Suitable directories to be added are usually located at /usr/share/X11/fonts and /usr/share/fonts, e.g.:

    xset fp= /usr/share/fonts/default/ghostscript/,/usr/share/fonts/default/Type1/,/usr/share/fonts/liberation/,built-ins

    (Warning: any invalid item would make the whole command fail).

    “built-ins” fonts aren’t in any directory, they stay in the display server itself.

    To start with the needed font path already set, consider editing of /usr/NX/etc/node.cfg in this way:

    DisplayServerExtraOptions "-fp /usr/share/fonts/default/ghostscript/,/usr/share/fonts/default/Type1/,/usr/share/fonts/liberation/,built-ins"

Viewing 2 posts - 1 through 2 (of 2 total)

This topic was marked as solved, you can't post.