You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#+TITLE: OK
| A | BBBBBBBBBBB |
| CCCCCCCCCC | D |
org-js produces:
<h1>OK</h1>
<ul></ul>
<table><tbody><tr><td> A </td>
<td> BBBBBBBBBBB </td>
</tr>
<tr><td> CCCCCCCCCC </td>
<td> D </td>
</tr>
</tbody>
</table>
As you may see, there is spurious whitespace in the generated HTML, which is not meaningful to HTML. My suggestion would be that org-js trim all fields which are going into HTML tables.
In some of the Org files I handle with org-js, there are tables with fairly wide columns (because of big link markup), and the generated HTML gets rather ugly because of all this whitespace. This is not a very serious issue as it does not prevent the table to display correctly in browsers; it is just that it makes the generated HTML less interesting to visit. :-)
François
P.S. On the other side of the fence, I noticed that the <table> tag does not always start on a new line in the generated HTML, it sometimes get bundled at the end of the preceding line, which is not nice HTML in my opinion. Once again, this does not prevent correct display in browsers. org-js could still try to produce nicer HTML.
The text was updated successfully, but these errors were encountered:
Hi, Masafumi.
Given this input:
org-js produces:
As you may see, there is spurious whitespace in the generated HTML, which is not meaningful to HTML. My suggestion would be that org-js trim all fields which are going into HTML tables.
In some of the Org files I handle with org-js, there are tables with fairly wide columns (because of big link markup), and the generated HTML gets rather ugly because of all this whitespace. This is not a very serious issue as it does not prevent the table to display correctly in browsers; it is just that it makes the generated HTML less interesting to visit. :-)
François
P.S. On the other side of the fence, I noticed that the
<table>
tag does not always start on a new line in the generated HTML, it sometimes get bundled at the end of the preceding line, which is not nice HTML in my opinion. Once again, this does not prevent correct display in browsers. org-js could still try to produce nicer HTML.The text was updated successfully, but these errors were encountered: