Permalink
Browse files

Markdown with @cond and @endcond

In case markdown files are processed and they contain @cond and @endcond these are replaced wit C-style end and begin comments (and code in between is correctly removed). The C-Style comments should not be placed as they are not understood in a markdown context (analogous to what happens in Fortram, Pythone etc.).
Note: in principle @cond should not be used as a markdown file is one "comment" block and thus @if should be used, though in any case no unwanted characters should be added.
  • Loading branch information...
albert-github committed Nov 14, 2015
1 parent e2dd835 commit dc26830396970d402ad42d20f1b99bd86f4a5961
Showing with 2 additions and 0 deletions.
  1. +2 −0 src/commentcnv.l
@@ -781,6 +781,7 @@ void replaceComment(int offset);
//printf("** Adding start of comment!\n");
if (g_lang!=SrcLangExt_Python &&
g_lang!=SrcLangExt_VHDL &&
g_lang!=SrcLangExt_Markdown &&
g_lang!=SrcLangExt_Fortran)
{
ADDCHAR('/');
@@ -800,6 +801,7 @@ void replaceComment(int offset);
{
if (g_lang!=SrcLangExt_Python &&
g_lang!=SrcLangExt_VHDL &&
g_lang!=SrcLangExt_Markdown &&
g_lang!=SrcLangExt_Fortran)
{
ADDCHAR('*');

0 comments on commit dc26830

Please sign in to comment.