Re: why is UNICODE space after literal markup (``) invalid, but after emphasis(*) or strong(**) ok?
Guenter Milde <[email protected]>
| Newsgroups | gmane.text.docutils.user |
|---|---|
| Message-ID | <[email protected]> |
Dear log4yes, thank you for the bug report and analysis. On 2016-12-19, log4yes wrote: > Hi, does anyone know that? For example, r"**a**\u2002b" is valid but > r"``a``\u2002b" will generate a warnning message. \u2002 is a whitespace. > I've checked the source code. Docutils uses regular expression to search > the end of inline markups. It compiles STRONG regex with re.UNICODE > option, so it matches the UNICODE space. But why doesn't it use the same > option with LITERAL regex? > Is here a mistake of implementation? Is there something specially different? It is an omission that hithero slipped our attention and tests. I prepared a patch that will be at the repository soon. Thanks, Günter ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Docutils-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/docutils-users Please use "Reply All" to reply to the list.