From b659c549ce83fc38c206aabd5ddc83579fb776f6 Mon Sep 17 00:00:00 2001 From: Kevin Day Date: Tue, 16 Jan 2024 09:55:47 -0600 Subject: [PATCH] Refactor: The backtick into the grave, for the specifications. This is a terminology change in the specifications and the code (both API or ABI) does not need to be changed. Changing the code would be ideal, but this would break API and likely ABI. The 0.6 version series will continue to use the word "backtick" in the code itself for this reason. --- specifications/fss-0000.txt | 4 ++-- specifications/fss-0001.txt | 4 ++-- specifications/fss-0002.txt | 4 ++-- specifications/fss-0003.txt | 4 ++-- specifications/fss.txt | 4 ++-- specifications/iki.txt | 6 +++--- 6 files changed, 13 insertions(+), 13 deletions(-) diff --git a/specifications/fss-0000.txt b/specifications/fss-0000.txt index fd181dc..a1f2203 100644 --- a/specifications/fss-0000.txt +++ b/specifications/fss-0000.txt @@ -1,7 +1,7 @@ # fss-0002 iki-0000 # # license open-standard-license-1.0 -# version 2023/07/14 +# version 2024/01/15 # # This file (assumed to be named fss-0000.txt) can be more easily read using the following iki_read commands: # iki_read fss-0000.txt +Q -w -WW character "'" "'" code '"' '"' @@ -15,7 +15,7 @@ Featureless Settings Specification: 0000 - Basic: White space separates an Object from the Content. An Object may be preceded by a new line character, in which case means that the Object has no Content. If only printing white spaces or non-printable characters follow a valid Object, then that Object is considered to have no Content. - An Object may be quoted to include white space where a single quote character:"'" (unicode:"U+0027"), a double quote character:'"' (unicode:"U+0022"), or a backtick character:'`' (unicode:"U+0060") are used to quote. + An Object may be quoted to include white space where a single quote character:"'" (unicode:"U+0027"), a double quote character:'"' (unicode:"U+0022"), or a grave character:'`' (unicode:"U+0060") are used to quote. An Object is only considered quoted if the first and last character of the Object are the same quote. Any quote characters in a non-quoted Object are treated as part of the Object rather than as a quote. An Object that properly starts with a quote character but is not properly terminated before the new line is reached is considered to be an Object terminating at the end of the line. diff --git a/specifications/fss-0001.txt b/specifications/fss-0001.txt index e1deb32..c779c54 100644 --- a/specifications/fss-0001.txt +++ b/specifications/fss-0001.txt @@ -1,7 +1,7 @@ # fss-0002 iki-0000 # # license open-standard-license-1.0 -# version 2023/07/14 +# version 2024/01/15 # # This file (assumed to be named fss-0001.txt) can be more easily read using the following iki_read commands: # iki_read fss-0001.txt +Q -w -WW character "'" "'" code '"' '"' @@ -15,7 +15,7 @@ Featureless Settings Specification: 0001 - Extended: White space separates an Object from the Content. An Object may be followed by a new line, in which case means that the Object has no Content. If only printing white spaces or non-printable characters follow a valid Object, then that Object is considered to have no Content. - An Object may be quoted to include white space where a single quote character:"'" (unicode:"U+0027"), a double quote character:'"' (unicode:"U+0022"), or a backtick character:'`' (unicode:"U+0060") are used to quote. + An Object may be quoted to include white space where a single quote character:"'" (unicode:"U+0027"), a double quote character:'"' (unicode:"U+0022"), or a grave character:'`' (unicode:"U+0060") are used to quote. An Object is only considered quoted if the first and last character of the Object are the same quote. Any quote characters in a non-quoted Object are treated as part of the Object rather than as a quote. An Object that properly starts with a quote character but is not properly terminated before the new line is reached is considered to be an Object terminating at the end of the line. diff --git a/specifications/fss-0002.txt b/specifications/fss-0002.txt index d47f9ae..0b0d50c 100644 --- a/specifications/fss-0002.txt +++ b/specifications/fss-0002.txt @@ -1,7 +1,7 @@ # fss-0002 iki-0000 # # license open-standard-license-1.0 -# version 2023/07/14 +# version 2024/01/15 # # This file (assumed to be named fss-0002.txt) can be more easily read using the following iki_read commands: # iki_read fss-0002.txt +Q -w -WW character "'" "'" code '"' '"' @@ -18,7 +18,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, double-quote, or backtick delimitation in this specification. + There is no single-quote (unicode:"U+0027"), double-quote (unicode:"U+0022"), or grave (unicode:"U+0060") delimitation in this specification. Only a colon character:":" (unicode:"U+003A") 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 5507725..6a3954c 100644 --- a/specifications/fss-0003.txt +++ b/specifications/fss-0003.txt @@ -1,7 +1,7 @@ # fss-0002 iki-0000 # # license open-standard-license-1.0 -# version 2023/07/14 +# version 2024/01/15 # # This file (assumed to be named fss-0003.txt) can be more easily read using the following iki_read commands: # iki_read fss-0003.txt +Q -w -WW character "'" "'" code '"' '"' @@ -20,7 +20,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 character:"}" (unicode:"U+007D") but a terminating new line must be present to designate a valid end of Content. - There is no single-quote, double-quote, or backtick delimitation in this specification. + There is no single-quote (unicode:"U+0027"), double-quote (unicode:"U+0022"), or grave (unicode:"U+0060") delimitation in this specification. Only an open-brace character:"{" (unicode:"U+007B") that would result in a valid Object or the close-brace character:"}" (unicode:"U+007D") that would terminate valid Content can be delimited. When inside potentially valid Content (which follows a valid Object) the open-brace character:"{" (unicode:"U+007B") 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 2d9f17a..4e661f1 100644 --- a/specifications/fss.txt +++ b/specifications/fss.txt @@ -1,7 +1,7 @@ # fss-0002 iki-0000 # # license open-standard-license-1.0 -# version 2023/07/14 +# version 2024/01/15 # # This file (assumed to be named fss.txt) can be more easily read using the following iki_read commands: # iki_read fss.txt +Q -w -rrrrrrrr anti-KISS anti-KISS ASCII ASCII BOM BOM FSS FSS KISS KISS UTF-8 UTF-8 URL URL XML XML -WWW character "'" "'" code '"' '"' italic '"' '"' @@ -61,7 +61,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 a single quote character:"'" (unicode:"U+0027"), a double quote character:'"' (unicode:"U+0022"), or a backtick character:'`' (unicode:"U+0060") and only a backslash character:"\\" (unicode:"U+005C") 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 grave character:'`' (unicode:"U+0060") and only a backslash character:"\\" (unicode:"U+005C") 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 0640281..1bc219d 100644 --- a/specifications/iki.txt +++ b/specifications/iki.txt @@ -1,7 +1,7 @@ # fss-0002 iki-0000 # # license open-standard-license-1.0 -# version 2023/07/14 +# version 2024/01/15 # # This file (assumed to be named iki.txt) can be more easily read using the following iki_read commands: # iki_read iki.txt +Q -w -WWW character "'" "'" code '"' '"' italic '"' '"' @@ -30,7 +30,7 @@ IKI Specifications: White space, non-word, and non character:"_" (unicode:"U+005F"), character:"-" (unicode:"U+002D"), character:"+" (unicode:"U+002B")) 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, 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"). + 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 grave 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. @@ -38,7 +38,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:"'" (unicode:"U+0027"), a double quote character:'"' (unicode:"U+0022"), or a backtick character:'`' (unicode:"U+0060"). + code:"\q" = either a single quote character:"'" (unicode:"U+0027"), a double quote character:'"' (unicode:"U+0022"), or a grave 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:"\\". -- 1.8.3.1