Ar an seachtú lá de mí na Nollaig, scríobh Uwe Brauer:
Aidan> One could probably do so. I loaded it in 21.5 out of
Aidan> curiosity while writing an answer to your last mail, and it
Aidan> seems our ISO 2022 Hebrew character set identifier doesn’t
Aidan> match theirs, so you would need to load it in GNU Emacs,
Aidan> change the coding cookie and save it as iso-8859-8 instead
Aidan> of iso-2022-7.
What do you mean by changing the coding cookies?
The GNU Emacs Hebrew input method has something like
-*- coding: iso-2022-7bit; -*-
in its first line. You need to change that to
-*- coding: iso-8859-8; -*-
and M-x set-buffer-file-coding-system RET iso-8859-8 RET, then save the
file.
Aidan> (If and when you have experience with GNU Emacs and
their
Aidan> BiDi support, I’d love if you’d post a summary of the
Aidan> situation here. I’d like to know what’s happening there.)
Ha, do you know about nntp+news.gmane.org:gmane.emacs.bidi?
No, I didn’t. It’s not an _immediate_ concern for me, but if I keep up the
Tajik I’ll need BiDi late next year to deal with Persian, with which it is
mutually intelligible. So thank you for the summary :-) .
--
I AM IN JAIL AND ALLOWED SEND ONLY ONE CABLE SINCE WAS ARRESTED WHILE
MEASURING FIFTEEN FOOT WALL OUTSIDE PALACE AND HAVE JUST FINISHED COUNTING
THIRTY EIGHT THOUSAND FIVE HUNDERED TWENTY TWO NAMES WHOS WHO IN MIDEAST.