<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><span style="font-family:Arial,Helvetica,sans-serif">On Tue, Feb 27, 2024 at 2:31 PM Mark Reinhold <<a href="mailto:mark.reinhold@oracle.com">mark.reinhold@oracle.com</a>> wrote:</span><br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><a href="https://openjdk.org/jeps/467" rel="noreferrer" target="_blank">https://openjdk.org/jeps/467</a><br>
<br>
  Summary: Enable JavaDoc documentation comments to be written in<br>
  Markdown rather than solely in a mixture of HTML and JavaDoc @-tags.<br></blockquote></div><span class="gmail_signature_prefix"><div><span class="gmail_signature_prefix"><br></span></div><div><span class="gmail_signature_prefix">I<span class="gmail_default" style="font-family:arial,helvetica,sans-serif"> read through this and I didn't notice any mention of how this would integrate with existing doc interfaces in the annotation processing API (Elements#getDocComment)? It would be great to be able to acquire at least the raw text if not the processed Markdown during annotation processing. It would also be good to be able to know what kind of doc text is being returned (Markdown vs HTML).</span></span></div><div><span class="gmail_signature_prefix"><span class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></span></span></div>-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr">- DML • he/him<br></div></div></div>