From: Kevin Day Date: Sat, 25 May 2024 14:06:58 +0000 (-0500) Subject: Update: Make Object and Content emphasized and add some abbreviations. X-Git-Url: https://git.kevux.org/?a=commitdiff_plain;h=38bda92277e44694cbc81b50e9fbd2692d501165;p=kevux.org-website Update: Make Object and Content emphasized and add some abbreviations. Make Object and Content emphasized for cases where Object and Content are used by themselves. Designate the HTML5 as an abbreviation in the same way HTML is. --- diff --git a/documentation/fake/specifications/fakefile.html b/documentation/fake/specifications/fakefile.html index d40f693..d35143b 100644 --- a/documentation/fake/specifications/fakefile.html +++ b/documentation/fake/specifications/fakefile.html @@ -105,7 +105,7 @@ A fakefile is broken up into multiple Basic Lists, referred to as Sections, with two special purpose reserved Sections.

- The Sections are broken up into multiple Extended Objects and their respective Contents, referred to as Section Operations. + The Sections are broken up into multiple Extended Objects and their respective Contents, referred to as Section Operations.

Each of these non-reserved Sections acts as a set to perform some set of Section Operations. diff --git a/fll/specifications.html b/fll/specifications.html index bb93807..cf88c0a 100644 --- a/fll/specifications.html +++ b/fll/specifications.html @@ -183,7 +183,7 @@

Unless otherwise specified, character/data delimits are performed only when required and not unilaterally. - In the case of Objects, delimits would only apply when that Object could be potentially identified as an Object. + In the case of Objects, delimits would only apply when that Object could be potentially identified as an Object. For example, FSS-0001 (Extended) needs quotes to group parts that include spaces, if there is no initial quote, then a quote following the data must not be delimited.

@@ -309,20 +309,20 @@ Object_2 This is multiple\" Contents and the trailing quote does not need to be

All specifications are expected to support or be of the character encoding UTF-8; however, there is no imposed restriction on supporting or using any other encoding. - Those encodings must only support the appropriate characters required by a given standard for differentiating Objects, Contents, and delimits. + Those encodings must only support the appropriate characters required by a given standard for differentiating Objects, Contents, and delimits. All specifications do assume ASCII and Unicode support.

Unless otherwise specified, comments are designated by the pound symbol # but only if only white space is to the left of the pound or the pound # is at the start of the line. There is no support for inline comments. - Unless otherwise specified, the start comment may be delimited by \ in the same manner as Objects and Contents are. + Unless otherwise specified, the start comment may be delimited by \ in the same manner as Objects and Contents are. This delimit only applies to the start of a comment (the pound # character) as there is no terminating character for a comment (other than a newline \n). A line containing a valid comment is in its entirety ignored. This means that if there is white space before the designation symbol (the pound # character) then that white space is ignored.

Unless otherwise specified, all designation characters must represent ASCII codes. - With designation characters being any character code used to designate how to identify an Object or Content (such as a colon : at the end of a basic list). + With designation characters being any character code used to designate how to identify an Object or Content (such as a colon : at the end of a basic list). This keeps the processing and logic simple and safe, for both UTF-8 and ASCII. White space used for designation characters must include support for UTF-8 white space characters, unless otherwise specified. However, these white space used as a designation character, must be printing white space that are not combining white space characters.