<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1433985009719_526134" dir="ltr">The conventions (https://wiki.openstack.org/wiki/Documentation/Markup_conventions#Avoid_long_lines)</div><div id="yui_3_16_0_1_1433985009719_526200" dir="ltr">specify a maximum 70 characters per line; currently, checkniceness balks at anything longer than 69 chars.</div><div id="yui_3_16_0_1_1433985009719_526251" dir="ltr"><br></div><div id="yui_3_16_0_1_1433985009719_526288" dir="ltr">I think the recommendation should be 80 chars rather than 70 -- it just seems more "natural" somehow</div><div id="yui_3_16_0_1_1433985009719_526402" dir="ltr">and is still short enough for gerrit displays.</div><div id="yui_3_16_0_1_1433985009719_526206" dir="ltr"><br></div><div id="yui_3_16_0_1_1433985009719_526124" dir="ltr">Personally, I favor short lines, broken along natural semantic boundaries (sentences, clauses) rather than</div><div id="yui_3_16_0_1_1433985009719_526208" dir="ltr">using the vi facility to just wrap the text arbitrarily but that may be too much for some people.</div><div id="yui_3_16_0_1_1433985009719_526269" dir="ltr"><br></div><div id="yui_3_16_0_1_1433985009719_526253" dir="ltr">checkniceness does allow for programlistings/screens and URLs but it doesn't differentiate tables and I'm</div><div id="yui_3_16_0_1_1433985009719_526210" dir="ltr">not sure it can. For this reason, I propose that the checkniceness limit be expanded, perhaps to 100. As</div><div id="yui_3_16_0_1_1433985009719_526212" dir="ltr">an example, check the table in this section:</div><div id="yui_3_16_0_1_1433985009719_526216" dir="ltr"><br></div><div id="yui_3_16_0_1_1433985009719_526214" dir="ltr"><a id="yui_3_16_0_1_1433985009719_526219" href="https://review.openstack.org/#/c/188974/8/doc/ha-guide/source/networking-ha-l3.rst">https://review.openstack.org/#/c/188974/8/doc/ha-guide/source/networking-ha-l3.rst</a></div><div dir="ltr"><br></div><div id="yui_3_16_0_1_1433985009719_526415" dir="ltr">The first column has some long strings that shouldn't be broken, so I ended up with a third column of 2-4 words,</div><div id="yui_3_16_0_1_1433985009719_526443" dir="ltr">which is annoying and would make it impossible to put a URL or even a full pathname in that column.</div><div id="yui_3_16_0_1_1433985009719_526417" dir="ltr">Worse, after I made these changes, the column widths in the formatted table are not correct -- the first column</div><div id="yui_3_16_0_1_1433985009719_526419" dir="ltr">ends up being much wider than is necessary and the third column has pretty much the very short lines that are</div><div id="yui_3_16_0_1_1433985009719_526427" dir="ltr">in the source.</div><div id="yui_3_16_0_1_1433985009719_526456" dir="ltr"><br></div><div id="yui_3_16_0_1_1433985009719_526474" dir="ltr">In the aforementioned CR, look at patch 5 or earlier to see this table before I had to redo it to placate</div><div dir="ltr">checkniceness. <br></div><div dir="ltr"><br></div><div dir="ltr">Other opinions?</div><div id="yui_3_16_0_1_1433985009719_526489" dir="ltr">Meg<br></div><div style="" class="" id="yui_3_16_0_1_1433985009719_526214" dir="ltr"><br style="" class=""></div></div></body></html>