Table export to html

[fuadlabgit]

Description

The table editor looks awesome but there seem to be some minor bugs when the table is changed. If I export to html (I also have some short TeX code in my table and also want to include references), the formatting is not always updated. maybe its I dont know what I should do to make it work... I just make the table (it looks nice in Zettlr). on export, the table looks different (?). It might also be because Zettlr does something weird to the "" letter.

Reproducing

In Git the table also looks nice:

Parameter	Value	Description
$\theta_{CX}$	0.5	share of labor
$\theta_{CZ}$	0.5	share of leisure
$\alpha_{TZ}$	0.5	leisure parameter of household
$\alpha_{TL}$	0.5	leisure/labor parameter of household
$\theta_{XV}$	0.97	share of value added in the $X$ sector
$\theta_{XS}$	0.096	cost share of energy services in the $X$ sector
$\theta_{VL}$	0.5	cost share of labor in value added sector
$\theta_{VK}$	0.5	cost share of capital in value added sector
$\alpha_X$	0.97	share of capital in $X$ sector
$\alpha_E$	0.03	share of capital in $E$ sector
$\sigma_X$	0.5	elasticity in $X$ sector between value added and services (Ballard 2000)
$\sigma_C$	0.4	elasticity between consumption and leisure
$\sigma_V$	0.5	elasticity between labor and capital

Zettlr Version

Stable (most recent version)

Specify version

2.3.0

Installation Method

From the Website or GitHub

Your Platform

• [X] Windows
• [ ] macOS
• [ ] Linux

Architecture

• [X] Intel 64bit
• [ ] ARM 64bit

Operating System Version

Windows 11

Additional Information

Doesnt seem to be a matter of windows version

[boring-cyborg[bot]]

Thanks so much for opening up your first issue here on the repository! 🎉 We would like to warmly welcome you to the community behind the app! ☺️ We'll check in soon and have a look at your issue. In the meantime, you can check your issue and make sure it aligns with our contribution guidelines! Here's the comprehensive list:

Enhancements

An enhancement takes a feature and improves or alters its behaviour. Please make sure to argue how your proposition will aid non-technical text workers, and why it can't be emulated easily with other features or apps!

Feature requests

Feature requests introduce whole new features into the app. This requires a lot of work, so these might be turned down if the implementation costs supersede the benefits we expect to see from implementing it. Please do not be disappointed if that happens. It likely has nothing to do with your great request but simply with us and our missing resources! You can of course always ask someone to implement this feature, because a PR with a working new feature has much higher chances of being merged! :)

Bug reports

Please note that one of the main reasons for why bug reports cannot be addressed is that there's not enough information for us to find and fix the bug you describe, so make sure you try to pinpoint the bug as close as possible. The ideal bug report for us has two qualities:

1. The bug is always reproducible, at least within a certain context. 2. We know exactly what specifically goes wrong, and there is consensus on what should happen instead.

Please note that if you encounter behaviour that does not align with your expectations of what would happen, this might as well be simply intended behaviour and we need to simply clarify why the behaviour is the way it is. This is not to be considered a bug and such issues may be closed! Suggest an enhancement instead! But now, have a great day and thank you again!

[nathanlesage]

Could be a problem with the Pandoc export? There is, for example, the issue that for Pandoc the lengths of the columns actually has a meaning, and it tends to produce weird looking tables if you have too much content in the cells. It's a tad difficult to implement, but I'll see to it later. (Or someone else with time can surely open a PR)

[nathanlesage]

I just tested this out - works as expected, so the bug possibly got fixed along the way!