[feature] Macros can't contain accents

[feature] Macros can't contain accents

[Sebastien Vauban]

Hello,

The following macro won't work:

--8<---------------cut here---------------start------------->8---
#+MACRO: max-déductible-remboursement-capital 2120.00

For 2011, the maximum is *{{{max-déductible-remboursement-capital}}} \EUR*.
--8<---------------cut here---------------end--------------->8---

When replacing `é' by `e', it does work.

I don't know if it's a bug, neither if corrective action needs to be taken.
Just signalling it...

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [feature] Macros can't contain accents

[Nicolas Goaziou]

Hello,

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:

> Hello,
>
> The following macro won't work:
>
> #+MACRO: max-déductible-remboursement-capital 2120.00
>
> For 2011, the maximum is *{{{max-déductible-remboursement-capital}}} \EUR*.
>
> When replacing `é' by `e', it does work.
>
> I don't know if it's a bug, neither if corrective action needs to be taken.
> Just signalling it...

Here is the regexp for a macro:

"{{{\\([a-zA-Z][-a-zA-Z0-9_]*\\)\\(([ \t\n]*\\([^\000]*?\\))\\)?}}}"

Its name must start with a letter and can only contain letter, numbers,
hyphens and underscores.  There is the same kind of limitation for
target names and probably other references (custom-id maybe).


Regards,

-- 
Nicolas Goaziou

Re: [feature] Macros can't contain accents

[Nicolas Goaziou]

Hello,

Christian Moe <mail@christianmoe.com> writes:

> Accented and a variety of other non-ascii characters do work in
> targets, IDs and CUSTOM_IDs, in my experience.

Right.

> Org-target-regexp is simply "<<\\([^<>]+\\)>>", so it's not
> picky. Perhaps the same could be done for macros (replacing angle
> brackets with curly braces), without screwing anything up...?

I'd rather do the opposite and restrict them all: this kind of regexp is
slow to parse and there is little gain to allow any character in targets
since they are all invisible now.


Regards,

-- 
Nicolas Goaziou

Re: [feature] Macros can't contain accents

[Christian Moe]

On 6/23/12 10:58 AM, Nicolas Goaziou wrote:

>> Accented and a variety of other non-ascii characters do work in
>> targets, IDs and CUSTOM_IDs, in my experience.
>
> Right.
>
>> Org-target-regexp is simply "<<\\([^<>]+\\)>>", so it's not
>> picky. Perhaps the same could be done for macros (replacing angle
>> brackets with curly braces), without screwing anything up...?
>
> I'd rather do the opposite and restrict them all: this kind of regexp is
> slow to parse and there is little gain to allow any character in targets
> since they are all invisible now.

My user perspective differs: I'm happy to be able to use my 
language(s) freely in Org, even in the invisible bits, and would not 
trade it in for a speedup.

That said, I don't particularly mind the status quo on macros. They're 
code-like, and we're used to ascii restrictions on computer code.

Yours,
Christian