-
-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make begemph and endemph more intelligent #1002
Comments
This further harmonizes the behavior and further simplifies the code. The new noemphchars can be used to achieve the old behavior. Related to #1002.
This further harmonizes the behavior and further simplifies the code. The new noemphchars can be used to achieve the old behavior. Related to #1002.
This further harmonizes the behavior and further simplifies the code. The new noemphchars can be used to achieve the old behavior. Related to #1002.
This further harmonizes the behavior and further simplifies the code. The new noemphchars can be used to achieve the old behavior. Related to #1002.
This further harmonizes the behavior and further simplifies the code. The new noemphchars can be used to achieve the old behavior. Related to #1002.
This further harmonizes the behavior and further simplifies the code. The new noemphchars can be used to achieve the old behavior. Related to #1002.
Fixed by #1006. This new paragraph in the documentation (6039326) summarizes how the behavior of begemph/endemph changed:
|
This further harmonizes the behavior and further simplifies the code. The new noemphchars can be used to achieve the old behavior. Related to #1002.
begemph
andendemph
should behave a bit more like the phrase indicators when it comes to determining the beginning and end of the emphasized passage. This means by default emphasis on non-letters should be ignored, and if defined, the newnoemphchars
(#905) should be taken into account.emphmodechars
should not be taken into account, this is strictly a word scope thing.The text was updated successfully, but these errors were encountered: