From: Carsten Dominik <dominik@science.uva.nl>
To: Daniel Clemente <n142857@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug with Unicode text on properties
Date: Sun, 2 Sep 2007 19:55:55 +0200 [thread overview]
Message-ID: <f8231115a776c7f37880dd7917718aa4@science.uva.nl> (raw)
In-Reply-To: <ae9590aa0709011330s67af95abq5d0239601670109a@mail.gmail.com>
On Sep 1, 2007, at 22:30, Daniel Clemente wrote:
> Hi,
>
>>
>> There are two issues here:
>>
>> 1. You are also using a dash-like character, \o4255. The Emacs
>> [:alnum:] class
>> does not match this, therefore this character will continue not
>> to be
>> recognized. Use the underscore in property names, I am supporting
>> this.
>
> Mmm... I used the normal underscore, _ (95, #o137, #x5f, U+005F). I
> don't find \o4255.
>
>>
>> 2. Think twice before using non-ascii characters in property names.
>> This will make you file non-portable. If you send it to someone
>> living in a different locale, he/she might find the file broken.
>>
> ASCII doesn't work with my language (ex: Spanish); therefore I
> don't use it.
> But what I used is Unicode, and I wouldn't call it „non-portable"
> nowadays (it works everywhere on the Internet and operating systems).
> Even if „there can be programs which don't support Unicode", that's
> not a reason to not using Unicode; what we must do --in my opinion--
> is fix the programs.
I agree, but it is a fact that text you sent me did not look at all
like spanish, but pretty much garbled.
Anyway, 5.08 will allow [[:alnum:]-_] for properties.
- Carsten
next prev parent reply other threads:[~2007-09-02 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-01 1:42 Bug with Unicode text on properties Daniel Clemente
2007-09-01 10:29 ` Carsten Dominik
2007-09-01 20:30 ` Daniel Clemente
2007-09-02 17:55 ` Carsten Dominik [this message]
2007-09-02 21:42 ` William Henney
2007-09-03 7:26 ` Carsten Dominik
2007-09-03 16:08 ` William Henney
2007-09-03 16:20 ` Daniel Clemente
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f8231115a776c7f37880dd7917718aa4@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=n142857@gmail.com \
/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/org-mode.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).