unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alexis <flexibeast@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Configuring fontsets with `unicode-fonts` [Was: Re: Should minibuffer prompt be made intangible by default?]
Date: Sat, 02 Apr 2016 13:32:33 +0300	[thread overview]
Message-ID: <83egaos3lq.fsf@gnu.org> (raw)
In-Reply-To: <87r3eos7zq.fsf@gmail.com> (message from Alexis on Sat, 02 Apr 2016 19:57:45 +1100)

> From: Alexis <flexibeast@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Sat, 02 Apr 2016 19:57:45 +1100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Installing fonts doesn't necessarily resolve the fontset 
> > configuration problems, especially since no package can know 
> > what other fonts are available on the end-user system.
> 
> Sorry, i'm not sure you understand what the `unicode-fonts` 
> package does?

I've read the code, but that doesn't necessarily mean I didn't miss
anything, of course.

However, I did read README.md as well, and upon re-reading now the
text you posted, I find nothing in it that would contradict what I
said.

> It doesn't provide fonts itself, but configures fontsets to use
> fonts on a users' system for maximum Unicode coverage.

I know; I've read the code before that original reply.

Maybe we are talking about 2 different issues.  My understanding of
the original stackexchange question was that the problems there were
related to the fact that fontset setup caused some characters to be
displayed with fonts other than what the user saw before changing his
setup.  It should be clear that the fonts used before changing the
setup depend on what is installed on the user's system, something that
no package can take into consideration.  Thus this part of what I
wrote:

> > Installing fonts doesn't necessarily resolve the fontset 
> > configuration problems, especially since no package can know
> >                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > what other fonts are available on the end-user system.
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

IOW, the problem here that I referred to is this:

  . User complains that some characters cannot be displayed
  . User is advised to install a fontset setup and additional fonts to
    fix that
  . The fontset setup causes some characters previously displayed with
    font A to be now displayed with font B, and the user doesn't like that

My point is that, once you get to the 3rd item, no external package
can be the correct answer; instead, you need to teach the user to
configure his/her fontset according to his/her preferences.  In
particular, the fontset setup should be based not only on Unicode
blocks, but also on the capabilities of the fonts present in the
original system configuration, and the user's preferences for using
particular font(s) for displaying particular ranges of characters.



  reply	other threads:[~2016-04-02 10:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30 16:46 Should minibuffer prompt be made intangible by default? (Was debbugs 21874: 25.0.50; point-entered no longer works) Kaushal Modi
2016-03-31 12:38 ` Stefan Monnier
2016-03-31 14:58   ` Kaushal Modi
2016-03-31 16:46   ` Clément Pit--Claudel
2016-03-31 21:37     ` Stefan Monnier
2016-03-31 22:04       ` Clément Pit--Claudel
2016-04-01  1:40         ` Configuring fontsets with `unicode-fonts` [Was: Re: Should minibuffer prompt be made intangible by default?] Alexis
2016-04-01  7:27           ` Eli Zaretskii
2016-04-01 10:00             ` Clément Pit--Claudel
2016-04-01 10:06               ` Eli Zaretskii
2016-04-02  8:57             ` Alexis
2016-04-02 10:32               ` Eli Zaretskii [this message]
2016-04-02 11:30                 ` Alexis
2016-04-01 10:00           ` Clément Pit--Claudel
2016-04-02 11:31             ` Alexis

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83egaos3lq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=flexibeast@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).