Re: Org markup and non-ASCII punctuation (was: org parser and priorities of inline elements)

2023-07-18 Thread Ihor Radchenko
Tom Gillespie writes: >> We might probably generalize to >> PRE = Zs Zl Pc Pd Ps Pi ' " >> POST = Zs Zl Pc Pd Pe Pf . ; : ! ? ' " \ [ > > If this works I think it is reasonable. We might want to > specify what to do in cases where an org implementation > might not fully support unicode, Just

Re: Org markup and non-ASCII punctuation (was: org parser and priorities of inline elements)

2023-07-17 Thread Tom Gillespie
> We might probably generalize to > PRE = Zs Zl Pc Pd Ps Pi ' " > POST = Zs Zl Pc Pd Pe Pf . ; : ! ? ' " \ [ If this works I think it is reasonable. We might want to specify what to do in cases where an org implementation might not fully support unicode, and might want to do a review of related

Re: Org markup and non-ASCII punctuation (was: org parser and priorities of inline elements)

2023-07-17 Thread Ihor Radchenko
Tom Gillespie writes: > The way I have implemented this is by maintaining an explicit list of > characters that are safe for pre markup and another for post markup. > > It is not possible to use unicode punctuation for this because there > are a variety of punctuation marks that cannot appear in

Re: Org markup and non-ASCII punctuation (was: org parser and priorities of inline elements)

2023-07-17 Thread Tom Gillespie
Hi Ihor, Thank you for looping me in. Best, Tom The way I have implemented this is by maintaining an explicit list of characters that are safe for pre markup and another for post markup. It is not possible to use unicode punctuation for this because there are a variety of punctuation marks