๐Ÿ’พ Archived View for station.martinrue.com โ€บ acidus โ€บ 2167eb3da2a84864980d3f706454f016 captured on 2024-07-08 at 23:48:42. Gemini links have been rewritten to link to archived content

View Raw

More Information

โฌ…๏ธ Previous capture (2024-05-26)

๐Ÿšง View Differences

-=-=-=-=-=-=-

๐Ÿ‘ฝ acidus

If you want to have tables in your gemtext, just burn them in:

gemini://gemi.dev/gemlog/2023-06-30-tables-in-gemtext.gmi

1 year ago ยท ๐Ÿ‘ sugar, tm85, jsreed5, danrl, mozz, gritty

Links

gemini://gemi.dev/gemlog/2023-06-30-tables-in-gemtext.gmi

Actions

๐Ÿ‘‹ Join Station

2 Replies

๐Ÿ‘ฝ danrl

we need to embrace the simplicity of gemini and not make it a do-it-all. burned in tables work just fine.

however, if clients want to render, they still can. a somewhat good heuristic can detect the most popular types of burned in tables and offer to render them differently. works for most cases, which is good enough. gemini is a lot about good enough and less about perfection. ยท 1 year ago

๐Ÿ‘ฝ jsreed5

I took this exact approach when I needed to render a table in one of my math articles: gemini://jsreed5.org/math/20220302-generating-crossed-ladders/ ยท 1 year ago

gemini://jsreed5.org/math/20220302-generating-crossed-ladders/