make sure you have space in .proto, if you want it in separate line , you need to something like this

/**

• Hello COmment in line1
• this is in line 2
  */

@sumancholleti This workaround is not practical as it impairs the readability of documentation comments in the .proto file.

I've just played around with v0.1.0-rc and the problem still exists. The parser should work similar to documentation generators such as javadoc and doxygen, i.e. a line break without a separating blank line does not cause:

1. a line break in the generated documentation (tested with HTML).
2. does not concat the lines together as described by @sumancholleti (tested with Markdown)

Only two line breaks, i.e. an additional blank line should cause a line break in the output format, imho.

I've not tested it with other output formats.

Sadly the current behavior makes the tool completely unusable for me, since I have to deal with a lot of documentation.

For me its even worse. The breakline is not being handled in markdown tables:

In both ways, the generated table is incorrect, I can't have a new line between my documentation text. @pseudomuto may you give a look? Issue since 2017 haha I will try to check if I can fix but I don't know when I will available.

You can replace all new lines in you template with html line breaks

"ProtoBuiltinTypes" $ProtoBuiltinTypes) -}} | {{ regexReplaceAll "\n" $Description "${1}<br/>" }}

I think @lucasoares's solution is the right one, and it'd be great if their PR could get merged. Only double newlines should be converted to <br><br>. If you convert all line breaks, then you will force the hard word wraps of long proto comments into the output HTML, which would not be ideal. Converting only double newlines is how markdown generally works.