unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
Cc: wl@gnu.org, emacs-devel@gnu.org, visuweshm@gmail.com
Subject: Re: Tamil fonts
Date: Fri, 03 Jun 2022 16:00:56 +0300	[thread overview]
Message-ID: <83fskldhpz.fsf@gnu.org> (raw)
In-Reply-To: <CAOR1sLxrsfRhVs24fJ6JTz0dUs8B1dmNsi=tXrE3qD+YExSkGw@mail.gmail.com> (message from समीर सिंह Sameer Singh on Fri, 3 Jun 2022 17:46:10 +0530)

> From: समीर सिंह Sameer Singh <lumarzeli30@gmail.com>
> Date: Fri, 3 Jun 2022 17:46:10 +0530
> Cc: Werner LEMBERG <wl@gnu.org>, emacs-devel@gnu.org, Visuwesh <visuweshm@gmail.com>
> 
> Great! I will send them in two different bug reports.

Thanks.

> I think we should also warn users that if they are trying to change the tamil font in their init.el, they should use
> codepoints instead of the script name,
> in the (set-fontset-font) function, because if their font does not support the supplement characters, they will
> once more be displayed as "tofu".

How is this different from any other font that supports only part of
the script's characters?  Many Unicode blocks have "supplement" parts,
and there's nothing to assure a user that a font which supports the
representative characters will necessarily support all of the others.
Users should be prepared to deal with such problems when they happen,
and there's no way Emacs could warn them about every possible case,
since there are too many fonts out there.

(Personally, I find it strange that a Tamil font doesn't support the
Supplement block, and even more strange that Google created a separate
font instead of extending an existing one.  Perhaps this is because
the Tamil Supplement block is relatively new.)



  reply	other threads:[~2022-06-03 13:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOR1sLxNSfNq5v_XfDGrcXRP4A-O8qQjNCwr8BhdC3CXKh+m7A@mail.gmail.com>
     [not found] ` <83czfsh9aa.fsf@gnu.org>
     [not found]   ` <CAOR1sLxoEiVFiWcqWun1V=sX4jbQRhtjLja04zC=1-yCZZZ7QA@mail.gmail.com>
2022-06-01 12:54     ` bug#55745: [PATCH] Add support for the Hanifi Rohingya script Eli Zaretskii
2022-06-01 13:25       ` समीर सिंह Sameer Singh
2022-06-01 13:32         ` Eli Zaretskii
2022-06-01 13:54           ` समीर सिंह Sameer Singh
2022-06-01 14:30             ` Werner LEMBERG
2022-06-01 16:55               ` समीर सिंह Sameer Singh
2022-06-01 17:39                 ` Tamil fonts (Was: bug#55745: [PATCH] Add support for the Hanifi Rohingya script) Eli Zaretskii
2022-06-02  2:55                   ` समीर सिंह Sameer Singh
2022-06-02  5:38                     ` Eli Zaretskii
2022-06-02  6:27                       ` Eli Zaretskii
2022-06-02  6:42                         ` Tamil fonts Visuwesh
2022-06-02 12:14                         ` Tamil fonts (Was: bug#55745: [PATCH] Add support for the Hanifi Rohingya script) समीर सिंह Sameer Singh
2022-06-02 12:45                           ` Eli Zaretskii
2022-06-02 12:50                             ` Tamil fonts Werner LEMBERG
2022-06-03 11:37                               ` समीर सिंह Sameer Singh
2022-06-03 11:49                                 ` Eli Zaretskii
2022-06-03 11:51                                   ` समीर सिंह Sameer Singh
2022-06-03 12:10                                     ` Eli Zaretskii
2022-06-03 12:16                                       ` समीर सिंह Sameer Singh
2022-06-03 13:00                                         ` Eli Zaretskii [this message]
2022-06-03 13:14                                           ` Visuwesh
2022-06-03 13:19                                             ` समीर सिंह Sameer Singh
2022-06-03 13:38                                             ` Eli Zaretskii

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=83fskldhpz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lumarzeli30@gmail.com \
    --cc=visuweshm@gmail.com \
    --cc=wl@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 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).