all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 53729@debbugs.gnu.org
Subject: bug#53729: 29.0.50; Tamil text not shaped in modeline
Date: Tue, 15 Feb 2022 07:17:12 +0530	[thread overview]
Message-ID: <878rucaokf.fsf@gmail.com> (raw)
In-Reply-To: <83ilthpmpq.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 14 Feb 2022 16:05:53 +0200")

[திங்கள், பிப்ரவரி 14 2022] Eli Zaretskii wrote:

>> From: Visuwesh <visuweshm@gmail.com>
>> Cc: 53729@debbugs.gnu.org
>> Date: Mon, 14 Feb 2022 08:31:38 +0530
>> 
>> >> If I turn off global-auto-composition-mode and do the above, none of the
>> >> text is shaped i.e., the buffer name produced by me and the buffer name
>> >> produced by Emacs both are not shaped.
>> >
>> > Of course they aren't shaped: turning off auto-composition-mode
>> > disables the shaping.  I'm asking whether both the buffer name
>> > produced by you and the buffer name produced by visiting that file
>> > look identical on the mode line, or do they somehow differ?  If they
>> > do differ, what is the difference?
>> >
>> 
>> I misunderstood what you meant, sorry.  They look the same.
>
> And what does Emacs display if you evaluate the below in the buffer
> whose file name is displayed on the mode line improperly:
>
>   (append (file-name-nondirectory (buffer-file-name)) nil)
>
> This should produce the list of character codes that constitute the
> file name; I want to see that there's no strange characters in the
> file name.

(2949 2965 3021 2985 3007 2970 3021 2970 3007 2993 2965 3009 2965 2995 3021 46 112 100 102)

>> >> I did this out of curiosity: in dired, I typed C M-n when over the file
>> >> and added ".1" to the end of new file name, and when I visit this file,
>> >> the buffer name is shaped properly.  [ The new filename is
>> >> அக்னிச்சிறகுகள்.pdf.1 ]
>> >
>> > So you are saying that changing the file-name extension affects the
>> > shaping on the mode line?
>> 
>> Yes, that seems to be the case.  I tried changing the extension to
>> "jpeg", and the shaping was incorrect.  If I completely remove the
>> extension, the text is shaped properly.
>
> 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.

> If you display the mode-line text as a string, does it display
> correctly?  Here's how to do that: evaluate:
>
>   (let ((str (format-mode-line mode-line-format)))
>     (remove-list-of-text-properties 0 (length str) '(help-echo face mouse-face local-map display keymap) str) str)
>

It is displayed correctly.

>> I'm not sure if that's the case.  If I rename that file in Emacs to
>> "வணக்கம்.pdf", the text is not shaped properly again.
>> 
>> Also, I found out that non-empty files (with Tamil names) don't have
>> their buffer name shaped properly.  If I create a new empty file in
>> dired, the buffer name is shaped properly but that is not the case if I
>> rename an existing, non-empty file.
>
> Again sounds like what's else on the mode line somehow affects the
> rendering of the Tamil file name.
>
> But I cannot reproduce this on my system, so it is hard to tell what
> is going on here.

That is really unfortunate.





  reply	other threads:[~2022-02-15  1:47 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 [this message]
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
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=878rucaokf.fsf@gmail.com \
    --to=visuweshm@gmail.com \
    --cc=53729@debbugs.gnu.org \
    --cc=eliz@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.