-
Notifications
You must be signed in to change notification settings - Fork 23
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
Different renderings comapared to original marked.js or github style #8
Comments
@McFoggy Thanks for explanation. : )
and rendered results is different from marked.js. |
@takezoe and what do you think about embedding Now that For this specific problem in the java version, I think the Grammer#BLOCK_PARAGRAPH lacks somehow an exclusion for a BLOCK_LIST that could follow ; but modifying those regexp is not very easy. |
@McFoggy markedj is not simply JVM port of marked.js. It is an extendable markdown processor for Java and other JVM based languages. And in my experience, Mustache.js on Nashorn has made memory leak. It was a troublesome problem which makes off-heap leak. So I would like to avoid to introduce Nashorn quickly. I know that maintenance of markedj is much painful. However I think this cost is meaningful to pay for GitBucket and other applications on JVM. |
It makes sense, was just an off proposition in case you did not thought about it. In the past with rhino especially embedding javascript was not a solution for real time but nashorn is far more better now. |
Also, I had some test about nashorn with marked.js. I found that It has some problems compared to rhino. especially wrong translations of regex. And Nashhorn is fast for read but slower for hash input. So I had to back to rhino. |
Marked4j is a kind of your proposal lol |
Hi~ thank you for your markedj lib. : )
I'm trying to use it, but I have found some different rendering results.
Tested strings are
markedJ results is..
github or marked.js rendering is
Message A
Is it bug? or do I use it wrong?
The text was updated successfully, but these errors were encountered: