<head>\r
<link rel="icon" type="image/x-icon" href="/favicon.ico">\r
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />\r
-<meta name="generator" content="AsciiDoc 8.6.9" />\r
+<meta name="generator" content="AsciiDoc 8.6.10" />\r
<title>i3: Layout saving in i3</title>\r
<link rel="stylesheet" href="/css/style.css" type="text/css" />\r
<link rel="stylesheet" href="/css/xhtml11.css" type="text/css" />\r
<div class="olist arabic"><ol class="arabic">\r
<li>\r
<p>\r
-Layout files contain multiple “JSON documents” on the top level, whereas the\r
- JSON standard only allows precisely one “document” (array or hash).\r
+Layout files contain multiple “JSON texts” at the top level. The JSON\r
+ standard doesn’t prohibit this, but in practice most JSON parsers only\r
+ allow precisely one “text” per document/file, and will mark multiple texts\r
+ as invalid JSON.\r
</p>\r
</li>\r
<li>\r
<p>\r
-Layout files contain comments which are not standardized, but understood by\r
- many parsers.\r
+Layout files contain comments which are not allowed by the JSON standard,\r
+ but are understood by many parsers.\r
</p>\r
</li>\r
</ol></div>\r
-<div class="paragraph"><p>Both deviations from the JSON standard are to make manual editing by humans\r
+<div class="paragraph"><p>Both of these deviations from the norm are to make manual editing by humans\r
easier. In case you are writing a more elaborate tool for manipulating these\r
layouts, you can either use a JSON parser that supports these deviations (for\r
example libyajl), transform the layout file to a JSON-conforming file, or\r
projects / i3 / i3.github.io / blobdiff