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: Mon, 14 Feb 2022 08:31:38 +0530 [thread overview]
Message-ID: <87fsomi225.fsf@gmail.com> (raw)
In-Reply-To: <83wnhypvh6.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 13 Feb 2022 18:44:21 +0200")
[ஞாயிறு, பிப்ரவரி 13 2022] Eli Zaretskii wrote:
Hi Eli,
>> From: Visuwesh <visuweshm@gmail.com>
>> Cc: 53729@debbugs.gnu.org
>> Date: Sun, 13 Feb 2022 20:26:17 +0530
>>
>> >> and the buffer name in the modeline has the right shaping! This is the
>> >> case for _every_ font I tried: including Noto Serif Tamil. But if I
>> >> open a file named "அக்னிச்சிறகுகள்.pdf", the shaping is as in the OP.
>> >
>> > What happens if you turn off auto-composition mode before repeating
>> > the above experiment? Do you see any difference in the buffer name
>> > produced by you and the buffer name produced by Emacs when visiting
>> > that file?
>>
>> 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.
>> 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.
>> I'm not sure if this has to do with the filename since when I yank the
>> file name from dired and create an empty file (M-x
>> dired-create-empty-file) by that name in another directory and visit it,
>> Emacs shapes the buffer name properly.
>
> Very strange. Is that the only file name with such problems? It
> sounds like maybe its file name has more than meets the eye (which is
> one reason why I asked you to disable auto-composition-mode).
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.
next prev parent reply other threads:[~2022-02-14 3:01 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 [this message]
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
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=87fsomi225.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.