From: Eli Zaretskii <eliz@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: bidi, hebrew: files may need to be utf-8 with a byte order mark
Date: Fri, 04 Jan 2019 22:26:29 +0200 [thread overview]
Message-ID: <831s5s2mq2.fsf@gnu.org> (raw)
In-Reply-To: <87h8eociej.fsf@mat.ucm.es> (message from Uwe Brauer on Fri, 04 Jan 2019 20:49:40 +0100)
> From: Uwe Brauer <oub@mat.ucm.es>
> Date: Fri, 04 Jan 2019 20:49:40 +0100
>
> > I don't think I understand the question. If you ask whether Emacs
> > supports UTF-8 encoding with BOM, then the answer is yes: see
> > coding-system utf-8-with-signature. Emacs has supported this since
> > long ago, not just on master. But this has no direct relation to
> > bidi.
>
> Well I just included the remark from the keyman project. So BOM means
> byte order mark, I presume and as I understand GNU emacs supports it.
>
> I recall some time ago some specific issue of the hebrew or better bidi
> implementation, like some missing feature which was only included
> recently (by this I mean ~25 or later. I call it recently since Ubuntu
> still ships officially GNU emacs 24).
If you mean support for changes introduced in Unicode 6.3, then Emacs
supports that since v25.1. But again, what does that have to do with
keyboard layouts?
> I also thought that BOM is related to bidi
No, it is related to automatic detection of the platform's endianness
i.e. big-endian vs little-endian.
> BTW is that a BOM ?
> (insert-char 8207 1 t)
No, the BOM is 0xFEFF, which is 65279 decimal.
next prev parent reply other threads:[~2019-01-04 20:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 17:13 bidi, hebrew: files may need to be utf-8 with a byte order mark Uwe Brauer
2019-01-04 18:54 ` Eli Zaretskii
2019-01-04 19:49 ` Uwe Brauer
2019-01-04 20:26 ` Eli Zaretskii [this message]
2019-01-04 20:48 ` Uwe Brauer
2019-01-04 21:13 ` Eli Zaretskii
2019-01-05 8:49 ` Uwe Brauer
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=831s5s2mq2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
/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.