public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Michael DePaulo <mikedep333@gmail.com> To: cygwin-xfree@cygwin.com Cc: jon.turney@dronecode.org.uk Subject: Re: How do fonts work when you have no font packages installed? Date: Sun, 06 Jul 2014 15:34:00 -0000 [thread overview] Message-ID: <CAMKht8jka16H1=wtphhPB6Ym_JDHpxuEWdDLqoHeFPmSvA0pNw@mail.gmail.com> (raw) In-Reply-To: <53B9666E.5030003@dronecode.org.uk> On Sun, Jul 6, 2014 at 11:08 AM, Jon TURNEY <jon.turney@dronecode.org.uk> wrote: > On 04/07/2014 08:16, Michael DePaulo wrote: >> >> I just installed cygwin64 with only the base packages, "xorg-server", >> and its dependencies installed. >> >> The FAQ (2014-04-29) states: >> 3.5. My favourite font has gone! The font Emacs uses is just boxes >> Only minimal fonts will be installed after the upgrade. >> >> However, on my system, /usr/share/fonts/ is empty. > > > The X server has a version of 6x13 fixed font built-in, to allow it and > (some) apps which use core fonts, to operate in this situation. > > If some local X clients were installed, this would (hopefully) cause any X > core fonts they require to be installed. > > >> Yet I am able to XDMCP into a GNOME2 CentOS 6.5 machine and all the >> fonts show up fine with the handful of apps I tested. >> >> Can someone explain how text is being rendered? Is Cygwin Xwin using >> fonts from the Windows OS? > > > While this is technically possible by adding the Windows font directory to > the X server font path, that is not done. > > (Although those fonts are made available to local clients by telling > fontconfig to look in the Windows font directory, although this is not > technically perfect as there isn't any mechanism to tell fontconfig to > update it's cache when Windows fonts are added or removed) > > >> Are the fonts being rendered client-side via XRender? > > Yes, if the apps you tested are modern, client-side fonts are almost > certainly being used. [1] explains this fairly well: > > "The first X11 clients used the core X11 protocol to draw text, as that was > the only choice. [...] Because GTK+ and Qt, the toolkits behind several > applications including all GNOME and KDE applications, switched to Xft, many > programs on most desktops [...] now use Xft." Thank you very much, this is a very good answer. I was not aware of Xft. > Core fonts are a legacy feature. > > If you want to use an older remote application which requires a particular > core font, you will have to install it. Yes, I've observed this too. At work we run an old (but actively maintained) commercial Linux application written in Motif, and it requires core fonts to be installed on the Windows machines running Cygwin X11 or VcXsrv. > > [1] http://en.wikibooks.org/wiki/Guide_to_X11/Fonts > > -- > Jon TURNEY > Volunteer Cygwin/X X Server maintainer Thanks again, -Mike DePaulo -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
prev parent reply other threads:[~2014-07-06 15:34 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-04 7:16 Michael DePaulo 2014-07-06 15:08 ` Jon TURNEY 2014-07-06 15:34 ` Michael DePaulo [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAMKht8jka16H1=wtphhPB6Ym_JDHpxuEWdDLqoHeFPmSvA0pNw@mail.gmail.com' \ --to=mikedep333@gmail.com \ --cc=cygwin-xfree@cygwin.com \ --cc=jon.turney@dronecode.org.uk \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).