4 ms·
Tabular data isn't hard, | Type | Host/Name | Value/Points to | | ----- | ------------- | ------------------------------- | |
by Jiocus 3y ago
Tabular data isn't hard,
| Type | Host/Name | Value/Points to |
| ----- | ------------- | ------------------------------- |
| CNAME | s1._domainkey | s1._domainkey.example.com |
| CNAME | s2._domainkey | s2._domainkey.example.com |
| TXT | _dmarc | v=DMARC1; p=quarantine; adkim=s |
Even .csv formatted stuff fares OK in plaintext.
But I agree with you on context and having data visible right there in the email. It's often the case that people forgo using email as the functional communication technology it is and settles with attachments only and the canned byline.
I want to see full markdown, mermaid and the like in email.
- notRobot 3y ago1. Tabular data in ASCII like that is really bad for accessibility 2. It looks terrible on mobile: https://i.imgur.io/ovzaJDG_d.webp?maxwidth=640&shape=thumb&fidelity=medium https://i.imgur.io/ovzaJDG_d.webp?maxwidth=640&shape=thumb&f...
- Jiocus 3y agoYou both have a point, but this formatting issue is because HN doesn't use `overflow: scroll` for pre/code snippets. Edit: Realized arguing for CSS properties defeats my point on plaintext. You are right, plaintext is problematic.
- Dudeman112 3y agoI'm on mobile. The tabular data did not work, obviously Ironic
- eviks 3y agoExcept it is hard, even your simplistic example fails - I can't read it on one of the most popular devices - mobile phones Also, it's awful for any serious editing Also, add a bit of *formatting* in the cells, and all your plain readability stemming from tabular alignment is gone