aboutsummaryrefslogtreecommitdiffstats
path: root/docs/writing_extensions.txt
diff options
context:
space:
mode:
authorWaylan Limberg <waylan@gmail.com>2010-09-20 14:45:52 -0400
committerWaylan Limberg <waylan@gmail.com>2010-09-20 14:45:52 -0400
commite4993fc56dd222c9b11fc96b1044e39f84e4544f (patch)
tree1737ed04ccf36e467f6744cda5e8d775726eeabf /docs/writing_extensions.txt
parent5ee12763465d123a313d43fc0fb497636f727d34 (diff)
downloadmarkdown-e4993fc56dd222c9b11fc96b1044e39f84e4544f.tar.gz
markdown-e4993fc56dd222c9b11fc96b1044e39f84e4544f.tar.bz2
markdown-e4993fc56dd222c9b11fc96b1044e39f84e4544f.zip
Added the re.UNICODE flag to inlinepatterns. Now all inlinepattern regex will match unicode characters when \w, \b, or \s is used. Also updated docs to reflect change.
Diffstat (limited to 'docs/writing_extensions.txt')
-rw-r--r--docs/writing_extensions.txt7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/writing_extensions.txt b/docs/writing_extensions.txt
index 1300d55..2ecd4c9 100644
--- a/docs/writing_extensions.txt
+++ b/docs/writing_extensions.txt
@@ -80,9 +80,10 @@ Note that any regular expression returned by ``getCompiledRegExp`` must capture
the whole block. Therefore, they should all start with ``r'^(.*?)'`` and end
with ``r'(.*?)!'``. When using the default ``getCompiledRegExp()`` method
provided in the ``Pattern`` you can pass in a regular expression without that
-and ``getCompiledRegExp`` will wrap your expression for you. This means that
-the first group of your match will be ``m.group(2)`` as ``m.group(1)`` will
-match everything before the pattern.
+and ``getCompiledRegExp`` will wrap your expression for you and set the
+`re.DOTALL` and `re.UNICODE` flags. This means that the first group of your
+match will be ``m.group(2)`` as ``m.group(1)`` will match everything before the
+pattern.
For an example, consider this simplified emphasis pattern: