CASE: different table structures

You can have different table structures within Silverfin, as you can see below:

The code to generate this all:

{% comment %}GREY header -- table A{% endcomment %}
{% stripnewlines %}
| Header A
| Header B
| Header C
| Header D
{% newline %}
|:----25%----:
|:----25%----:
|:----25%----:
|:----25%----:#
{% newline %}
| content
| content
| content
| content
{% endstripnewlines %}

<br>

{% comment %}GREY SELECTED header -- table B{% endcomment %}
{% stripnewlines %}
|:----25%----:
|:----25%----:
|:----25%----:
|:----25%----:#
{% newline %}
| Header A
| Header B
| Header C
| Header D
{% newline %}
| content
| content
| content
| content
{% endstripnewlines %}

<br>

{% comment %}BLACK LINE header -- table C{% endcomment %}
{% stripnewlines %}
| Header A
| Header B
| Header C
| Header D
{% newline %}
|:----25%----:
|:----25%----:
|:----25%----:
|:----25%----:+
{% newline %}
| content
| content
| content
| content
{% endstripnewlines %}

<br>

{% comment %}NO BLACK LINE header -- table D{% endcomment %}
{% stripnewlines %}
|:----25%----:
|:----25%----:
|:----25%----:
|:----25%----:+
{% newline %}
| Header A
| Header B
| Header C
| Header D
{% newline %}
| content
| content
| content
| content
{% endstripnewlines %} 

Now, the grey headers are be-au-ti-ful but you probably won’t have them in PDF export. Luckily, there’s a way to avoid that.

So in input-mode you’ll have this:

In export this:

This is how you can do it:

{% comment %}have the GREY header in INPUT, while having the BLACK LINE header in export{% endcomment %}
{% comment %}GREY header{% endcomment %}
{% stripnewlines %}
| Header A
| Header B
| Header C
| Header D
{% newline %}
|:----25%----:
|:----25%----:
|:----25%----:
|:----25%----:
{% ic %}#{% endic %}  {% comment %}shows GREY header in INPUT mode{% endcomment %}
{% nic %}+{% endnic %}{% comment %}shows BLACK LINE header in OUTPUT mode{% endcomment %}
{% newline %}
| content
| content
| content
| content
{% endstripnewlines %}