From: Waleed Yousef <wyousef@fcih.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23722@debbugs.gnu.org
Subject: bug#23722: 24.5; Problem of displaying arabic font in dired mode
Date: Wed, 08 Jun 2016 18:35:01 +0000 [thread overview]
Message-ID: <874m93leay.fsf@fcih.net> (raw)
In-Reply-To: <83ziqwqu36.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 08 Jun 2016 05:42:53 +0300")
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
Thanks so much for reply,
I do not know the update; I am just guessing. Attached is a snapshot of
the problem. I tried set-buffer-file-coding-system with no hope!
Eli Zaretskii <eliz@gnu.org> writes:
>> From: wyousef@fcih.net
>> Date: Wed, 08 Jun 2016 00:02:17 +0000
>>
>> I use "dired" mode; some file and directory names are in Arabic. I did
>> not have any problem. All of the sudden, just few days ago (probably
>> after an update), the Arabic names of the files and directory are shown
>> as garbage.
>
> Please tell more: what was that update, what kind of garbage do you
> see, what is the value of default-file-name-coding-system?
>
> Thanks.
[-- Attachment #2: 2016-06-07--18.12.15.png --]
[-- Type: image/png, Size: 102419 bytes --]
next prev parent reply other threads:[~2016-06-08 18:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 0:02 bug#23722: 24.5; Problem of displaying arabic font in dired mode wyousef
2016-06-08 2:42 ` Eli Zaretskii
2016-06-08 18:35 ` Waleed Yousef [this message]
2016-06-08 17:13 ` Eli Zaretskii
2016-06-08 20:45 ` Glenn Morris
2016-06-09 0:10 ` Waleed Yousef
2016-06-09 5:01 ` Eli Zaretskii
2016-06-09 4:57 ` Eli Zaretskii
2016-06-09 13:32 ` Waleed Yousef
2016-06-09 14:11 ` Waleed Yousef
2016-06-09 14:23 ` Waleed Yousef
2016-06-09 13:59 ` Eli Zaretskii
2016-06-09 16:53 ` Waleed Yousef
2016-06-09 15:05 ` Eli Zaretskii
2016-06-09 17:33 ` Waleed Yousef
2016-06-09 17:27 ` Eli Zaretskii
2016-06-09 17:32 ` Glenn Morris
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=874m93leay.fsf@fcih.net \
--to=wyousef@fcih.net \
--cc=23722@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 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).