all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Lafleur, Henry" <Henry.LaFleur@canrig.com>
To: <1502@emacsbugs.donarmstrong.com>
Subject: bug#1502: Info received (bug#1502: CR/LF Unicode Problem)
Date: Mon, 8 Dec 2008 16:11:53 -0600	[thread overview]
Message-ID: <2905B00E9FC955468D756D43D7BF17543F84AC@USHOUXMB02.nabors.com> (raw)
In-Reply-To: <handler.1502.B1502.122877160131909.ackinfo@emacsbugs.donarmstrong.com>

One more thing to throw in the mix, I have this in my .emacs file for
UTF-16:

;;
;; Auto-detect UTF-16 files
;;

    ;; Add missing support functions
    (defun utf-16-le-pre-write-conversion (start end) nil)
    (defun utf-16-be-pre-write-conversion (start end) nil)

    ;; Set up auto-load of UTF-16 files using the appropriate coding
system.
    (setq coding-category-utf-16-le 'utf-16-le)
    (push 'coding-category-utf-16-le coding-category-list)

    ;; Detect endianness of UTF-16 containing a Byte Order Mark U+FEFF
    ;; Detect EOL mode by looking for CR/LF on the first line
    (add-to-list 'auto-coding-regexp-alist '("^\xFF\xFE.*\x0D\x00$" .
utf-16-le-dos) t)
    (add-to-list 'auto-coding-regexp-alist '("^\xFE\xFF.*\x0D\x00$" .
utf-16-be-dos) t)
    (add-to-list 'auto-coding-regexp-alist '("^\xFF\xFE" . utf-16-le) t)
    (add-to-list 'auto-coding-regexp-alist '("^\xFE\xFF" . utf-16-be) t)

I have no idea if this would cause the problem. These files start with
xEF xBB xBF, which shouldn't match the byte order marks above.

Thanks,

Henry. 

-----Original Message-----
From: Emacs bug Tracking System [mailto:don@donarmstrong.com] 
Sent: Monday, December 08, 2008 3:35 PM
To: Lafleur, Henry
Subject: bug#1502: Info received (bug#1502: CR/LF Unicode Problem)


Thank you for the additional information you have supplied regarding
this bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Emacs Bugs <bug-gnu-emacs@gnu.org>

If you wish to submit further information on this problem, please send
it to 1502@emacsbugs.donarmstrong.com, as before.

Please do not send mail to don@donarmstrong.com unless you wish to
report a problem with the Bug-tracking system.


--
1502: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=1502
Emacs Bug Tracking System
Contact don@donarmstrong.com with problems

-----------------------------------------
CANRIG EMAIL NOTICE - This transmission may be strictly
confidential. If you are not the intended recipient of this
message, you may not disclose, print, copy, or disseminate this
information. If you have received this in error, please reply and
notify the sender (only) and delete the message. Unauthorized
interception of this e-mail is a violation of federal criminal law.
This communication does not reflect an intention by the sender or
the sender's principal to conduct a transaction or make any
agreement by electronic means. Nothing contained in this message or
in any attachment shall satisfy the requirements for a writing, and
nothing contained herein shall constitute a contract or electronic
signature under the Electronic Signatures in Global and National
Commerce Act, any version of the Uniform Electronic Transactions
Act, or any other statute governing electronic transactions.






      parent reply	other threads:[~2008-12-08 22:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 22:33 bug#1502: CR/LF Unicode Problem Lafleur, Henry
2008-12-06  8:02 ` Eli Zaretskii
     [not found]   ` <2905B00E9FC955468D756D43D7BF175475BBA4@USHOUXMB02.nabors.com>
2008-12-06 17:27     ` bug#1502: FW: " Henry Lafleur
2008-12-07 15:58 ` Jason Rumney
2008-12-08 21:26   ` Lafleur, Henry
     [not found]     ` <handler.1502.B1502.122877160131909.ackinfo@emacsbugs.donarmstrong.com>
2008-12-08 22:11       ` Lafleur, Henry [this message]

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=2905B00E9FC955468D756D43D7BF17543F84AC@USHOUXMB02.nabors.com \
    --to=henry.lafleur@canrig.com \
    --cc=1502@emacsbugs.donarmstrong.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 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.