all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Werner LEMBERG <wl@gnu.org>, emacs-devel@gnu.org
Subject: Re: Tamil fonts (Was: bug#55745: [PATCH] Add support for the Hanifi Rohingya script)
Date: Thu, 2 Jun 2022 08:25:41 +0530	[thread overview]
Message-ID: <CAOR1sLzODih2QJ=Kn+guZ+oWmcAHdSiLy9QbkcPYstDrsnGroQ@mail.gmail.com> (raw)
In-Reply-To: <83tu94ffkx.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]

Then can we do something like
  (set-fontset-font "fontset-default" '(#x11FC0 . #x11FFF)
                    '("Noto Sans Tamil Supplement" . "iso10646-1") nil
'prepend)

in lisp/international/fontset.el?
After doing this both the "base" and supplement characters are being
displayed correctly.

On Wed, Jun 1, 2022 at 11:09 PM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: समीर सिंह Sameer Singh <lumarzeli30@gmail.com>
> > Date: Wed, 1 Jun 2022 22:25:52 +0530
> > Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> >
> >  This is a sub-optimal solution IMHO.  There will always be cases where
> >  a script is split into multiple Unicode blocks, probably mapped to
> >  different fonts.  AFAICS, the Tamil supplement characters don't
> >  interact typographically with normal Tamil characters, so a two-font
> >  solution in this case is valid.  In case my assumption is invalid you
> >  should submit a bug to the Noto project :-)
> >
> > I agree it is somewhat sub optimal, but Emacs does not differentiate
> between supplement and "base"
> > characters, so setting different fonts for both of them does not seem
> possible.
>
> Of course, it's possible: set-fontset-font can accept ranges of
> codepoints and use different font for each range.  It doesn't have to
> accept only script names.
>
> > There also seems to be no font which supports both Tamil and its
> supplement characters OOTB.
>
> That part is indeed sub-optimal, but not a catastrophe if they are
> displayed independently, i.e. there are no composition rules that
> cross the boundary between the blocks.
>

[-- Attachment #2: Type: text/html, Size: 2317 bytes --]

  reply	other threads:[~2022-06-02  2:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01  2:40 bug#55745: [PATCH] Add support for the Hanifi Rohingya script समीर सिंह Sameer Singh
2022-06-01 12:12 ` Eli Zaretskii
2022-06-01 12:24   ` समीर सिंह Sameer Singh
2022-06-01 12:54     ` 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 [this message]
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
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

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

  git send-email \
    --in-reply-to='CAOR1sLzODih2QJ=Kn+guZ+oWmcAHdSiLy9QbkcPYstDrsnGroQ@mail.gmail.com' \
    --to=lumarzeli30@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.