unofficial mirror of bug-gnu-emacs@gnu.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: Tue, 15 Feb 2022 16:26:07 +0200	[thread overview]
Message-ID: <83y22c2olc.fsf@gnu.org> (raw)
In-Reply-To: <878rucaokf.fsf@gmail.com> (message from Visuwesh on Tue, 15 Feb 2022 07:17:12 +0530)

> From: Visuwesh <visuweshm@gmail.com>
> Cc: 53729@debbugs.gnu.org
> Date: Tue, 15 Feb 2022 07:17:12 +0530
> 
> > Looks like the rendering of the file name is affected by the non-Tamil
> > text that follows it?
> >
> 
> And it looks like it is not just any non-Tamil text that affects it but
> only image like extensions?  For example, if the extension is .txt, .sh,
> .c, .el, .svg, .djvu, then the buffer name is shaped properly.  But if I
> use the extensions .tiff, .png, .jpeg, .pdf, .jpg, then the buffer name
> is not shaped.  The file I renamed was a bash script.

The display code which renders this doesn't know anything about the
meaning of the extensions, it only cares about the characters it needs
to display.  So if image-file extensions tend to cause this, it's
because of the characters that are part of the extensions, or maybe
because having an image file visited by the buffer affects the mode
line in some other way that causes this issue.

> > But I cannot reproduce this on my system, so it is hard to tell what
> > is going on here.
> 
> That is really unfortunate.

Maybe someone else can reproduce this?





  reply	other threads:[~2022-02-15 14:26 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 [this message]
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
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

  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=83y22c2olc.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 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).