[section]
[subsection1]
key1=value1
key2=value2
[subsection2]
key1=value1
key2=value2
or
[section]
[[subsection1]]
key1=value1
key2=value2
[[subsection2]]
key1=value1
key2=value2
[section]
[subsection1]
key1=value1
key2=value2
[subsection2]
key1=value1
key2=value2
or
[section]
[[subsection1]]
key1=value1
key2=value2
[[subsection2]]
key1=value1
key2=value2
I should clarify that I mean nested sections. My examples would translate to JSON as:
{ "section" => { "subsection1" => { "key1"=>"value1", "key2"=>"value2" },
"subsection2" => { "key1"=>"value1", "key2"=>"value2" } } }
But now that I look at your example again, maybe that's what you meant too. I have just never seen that notation before and there seems to be no mention of it on Wikipedia.
Note, TOML is using something similar:
[section.subsection1]
key1=value1
key2=value2
[section.subsection2]
key1=value1
key2=value2
@trans, look in any Git config file. Those are INI, albeit yet another special version of INI.
This doesn't really nest in any way that I can see.
Also take a look at JSONY. https://github.com/ingydotnet/jsony-pm#readme
; Doesn't this already work?
[section "subsection1"]
key1=value1
key2=value2
[section "subsection2"]
key1=value1
key2=value2