Skip to content
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

sequence of <em>'s is mis-rendered in some cases. #33

Closed
leeoniya opened this issue Feb 17, 2012 · 2 comments
Closed

sequence of <em>'s is mis-rendered in some cases. #33

leeoniya opened this issue Feb 17, 2012 · 2 comments

Comments

@leeoniya
Copy link

by itself,

#### *expression<sub>1</sub>* *expression<sub>2</sub>* ... *expression<sub>n</sub>*

renders correctly as

<h4><em>expression<sub>1</sub></em> <em>expression<sub>2</sub></em> ... <em>expression<sub>n</sub></em></h4>

but in the context of https://raw.github.com/dmajda/pegjs/master/README.md renders as

<h4><em>expression<sub>1</sub></em> / <em>expression<sub>2</sub></em> / ... / <em>expression<sub>n</sub></em></h4>

maybe a parser issue?
thanks!

@chjj
Copy link
Member

chjj commented Feb 18, 2012

I think you're looking at it wrong. This is probably best explained by some commandline examples.

$ marked readme.md | grep sub
...
<h4><em>expression<sub>1</sub></em> <em>expression<sub>2</sub></em> ... <em>expression<sub>n</sub></em></h4>
<h4><em>expression<sub>1</sub></em> / <em>expression<sub>2</sub></em> / ... / <em>expression<sub>n</sub></em></h4>

$ cat readme.md | grep sub
...
#### *expression<sub>1</sub>* *expression<sub>2</sub>* ... *expression<sub>n</sub>*
#### *expression<sub>1</sub>* / *expression<sub>2</sub>* / ... / *expression<sub>n</sub>*

There are two separate locations for that heading. One has slashes, one doesn't.

@leeoniya
Copy link
Author

oh, woops, sry. closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants