all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: 53729@debbugs.gnu.org
Subject: bug#53729: 29.0.50; Tamil text not shaped in modeline
Date: Fri, 18 Feb 2022 14:59:56 +0200	[thread overview]
Message-ID: <831r001gab.fsf@gnu.org> (raw)
In-Reply-To: <87bkz4pekm.fsf@gmail.com> (message from Visuwesh on Fri, 18 Feb 2022 17:33:05 +0530)

> From: Visuwesh <visuweshm@gmail.com>
> Cc: 53729@debbugs.gnu.org
> Date: Fri, 18 Feb 2022 17:33:05 +0530
> 
> I have not tried reproducing it in other systems but I did try latest
> master, and the text is still not shaped.  However, I just noticed that
> I missed this warning message that was written to stdout (which is
> mostly why I did not notice it) when I close Emacs:
> 
>     Warning: Missing charsets in String to FontSet conversion
> 
> I tried quickly grepping for "Missing charsets" and "Warning: " in Emacs
> git repo but I don't see this particular warning in the results.

This is not an Emacs warning.  Searching for it on the Internet brings
these pages, please see if anything there is relevant to your setup:

  https://www.ibm.com/support/pages/using-gui-results-missing-charsets-string-fontset-conversion-warning
  https://access.redhat.com/solutions/409033
  https://superuser.com/questions/1531413/getting-warning-missing-charsets-in-string-to-fontset-conversion
  https://gromnitsky.blogspot.com/2021/05/missing-charsets-in-string-to-fontset.html

After skimming those, it seems to be related to the X font setup, so
maybe it is relevant to the display problems you see.  Not sure.





  reply	other threads:[~2022-02-18 12:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 16:55 bug#53729: 29.0.50; Tamil text not shaped in modeline Visuwesh
2022-02-02 18:54 ` Eli Zaretskii
2022-02-03  1:45   ` Visuwesh
2022-02-03  7:39     ` Eli Zaretskii
2022-02-03  8:07       ` Visuwesh
2022-02-03  9:23         ` Eli Zaretskii
2022-02-03 10:05           ` Visuwesh
     [not found]             ` <877da2amw9.fsf@gmail.com>
2022-02-13 13:53               ` Eli Zaretskii
2022-02-13 14:56                 ` Visuwesh
2022-02-13 16:44                   ` Eli Zaretskii
2022-02-14  3:01                     ` Visuwesh
2022-02-14 14:05                       ` Eli Zaretskii
2022-02-15  1:47                         ` Visuwesh
2022-02-15 14:26                           ` Eli Zaretskii
2022-02-16 14:06                             ` Visuwesh
2022-02-16 14:07                               ` Eli Zaretskii
2022-02-18 12:03                               ` Visuwesh
2022-02-18 12:59                                 ` Eli Zaretskii [this message]
2022-02-18 13:20                                   ` Visuwesh
2022-02-19  4:20                             ` Jai Vetrivelan
2022-02-19  4:51                               ` Visuwesh
2022-02-19  5:22                                 ` Jai Vetrivelan
2022-02-19  5:31                                   ` Jai Vetrivelan
2022-02-19  8:23                               ` Eli Zaretskii
2022-02-19  9:22                                 ` Eli Zaretskii
2022-02-19 10:27                                   ` Visuwesh
2022-02-19 12: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=831r001gab.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=53729@debbugs.gnu.org \
    --cc=visuweshm@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 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.