From: Dave Love <fx@gnu.org>
To: "Ernest Adrogué" <eadrogue@gmx.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: changing word boundaries
Date: Sun, 01 Nov 2009 19:09:53 +0000 [thread overview]
Message-ID: <87ljiqcb9a.fsf@fx-laptop.ukfsn.org> (raw)
In-Reply-To: mailman.9059.1255887881.2239.help-gnu-emacs@gnu.org
Ernest Adrogué <eadrogue@gmx.net> writes:
> Hi there,
>
> The Catalan language has a ligature consisting in one
> "l" character, followed by a middle dot ("·"), followed
> by another "l". See here for more details:
> http://en.wikipedia.org/wiki/L·l#Catalan
>
> Is there a way to make emacs aware of this, so that it
> doesn't treat a word containing "l·l" as two separate
> words?
[You're probably not really interested in word boundaries, just word
constituents. For an illustration of the difference, see variable
`word-combining-categories' and what capitalized-words-mode does in
Emacs 23.]
You should define a Catalan language environment to be used in ca_ES
locales. (I'm surprised I didn't do it, as there's a relevant input
method.) It should set the base syntax of · to word, and set a suitable
default input method. The existing one, `catalan-prefix', should
presumably bind `~.' to `·', as in latin-prefix; it doesn't currently,
and maybe needs other fixes.
The environment would be something like this (untested), which is
probably better then trying to use categories. [The default Latin-1
character set is overridden in, say, ca_ES.UTF-8.]
(push '("ca" . "Catalan") locale-language-names)
(set-language-info-alist
"Catalan" '((tutorial . "TUTORIAL.es") ; maybe...
(charset iso-8859-1)
(coding-system iso-latin-1 iso-latin-9)
(coding-priority iso-latin-1)
(input-method . "catalan-prefix")
(nonascii-translation . iso-8859-1)
(unibyte-display . iso-latin-1)
(setup-function
. (lambda ()
(modify-syntax-entry ?· "w" (standard-syntax-table))))
(exit-function
. (lambda ()
(modify-syntax-entry ?· "_" (standard-syntax-table))))
;; Fixme:
;; (sample-text . "Spanish (Español) ¡Hola!")
(documentation . "\
This language environment uses the Latin-1 character set, sets
the default input method to \"catalan-prefix\", and sets the
syntax of `·' to word. It selects the Spanish tutorial, in the
absence of a Catalan translation."))
'("European"))
You could make a bug report if you have more luck than me with reports
about stuff I worked on.
next parent reply other threads:[~2009-11-01 19:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.9059.1255887881.2239.help-gnu-emacs@gnu.org>
2009-11-01 19:09 ` Dave Love [this message]
2009-11-08 17:07 ` changing word boundaries Ernest Adrogué
2009-11-11 14:57 ` Kevin Rodgers
2009-10-18 16:27 Ernest Adrogué
2009-10-18 19:24 ` Peter Dyballa
2009-10-18 21:19 ` Ernest Adrogué
2009-10-18 21:08 ` Andreas Politz
2009-10-20 0:06 ` Ernest Adrogué
[not found] ` <mailman.9139.1255997204.2239.help-gnu-emacs@gnu.org>
2009-11-01 19:10 ` Dave Love
2009-10-18 21:09 ` Andreas Politz
[not found] ` <mailman.9065.1255893858.2239.help-gnu-emacs@gnu.org>
2009-11-01 19:15 ` Dave Love
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=87ljiqcb9a.fsf@fx-laptop.ukfsn.org \
--to=fx@gnu.org \
--cc=eadrogue@gmx.net \
--cc=help-gnu-emacs@gnu.org \
/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.
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).