From: Roel Janssen <roel@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: emacs: Use libotf.
Date: Mon, 14 Mar 2016 13:22:09 +0100 [thread overview]
Message-ID: <871t7ds0zy.fsf@gnu.org> (raw)
In-Reply-To: <87ziu5x9ng.fsf@gnu.org>
[-- Attachment #1: emacs-from-guix.png --]
[-- Type: image/png, Size: 126444 bytes --]
[-- Attachment #2: emacs-from-fedora.png --]
[-- Type: image/png, Size: 126047 bytes --]
[-- Attachment #3: Type: text/plain, Size: 1272 bytes --]
Ludovic Courtès writes:
> Roel Janssen <roel@gnu.org> skribis:
>
>> Here's a very small patch to compile Emacs with libotf support.
>> Unfortunately for me, it hasn't given me better font rendering.
>
> Does the resulting Emacs refer to libotf, as per:
>
> guix gc --references $(./pre-inst-env guix build emacs) | grep libotf
>
> ?
Yes, here's the output:
[roel@roel-tp guix]$ guix gc --references $(./pre-inst-env guix build emacs) | grep libotf
/gnu/store/kzc2zkdl3aadrs3iiml7vva80fgsd2b9-libotf-0.9.13
You can also see "Does Emacs use libotf?" turn to "yes" with my patch in
the overview at the end of the configure phase.
> If it does, could you check how it’s supposed to use it? I don’t see
> how it would be used, but I guess this has nothing to do with rendering.
It seems that Emacs can use it for complex font rendering of OTF fonts:
https://www.gnu.org/software/emacs/manual/html_node/elisp/Low_002dLevel-Font.html
(search for "libotf").
> How “wrong” is font rendering for you?
I attached two screenshots, emacs-from-guix.png and
emacs-from-fedora.png. Both are compiled with libotf support. Besides
the missing Fira font, the text on the Emacs from Guix looks stretched
and not properly anti-aliased to me.
Kind regards,
Roel Janssen
next prev parent reply other threads:[~2016-03-14 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 21:30 [PATCH] gnu: emacs: Use libotf Roel Janssen
2016-03-11 16:27 ` Ludovic Courtès
2016-03-14 12:22 ` Roel Janssen [this message]
2016-03-14 20:20 ` Alex Kost
2016-03-15 16:08 ` Ludovic Courtès
2016-03-15 16:01 ` Ludovic Courtès
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=871t7ds0zy.fsf@gnu.org \
--to=roel@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.