unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: J S <jszabo_98@hotmail.com>
Cc: "35766@debbugs.gnu.org" <35766@debbugs.gnu.org>,
	"npostavs@gmail.com" <npostavs@gmail.com>
Subject: bug#35766: emacs saves utf-16 le xml files as utf-16 be
Date: Sun, 19 May 2019 07:58:01 +0300	[thread overview]
Message-ID: <062CAA71-E754-4977-90FC-9F94487415A7@gnu.org> (raw)
In-Reply-To: <BL0PR11MB3475AB95C0692C46A6D26F5C9E040@BL0PR11MB3475.namprd11.prod.outlook.com>

On May 18, 2019 11:57:51 PM GMT+03:00, J S <jszabo_98@hotmail.com> wrote:
> RFC 2781 under "4.3 Interpreting text labelled as UTF-16" says is that
> if a document is labelled "UTF-16", the application should check the
> byte order mark to see if it is little endian or big endian   Only if
> there's no byte order mark, should the document be interpreted as big
> endian.
> 


If you are talking about visiting an existing file, then the change I installed does just that.  I was talking about saving a file, in which case there's no BOM, since it isn't present in the buffer 





  reply	other threads:[~2019-05-19  4:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 17:11 bug#35766: emacs saves utf-16 le xml files as utf-16 be J S
2019-05-16 18:22 ` Eli Zaretskii
     [not found]   ` <BL0PR11MB34754605999DC2A03A6DF45A9E0A0@BL0PR11MB3475.namprd11.prod.outlook.com>
2019-05-16 19:21     ` J S
2019-05-16 20:57       ` J S
2019-05-17  9:26         ` Eli Zaretskii
2019-05-17 11:26           ` J S
2019-05-17 11:48             ` Noam Postavsky
2019-05-17 15:34               ` Eli Zaretskii
2019-05-17 16:27                 ` npostavs
2019-05-17 16:57                   ` J S
2019-05-17 19:46                     ` Eli Zaretskii
2019-05-17 20:16                       ` J S
2019-05-18  5:33                         ` Eli Zaretskii
2019-05-18 20:57                           ` J S
2019-05-19  4:58                             ` Eli Zaretskii [this message]
2019-05-19 14:12                               ` J S
2019-05-18  7:26                   ` 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=062CAA71-E754-4977-90FC-9F94487415A7@gnu.org \
    --to=eliz@gnu.org \
    --cc=35766@debbugs.gnu.org \
    --cc=jszabo_98@hotmail.com \
    --cc=npostavs@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).