Github user cloverhearts commented on the issue:

    https://github.com/apache/zeppelin/pull/2509
  
    @Leemoonsoo 
    
    ## Original Markdown
    ```
    --------  -----------------------
    keyword   text
    --------  -----------------------
    red       Sunsets, apples, and
              other red or reddish
              things.
    
    green     Leaves, grass, frogs
              and other things it's
              not easy being.
    --------  -----------------------
    ```
    
    ## Jupyter
    ```
    <hr>
    <p>keyword text</p>
    <p>
      red       Sunsets, apples, and
      other red or reddish
      things.
    </p>
    <p>
      green     Leaves, grass, frogs
      and other things it's
      not easy being.
    </p>
    <hr>
    ```
    ## Pagedown
    ```
    <p>
      keyword text<br>
      ——– ———————–<br>
      red Sunsets, apples, and<br> 
      other red or reddish<br> things.
    </p>
    ```
    
    ## Markdown4j
    ```
    <hr>
    <h2>keyword   text</h2>
    <p>red       Sunsets, apples, and</p>
    <pre><code class="hljs vim">      other <span 
class="hljs-keyword">red</span> <span class="hljs-built_in">or</span> reddish
          things.
    </code></pre>
    <p>green     Leaves, grass, frogs</p>
    <pre>
      <code class="hljs ada">      
        <span class="hljs-keyword">and</span> other things it<span 
class="hljs-symbol">'s</span>
        <span class="hljs-keyword">not</span> easy being.
      </code>
    </pre>
    <hr>
    ```
    
    I did some testing.
    And some of the Markdown documents I used as samples
    Sometimes there are grammars close to exceptions.
    
    When I checked in jupyter,
    If you try to apply a syntax close to the exception,
    The structure of the changed html document is most similar to Markdown4j.
    (actually, some element is little different)
    If the structure of the document is similar, it is easy to implement the 
same experience as Jupyter in `LooknFeel`, so I chose Markdown4j which showed 
the most similar results.
    
    one problem is that if you run the markdown paragraph with the default 
interpreter,
    some results may look different.
    
    What do you think?
    



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to