From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel Clemente" Subject: Re: Bug with Unicode text on properties Date: Sat, 1 Sep 2007 22:30:20 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IRZbs-000628-Jf for emacs-orgmode@gnu.org; Sat, 01 Sep 2007 16:30:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IRZbq-00061v-NK for emacs-orgmode@gnu.org; Sat, 01 Sep 2007 16:30:23 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IRZbq-00061k-D6 for emacs-orgmode@gnu.org; Sat, 01 Sep 2007 16:30:22 -0400 Received: from fk-out-0910.google.com ([209.85.128.184]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IRZbq-0006kG-28 for emacs-orgmode@gnu.org; Sat, 01 Sep 2007 16:30:22 -0400 Received: by fk-out-0910.google.com with SMTP id 19so1228680fkr for ; Sat, 01 Sep 2007 13:30:20 -0700 (PDT) In-Reply-To: Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: emacs-orgmode@gnu.org 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 =84non-portable" nowadays (it works everywhere on the Internet and operating systems). Even if =84there 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. Greetings, Daniel