10:25 a.m.
Hello
Some days ago I asked for an equivalent to iso-unaccentuate for quail
input methods. Since as I learnt xemacs does not use the GNU Emacs
idea of multi-byte chars, iso-unaccentuate should work without
problems for ó and the like.
Now I asked for a similar feature for the TeX input methods:
TeX-2-utf8(TeXtuate)
\int ---------------> ∫
utf8-2-TeX(TeXuntuate)
∫ ---------------> \int
Now I looked into a attic package (1994)
iso-sgml, (written by Frederic Lepied <lepied(a)cenaath.cena.dgac.fr>),
whose logic I could understand,
which changed iso-8859-1 chars to the SGML entities.
A main point was the variable sgml2iso-trans-tab, which looks
basically like:
(defvar sgml2iso-trans-tab
'(
("Æ\;" "Æ")
))
Which changed Æ to Æ and back.
So I boldly modified the variable to the following
(defvar tex2utf8symb-trans-tab
'(
("\int" "∫")
))
I am not sure whether I could treat ∫ as a string, for example in the
file latin-ltx.el I see
("\\int" ?∫)
Anyhow the code worked, but there is a problem:
(defvar tex2utf8symb-trans-tab
'(
("\\in" "∈")
("\\infty" "∞")
("\\int" "∫")
))
While
\in and \int are transformed correctly
\infty is changed to ∈fty,
which is wrong (on the other hand I don't understand why
\int is not transformed to ∈t but anyhow).
So the question is how shall I define the tex commands uniquely?
thanks
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
12:38 p.m.
Ar an seachtú lá de mí Eanair, scríobh Uwe Brauer:
Anyhow the code worked, but there is a problem:
(defvar tex2utf8symb-trans-tab
'(
("\\in" "∈")
("\\infty" "∞")
("\\int" "∫")
))
While
\in and \int are transformed correctly
\infty is changed to ∈fty,
which is wrong (on the other hand I don't understand why
\int is not transformed to ∈t but anyhow).
So the question is how shall I define the tex commands uniquely?
What you need to do is rewrite the code to use #'posix-search-forward, which
guarantees that it will return the longest match (that is, it will always
try to match "\\infty" if possible, and only then look for "\in".) You
might
also want to look into the #'regexp-opt function, which, given a list of
strings, returns a theoretically fast regexp to match that list--you’ll need
the regexp to pass to posix-search-forward. (I’m not however certain if
regexp-opt interacts well with posix-search-forward; anyone else know?)
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghé, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
2:26 p.m.
>>>> "Aidan" == Aidan Kehoe
<kehoea(a)parhasard.net> writes:
Ar an seachtú lá de mí Eanair, scríobh Uwe Brauer:
> Anyhow the code worked, but there is a problem:
>
> (defvar tex2utf8symb-trans-tab
> '(
> ("\\in" "∈")
> ("\\infty" "∞")
> ("\\int" "∫")
>
> ))
>
> While
> \in and \int are transformed correctly
> \infty is changed to ∈fty,
>
> which is wrong (on the other hand I don't understand why
> \int is not transformed to ∈t but anyhow).
>
> So the question is how shall I define the tex commands uniquely?
What you need to do is rewrite the code to use
#'posix-search-forward, which guarantees that it will return the
longest match (that is, it will always try to match "\\infty" if
possible, and only then look for "\in".) You might also want to
look into the #'regexp-opt function, which, given a list of
strings, returns a theoretically fast regexp to match that
list--you’ll need the regexp to pass to
posix-search-forward. (I’m not however certain if regexp-opt
interacts well with posix-search-forward; anyone else know?)
Hm the code is this
(defun fix-tex2utf8symbol ()
"Replace SGML entity references with ISO 8859-1 (aka Latin-1) characters."
(interactive)
; (if (member major-mode utf8symbol-modes-list)
(let ((buffer-modified-p (buffer-modified-p)))
(unwind-protect
(utf8symbol-translate-conventions tex2utf8symbol-trans-tab)
(set-buffer-modified-p buffer-modified-p))))
And the most relevant function:
(defun utf8symbol-translate-conventions (trans-tab)
"Use the translation table argument to translate the current buffer."
(save-excursion
(let ((beg (point-min-marker)) ; see the `(elisp)Narrowing' Info node
(end (point-max-marker)))
(unwind-protect
(progn
(widen)
(goto-char (point-min))
(let ((buffer-read-only nil) ; (inhibit-read-only t)?
(case-fold-search nil))
(while trans-tab
(save-excursion
(let ((trans-this (car trans-tab)))
(while (search-forward (car trans-this) nil t)
(replace-match (car (cdr trans-this)) t t)))
(setq trans-tab (cdr trans-tab))))))
(narrow-to-region beg end)))))
So tried to replace the line:
(while (search-forward (car trans-this) nil t)
By
(while (posix-search-forward (car trans-this) nil t)
but I obtained an error.
So I thought of using regexp-opt, as you suggested
For me the following looked "logical":
(defun utf8symbol-translate-conventions (trans-tab)
"Use the translation table argument to translate the current buffer."
(save-excursion
(let ((beg (point-min-marker)) ; see the `(elisp)Narrowing' Info node
(end (point-max-marker)))
(unwind-protect
(progn
(widen)
(goto-char (point-min))
(let ((buffer-read-only nil) ; (inhibit-read-only t)?
(case-fold-search nil))
(while trans-tab
(save-excursion
(let ((trans-this (car trans-tab)))
(regexp-opt trans-this)
^^^^^^^^^^^^^^^^^^^^^^
(while (search-forward (car trans-this) nil t)
(replace-match (car (cdr trans-this)) t t)))
(setq trans-tab (cdr trans-tab))))))
(narrow-to-region beg end)))))
But this did not work neither.
Uwe
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
12:31 a.m.
Uwe Brauer writes:
I am not sure whether I could treat ~ as a string, for example in
the
file latin-ltx.el I see
("\\int" ?~)
For this purpose, the semantics of a character and of a string of
length 1 are the same.
So the question is how shall I define the tex commands uniquely?
Try reordering the strings to be converted longest first.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
2:32 p.m.
>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
Uwe Brauer writes:
> I am not sure whether I could treat ~ as a string, for example in the
> file latin-ltx.el I see
> ("\\int" ?~)
For this purpose, the semantics of a character and of a string of
length 1 are the same.
> So the question is how shall I define the tex commands uniquely?
Try reordering the strings to be converted longest first.
Is
there any command doing this, sort lines seems not.
Uwe
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
8:14 p.m.
Uwe Brauer writes:
>>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
> Uwe Brauer writes:
>> I am not sure whether I could treat ~ as a string, for example in the
>> file latin-ltx.el I see
>> ("\\int" ?~)
> For this purpose, the semantics of a character and of a string of
> length 1 are the same.
>> So the question is how shall I define the tex commands uniquely?
> Try reordering the strings to be converted longest first.
Is there any command doing this, sort lines seems not.
C-h f sort
You'll need to actually read that alist into Lisp, then use a
comparsion function like
(lambda (a b) (< (length (car a)) (length (car b))))
to extract the keys and compare their lengths.
You could also try C-h a ^sort to see if there are other sort
functions better suited to what you need to do.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6193
days inactive
6194
days old
5 comments
3 participants
participants (3)
-
Aidan Kehoe -
Stephen J. Turnbull -
Uwe Brauer