Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Table fields not trimmed #11

Open
pinard opened this issue Mar 31, 2014 · 0 comments
Open

Table fields not trimmed #11

pinard opened this issue Mar 31, 2014 · 0 comments

Comments

@pinard
Copy link
Contributor

pinard commented Mar 31, 2014

Hi, Masafumi.

Given this input:

#+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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant