From: Kevin Day Date: Tue, 6 Dec 2022 01:11:09 +0000 (-0600) Subject: Update: FSS and IKI specification now supports backticks for quoting similar to singl... X-Git-Tag: 0.6.2~60 X-Git-Url: https://git.kevux.org/?a=commitdiff_plain;h=5cd3395bf235ada0505bdfd10dab9dedaff1ee7e;p=fll Update: FSS and IKI specification now supports backticks for quoting similar to single and double quotes. The 0.6 version is not having this support added to prevent API breakage. This should be supported in 0.7 and greater. --- diff --git a/specifications/fss-0002.txt b/specifications/fss-0002.txt index bb8d325..550e9f5 100644 --- a/specifications/fss-0002.txt +++ b/specifications/fss-0002.txt @@ -17,7 +17,7 @@ Featureless Settings Specification: 0002 - Basic List: Content is represented as a single Content column of every line following a valid object until the end of file (or string) or until the next valid Object is found. Any Content that could be interpreted as a valid Object must have the colon delimited. - There is no single-quote or double-quote delimitation in this specification. + There is no single-quote, double-quote, or backtick delimitation in this specification. Only the colon that would result in a valid Object can be delimited. Empty Objects are allowed, that is, the length of the object may be zero. diff --git a/specifications/fss-0003.txt b/specifications/fss-0003.txt index 5d2bb8d..f8a436c 100644 --- a/specifications/fss-0003.txt +++ b/specifications/fss-0003.txt @@ -19,7 +19,7 @@ Featureless Settings Specification: 0003 - Extended List: Any Content column that could be interpreted as an end of Content must be delimited if it should be part of the Content. White space may follow a valid close-brace but a terminating newline must be present to designate a valid end of Content. - There is no single-quote or double-quote delimitation in this specification. + There is no single-quote, double-quote, or backtick delimitation in this specification. Only the open-brace that would result in a valid Object or the close-brace that would terminate valid Content can be delimited. When inside potentially valid Content (which follows a valid Object) the open-brace cannot be delimited because this standard is not-recursive. When not inside any potentially valid Content (that is, there is no previous unclosed Object), then the Object may be delimited. diff --git a/specifications/fss.txt b/specifications/fss.txt index a56e5f4..00a5ad1 100644 --- a/specifications/fss.txt +++ b/specifications/fss.txt @@ -60,7 +60,7 @@ Featureless Settings Specifications: Unless otherwise specified, white space immediately both before (and after, outside of the terminating quote) an Object is not considered part of the Object. This simplifies identifying the object, use quoted Objects to support white space before/after an object for styling purposes. - Unless otherwise specified, quotes may only be either a single quote character:"'" or a double quote character:'"' and only a backslash character:"\\" may be used as a delimiter. + Unless otherwise specified, quotes may only be a single quote character:"'" (unicode:"U+0027"), a double quote character:'"' (unicode:"U+0022"), or a backtick character:'`' and only a backslash character:"\\" may be used as a delimiter. For example, code:"FSS-0000 (Basic)"\: \"Object 1" has content starting at the '1', with an Object named '"Object'. \\"Object 1" has content starting at the '1', with an Object named '\"Object'. diff --git a/specifications/iki.txt b/specifications/iki.txt index 962b879..a981b28 100644 --- a/specifications/iki.txt +++ b/specifications/iki.txt @@ -24,7 +24,7 @@ IKI Specifications: White space and non-word (and non character:"_", character:"-", character:"+") character punctuations may not exist as part of the variable name. The only Unicode dash-like characters allowed as a "dash" are those intended to connect, such as the Unicode hyphens (unicode:"U+2010" and unicode:"U+2011"). - Any potential IKI data must be escaped to make it treated as non-IKI data by prepending a backslash character:"\\" before the colon character:":" that is before the opening quote (single or double). Potential IKI data refers to any valid IKI sequence without considering the closing single quote character:"'" or closing double quote character:'"'. + Any potential IKI data must be escaped to make it treated as non-IKI data by prepending a backslash character:"\\" before the colon character:":" that is before the opening quote (single, double, or backtic). Potential IKI data refers to any valid IKI sequence without considering the closing single quote character:"'" (unicode:"U+0027"), closing double quote character:'"' (unicode:"U+0022"), or closing backtick character:'`' (unicode:"U+0060"). Unicode punctuation connector characters are supported just like character:"_", except when they connect outside the current line (such as unicode:"U+FE33" character:"︳"). Unicode invisible punctuations (such as invisible plus: unicode:"U+2064") are not considered a punctuations in this standard (because they a zero-width characters), therefore they are not to be considered a valid character:"_", character:"-", or character:"+" Unicode equivalents. @@ -32,7 +32,7 @@ IKI Specifications: Key\: code:"\o" = any printable word character, including character:"_", character:"-", character:"+" (and Unicode equivalents). code:"\c" = any character, including white space and non-printing, and any delimited quote (used as the opening quote) or a any quote (undelimited) not used as the opening quote. - code:"\q" = either a single quote character:"'" or a double quote character:'"'. + code:"\q" = either a single quote character:"'" (unicode:"U+0027"), a double quote character:'"' (unicode:"U+0022"), or a backtick character:'`' (unicode:"U+0060"). code:"\x" = any character. code:"\W" = any non-word character, discluding character:"_", character:"-", character:"+" (and Unicode equivalents). code:"\e" = an optional escape sequence of any number of backslashes, such as character:"\\".