Re: Issues with japanese support
Ralf Angeli <[email protected]>
| Newsgroups | gmane.emacs.auc-tex |
|---|---|
| Message-ID | <[email protected]> |
* Masayuki Ataka (2005-02-18) writes:
>> It would be good to use something like the value of
>> `word-across-newline' in the regular expression,
>> i.e. "\\(\\cj\\|\\cc\\|\\ct\\)\n\\(\\cj\\|\\cc\\|\\ct\\)". If the
>> variable `word-across-newline' should be used, one somehow will have
>> to silence the byte compiler.
>
> To define `LaTeX-nospace-between-char-regexp' looks good to me.
>
> (defcustom LaTeX-nospace-between-char-regexp
> (when (featurep 'mule)
> (if (boundp 'word-across-newline)
> word-across-newline
> "\\c|"))
Hm, it is a bit dangerous to have a value of nil here because the code
in `LaTeX-fill-delete-newlines' could then match only "\n". Of course
this is very unlikely to happen because there is a test for mule as
well. But if we suppose that somebody removes that test without
looking at `LaTeX-nospace-between-char-regexp' this could lead to
problems.
How about the following?
(if (featurep 'xemacs)
(if (boundp 'word-across-newline)
word-across-newline
"\\cj\\|\\cc\\|\\ct")
"\\c|")
> "Regular expression of such characters which can be a word across newline."
This does not refer to the variables's name. Maybe the following is a
bit clearer:
"Regexp matching a character where no interword space is necessary.
Words formed by such characters can be broken across newlines."
> :group 'LaTeX
> :type 'regexp)
>
> # Where to put it?
> # After `;;; Filling' ?
Yes.
--
Ralf