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
> 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
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
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
Max Nikulin writes:
> On 21/11/2021 16:28, Ihor Radchenko wrote:
>>
>> Also, is there any reason why we are not simply using punctuation
>> character class instead of listing punctuation chars explicitly (and
>> only for English)? What about "_你叫什么名字_？"
>
> It seems punctuation character class
