Fred2834 wrote: I would not want a very long hash table to be described without any special character. In the real world, large XML or JSON files are a reality. I would. If i had to enter/edit the data manually, then i would want a long hash table to be described without any special character. I had to achieve exactly that with a new Javascript tool i created. I had to figure out a way to store human-editable data in html -- ie, plain text. So, no formatting, no tabular display. Here's my solution. It uses no special characters at all, no tags, and unlike XML/JSON the fieldnames aren't repeated for every record. I find this quite readable. It's optimized for low-risk editing. There are no syntax to screw up or special symbols to put in the wrong place, no punctuation to get wrong. And it's far less laborious without having to type all those tags or braces. NAME LINK DESCRIPTION Genevieve Dupre https://www.genevievetattoos.com This isn't what you expected. Joey Armstrong https://thunderhandtattoo.com The most amazing. GitHub - johnaweiss/HTML-Micro-Templating: Lightweight, robust HTML templating system.[^] Granted, this would quickly become unwieldy with a lot of fields. The solution above isn't intended for data with a ton of fields. But if i had a lot of fields, then i wouldn't be manually editing raw data in plain text format. Dude, why are you doing that? XML/JSON are best suited for machine manipulation, not human reading/editing. But this thread is about human readable languages, not machine languages. So i'm unclear how your XML/JSON contradicts my desire for human-readable code. https://github.com/johnaweiss?tab=repositories