mocobeta opened a new pull request, #20:
URL: https://github.com/apache/lucene-jira-archive/pull/20

   The default `Quote` and `BlockQuote` implementation of `jira2markdown` does 
not preserve indents; due to that, the following paragraph is mistakenly 
interpreted as also part of the quotation in markdown.
   
   **bq. quote**
   
   broken indent example:
   ![Screenshot from 2022-07-09 
14-51-20](https://user-images.githubusercontent.com/1825333/178093546-cfeb3e0e-20eb-4c00-b7b2-449708ec79e1.png)
   
   with this patch:
   ![Screenshot from 2022-07-09 
14-56-23](https://user-images.githubusercontent.com/1825333/178093677-4c40d91b-9f2d-4d7e-ab49-7b4bf2acf60f.png)
   
   **{quote} quote block**
   
   broken indent example:
   ![Screenshot from 2022-07-09 
14-58-20](https://user-images.githubusercontent.com/1825333/178093745-0df61545-2b0b-4d39-b453-e3d24f14bc3d.png)
   
   with this patch:
   ![Screenshot from 2022-07-09 
14-59-58](https://user-images.githubusercontent.com/1825333/178093795-e7241428-9716-4e92-9f0c-d0beb69869d2.png)
   
   This also escapes numbered lists in block quotes so that the number is 
preserved.
   
   error example (a block quote include a numbered list):
   ![Screenshot from 2022-07-09 
15-01-58](https://user-images.githubusercontent.com/1825333/178093851-64a4d60e-f5c7-4938-a494-f8afccc29b98.png)
   
   with this patch:
   ![Screenshot from 2022-07-09 
15-03-15](https://user-images.githubusercontent.com/1825333/178093867-c401fbac-70a3-43fe-b662-642d294fd20a.png)
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to