From: Eli Zaretskii <eliz@gnu.org>
To: Eric Abrahamsen <girzel@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: fontsets/charsets documentation suggestion
Date: Thu, 02 Jul 2009 22:15:30 +0300 [thread overview]
Message-ID: <83prci3nhp.fsf@gnu.org> (raw)
In-Reply-To: <2349B30D-81A8-4018-A484-80EA84FB6498@gmail.com>
> From: Eric Abrahamsen <girzel@gmail.com>
> Date: Wed, 1 Jul 2009 23:19:51 -0700
>
> 2. A glossary. What is a charset, what is a font registry, what is a
> script name symbol, what is encoding and how are these things related?
> A ground-up explanation of the ecology of bytes, encodings, charsets
> and fonts would be great. Even, dare I say it, a diagram. This stuff
> is very confusing.
This is in the manual, see the node "Character Sets" and maybe the
other nodes from its parent "Non-ASCII Characters", if you need more
background.
If something is missing or unclear, please post more specific gripes.
> 3. What are the relevant functions and variables? As a non-expert user
> of middling programming ability, I was totally baffled by set-fontset-
> font and all the possible permutations of its arguments. Likewise for
> create-fontset-from-fontset-spec. Since those two functions seem to be
> the weapons of choice for font manipulation, their descriptions could
> stand to be about four times as long as they are, with LOTS more
> examples. And when you're trying to get your fontsets right
> (particularly with multiple languages), you need to see lists of
> possible charsets and registries. These lists are in variables like
> charset-list and charset-script-alist which *aren't mentioned in the
> docs*.
Can you give a list of use-cases for which you'd like to have
examples, and/or point out what is unclear or insufficiently detailed
in the "Fontsets" node of the manual?
next prev parent reply other threads:[~2009-07-02 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 6:19 fontsets/charsets documentation suggestion Eric Abrahamsen
2009-07-02 19:15 ` Eli Zaretskii [this message]
2009-07-04 1:40 ` Eric Abrahamsen
2009-07-04 8:07 ` Eli Zaretskii
2009-07-04 22:14 ` Eric Abrahamsen
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=83prci3nhp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=girzel@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).