← Back to team overview

zim-wiki team mailing list archive

Re: Is there an easy way to insert tables into zim?

 

I don't know if this will help you in your case:

I just use tab separated text for tabular data -- easy to read, easy to edit.

If you would enclose the table contents with verbatim formatting, that
would also prevent lines from wrapping.

On Tue, Apr 14, 2009 at 11:21, Svenn Are Bjerkem
<svenn.bjerkem@xxxxxxxxxxxxxx> wrote:
> Hi,
> I am using zim to document FPGA hardware development in VHDL. I am
> looking for a way to insert tables into my text. This does not
> necessarily need to be tables in wiki syntax, I am perfectly happy
> with using an external program to generate a png to include. I could
> use the table function from LaTex, but I do not quite like the syntax
> of LaTex for tables.
>
> The tables that I generate tend to be very wide since I am documenting
> 32-bit registers and then the table will have at least 32 columns and
> 3 to 4 rows. And then one such table for each register in my design.
> Tend to be something like 50 to 100 tables since there are that many
> registers in my design.
>
> I could try to roll my own table generator tool for this kind of use
> and bind it into zim with a plugin (that is actually my preferred
> solution as wiki syntax tables tend to fill a lot of editor space
> without adding information) But I wanted to throw in a question here
> in case somebody else have done something similar.
>
> --
> Svenn
>
> _______________________________________________
> Mailing list: https://launchpad.net/~zim-wiki
> Post to     : zim-wiki@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Emilis Dambauskas

emilis.d@xxxxxxxxx
gsm: +370-686-07732
irc: emilis_info@xxxxxxxxxxxxxxxx
http://emilis.info

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT/CC/MC/O dpu(-) s:- a- C++ UBLHS++ P(+) L+++ E--- W+++$ N+ o-- K?
!w O? M-@ V? PS+(--) PE Y+>++ PGP t- 5? X+@ R- !tv b+ DI++++ D G e++
h---- r+++ y++++
------END GEEK CODE BLOCK------



Follow ups

References