From: Andreas Schwab <schwab@suse.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-devel@gnu.org
Subject: Re: problem with old hebrew latex files in iso 8859-8 coding
Date: Thu, 18 Jul 2019 15:05:08 +0200 [thread overview]
Message-ID: <mvmr26n1ojf.fsf@suse.de> (raw)
In-Reply-To: <831ryny0vf.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 18 Jul 2019 15:37:40 +0300")
On Jul 18 2019, Eli Zaretskii <eliz@gnu.org> wrote:
>> And the new one emacs displays perfectly. So I conclude the old ones
>> were in iso8859-8 encoding.
>
> No, they were in codepage-1255. See my other message.
How do you know? They are identical for the characters in the files.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2019-07-18 13:05 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 11:31 problem with old hebrew latex files in iso 8859-8 coding Uwe Brauer
2019-07-18 11:48 ` Eli Zaretskii
2019-07-18 12:06 ` Uwe Brauer
2019-07-18 12:11 ` Lars Ingebrigtsen
2019-07-18 12:17 ` Uwe Brauer
2019-07-18 12:35 ` Eli Zaretskii
2019-07-18 13:03 ` Uwe Brauer
2019-07-18 13:56 ` Eli Zaretskii
2019-07-18 13:14 ` Uwe Brauer
2019-07-18 13:27 ` Andreas Schwab
2019-07-18 13:52 ` Uwe Brauer
2019-07-18 13:54 ` Uwe Brauer
2019-07-18 14:12 ` Eli Zaretskii
2019-07-18 14:00 ` Eli Zaretskii
2019-07-20 13:39 ` [Warning and iso 8859-1 default?] (was: problem with old hebrew latex files in iso 8859-8 coding) Uwe Brauer
2019-07-20 13:53 ` Eli Zaretskii
2019-07-20 13:57 ` [Warning and iso 8859-1 default?] Uwe Brauer
2019-07-20 14:09 ` Eli Zaretskii
2019-07-20 14:16 ` Uwe Brauer
2019-07-20 15:51 ` Eli Zaretskii
2019-07-20 16:17 ` Uwe Brauer
2019-07-20 16:46 ` Eli Zaretskii
2019-07-20 17:17 ` Eli Zaretskii
2019-07-20 16:48 ` Eli Zaretskii
2019-07-20 17:29 ` Stefan Monnier
2019-07-20 18:08 ` Uwe Brauer
2019-07-20 14:20 ` Stefan Monnier
2019-07-20 16:20 ` Uwe Brauer
2019-07-20 17:27 ` Stefan Monnier
2019-07-20 17:33 ` Eli Zaretskii
2019-07-20 17:37 ` Stefan Monnier
2019-07-20 17:40 ` Eli Zaretskii
2019-07-21 13:24 ` Stefan Monnier
2019-07-18 12:15 ` problem with old hebrew latex files in iso 8859-8 coding Eli Zaretskii
2019-07-18 12:19 ` Uwe Brauer
2019-07-18 12:37 ` Eli Zaretskii
2019-07-18 12:55 ` Uwe Brauer
2019-07-18 13:55 ` Eli Zaretskii
2019-07-18 14:04 ` Uwe Brauer
2019-07-18 14:14 ` Eli Zaretskii
2019-07-18 14:26 ` Uwe Brauer
2019-07-18 14:31 ` Eli Zaretskii
2019-07-18 13:05 ` Andreas Schwab [this message]
2019-07-18 13:57 ` Eli Zaretskii
2019-07-18 12:29 ` Andreas Schwab
2019-07-18 15:02 ` Stefan Monnier
2019-07-18 15:24 ` Uwe Brauer
2019-07-18 16:06 ` Eli Zaretskii
2019-07-18 17:10 ` Eli Zaretskii
2019-08-21 7:40 ` Arne Jørgensen
2019-08-21 7:43 ` 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
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=mvmr26n1ojf.fsf@suse.de \
--to=schwab@suse.de \
--cc=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 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).