border-right: 1px dotted;
}
-.kevux.documentation > .content-block > .main-block .dl {
+.kevux > .content-block > .main-block .dl {
border: 1px solid #e0e0e0;
width: fit-content;
}
-.kevux.documentation > .content-block > .main-block .dl > .di {
+.kevux > .content-block > .main-block .dl > .di {
padding: 4px;
}
-.kevux.documentation > .content-block > .main-block .dl > .di > .dt {
+.kevux > .content-block > .main-block .dl > .di > .dt {
font-weight: bold;
padding: 2px;
}
-.kevux.documentation > .content-block > .main-block .dl > .di:nth-child(odd) {
+.kevux > .content-block > .main-block .dl > .di:nth-child(odd) {
background-color: #efefef;
}
+.kevux > .content-block > .main-block .preserve {
+ box-sizing: border-box;
+
+ white-space: pre-wrap;
+
+ background-color: #fffff5;
+
+ border: 1px solid #e6e78d;
+ margin: 2px 4px;
+ padding: 4px 8px;
+}
+
+.kevux > .content-block > .main-block .preserve.margin-below {
+ margin-bottom: 1rem;
+}
+
+.kevux > .content-block > .main-block .code {
+ box-sizing: border-box;
+
+ font-family: monospace;
+
+ color: #724801;
+}
.kevux.documentation > .content-block > .main-block .table.context-parameters > .set > .row:nth-child(even) {
background-color: #efefef;
<ul>
<br>
<li><span class="bold">Step 1</span>, generate the key (-d is for DSA, no -d is for RSA)<br>
- <code> <span class="notice">ssh-keygen -d</span></code></li>
+ <code class="code"> <span class="notice">ssh-keygen -d</span></code></li>
<br>
<li><span class="bold">Step 2</span>, Skipping password, just press enter on password prompt to leave it empty so that passwordless handshaking can work.<br>
This should create the .ssh/id_dsa and the .ssh/id_dsa.pub files, and this may take some time, depending on your hardware.</li>
<span class="notice">remotehost</span> = the address used to connect to the server<br>
<span class="notice">/yourhome/directiry</span> = the path to your home directory<br>
<br>
- <code> <span class="notice">scp .ssh/id_dsa.pub username@remotehost:/yourhome/directory/</span></code><br>
- <code> <span class="notice">ssh username@remotehost</span></code><br>
- <code> <span class="notice">mkdir -p ~/.ssh/</span></code><br>
- <code> <span class="notice">cat ~/id_dsa.pub >> ~/.ssh/authorized_keys</span></code></li>
+ <code class="code"> <span class="notice">scp .ssh/id_dsa.pub username@remotehost:/yourhome/directory/</span></code><br>
+ <code class="code"> <span class="notice">ssh username@remotehost</span></code><br>
+ <code class="code"> <span class="notice">mkdir -p ~/.ssh/</span></code><br>
+ <code class="code"> <span class="notice">cat ~/id_dsa.pub >> ~/.ssh/authorized_keys</span></code></li>
<br>
<li><span class="bold">Step 4</span>, now you can delete the id_dsa.pub file from the remote host and exit.<br>
- <code> <span class="notice">rm id_dsa.pub</span></code><br>
- <code> <span class="notice">exit</span></code></li>
+ <code class="code"> <span class="notice">rm id_dsa.pub</span></code><br>
+ <code class="code"> <span class="notice">exit</span></code></li>
<br>
<li><span class="bold">Step 5</span>, DONE<br>
You should be able to ssh to the remote host without a password now, given that the .ssh/id_dsa file and the .ssh/id_dsa.pub file exist on your client machine for the user you intend to connect with.</li>
Now that you can handshake from the above example, you should now be able to run the sshfs command and even put it in a logon or boot script, without exposing your password</li>
<br>
<li>Mounting from sshfs<br>
- <code> <span class="notice">sshfs username@remotehost:/remote/directory/ /local/directory/</span></code></li>
+ <code class="code"> <span class="notice">sshfs username@remotehost:/remote/directory/ /local/directory/</span></code></li>
<br>
<li>Unmounting from sshfs<br>
- <code> <span class="notice">fusermount -u /local/directory/</span></code></li>
+ <code class="code"> <span class="notice">fusermount -u /local/directory/</span></code></li>
<br>
<li>If you did not use the SSH Handshaking above, then you will be prompted for a password on the sshfs command</li>
<li>If you did use the SSH Handshaking above, and are still being asked for a password, then there is a problem with the RSA/DSA keys</li>
Lets say you wanted to encrypt a partition (/dev/sda6) and use a key file.<br>
<ol>
<li>Fill the drive with random data <span class="error">(this will delete all data on the device /dev/sda6)</span>:<br>
- <code><span class="notice">dd if=/dev/urandom of=/dev/sda6</span></code><br>
+ <code class="code"><span class="notice">dd if=/dev/urandom of=/dev/sda6</span></code><br>
<br>
</li>
<li>Create a keyfile using randomly generated data:<br>
- <code><span class="notice">dd if=/dev/urandom of=~/some.key bs=1c count=512</span></code><br>
+ <code class="code"><span class="notice">dd if=/dev/urandom of=~/some.key bs=1c count=512</span></code><br>
<br>
</li>
<li>Use the keyfile to encrypt the device with LUKS encryption:<br>
- <code><span class="notice">cryptsetup -c aes-xts-plain:sha512 -s 512 luksFormat /dev/sda6 ~/some.key</span></code><br>
+ <code class="code"><span class="notice">cryptsetup -c aes-xts-plain:sha512 -s 512 luksFormat /dev/sda6 ~/some.key</span></code><br>
<br>
Alternatively, try this encryption:<br>
- <code><span class="notice">cryptsetup -c aes-cbc-essiv:sha256 -s 256 luksFormat /dev/sda6 ~/some.key</span></code><br>
+ <code class="code"><span class="notice">cryptsetup -c aes-cbc-essiv:sha256 -s 256 luksFormat /dev/sda6 ~/some.key</span></code><br>
<br>
</li>
<li>Now that the device is encrypted, decrypt the device so that the device can be properly formatted (calling the decrypted device: some_name_here):<br>
- <code><span class="notice">cryptsetup luksOpen /dev/sda6 some_name_here -d ~/some-key</span></code><br>
+ <code class="code"><span class="notice">cryptsetup luksOpen /dev/sda6 some_name_here -d ~/some-key</span></code><br>
<br>
</li>
<li>Format the decypted device (this example format creates an ext4 filesystem with a label of: some_fs_label):<br>
- <code><span class="notice">mkfs.ext4 -L some_fs_label /dev/mapper/some_name_here</span></code><br>
+ <code class="code"><span class="notice">mkfs.ext4 -L some_fs_label /dev/mapper/some_name_here</span></code><br>
<br>
</li>
</ol>
Lets say you wanted to encrypt a partition (/dev/sda6) and use a password.<br>
<ol>
<li>Fill the drive with random data <span class="error">(this will delete all data on the device /dev/sda6)</span>:<br>
- <code><span class="notice">dd if=/dev/urandom of=/dev/sda6</span></code><br>
+ <code class="code"><span class="notice">dd if=/dev/urandom of=/dev/sda6</span></code><br>
<br>
</li>
<li>Encrypt the device with LUKS encryption:<br>
- <code><span class="notice">cryptsetup -c aes-xts-plain:sha512 -y -s 512 luksFormat /dev/sda6</span></code><br>
+ <code class="code"><span class="notice">cryptsetup -c aes-xts-plain:sha512 -y -s 512 luksFormat /dev/sda6</span></code><br>
Then enter in your desired password when prompted.<br>
<br>
Alternatively, try this encryption:<br>
- <code><span class="notice">cryptsetup -c aes-cbc-essiv:sha256 -y -s 256 luksFormat /dev/sda6</span></code><br>
+ <code class="code"><span class="notice">cryptsetup -c aes-cbc-essiv:sha256 -y -s 256 luksFormat /dev/sda6</span></code><br>
<br>
</li>
<li>Now that the device is encrypted, decrypt the device so that the device can be properly formatted (calling the decrypted device: some_name_here):<br>
- <code><span class="notice">cryptsetup luksOpen /dev/sda6 some_name_here</span></code><br>
+ <code class="code"><span class="notice">cryptsetup luksOpen /dev/sda6 some_name_here</span></code><br>
Enter in the password you used in the previous step when prompted.<br>
<br>
</li>
<li>Format the decypted device (this example format creates an ext4 filesystem with a label of: some_fs_label):<br>
- <code><span class="notice">mkfs.ext4 -L some_fs_label /dev/mapper/some_name_here</span></code><br>
+ <code class="code"><span class="notice">mkfs.ext4 -L some_fs_label /dev/mapper/some_name_here</span></code><br>
<br>
</li>
</ol>
Lets say you wanted add a new key to an existing encrypted device.<br>
<ol>
<li>If not already created, create a new key using random data:<br>
- <code><span class="notice">dd if=/dev/urandom of=~/new.key bs=1c count=512</span></code><br>
+ <code class="code"><span class="notice">dd if=/dev/urandom of=~/new.key bs=1c count=512</span></code><br>
<br>
</li>
<li>Add the new key (Assuming that the old key is called old.key and is stored in your home directory):<br>
- <code><span class="notice">cryptsetup -d ~/old.key luksAddKey /dev/sda6 ~/new.key</span></code><br>
+ <code class="code"><span class="notice">cryptsetup -d ~/old.key luksAddKey /dev/sda6 ~/new.key</span></code><br>
<br>
If the encrypted device did not use a key, then use the following command instead and enter in the appropriate password when prompted:<br>
- <code><span class="notice">cryptsetup luksAddKey /dev/sda6 ~/new.key</span></code><br>
+ <code class="code"><span class="notice">cryptsetup luksAddKey /dev/sda6 ~/new.key</span></code><br>
<br>
</li>
</ol>
Lets say you wanted add a new password to an existing encrypted device.<br>
<ol>
<li>Add the new key (Assuming that the old key is called old.key and is stored in your home directory):<br>
- <code><span class="notice">cryptsetup -d ~/old.key luksAddKey /dev/sda6</span></code><br>
+ <code class="code"><span class="notice">cryptsetup -d ~/old.key luksAddKey /dev/sda6</span></code><br>
Then enter in your desired password when prompted.<br>
<br>
If the encrypted device did not use a key, then use the following command instead:<br>
- <code><span class="notice">cryptsetup luksAddKey /dev/sda6</span></code><br>
+ <code class="code"><span class="notice">cryptsetup luksAddKey /dev/sda6</span></code><br>
You will first be prompted for the decryption password, enter in that first.<br>
Enter in the new password after the first password properly decrypts the device.<br>
<br>
Whenever the device gets decrypted a message should be presented, stating which key slot was used.<br>
<br>
Once you have the propery slot identified (lets call this desired_slot), delete that slot (Assuming that the old key is called old.key and is stored in your home directory):
- <code><span class="notice">cryptsetup -d ~/old.key luksDelKey /dev/sda6 desired_slot</span></code><br>
+ <code class="code"><span class="notice">cryptsetup -d ~/old.key luksDelKey /dev/sda6 desired_slot</span></code><br>
<br>
If the encrypted device did not use a key, then use the following command instead:<br>
- <code><span class="notice">cryptsetup luksDelKey /dev/sda6 desired_slot</span></code><br>
+ <code class="code"><span class="notice">cryptsetup luksDelKey /dev/sda6 desired_slot</span></code><br>
Enter in the decryption password when prompted.<br>
<br>
</li>
<br>
<span class="bold">Example comparison between raw iptables command and the default-firewall syntax:</span><br>
<span class="notice">Raw Iptables Syntax</span>:<br>
- <code>
+ <code class="code">
/sbin/iptables -A INPUT -i eth0 -p tcp --dport 47288 -j ACCEPT<br>
/sbin/iptables -A INPUT -i eth0 -p udp --sport 47288:47544 -j ACCEPT<br>
/sbin/iptables -A INPUT -i eth0 -p udp --dport 47288:47544 -j ACCEPT<br>
/sbin/iptables -A OUTPUT -o eth0 -p udp --sport 123 --dport 123 -j ACCEPT<br>
</code><br>
<span class="notice">default-firewall Syntax</span>:<br>
- <code>
+ <code class="code">
direction input<br>
device eth0<br>
action append<br>
Scroll to the bottom and uncomment and set the Driver to whatever you need it to be.<br>
<br>
If you are on an OLPC, you could copy the pre-created olpc xorg configuration file:<br>
- <code><span class="notice">
+ <code class="code"><span class="notice">
cd /etc/X11/<br>
cp -v xorg.conf.olpc xorg.conf<br>
</span></code>
To update <span class="notice">/etc/usb.ids</span> to the latest version, download: <a href="http://www.linux-usb.org/usb.ids">http://www.linux-usb.org/usb.ids</a><br>
<br>
Once this is done, make sure that the file permissions are correct:<br>
- <code><span class="notice">
+ <code class="code"><span class="notice">
chgrp hardware_browse /etc/{pci,usb}.ids<br>
chmod g-wx+r,o-rwx /etc/{pci,usb}.ids<br>
</span></code>
Lets say that you also dowloaded the appropriate kernel modules and it is called <span class="notice">2.6.26.5-olpc.tz2</span>.<br>
You will also need to extract the kernel modules to <span class="notice">modules/</span><br>
What you would do is:<br>
- <code><span class="notice">
+ <code class="code"><span class="notice">
mv -v turtle-2.6.26.5-olpc boot/<br>
ln -vs turtle-2.6.26.5-olpc boot/turtle-olpc<br>
tar -xf 2.6.26.5-olpc.tz2 -C modules/<br>
</span></code>
<br>
Replace the default <span class="notice">xorg.conf</span> file with the the <span class="notice">xorg.conf.olpc</span> file so that you can get a working graphical display:<br>
- <code><span class="notice">
+ <code class="code"><span class="notice">
cp -v etc/X11/xorg.conf.olpc etc/X11/xorg.conf<br>
</span></code>
<br>
<i>To boot a live-usb on a usb 1.1 system, you will need a live cdrom that contains the appropriate grub.</i><br>
<br>
<span class="bold">Available Boot Options:</span><br>
- <code><span class="notice">
+ <code class="code"><span class="notice">
Install Kevux System<br>
Boot Live System - Run From Memory<br>
Boot Live System - Run From CD-Rom<br>
<li id="boot_option_etcdevice"><span class="bold notice">etcdevice=</span><br>
Specify the physical partition that contains the etc directory.<br>
This will be mounted to the /etc directory of the finalroot system.<br>
- For using an ecrypted partition, this should be set to something like: <code>etcdevice=/dev/mapper/etc</code><br>
+ For using an ecrypted partition, this should be set to something like: <code class="code">etcdevice=/dev/mapper/etc</code><br>
<br>
</li>
<li id="boot_option_homedevice"><span class="bold notice">homedevice=</span><br>
Specify the physical partition that contains the home directory.<br>
This will be mounted to the /home directory of the finalroot system.<br>
- For using an ecrypted partition, this should be set to something like: <code>homedevice=/dev/mapper/home</code><br>
+ For using an ecrypted partition, this should be set to something like: <code class="code">homedevice=/dev/mapper/home</code><br>
<br>
</li>
<li id="boot_option_vardevice"><span class="bold notice">vardevice=</span><br>
Specify the physical partition that contains the var directory.<br>
This will be mounted to the /var directory of the finalroot system.<br>
- For using an ecrypted partition, this should be set to something like: <code>vardevice=/dev/mapper/var</code><br>
+ For using an ecrypted partition, this should be set to something like: <code class="code">vardevice=/dev/mapper/var</code><br>
<br>
</li>
<li id="boot_option_tmpdevice"><span class="bold notice">tmpdevice=</span><br>
Specify the physical partition that contains the tmp directory.<br>
This will be mounted to the /tmp directory of the finalroot system.<br>
- For using an ecrypted partition, this should be set to something like: <code>tmpdevice=/dev/mapper/tmp</code><br>
+ For using an ecrypted partition, this should be set to something like: <code class="code">tmpdevice=/dev/mapper/tmp</code><br>
<br>
</li>
<li id="boot_option_xorg"><span class="bold notice">xorg=</span><br>
<span class="bold">Notes:</span>
<ul>
<li>The configuration file is an XML file, XML syntax rules do apply.</li>
- <li><code><span class="notice"><path>/dev/video0</path></span></code> specifies the Video Device to use</li>
- <li><code><span class="notice"><input>0</input></span></code> specifies the particular capture port on the card</li>
- <li><code><span class="notice"><norm>ntfs0</norm></span></code> specifies the media format the signal is transmitted as</li>
+ <li><code class="code"><span class="notice"><path>/dev/video0</path></span></code> specifies the Video Device to use</li>
+ <li><code class="code"><span class="notice"><input>0</input></span></code> specifies the particular capture port on the card</li>
+ <li><code class="code"><span class="notice"><norm>ntfs0</norm></span></code> specifies the media format the signal is transmitted as</li>
</ul>
</p>
</div>
<span class="bold">Notes:</span>
<ul>
<li>The configuration file format is a bash-like syntax; bash comment rules apply.</li>
- <li><code><span class="notice">server.document-root</span></code> specifies the system path where the website root exists, default is /home/websites/</li>
- <li><code><span class="notice">server.port</span></code> specifies the port the server listens on, default is 80</li>
+ <li><code class="code"><span class="notice">server.document-root</span></code> specifies the system path where the website root exists, default is /home/websites/</li>
+ <li><code class="code"><span class="notice">server.port</span></code> specifies the port the server listens on, default is 80</li>
</ul>
</p>
</div>
<span class="bold">Notes:</span>
<ul>
<li>The configuration file format is a bash-like syntax; bash comment rules apply.</li>
- <li><code><span class="notice">music_directory</span></code> specifies where the available music exists, default is /home/music/</li>
- <li><code><span class="notice">port</span></code> specifies where the port the server listens on, default is 6600</li>
+ <li><code class="code"><span class="notice">music_directory</span></code> specifies where the available music exists, default is /home/music/</li>
+ <li><code class="code"><span class="notice">port</span></code> specifies where the port the server listens on, default is 6600</li>
</ul>
</p>
</div>
<span class="bold">Initial Setup:</span><br>
Create the database:<br>
- <code><span class="notice">su - t_database -c '/bin/initdb -D /home/targets/database/data -E UTF8 --locale=en_US.UTF-8'</span></code><br>
+ <code class="code"><span class="notice">su - t_database -c '/bin/initdb -D /home/targets/database/data -E UTF8 --locale=en_US.UTF-8'</span></code><br>
<br>
<span class="bold">Notes:</span>
<ul>
<li>The configuration file <span class="bold">Initial Setup:</span><br>
Create the database:<br>
- <code><span class="notice">su - postgresd -c '/bin/initdb -D /home/targets/postgresd/database'</span></code><br>
+ <code class="code"><span class="notice">su - postgresd -c '/bin/initdb -D /home/targets/postgresd/database'</span></code><br>
<br>format is a bash-like syntax; bash comment rules apply.</li>
</ul>
</p>
<span class="bold">Files 5 to 12:</span><br>
These files are auto-generated by the initng start script.<br>
- You can create these manually by calling the <code><span class="notice">setup_ssh_host_keys</span></code> script.<br>
+ You can create these manually by calling the <code class="code"><span class="notice">setup_ssh_host_keys</span></code> script.<br>
<br>
<span class="bold">Notes:</span>
<ul>
<li>The configuration file format is a bash-like syntax; bash comment rules apply.</li>
<li>The setup_ssh_host_keys command will create more files in the /home/targets/ssh/settings/ directory. These files begin with ssh_host_.</li>
- <li><code><span class="notice">Port</span></code> specifies where the port the server listens on, default is 22</li>
- <li><code><span class="notice">Banner</span></code> specify a file to enable, comment out to disable</li>
+ <li><code class="code"><span class="notice">Port</span></code> specifies where the port the server listens on, default is 22</li>
+ <li><code class="code"><span class="notice">Banner</span></code> specify a file to enable, comment out to disable</li>
</ul>
</p>
</div>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
<ol>
<li>The first part, on the left mode side of the output, contains 16 upper case hexidecimal digits representing the maximum length supported by the <strong>byte_dump</strong> program.</li>
<li>The second part displays the individual bytes in a numeric format or similar (depending on parameters). In the second part, the hexidecimal digits are never swapped based on endianness.</li>
- <li>The third part, which only appears when using the <code>-t/--text<code> parameter, displays the character each digit or set of digits may represent. Any characters considered unsafe or improper are substituted with a replacement character.</li>
+ <li>The third part, which only appears when using the <code class="code">-t/--text<code class="code"> parameter, displays the character each digit or set of digits may represent. Any characters considered unsafe or improper are substituted with a replacement character.</li>
</ol>
</div>
</section>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
</table>
</div>
<p>
- When the <code>--socket</code> parameter represents a directory path then the file name is generated from either the <code>--name</code> parameter or from the control settings file.
+ When the <code class="code">--socket</code> parameter represents a directory path then the file name is generated from either the <code class="code">--name</code> parameter or from the control settings file.
</p>
<p>
- A rule action allows for either the full rule path, such as '<code>boot/root</code>' as a single parameter or two parameters with the first representing the rule directory path 'boot' and the second representing the rule base name '<code>root</code>'.
+ A rule action allows for either the full rule path, such as '<code class="code">boot/root</code>' as a single parameter or two parameters with the first representing the rule directory path 'boot' and the second representing the rule base name '<code class="code">root</code>'.
</p>
<p>
- The <code>--return</code> parameter is intended to be used for scripting and is of the form "<code>response [type] [action] [status]</code>".
+ The <code class="code">--return</code> parameter is intended to be used for scripting and is of the form "<code class="code">response [type] [action] [status]</code>".
</p>
<p>
- Be sure to use the <code>++quiet</code> parameter to suppress output when using this in scripting.
+ Be sure to use the <code class="code">++quiet</code> parameter to suppress output when using this in scripting.
No response is returned on program errors, especially those errors that prevent communicating to the controller.
</p>
</div>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
</table>
</div>
<p>
- When both the <code>--simulate</code> parameter and the <code>--validate</code> parameter are specified, then additional information on each would be executed rule is printed but no simulation is performed.
+ When both the <code class="code">--simulate</code> parameter and the <code class="code">--validate</code> parameter are specified, then additional information on each would be executed rule is printed but no simulation is performed.
</p>
<p>
- The default interrupt behavior is to operate as if the <code>--interruptible</code> parameter is passed.
+ The default interrupt behavior is to operate as if the <code class="code">--interruptible</code> parameter is passed.
</p>
<p>
- Specify an empty string for the <code>--pid</code> parameter to disable pid file creation for this program.
+ Specify an empty string for the <code class="code">--pid</code> parameter to disable pid file creation for this program.
</p>
</div>
</section>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
</table>
</div>
<p>
- When using the <code>-d/--define</code> parameter the define structure must be passed as-is and may even need to be quoted if there is whitespace.
+ When using the <code class="code">-d/--define</code> parameter the define structure must be passed as-is and may even need to be quoted if there is whitespace.
</p>
<p>
- For example, in the <strong>C</strong> programming, passing a macro to the compiler might look like '<code>-DMY_MACRO=1</code>'. To do this using <code>-d/--define</code>, there would be two parameters passed like this: '<code>-d -DMY_MACRO=1</code>'. This works because the parameter after the <code>-d/--define</code> is not interpreted and is treated exactly as is without interpreting it as a parameter to the <strong>fake</strong> program.
+ For example, in the <strong>C</strong> programming, passing a macro to the compiler might look like '<code class="code">-DMY_MACRO=1</code>'. To do this using <code class="code">-d/--define</code>, there would be two parameters passed like this: '<code class="code">-d -DMY_MACRO=1</code>'. This works because the parameter after the <code class="code">-d/--define</code> is not interpreted and is treated exactly as is without interpreting it as a parameter to the <strong>fake</strong> program.
</p>
<p>
- Because of this, passing '<code>-d -h</code>' would not print the program help because the '<code>-h</code>' is considered a value associated with the '<code>-d</code>' parameter rather than a parameter itself.
+ Because of this, passing '<code class="code">-d -h</code>' would not print the program help because the '<code class="code">-h</code>' is considered a value associated with the '<code class="code">-d</code>' parameter rather than a parameter itself.
</p>
</div>
</section>
</table>
</div>
<p>
- When performing the build operation, the <code>--mode</code> parameter specifies a name (limited to alpha-numeric, underscore, and dash) to be used in addition to the global.
+ When performing the build operation, the <code class="code">--mode</code> parameter specifies a name (limited to alpha-numeric, underscore, and dash) to be used in addition to the global.
</p>
<p>
- For example, when a mode of '<code>fll_monolithic</code>' is specified, build libraries from both '<code>build_libraries</code>' and '<code>build_libraries-fll_monolithic</code>' are used (but not '<code>build_libraries-fll_level</code>').
+ For example, when a mode of '<code class="code">fll_monolithic</code>' is specified, build libraries from both '<code class="code">build_libraries</code>' and '<code class="code">build_libraries-fll_monolithic</code>' are used (but not '<code class="code">build_libraries-fll_level</code>').
</p>
<p>
- When specifying the <code>fakefile</code> or the settings parameters, the filenames are relative to the data build directory, unless a path is used.
+ When specifying the <code class="code">fakefile</code> or the settings parameters, the filenames are relative to the data build directory, unless a path is used.
</p>
<p>
- For example, with '<code>--fakefile my_fakefile</code>' the fakefile at '<code>./data/build/my_fakefile</code>' would be used, however with '<code>--fakefile ./my_fakefile</code>' the fakefile at '<code>./my_fakefile</code>' would be used.
+ For example, with '<code class="code">--fakefile my_fakefile</code>' the fakefile at '<code class="code">./data/build/my_fakefile</code>' would be used, however with '<code class="code">--fakefile ./my_fakefile</code>' the fakefile at '<code class="code">./my_fakefile</code>' would be used.
</p>
</div>
</section>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
For example, a file of 17 lines would range from 0 to 16.
</p>
<p>
- When using the <code>--depth</code> option, an order of operations is enforced on the parameters.
+ When using the <code class="code">--depth</code> option, an order of operations is enforced on the parameters.
</p>
<p>
When this order of operations is in effect, parameters to the right of a depth parameter are influenced by that depth parameter:
</p>
<dl class="dl">
<div class="di">
- <dt class="dt"><code>--at</code></dt><dd class="dd">An Object index at the specified depth.</dd>
+ <dt class="dt"><code class="code">--at</code></dt><dd class="dd">An Object index at the specified depth.</dd>
</div>
<div class="di">
- <dt class="dt"><code>--depth</code></dt><dd class="dd">A new depth within the specified depth, indexed from the root.</dd>
+ <dt class="dt"><code class="code">--depth</code></dt><dd class="dd">A new depth within the specified depth, indexed from the root.</dd>
</div>
<div class="di">
- <dt class="dt"><code><code>--name</code></code></dt><dd class="dd">An Object name at the specified depth.</dd>
+ <dt class="dt"><code class="code"><code class="code">--name</code></code></dt><dd class="dd">An Object name at the specified depth.</dd>
</div>
</dl>
<p>
- The parameter <code>--depth</code> must be in numeric order, but values in between may be skipped.
+ The parameter <code class="code">--depth</code> must be in numeric order, but values in between may be skipped.
</p>
<ul>
<li>('-d 0 -a 1 -d 2 -a 2' would specify index 1 at depth 0, any index at depth 1, and index 2 at depth 2.)</li>
<li>('-d 2 -a 1 -d 0 -a 2' would be invalid because depth 2 is before depth 1.)</li>
</ul>
<p>
- The parameter <code>--select</code> selects a Content column.
+ The parameter <code class="code">--select</code> selects a Content column.
</p>
<p>
- Specify both <code>--object</code> and the --total parameters to get the total objects.
+ Specify both <code class="code">--object</code> and the --total parameters to get the total objects.
</p>
<p>
- When both <code>--at</code> and <code>--name</code> parameters are specified (at the same depth), the <code>--at</code> parameter value will be treated as a position relative to the specified <code>--name</code> parameter value.
+ When both <code class="code">--at</code> and <code class="code">--name</code> parameters are specified (at the same depth), the <code class="code">--at</code> parameter value will be treated as a position relative to the specified <code class="code">--name</code> parameter value.
</p>
<p>
- This program may support parameters, such as <code>--depth</code> or <code>--select</code>, even if not supported by the standard.
+ This program may support parameters, such as <code class="code">--depth</code> or <code class="code">--select</code>, even if not supported by the standard.
</p>
<p>
This is done to help ensure consistency for scripting.
</p>
<p>
- For parameters like <code>--depth</code>, if the standard doesn't support nested Content, then only a depth of 0 would be valid.
+ For parameters like <code class="code">--depth</code>, if the standard doesn't support nested Content, then only a depth of 0 would be valid.
</p>
<p>
- For parameters like <code>--select</code>, if the standard doesn't support multiple Content groups, then only a select of 0 would be valid.
+ For parameters like <code class="code">--select</code>, if the standard doesn't support multiple Content groups, then only a select of 0 would be valid.
</p>
<p>
- The parameter <code>--trim</code> will remove leading and trailing white spaces when selecting objects or when printing objects.
+ The parameter <code class="code">--trim</code> will remove leading and trailing white spaces when selecting objects or when printing objects.
</p>
<p>
- When specifying both the <code>--object</code> parameter and the <code>--content</code> parameter, the entire Object and Content are printed, including the formatting.
+ When specifying both the <code class="code">--object</code> parameter and the <code class="code">--content</code> parameter, the entire Object and Content are printed, including the formatting.
</p>
<p>
Both the Object and Content printed are already escaped.
Both the Object and Content are separated by a New Line character '<kbd>\n</kbd>' (U+000A).
</p>
<p>
- The parameter <code>--delimit</code> accepts the following:
+ The parameter <code class="code">--delimit</code> accepts the following:
</p>
<dl class="dl">
<div class="di">
</div>
</dl>
<p>
- The <code>--delimit</code> parameter may be specified multiple times to customize the delimit behavior.
+ The <code class="code">--delimit</code> parameter may be specified multiple times to customize the delimit behavior.
</p>
<p>
- The <code>--delimit</code> values none and all, overrule all other delimit values.
+ The <code class="code">--delimit</code> values none and all, overrule all other delimit values.
</p>
<p>
- The parameters <code>--columns</code> and <code>--select</code> refer to a Content column.
+ The parameters <code class="code">--columns</code> and <code class="code">--select</code> refer to a Content column.
</p>
<p>
The word "<em>column</em>" is being loosely defined to refer to a specific Content.
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
For the pipe, an Object is terminated by either a Backspace character '<kbd>\b</kbd>' (U+0008) or a Form Feed character '<kbd>\f</kbd>' (U+000C). The end of the pipe represents the end of any Object or Content.
</p>
<p>
- The FSS-0002 (Basic List) specification does not support quoted names, therefore the parameters <code>--single</code> and <code>--double</code> do nothing.
+ The FSS-0002 (Basic List) specification does not support quoted names, therefore the parameters <code class="code">--single</code> and <code class="code">--double</code> do nothing.
</p>
<p>
- This program does not use the parameter <code>--ignore</code>, which therefore does nothing. This parameter requires two values.
+ This program does not use the parameter <code class="code">--ignore</code>, which therefore does nothing. This parameter requires two values.
</p>
</div>
</section>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
For example, a file of 17 lines would range from 0 to 16.
</p>
<p>
- When using the <code>--depth</code> option, an order of operations is enforced on the parameters.
+ When using the <code class="code">--depth</code> option, an order of operations is enforced on the parameters.
</p>
<p>
When this order of operations is in effect, parameters to the right of a depth parameter are influenced by that depth parameter:
</p>
<dl class="dl">
<div class="di">
- <dt class="dt"><code>--at</code></dt><dd class="dd">An Object index at the specified depth.</dd>
+ <dt class="dt"><code class="code">--at</code></dt><dd class="dd">An Object index at the specified depth.</dd>
</div>
<div class="di">
- <dt class="dt"><code>--depth</code></dt><dd class="dd">A new depth within the specified depth, indexed from the root.</dd>
+ <dt class="dt"><code class="code">--depth</code></dt><dd class="dd">A new depth within the specified depth, indexed from the root.</dd>
</div>
<div class="di">
- <dt class="dt"><code><code>--name</code></code></dt><dd class="dd">An Object name at the specified depth.</dd>
+ <dt class="dt"><code class="code"><code class="code">--name</code></code></dt><dd class="dd">An Object name at the specified depth.</dd>
</div>
</dl>
<p>
- The parameter <code>--depth</code> must be in numeric order, but values in between may be skipped.
+ The parameter <code class="code">--depth</code> must be in numeric order, but values in between may be skipped.
</p>
<ul>
<li>('-d 0 -a 1 -d 2 -a 2' would specify index 1 at depth 0, any index at depth 1, and index 2 at depth 2.)</li>
<li>('-d 2 -a 1 -d 0 -a 2' would be invalid because depth 2 is before depth 1.)</li>
</ul>
<p>
- The parameter <code>--select</code> selects a Content column.
+ The parameter <code class="code">--select</code> selects a Content column.
</p>
<p>
- Specify both <code>--object</code> and the --total parameters to get the total objects.
+ Specify both <code class="code">--object</code> and the --total parameters to get the total objects.
</p>
<p>
- When both <code>--at</code> and <code>--name</code> parameters are specified (at the same depth), the <code>--at</code> parameter value will be treated as a position relative to the specified <code>--name</code> parameter value.
+ When both <code class="code">--at</code> and <code class="code">--name</code> parameters are specified (at the same depth), the <code class="code">--at</code> parameter value will be treated as a position relative to the specified <code class="code">--name</code> parameter value.
</p>
<p>
- This program may support parameters, such as <code>--depth</code> or <code>--select</code>, even if not supported by the standard.
+ This program may support parameters, such as <code class="code">--depth</code> or <code class="code">--select</code>, even if not supported by the standard.
</p>
<p>
This is done to help ensure consistency for scripting.
</p>
<p>
- For parameters like <code>--depth</code>, if the standard doesn't support nested Content, then only a depth of 0 would be valid.
+ For parameters like <code class="code">--depth</code>, if the standard doesn't support nested Content, then only a depth of 0 would be valid.
</p>
<p>
- For parameters like <code>--select</code>, if the standard doesn't support multiple Content groups, then only a select of 0 would be valid.
+ For parameters like <code class="code">--select</code>, if the standard doesn't support multiple Content groups, then only a select of 0 would be valid.
</p>
<p>
- The parameter <code>--trim</code> will remove leading and trailing white spaces when selecting objects or when printing objects.
+ The parameter <code class="code">--trim</code> will remove leading and trailing white spaces when selecting objects or when printing objects.
</p>
<p>
- When specifying both the <code>--object</code> parameter and the <code>--content</code> parameter, the entire Object and Content are printed, including the formatting.
+ When specifying both the <code class="code">--object</code> parameter and the <code class="code">--content</code> parameter, the entire Object and Content are printed, including the formatting.
</p>
<p>
Both the Object and Content printed are already escaped.
Both the Object and Content are separated by a space.
</p>
<p>
- The parameter <code>--delimit</code> accepts the following:
+ The parameter <code class="code">--delimit</code> accepts the following:
</p>
<dl class="dl">
<div class="di">
</div>
</dl>
<p>
- The <code>--delimit</code> parameter may be specified multiple times to customize the delimit behavior.
+ The <code class="code">--delimit</code> parameter may be specified multiple times to customize the delimit behavior.
</p>
<p>
- The <code>--delimit</code> values none and all, overrule all other delimit values.
+ The <code class="code">--delimit</code> values none and all, overrule all other delimit values.
</p>
<p>
- The parameters <code>--columns</code> and <code>--select</code> refer to a Content column.
+ The parameters <code class="code">--columns</code> and <code class="code">--select</code> refer to a Content column.
</p>
<p>
The word "<em>column</em>" is being loosely defined to refer to a specific Content.
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
For the pipe, an Object is terminated by either a Backspace character '<kbd>\b</kbd>' (U+0008) or a Form Feed character '<kbd>\f</kbd>' (U+000C). The end of the pipe represents the end of any Object or Content.
</p>
<p>
- The FSS-0000 (Basic) specification does not support multi-line Content, therefore the parameter <code>--prepend</code> does nothing.
+ The FSS-0000 (Basic) specification does not support multi-line Content, therefore the parameter <code class="code">--prepend</code> does nothing.
</p>
<p>
- This program does not use the parameter <code>--ignore</code>, which therefore does nothing. This parameter requires two values.
+ This program does not use the parameter <code class="code">--ignore</code>, which therefore does nothing. This parameter requires two values.
</p>
</div>
</section>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
For example, a file of 17 lines would range from 0 to 16.
</p>
<p>
- When using the <code>--depth</code> option, an order of operations is enforced on the parameters.
+ When using the <code class="code">--depth</code> option, an order of operations is enforced on the parameters.
</p>
<p>
When this order of operations is in effect, parameters to the right of a depth parameter are influenced by that depth parameter:
</p>
<dl class="dl">
<div class="di">
- <dt class="dt"><code>--at</code></dt><dd class="dd">An Object index at the specified depth.</dd>
+ <dt class="dt"><code class="code">--at</code></dt><dd class="dd">An Object index at the specified depth.</dd>
</div>
<div class="di">
- <dt class="dt"><code>--depth</code></dt><dd class="dd">A new depth within the specified depth, indexed from the root.</dd>
+ <dt class="dt"><code class="code">--depth</code></dt><dd class="dd">A new depth within the specified depth, indexed from the root.</dd>
</div>
<div class="di">
- <dt class="dt"><code><code>--name</code></code></dt><dd class="dd">An Object name at the specified depth.</dd>
+ <dt class="dt"><code class="code"><code class="code">--name</code></code></dt><dd class="dd">An Object name at the specified depth.</dd>
</div>
</dl>
<p>
- The parameter <code>--depth</code> must be in numeric order, but values in between may be skipped.
+ The parameter <code class="code">--depth</code> must be in numeric order, but values in between may be skipped.
</p>
<ul>
<li>('-d 0 -a 1 -d 2 -a 2' would specify index 1 at depth 0, any index at depth 1, and index 2 at depth 2.)</li>
<li>('-d 2 -a 1 -d 0 -a 2' would be invalid because depth 2 is before depth 1.)</li>
</ul>
<p>
- The parameter <code>--select</code> selects a Content column.
+ The parameter <code class="code">--select</code> selects a Content column.
</p>
<p>
- Specify both <code>--object</code> and the --total parameters to get the total objects.
+ Specify both <code class="code">--object</code> and the --total parameters to get the total objects.
</p>
<p>
- When both <code>--at</code> and <code>--name</code> parameters are specified (at the same depth), the <code>--at</code> parameter value will be treated as a position relative to the specified <code>--name</code> parameter value.
+ When both <code class="code">--at</code> and <code class="code">--name</code> parameters are specified (at the same depth), the <code class="code">--at</code> parameter value will be treated as a position relative to the specified <code class="code">--name</code> parameter value.
</p>
<p>
- This program may support parameters, such as <code>--depth</code> or <code>--select</code>, even if not supported by the standard.
+ This program may support parameters, such as <code class="code">--depth</code> or <code class="code">--select</code>, even if not supported by the standard.
</p>
<p>
This is done to help ensure consistency for scripting.
</p>
<p>
- For parameters like <code>--depth</code>, if the standard doesn't support nested Content, then only a depth of 0 would be valid.
+ For parameters like <code class="code">--depth</code>, if the standard doesn't support nested Content, then only a depth of 0 would be valid.
</p>
<p>
- For parameters like <code>--select</code>, if the standard doesn't support multiple Content groups, then only a select of 0 would be valid.
+ For parameters like <code class="code">--select</code>, if the standard doesn't support multiple Content groups, then only a select of 0 would be valid.
</p>
<p>
- The parameter <code>--trim</code> will remove leading and trailing white spaces when selecting objects or when printing objects.
+ The parameter <code class="code">--trim</code> will remove leading and trailing white spaces when selecting objects or when printing objects.
</p>
<p>
- When specifying both the <code>--object</code> parameter and the <code>--content</code> parameter, the entire Object and Content are printed, including the formatting.
+ When specifying both the <code class="code">--object</code> parameter and the <code class="code">--content</code> parameter, the entire Object and Content are printed, including the formatting.
</p>
<p>
Both the Object and Content printed are already escaped.
Both the Object and Content are separated by a New Line character '<kbd>\n</kbd>' (U+000A).
</p>
<p>
- The parameter <code>--delimit</code> accepts the following:
+ The parameter <code class="code">--delimit</code> accepts the following:
</p>
<dl class="dl">
<div class="di">
</div>
</dl>
<p>
- The <code>--delimit</code> parameter may be specified multiple times to customize the delimit behavior.
+ The <code class="code">--delimit</code> parameter may be specified multiple times to customize the delimit behavior.
</p>
<p>
- The <code>--delimit</code> values none and all, overrule all other delimit values.
+ The <code class="code">--delimit</code> values none and all, overrule all other delimit values.
</p>
<p>
- The parameters <code>--columns</code> and <code>--select</code> refer to a Content column.
+ The parameters <code class="code">--columns</code> and <code class="code">--select</code> refer to a Content column.
</p>
<p>
The word "<em>column</em>" is being loosely defined to refer to a specific Content.
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
For the pipe, an Object is terminated by either a Backspace character '<kbd>\b</kbd>' (U+0008) or a Form Feed character '<kbd>\f</kbd>' (U+000C). The end of the pipe represents the end of any Object or Content.
</p>
<p>
- The FSS-0008 (Embedded List) specification does not support quoted names, therefore the parameters <code>--single</code> and <code>--double</code> do nothing.
+ The FSS-0008 (Embedded List) specification does not support quoted names, therefore the parameters <code class="code">--single</code> and <code class="code">--double</code> do nothing.
</p>
<p>
- This program uses the parameter <code>--ignore</code>, which designates to not escape any valid nested Object or Content within some Content. This parameter requires two values. This parameter is not used for ignoring anything from the input pipe. This parameter must be specified after a <code>--content</code> parameter and this applies only to the Content represented by that specific <code>--content</code> parameter.
+ This program uses the parameter <code class="code">--ignore</code>, which designates to not escape any valid nested Object or Content within some Content. This parameter requires two values. This parameter is not used for ignoring anything from the input pipe. This parameter must be specified after a <code class="code">--content</code> parameter and this applies only to the Content represented by that specific <code class="code">--content</code> parameter.
</p>
</div>
</section>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
For example, a file of 17 lines would range from 0 to 16.
</p>
<p>
- When using the <code>--depth</code> option, an order of operations is enforced on the parameters.
+ When using the <code class="code">--depth</code> option, an order of operations is enforced on the parameters.
</p>
<p>
When this order of operations is in effect, parameters to the right of a depth parameter are influenced by that depth parameter:
</p>
<dl class="dl">
<div class="di">
- <dt class="dt"><code>--at</code></dt><dd class="dd">An Object index at the specified depth.</dd>
+ <dt class="dt"><code class="code">--at</code></dt><dd class="dd">An Object index at the specified depth.</dd>
</div>
<div class="di">
- <dt class="dt"><code>--depth</code></dt><dd class="dd">A new depth within the specified depth, indexed from the root.</dd>
+ <dt class="dt"><code class="code">--depth</code></dt><dd class="dd">A new depth within the specified depth, indexed from the root.</dd>
</div>
<div class="di">
- <dt class="dt"><code><code>--name</code></code></dt><dd class="dd">An Object name at the specified depth.</dd>
+ <dt class="dt"><code class="code"><code class="code">--name</code></code></dt><dd class="dd">An Object name at the specified depth.</dd>
</div>
</dl>
<p>
- The parameter <code>--depth</code> must be in numeric order, but values in between may be skipped.
+ The parameter <code class="code">--depth</code> must be in numeric order, but values in between may be skipped.
</p>
<ul>
<li>('-d 0 -a 1 -d 2 -a 2' would specify index 1 at depth 0, any index at depth 1, and index 2 at depth 2.)</li>
<li>('-d 2 -a 1 -d 0 -a 2' would be invalid because depth 2 is before depth 1.)</li>
</ul>
<p>
- The parameter <code>--select</code> selects a Content column.
+ The parameter <code class="code">--select</code> selects a Content column.
</p>
<p>
- Specify both <code>--object</code> and the --total parameters to get the total objects.
+ Specify both <code class="code">--object</code> and the --total parameters to get the total objects.
</p>
<p>
- When both <code>--at</code> and <code>--name</code> parameters are specified (at the same depth), the <code>--at</code> parameter value will be treated as a position relative to the specified <code>--name</code> parameter value.
+ When both <code class="code">--at</code> and <code class="code">--name</code> parameters are specified (at the same depth), the <code class="code">--at</code> parameter value will be treated as a position relative to the specified <code class="code">--name</code> parameter value.
</p>
<p>
- This program may support parameters, such as <code>--depth</code> or <code>--select</code>, even if not supported by the standard.
+ This program may support parameters, such as <code class="code">--depth</code> or <code class="code">--select</code>, even if not supported by the standard.
</p>
<p>
This is done to help ensure consistency for scripting.
</p>
<p>
- For parameters like <code>--depth</code>, if the standard doesn't support nested Content, then only a depth of 0 would be valid.
+ For parameters like <code class="code">--depth</code>, if the standard doesn't support nested Content, then only a depth of 0 would be valid.
</p>
<p>
- For parameters like <code>--select</code>, if the standard doesn't support multiple Content groups, then only a select of 0 would be valid.
+ For parameters like <code class="code">--select</code>, if the standard doesn't support multiple Content groups, then only a select of 0 would be valid.
</p>
<p>
- The parameter <code>--trim</code> will remove leading and trailing white spaces when selecting objects or when printing objects.
+ The parameter <code class="code">--trim</code> will remove leading and trailing white spaces when selecting objects or when printing objects.
</p>
<p>
- When specifying both the <code>--object</code> parameter and the <code>--content</code> parameter, the entire Object and Content are printed, including the formatting.
+ When specifying both the <code class="code">--object</code> parameter and the <code class="code">--content</code> parameter, the entire Object and Content are printed, including the formatting.
</p>
<p>
Both the Object and Content printed are already escaped.
Both the Object and Content are separated by a New Line character '<kbd>\n</kbd>' (U+000A).
</p>
<p>
- The parameter <code>--delimit</code> accepts the following:
+ The parameter <code class="code">--delimit</code> accepts the following:
</p>
<dl class="dl">
<div class="di">
</div>
</dl>
<p>
- The <code>--delimit</code> parameter may be specified multiple times to customize the delimit behavior.
+ The <code class="code">--delimit</code> parameter may be specified multiple times to customize the delimit behavior.
</p>
<p>
- The <code>--delimit</code> values none and all, overrule all other delimit values.
+ The <code class="code">--delimit</code> values none and all, overrule all other delimit values.
</p>
<p>
- The parameters <code>--columns</code> and <code>--select</code> refer to a Content column.
+ The parameters <code class="code">--columns</code> and <code class="code">--select</code> refer to a Content column.
</p>
<p>
The word "<em>column</em>" is being loosely defined to refer to a specific Content.
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
For the pipe, an Object is terminated by either a Backspace character '<kbd>\b</kbd>' (U+0008) or a Form Feed character '<kbd>\f</kbd>' (U+000C). The end of the pipe represents the end of any Object or Content.
</p>
<p>
- The FSS-0003 (Extended List) specification does not support quoted names, therefore the parameters <code>--single</code> and <code>--double</code> do nothing.
+ The FSS-0003 (Extended List) specification does not support quoted names, therefore the parameters <code class="code">--single</code> and <code class="code">--double</code> do nothing.
</p>
<p>
- This program uses the parameter <code>--ignore</code>, which designates to not escape any valid nested Object or Content within some Content. This parameter requires two values. This parameter is not used for ignoring anything from the input pipe. This parameter must be specified after a <code>--content</code> parameter and this applies only to the Content represented by that specific <code>--content</code> parameter.
+ This program uses the parameter <code class="code">--ignore</code>, which designates to not escape any valid nested Object or Content within some Content. This parameter requires two values. This parameter is not used for ignoring anything from the input pipe. This parameter must be specified after a <code class="code">--content</code> parameter and this applies only to the Content represented by that specific <code class="code">--content</code> parameter.
</p>
</div>
</section>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
For example, a file of 17 lines would range from 0 to 16.
</p>
<p>
- When using the <code>--depth</code> option, an order of operations is enforced on the parameters.
+ When using the <code class="code">--depth</code> option, an order of operations is enforced on the parameters.
</p>
<p>
When this order of operations is in effect, parameters to the right of a depth parameter are influenced by that depth parameter:
</p>
<dl class="dl">
<div class="di">
- <dt class="dt"><code>--at</code></dt><dd class="dd">An Object index at the specified depth.</dd>
+ <dt class="dt"><code class="code">--at</code></dt><dd class="dd">An Object index at the specified depth.</dd>
</div>
<div class="di">
- <dt class="dt"><code>--depth</code></dt><dd class="dd">A new depth within the specified depth, indexed from the root.</dd>
+ <dt class="dt"><code class="code">--depth</code></dt><dd class="dd">A new depth within the specified depth, indexed from the root.</dd>
</div>
<div class="di">
- <dt class="dt"><code><code>--name</code></code></dt><dd class="dd">An Object name at the specified depth.</dd>
+ <dt class="dt"><code class="code"><code class="code">--name</code></code></dt><dd class="dd">An Object name at the specified depth.</dd>
</div>
<div class="di">
</dl>
<p>
- The parameter <code>--depth</code> must be in numeric order, but values in between may be skipped.
+ The parameter <code class="code">--depth</code> must be in numeric order, but values in between may be skipped.
</p>
<ul>
<li>('-d 0 -a 1 -d 2 -a 2' would specify index 1 at depth 0, any index at depth 1, and index 2 at depth 2.)</li>
<li>('-d 2 -a 1 -d 0 -a 2' would be invalid because depth 2 is before depth 1.)</li>
</ul>
<p>
- The parameter <code>--select</code> selects a Content column.
+ The parameter <code class="code">--select</code> selects a Content column.
</p>
<p>
- Specify both <code>--object</code> and the --total parameters to get the total objects.
+ Specify both <code class="code">--object</code> and the --total parameters to get the total objects.
</p>
<p>
- When both <code>--at</code> and <code>--name</code> parameters are specified (at the same depth), the <code>--at</code> parameter value will be treated as a position relative to the specified <code>--name</code> parameter value.
+ When both <code class="code">--at</code> and <code class="code">--name</code> parameters are specified (at the same depth), the <code class="code">--at</code> parameter value will be treated as a position relative to the specified <code class="code">--name</code> parameter value.
</p>
<p>
- This program may support parameters, such as <code>--depth</code> or <code>--select</code>, even if not supported by the standard.
+ This program may support parameters, such as <code class="code">--depth</code> or <code class="code">--select</code>, even if not supported by the standard.
</p>
<p>
This is done to help ensure consistency for scripting.
</p>
<p>
- For parameters like <code>--depth</code>, if the standard doesn't support nested Content, then only a depth of 0 would be valid.
+ For parameters like <code class="code">--depth</code>, if the standard doesn't support nested Content, then only a depth of 0 would be valid.
</p>
<p>
- For parameters like <code>--select</code>, if the standard doesn't support multiple Content groups, then only a select of 0 would be valid.
+ For parameters like <code class="code">--select</code>, if the standard doesn't support multiple Content groups, then only a select of 0 would be valid.
</p>
<p>
- The parameter <code>--trim</code> will remove leading and trailing white spaces when selecting objects or when printing objects.
+ The parameter <code class="code">--trim</code> will remove leading and trailing white spaces when selecting objects or when printing objects.
</p>
<p>
- When specifying both the <code>--object</code> parameter and the <code>--content</code> parameter, the entire Object and Content are printed, including the formatting.
+ When specifying both the <code class="code">--object</code> parameter and the <code class="code">--content</code> parameter, the entire Object and Content are printed, including the formatting.
</p>
<p>
Both the Object and Content printed are already escaped.
Both the Object and Content are separated by a space.
</p>
<p>
- The parameter <code>--delimit</code> accepts the following:
+ The parameter <code class="code">--delimit</code> accepts the following:
</p>
<dl class="dl">
<div class="di">
</div>
</dl>
<p>
- The <code>--delimit</code> parameter may be specified multiple times to customize the delimit behavior.
+ The <code class="code">--delimit</code> parameter may be specified multiple times to customize the delimit behavior.
</p>
<p>
- The <code>--delimit</code> values none and all, overrule all other delimit values.
+ The <code class="code">--delimit</code> values none and all, overrule all other delimit values.
</p>
<p>
- The parameters <code>--columns</code> and <code>--select</code> refer to a Content column.
+ The parameters <code class="code">--columns</code> and <code class="code">--select</code> refer to a Content column.
</p>
<p>
The word "<em>column</em>" is being loosely defined to refer to a specific Content.
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
For the pipe, an Object is terminated by either a Backspace character '<kbd>\b</kbd>' (U+0008) or a Form Feed character '<kbd>\f</kbd>' (U+000C). The end of the pipe represents the end of any Object or Content.
</p>
<p>
- The FSS-0001 (Extended) specification does not support multi-line Content, therefore the parameter <code>--prepend</code> does nothing.
+ The FSS-0001 (Extended) specification does not support multi-line Content, therefore the parameter <code class="code">--prepend</code> does nothing.
</p>
<p>
- This program does not use the parameter <code>--ignore</code>, which therefore does nothing. This parameter requires two values.
+ This program does not use the parameter <code class="code">--ignore</code>, which therefore does nothing. This parameter requires two values.
</p>
</div>
</section>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
</table>
</div>
<p>
- The <code>--line</code> parameter refers to the file lines and not the lines in a given file.
+ The <code class="code">--line</code> parameter refers to the file lines and not the lines in a given file.
</p>
<p>
- If neither the <code>--object</code> nor <code>--content</code> are specified, then the default behavior is to print both.
+ If neither the <code class="code">--object</code> nor <code class="code">--content</code> are specified, then the default behavior is to print both.
</p>
<p>
- When specifying the <code>--total</code> parameter, neither the <code>--object</code> nor the <code>--content</code> parameter may be specified.
+ When specifying the <code class="code">--total</code> parameter, neither the <code class="code">--object</code> nor the <code class="code">--content</code> parameter may be specified.
</p>
<p>
- An FSS file is identified by the format "<code># Object-Content</code>" where the Object, is a machine-name representing the name and may only consist of "word" characters and the Content is a 4-digit hexidecimal number representing a particular variant of the Object. This identifier, if provided, must exist on the first line in a file and must begin with the pound character: "<code>#</code>". White space must follow this pound character. There may be multiple Object and Content pairs, separated by white space, such as: "<code># fss-0002 fss-0000 iki-0002</code>".
+ An FSS file is identified by the format "<code class="code"># Object-Content</code>" where the Object, is a machine-name representing the name and may only consist of "word" characters and the Content is a 4-digit hexidecimal number representing a particular variant of the Object. This identifier, if provided, must exist on the first line in a file and must begin with the pound character: "<code class="code">#</code>". White space must follow this pound character. There may be multiple Object and Content pairs, separated by white space, such as: "<code class="code"># fss-0002 fss-0000 iki-0002</code>".
</p>
</div>
</section>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
For example, a file of 17 lines would range from 0 to 16.
</p>
<p>
- When using the <code>--depth</code> option, an order of operations is enforced on the parameters.
+ When using the <code class="code">--depth</code> option, an order of operations is enforced on the parameters.
</p>
<p>
When this order of operations is in effect, parameters to the right of a depth parameter are influenced by that depth parameter:
</p>
<dl class="dl">
<div class="di">
- <dt class="dt"><code>--at</code></dt><dd class="dd">An Object index at the specified depth.</dd>
+ <dt class="dt"><code class="code">--at</code></dt><dd class="dd">An Object index at the specified depth.</dd>
</div>
<div class="di">
- <dt class="dt"><code>--depth</code></dt><dd class="dd">A new depth within the specified depth, indexed from the root.</dd>
+ <dt class="dt"><code class="code">--depth</code></dt><dd class="dd">A new depth within the specified depth, indexed from the root.</dd>
</div>
<div class="di">
- <dt class="dt"><code><code>--name</code></code></dt><dd class="dd">An Object name at the specified depth.</dd>
+ <dt class="dt"><code class="code"><code class="code">--name</code></code></dt><dd class="dd">An Object name at the specified depth.</dd>
</div>
</dl>
<p>
- The parameter <code>--depth</code> must be in numeric order, but values in between may be skipped.
+ The parameter <code class="code">--depth</code> must be in numeric order, but values in between may be skipped.
</p>
<ul>
<li>('-d 0 -a 1 -d 2 -a 2' would specify index 1 at depth 0, any index at depth 1, and index 2 at depth 2.)</li>
<li>('-d 2 -a 1 -d 0 -a 2' would be invalid because depth 2 is before depth 1.)</li>
</ul>
<p>
- The parameter <code>--select</code> selects a Content column.
+ The parameter <code class="code">--select</code> selects a Content column.
</p>
<p>
- Specify both <code>--object</code> and the --total parameters to get the total objects.
+ Specify both <code class="code">--object</code> and the --total parameters to get the total objects.
</p>
<p>
- When both <code>--at</code> and <code>--name</code> parameters are specified (at the same depth), the <code>--at</code> parameter value will be treated as a position relative to the specified <code>--name</code> parameter value.
+ When both <code class="code">--at</code> and <code class="code">--name</code> parameters are specified (at the same depth), the <code class="code">--at</code> parameter value will be treated as a position relative to the specified <code class="code">--name</code> parameter value.
</p>
<p>
- This program may support parameters, such as <code>--depth</code> or <code>--select</code>, even if not supported by the standard.
+ This program may support parameters, such as <code class="code">--depth</code> or <code class="code">--select</code>, even if not supported by the standard.
</p>
<p>
This is done to help ensure consistency for scripting.
</p>
<p>
- For parameters like <code>--depth</code>, if the standard doesn't support nested Content, then only a depth of 0 would be valid.
+ For parameters like <code class="code">--depth</code>, if the standard doesn't support nested Content, then only a depth of 0 would be valid.
</p>
<p>
- For parameters like <code>--select</code>, if the standard doesn't support multiple Content groups, then only a select of 0 would be valid.
+ For parameters like <code class="code">--select</code>, if the standard doesn't support multiple Content groups, then only a select of 0 would be valid.
</p>
<p>
- The parameter <code>--trim</code> will remove leading and trailing white spaces when selecting objects or when printing objects.
+ The parameter <code class="code">--trim</code> will remove leading and trailing white spaces when selecting objects or when printing objects.
</p>
<p>
- When specifying both the <code>--object</code> parameter and the <code>--content</code> parameter, the entire Object and Content are printed, including the formatting.
+ When specifying both the <code class="code">--object</code> parameter and the <code class="code">--content</code> parameter, the entire Object and Content are printed, including the formatting.
</p>
<p>
Both the Object and Content printed are already escaped.
Both the Object and Content are separated by a New Line character '<kbd>\n</kbd>' (U+000A).
</p>
<p>
- The parameter <code>--delimit</code> accepts the following:
+ The parameter <code class="code">--delimit</code> accepts the following:
</p>
<dl class="dl">
<div class="di">
</div>
</dl>
<p>
- The <code>--delimit</code> parameter may be specified multiple times to customize the delimit behavior.
+ The <code class="code">--delimit</code> parameter may be specified multiple times to customize the delimit behavior.
</p>
<p>
- The <code>--delimit</code> values none and all, overrule all other delimit values.
+ The <code class="code">--delimit</code> values none and all, overrule all other delimit values.
</p>
<p>
- The parameters <code>--columns</code> and <code>--select</code> refer to a Content column.
+ The parameters <code class="code">--columns</code> and <code class="code">--select</code> refer to a Content column.
</p>
<p>
The word "<em>column</em>" is being loosely defined to refer to a specific Content.
This is not to be confused with a depth.
</p>
<p>
- As an exceptional case, a <code>--depth</code> of 1 applies only to the explicit Object of "<em>header</em>".
+ As an exceptional case, a <code class="code">--depth</code> of 1 applies only to the explicit Object of "<em>header</em>".
</p>
<p>
Content at this depth is processed as FSS-0001 (Extended).
</p>
<p>
- The Content of the explicit Object of 'payload' will not contain any Content close pipe control codes when using <code>--pipe</code>.
+ The Content of the explicit Object of 'payload' will not contain any Content close pipe control codes when using <code class="code">--pipe</code>.
</p>
</div>
</section>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
For the pipe, an Object is terminated by either a Backspace character '<kbd>\b</kbd>' (U+0008) or a Form Feed character '<kbd>\f</kbd>' (U+000C). The end of the pipe represents the end of any Object or Content.
</p>
<p>
- The FSS-000E (Payload) specification does not support quoted names, therefore the parameters <code>--single</code> and <code>--double</code> do nothing.
+ The FSS-000E (Payload) specification does not support quoted names, therefore the parameters <code class="code">--single</code> and <code class="code">--double</code> do nothing.
</p>
<p>
- This program does not use the parameter <code>--ignore</code>, which therefore does nothing. This parameter requires two values.
+ This program does not use the parameter <code class="code">--ignore</code>, which therefore does nothing. This parameter requires two values.
</p>
</div>
</section>
The <strong>fss_status_code</strong> program is a tool for interpretting and changing the status codes received from programs into code words or vice-versa. This is intended to be easily scriptable. The code words are still machine-friendly and scriptable.
</p>
<p>
- This program handles standard <abbr title="Featureless Linux Library">FLL</abbr> status codes as well as <abbr title="Featureless Settings Specifications">FSS</abbr> status codes. The max status code supported is represented by the code words <code>F_fss_status_code_last</code>.
+ This program handles standard <abbr title="Featureless Linux Library">FLL</abbr> status codes as well as <abbr title="Featureless Settings Specifications">FSS</abbr> status codes. The max status code supported is represented by the code words <code class="code">F_fss_status_code_last</code>.
</p>
</div>
</section>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
<tr class="row">
<td class="column"><code class="code">-f</code></td>
<td class="column"><code class="code">--fine</code></td>
- <td class="column">Print <code>F_true</code> or <code>F_false</code> if status code is neither an error nor a warning or print number with neither the error code nor the warning code bits set.</td>
+ <td class="column">Print <code class="code">F_true</code> or <code class="code">F_false</code> if status code is neither an error nor a warning or print number with neither the error code nor the warning code bits set.</td>
</tr>
<tr class="row">
<td class="column"><code class="code">-w</code></td>
<td class="column"><code class="code">--warning</code></td>
- <td class="column">Print <code>F_true</code> or <code>F_false</code> if status code is a warning or print number with warning code bit set.</td>
+ <td class="column">Print <code class="code">F_true</code> or <code class="code">F_false</code> if status code is a warning or print number with warning code bit set.</td>
</tr>
<tr class="row">
<td class="column"><code class="code">-e</code></td>
<td class="column"><code class="code">--error</code></td>
- <td class="column">Print <code>F_true</code> or <code>F_false</code> if status code is an error or print number with error code bit set.</td>
+ <td class="column">Print <code class="code">F_true</code> or <code class="code">F_false</code> if status code is an error or print number with error code bit set.</td>
</tr>
<tr class="row">
<td class="column"><code class="code">-n</code></td>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
</table>
</div>
<p>
- The <code>-r/--replace</code> option requires 2 additional parameters: <code><vocabulary> <with></code>.
+ The <code class="code">-r/--replace</code> option requires 2 additional parameters: <code class="code"><vocabulary> <with></code>.
</p>
<dl class="dl">
<div class="di">
</div>
</dl>
<p>
- The <code>-s/--substitute</code> option requires 3 additional parameters: <code><vocabulary> <replace> <with></code>.
+ The <code class="code">-s/--substitute</code> option requires 3 additional parameters: <code class="code"><vocabulary> <replace> <with></code>.
</p>
<dl class="dl">
<div class="di">
The <em>vocabulary</em> and <em>replacement</em> are case-sensitive and must exactly match.
</p>
<p>
- The <code>-W/--wrap</code> option requires 3 additional parameters: <code><vocabulary> <before> <after></code>.
+ The <code class="code">-W/--wrap</code> option requires 3 additional parameters: <code class="code"><vocabulary> <before> <after></code>.
</p>
<dl class="dl">
<div class="di">
</div>
</dl>
<p>
- The difference between <code>-r/--replace</code> and <code>-s/--substitute</code> is that the <code>-r/--replace</code> option substitutes all matching vocabulary names and the <code>-s/--substitute</code> option substitutes all matching vocabulary names that must also have the given matching content.
+ The difference between <code class="code">-r/--replace</code> and <code class="code">-s/--substitute</code> is that the <code class="code">-r/--replace</code> option substitutes all matching vocabulary names and the <code class="code">-s/--substitute</code> option substitutes all matching vocabulary names that must also have the given matching content.
</p>
<p>
- The <code>-s/--substitute</code> option takes priority over the <code>-r/--replace</code> option when matching the same variable.
+ The <code class="code">-s/--substitute</code> option takes priority over the <code class="code">-r/--replace</code> option when matching the same variable.
</p>
<p>
- The <code>-W/--wrap</code> option is ignored when the <code>-s/--substitute</code> option is matching the same variable.
+ The <code class="code">-W/--wrap</code> option is ignored when the <code class="code">-s/--substitute</code> option is matching the same variable.
</p>
<p>
The default behavior is to only display content portion of the IKI variable.
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
The <strong>status_code</strong> program is a tool for interpretting and changing the status codes received from programs into code words or vice-versa. This is intended to be easily scriptable. The code words are still machine-friendly and scriptable.
</p>
<p>
- This tool only handles standard <abbr title="Featureless Linux Library">FLL</abbr> status codes. The max status code supported is represented by the code words <code>F_status_code_last</code>.
+ This tool only handles standard <abbr title="Featureless Linux Library">FLL</abbr> status codes. The max status code supported is represented by the code words <code class="code">F_status_code_last</code>.
</p>
</div>
</section>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
<tr class="row">
<td class="column"><code class="code">-f</code></td>
<td class="column"><code class="code">--fine</code></td>
- <td class="column">Print <code>F_true</code> or <code>F_false</code> if status code is neither an error nor a warning or print number with neither the error code nor the warning code bits set.</td>
+ <td class="column">Print <code class="code">F_true</code> or <code class="code">F_false</code> if status code is neither an error nor a warning or print number with neither the error code nor the warning code bits set.</td>
</tr>
<tr class="row">
<td class="column"><code class="code">-w</code></td>
<td class="column"><code class="code">--warning</code></td>
- <td class="column">Print <code>F_true</code> or <code>F_false</code> if status code is a warning or print number with warning code bit set.</td>
+ <td class="column">Print <code class="code">F_true</code> or <code class="code">F_false</code> if status code is a warning or print number with warning code bit set.</td>
</tr>
<tr class="row">
<td class="column"><code class="code">-e</code></td>
<td class="column"><code class="code">--error</code></td>
- <td class="column">Print <code>F_true</code> or <code>F_false</code> if status code is an error or print number with error code bit set.</td>
+ <td class="column">Print <code class="code">F_true</code> or <code class="code">F_false</code> if status code is an error or print number with error code bit set.</td>
</tr>
<tr class="row">
<td class="column"><code class="code">-n</code></td>
</table>
</div>
<p>
- The <code>+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code>+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code>+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
+ The <code class="code">+q/++quiet</code> parameter silences all output that is not the intent and purpose of the program. For example, the purpose of the <strong>utf8</strong> program is to print the Unicode code point or the <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> byte code. The <code class="code">+q/++quiet</code> will not suppress this output. The new line printed at the end of the program, is however, not printed. The <code class="code">+q/++quiet</code> is ideal for using in scripting to help guarantee more consistent and controlled output.
</p>
<p>
- The <code>+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
+ The <code class="code">+n/++no_color</code> simplifies the output to avoid the special color character codes. The special color character codes tend to take up a lot of extra space and may slow down printing performance.
</p>
</div>
</section>
Multiple input sources are allowed but only a single output destination is allowed.
</p>
<p>
- When using the parameter <code>--verify</code>, no data is printed and 0 is returned if valid or 1 is returned if invalid.
+ When using the parameter <code class="code">--verify</code>, no data is printed and 0 is returned if valid or 1 is returned if invalid.
</p>
<p>
- When using the parameter <code>--to_combining</code> with the parameter <code>--to_width</code>, the 'C' character is printed to represent the combining and the digits are used to represent widths. The combining characters should be considered 1-width by themselves or 0-width when combined.
+ When using the parameter <code class="code">--to_combining</code> with the parameter <code class="code">--to_width</code>, the 'C' character is printed to represent the combining and the digits are used to represent widths. The combining characters should be considered 1-width by themselves or 0-width when combined.
</p>
</div>
</section>
<div class="nav-item block">
<a href="fll.html#release" class="nav-text link">Current Release</a>
</div>
+ <div class="nav-item block">
+ <a href="fll/specifications.html" class="nav-text link">Specifications</a>
+ </div>
<div class="nav-item block ellipses">
<a href="fll.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
<a href="fll.html" class="nav-text link close">Collapse Menu</a>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications</title>
+
+ <base href="../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">Featureless Linux Library</div>
+ <div class="nav-text unlink">Specifications</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications.html#about" class="nav-text link">About</a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications.html#fss" class="nav-text link">Featureless Settings Specifications</a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0000.html" class="nav-text link"><div>FSS-0000</div><div>(Basic)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0001.html" class="nav-text link"><div>FSS-0001</div><div>(Extended)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0002.html" class="nav-text link"><div>FSS-0002</div><div>(Basic List)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0003.html" class="nav-text link"><div>FSS-0003</div><div>(Extended List)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0004.html" class="nav-text link"><div>FSS-0004</div><div>(Very Basic List)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0005.html" class="nav-text link"><div>FSS-0005</div><div>(Somewhat Basic List)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0006.html" class="nav-text link"><div>FSS-0006</div><div>(Somewhat Extended List)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0007.html" class="nav-text link"><div>FSS-0007</div><div>(Very Extended List)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0008.html" class="nav-text link"><div>FSS-0008</div><div>(Embedded List)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0009.html" class="nav-text link"><div>FSS-0009</div><div>(Reverse Mapping)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-000a.html" class="nav-text link"><div>FSS-000A</div><div>(Extended Reverse Mapping)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-000b.html" class="nav-text link"><div>FSS-000B</div><div>(Simple List)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-000c.html" class="nav-text link"><div>FSS-000C</div><div>(IKI Text)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-000d.html" class="nav-text link"><div>FSS-000D</div><div>(Basic Rule)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-000e.html" class="nav-text link"><div>FSS-000E</div><div>(Payload)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-000f.html" class="nav-text link"><div>FSS-000F</div><div>(Simple Packet)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications.html#iki" class="nav-text link">IKI</a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/iki/iki-0000.html" class="nav-text link"><div>IKI-0000</div><div>(Unrestricted)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/iki/iki-0001.html" class="nav-text link"><div>IKI-0001</div><div>(Basic)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/iki/iki-0002.html" class="nav-text link"><div>IKI-0002</div><div>(Simple Script)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications.html#completeness_theorem" class="nav-text link">Completeness Theorem</a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications.html#terminology" class="nav-text link">Terminology</a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specifications</h1>
+ </header>
+
+ <section id="about" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">About</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ The Featureless Linux Library defines several standards for use in this project. Many of these standards are defined via the Featureless Settings Specifications. Most of these are focused on settings files (configuration files) but are written general enough to support a wide range of uses. The original project that the <abbr title="Featureless Linux Library">FLL</abbr> project is built around is the <em>Featureless Make</em> program, also called <strong>Fake</strong>. The <strong>Fake</strong> program is a great example on how the <abbr title="Featureless Settings Specifications">FSS</abbr> are intended to be used.
+ </p>
+ <p>
+ The standards are not limited to those defined in the <abbr title="Featureless Settings Specifications">FSS</abbr>. There are the <em>IKI</em> standards (which is not an acronym). The term <em>IKI</em> plays off of the term <em>Wiki</em>. The <em>IKI</em> standard is intended to have simpler syntax than a <em>Wiki</em> syntax and is used in several <abbr title="Featureless Linux Library">FLL</abbr> projects and even inside standards defined by <abbr title="Featureless Settings Specifications">FSS</abbr>.
+ </p>
+ </div>
+ </section>
+
+ <section id="fss" class="section">
+ <header class="section-header header separate">
+ <h2 class="section-title h h2">Featureless Settings Specifications</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ The Featureless Settings Specifications describe a set of standards designed around the age-old design principle referred to as <em>Keep It Simple Stupid</em>, aka <abbr title="Keep It Simple Stupid">KISS</abbr>. The <abbr title="Featureless Settings Specifications">FSS</abbr> are primarily intended for settings files but are extensible enough to be used beyond that.
+ </p>
+ <p>
+ The <abbr title="Featureless Settings Specifications">FSS</abbr> defines the following:
+ </p>
+ <ul>
+ <li>Will consist of numerous different kinds of specification files, depending on the type of information stored.</li>
+ <li>As with the practice of "<code class="code">#!/bin/bash</code>", the setting files <em>should</em> have the following: "<code class="code"># fss-????" format, such as "# fss-0001</code>".</li>
+ <li>Multiple sub-standards may be appended to the FSS header, using the same format structure, such as supporting IKI: "# fss-0000 iki-0000" or HTML5: "# fss-0000 html-0005".</li>
+ <li>With the <code class="code">?</code> representing the (hexadecimal/base-16) number that represents the particular specification structure.</li>
+ <li>All settings specifications <em>should</em> avoid any form of noise, relative to the data being stored.</li>
+ <li><abbr title="Extensible Markup Language">XML</abbr> would be considered anti-<abbr title="Keep It Simple Stupid">KISS</abbr> due to the extreme level of noise generated by the <abbr title="Extensible Markup Language">XML</abbr> language (not easy to read).</li>
+ <li>The settings files are setup so that they should (reasonably) produce easy readability on both the console and in a GUI.</li>
+ <li>The specifications should strive for completeness (see the <a href="fll/specifications.html#completeness_theorem" class="link">Completeness Theorem</a>).</li>
+ </ul>
+ <p>
+ The most basic form of <abbr title="Featureless Settings Specifications">FSS</abbr> consists of two main parts: an <em>Object</em> and the <em>Content</em>.
+ </p>
+ <dl class="dl">
+ <div class="di">
+ <dt class="dt"><strong>Object</strong></dt>
+ <dd class="dd">Considered the name or identifier of some property or data. Objects do not require an associated <em>Content</em>.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt"><strong>Content</strong></dt>
+ <dd class="dd">The data associated with a given Object; all Content <em>must</em> have an associated <em>Object</em>.</dd>
+ </div>
+ </dl>
+ <p>
+ Objects and Contents can include any characters allowed by the specifications.
+ The specification may choose how a given Object or Content are represented and parsed.
+ For example, in <code class="code">fss-0000 (Basic)</code>, Content is treated as a single item whereas in <code class="code">fss-0001 (Extended)</code>, Content is broken apart in multiple sub parts.
+ </p>
+ <p>
+ Contents may be broken up into zero or more discrete sets of Content.
+ Each of these discrete sets of Content are referred to as a column.
+ These columns do not need to be setup in a column structure, the word <em>column</em> is simply used as a grouping terminology.
+ While a Content refers to the entire set, a column (more specifically, a Content column) refers to the individual discrete sets within the Content.
+ For example, in <code class="code">fss-000 (Basic)</code> the entire Content may be further represented as a single column.
+ For example, in <code class="code">fss-001 (Extended)</code> the entire Content may be further represented as multiple columns.
+ </p>
+ <p>
+ In all cases, specifications that separate Objects from Contents using white space, the first white space separating the Object and Content must not be considered part of the Object nor part of the Content.
+ All spaces after the first separating white space is generally ignored until the first non white space character is found, unless otherwise specified.
+ </p>
+ <p>
+ Unless otherwise specified, all specifications are newline sensitive (<code class="code">\n</code> only).
+ Newline characters are only <code class="code">\n</code> and are never anything else (<code class="code">\r</code> is not considered newline in any manner).
+ White spaces characters that are printable, such as tabs and spaces, must be considered the same type for the purposes of parsing.
+ Non-printing white spaces characters (zero-width characters) are ignored, are treated as placeholders for processing, or are considered part of the appropriate character if they are Unicode combining characters (this includes zero-width punctuation characters and similar).
+ In terms of processing, it is recommended that the <code class="code">NULL</code> character is not considered the end of a string, but this is only a suggestion.
+ </p>
+ <p>
+ Unless otherwise specified, newlines designate the potential start (or end) of an Object or Content.
+ </p>
+ <p>
+ Unless otherwise specified, white space may exist to the left of the start of Objects.
+ Unless otherwise specified, white space may exist to the right of the end of Objects, but only if that given Object is properly quoted and the white space is after the terminating quote but before any Content.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ Unless otherwise specified, quotes may only be either a single quote <code class="code">'</code> or a double quote <code class="code">"</code> and only a backslash <code class="code">\</code> may be used as a delimiter.
+ </p>
+ <p>
+ For example, <code class="code">fss-0000 (Basic)</code>:
+ </p>
+ <ul>
+ <li><code class="code">\"Object 1"</code> has content starting at the <code class="code">1</code>, with an Object named <code class="code">"Object</code>.</li>
+ <li><code class="code">\\"Object 1"</code> has content starting at the <code class="code">1</code>, with an Object named <code class="code">\"Object</code>.</li>
+ <li><code class="code">"Object 1\"</code> is an unterminated object due to the escaped closing quote.</li>
+ <li><code class="code">"Object 1\\"</code> has content starting at the <code class="code">has</code>, with an Object named <code class="code">"Object 1\"</code>.</li>
+ </ul>
+ <p>
+ 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.
+ For example, <code class="code">fss-0001 (Extended)</code> needs quotes to group parts that include spaces, if there is no initial quote, then a quote following the data <em>must not</em> be delimited.
+ </p>
+ <p>
+ Such as these following three lines:
+ </p><pre class="preserve">
+"Object 1" "This is a single quoted Content." \"Additional unquoted Content."
+Object_2 This is multiple" Contents and the trailing quote does not need to be delimited.
+"Object \"3" 'Wouldn't require delimits if no white space or end of string after.'
+</pre>
+ <p>
+ Unlike this specification, a more traditional delimit process would have the above three lines instead represented as:
+ </p><pre class="preserve">
+"Object 1" "This is a single quoted Content." \"Additional unquoted Content.\"
+Object_2 This is multiple\" Contents and the trailing quote does not need to be delimited.
+"Object \\"3" 'Wouldn\'t require delimits if no white space or end of string after.'
+</pre>
+ <p>
+ These examples would resolve as follows:
+ </p><pre class="preserve">
+1) Object\:
+ - Object 1
+ Content\:
+ - This is a single quoted Content.
+ - "Additional
+ - unquoted
+ - Content"
+2) Object\:
+ - Object_2
+ Content\:
+ - This
+ - is
+ - multiple"
+ - Contents
+ - and
+ - the
+ - trailing
+ - quote
+ - does
+ - not
+ - need
+ - to
+ - be
+ - delimited.
+3) Object\:
+ - Object \"3
+ Content\:
+ - Wouldn't require delimits if no white space or end of string after.
+</pre>
+ <p>
+ All specifications are expected to support or be of the character encoding <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr>; 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.
+ All specifications do assume <abbr title="American Standard Code for Information Interchange">ASCII</abbr> and Unicode support.
+ </p>
+ <p>
+ Unless otherwise specified, comments are designated by the pound symbol <code class="code">#</code> but only if only white space is to the left of the pound or the pound <code class="code">#</code> is at the start of the line.
+ There is no support for inline comments.
+ Unless otherwise specified, the start comment may be delimited by <code class="code">" in the same manner as Objects and Contents are.
+ This delimit only applies to the start of a comment (the pound code:</code>#" character) as there is no terminating character for a comment (other than a newline <code class="code">\n</code>).
+ 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 <code class="code">#</code> character) then that white space is ignored.
+ </p>
+ <p>
+ Unless otherwise specified, all designation characters <em>must</em> represent <abbr title="American Standard Code for Information Interchange">ASCII</abbr> codes.
+ With designation characters being any character code used to designate how to identify an Object or Content (such as a colon <code class="code">:</code> at the end of a basic list).
+ This keeps the processing and logic simple and safe, for both <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> and <abbr title="American Standard Code for Information Interchange">ASCII</abbr>.
+ White space used for designation characters <em>must</em> include support for <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> 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.
+ Any visible/graph character that is considered a white space (such as <code class="code">U+1680</code> <code class="code"> </code>) is not to be considered a white space, unless otherwise specified.
+ </p>
+ <p>
+ When used for syntax matching purposes, zero-width Unicode characters are only to be considered zero-width unless otherwise specified.
+ For example, the <em>invisible plus</em> character (<code class="code">U+2064</code>) is not to be considered as a plus.
+ </p>
+ <p>
+ The <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> <abbr title="Byte Order Mark">BOM</abbr> is not allowed as a Byte Order Mark; instead, it must always be treated as the character represented by its code (unless explicitly allowed to represent a <abbr title="Byte Order Mark">BOM</abbr> by a standard).
+ </p>
+ <p>
+ The only Unicode dash-like characters allowed as a <em>dash</em> are those intended to connect, such as the Unicode hyphens (<code class="code">U+2010</code> and <code class="code">U+2011</code>) (unless otherwise specified).
+ </p>
+ <p>
+ In any specification where security is intended, if there exists a Unicode character that matches an <abbr title="American Standard Code for Information Interchange">ASCII</abbr> character, that Unicode character <em>may</em> be prohibited by that standard in favor of the <abbr title="American Standard Code for Information Interchange">ASCII</abbr> equivalent.
+ One such example is in the case of a <abbr title="Byte Order Mark">URL</abbr>, where the name could be used to trick a person (<code class="code">http://this-site.com/</code> vs <code class="code">http://this‐site.com/</code>).
+ This (potential insecure behavior) is allowed in general because a well written program would be able to detect and communicate the possible misunderstanding and thereby avoid mistakes without imposing any character restrictions.
+ </p>
+ <p>
+ This is a common behavior for security reasons, each character used for any special purposes must be visibly distinct, with white space and non-printing characters as the exception to the words <em>visibly distinct</em>.
+ </p>
+ <p>
+ The following are core specifications (each with a common name associated with the specification number):
+ </p>
+ <ul>
+ <li><a href="fll/specifications/fss/fss-0000.html" class="link">fss-0000: Basic</a></li>
+ <li><a href="fll/specifications/fss/fss-0001.html" class="link">fss-0001: Extended</a></li>
+ <li><a href="fll/specifications/fss/fss-0002.html" class="link">fss-0002: Basic List</a></li>
+ <li><a href="fll/specifications/fss/fss-0003.html" class="link">fss-0003: Extended List</a></li>
+ <li><a href="fll/specifications/fss/fss-0004.html" class="link">fss-0004: Very Basic List</a></li>
+ <li><a href="fll/specifications/fss/fss-0005.html" class="link">fss-0005: Somewhat Basic List</a></li>
+ <li><a href="fll/specifications/fss/fss-0006.html" class="link">fss-0006: Somewhat Extended List</a></li>
+ <li><a href="fll/specifications/fss/fss-0007.html" class="link">fss-0007: Very Extended List</a></li>
+ <li><a href="fll/specifications/fss/fss-0008.html" class="link">fss-0008: Embedded List</a></li>
+ <li><a href="fll/specifications/fss/fss-0009.html" class="link">fss-0009: Reverse Mapping</a></li>
+ <li><a href="fll/specifications/fss/fss-000a.html" class="link">fss-000a: Extended Reverse Mapping</a></li>
+ <li><a href="fll/specifications/fss/fss-000b.html" class="link">fss-000b: Simple List</a></li>
+ <li><a href="fll/specifications/fss/fss-000c.html" class="link">fss-000c: Iki Text</a></li>
+ <li><a href="fll/specifications/fss/fss-000d.html" class="link">fss-000d: Basic Rule</a></li>
+ <li><a href="fll/specifications/fss/fss-000e.html" class="link">fss-000e: Payload</a></li>
+ <li><a href="fll/specifications/fss/fss-000f.html" class="link">fss-000f: Simple Packet</a></li>
+ </ul>
+ </div>
+ </section>
+
+ <section id="iki" class="section">
+ <header class="section-header header separate">
+ <h2 class="section-title h h2">IKI</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ IKI is a minimally structured WIKI-like syntax meant to be simpler than WIKI syntax.
+ </p>
+ <p>
+ The IKI syntax provides a vocabulary name (with specific context associated with it) followed by quoted code that is associated with the given vocabulary name.
+ The vocabulary represents a list of allowed variable names that may also have specific contextual meaning defined by a given IKI specification.
+ The variable name is considered the <em>Object</em>.
+ The variable value is considered the <em>Content</em>.
+ </p>
+ <p>
+ The IKI format will use <code class="code">iki-0000</code> to represent an IKI with no explicitly defined vocabulary.
+ Whereas <code class="code">iki-0001</code> and beyond represent a specific IKI vocabulary.
+ </p>
+ <p>
+ A potential IKI variable name starts on word (or <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code>) characters.
+ White space and non-word (and non <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code>) 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 (<code class="code">U+2010</code> and <code class="code">U+2011</code>).
+ </p>
+ <p>
+ Any valid IKI data may be escaped to make it treated as non-IKI data by prepending a backslash <code class="code">" before the colon code:</code>:" that is before the opening quote (single or double).
+ </p>
+ <p>
+ Unicode punctuation connector characters are supported just like <code class="code">_</code>, except when they connect outside the current line (such as <code class="code">U+FE33</code> <code class="code">︳</code>).
+ Unicode invisible punctuations (such as invisible plus: <code class="code">U+2064</code>) are not considered a punctuations in this standard (because they a zero-width characters), therefore they are not to be considered a valid <code class="code">_</code>, <code class="code">-</code>, or <code class="code">+</code> Unicode equivalents.
+ </p>
+ <p>
+ Key:
+ </p>
+ <ul>
+ <li><code class="code">\o</code> = any printable word character, including <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code> (and Unicode equivalents).</li>
+ <li><code class="code">\c</code> = 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.</li>
+ <li><code class="code">\q</code> = either a single quote <code class="code">'</code> or a double quote <code class="code">"</code>.</li>
+ <li><code class="code">\x</code> = any character.</li>
+ <li><code class="code">\W</code> = any non-word character, discluding <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code> (and Unicode equivalents).</li>
+ <li><code class="code">\e</code> = an optional escape sequence of any number of backslashes, such as <code class="code">\</code>.</li>
+ <li><code class="code">*</code> = 0 or more occurrences.</li>
+ <li><code class="code">~</code> = one or more occurrences, or 0 if at start of file.</li>
+ </ul>
+ <p>
+ Before Structure:
+ </p>
+ <ul>
+ <li><code class="code">\x*\W~\*:*</code></li>
+ </ul>
+ <p>
+ Structure:
+ </p>
+ <ul>
+ <li><code class="code">\o\e:\q\c\q</code></li>
+ </ul>
+ <p>
+ After Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Example File:
+ </p><pre class="preserve">
+# fss-000c iki-0000
+
+This is my sentence, anything can go here but sometimes I want to emphasis:"emphasize some text".
+
+Other times I want to render a url such as this example url: url:'http://www.example.com/url with space/'.
+
+There are no comments, except for maybe the FSS header (which would not resolve to any IKI syntax anyway).
+
+Quotes may be included, such as: code:"const char *string = \"My \\\"quoted\\\" C string.\";".
+
+The following emphasis\:"is escaped to not be treated as IKI data".
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve">
+Objects would be:
+ 1) emphasis
+ 2) url
+ 3) code
+
+Contents would be:
+ 1.1) emphasize some text
+ 2.1) http://www.example.com/url with space/
+ 3.1) const char *string = "My \"quoted\" C string.";
+</pre>
+ <p>
+ The following are core specifications (each with a common name associated with the specification number):
+ </p>
+ <ul>
+ <li><a href="fll/specifications/iki/iki-0000.html" class="link">iki-0000: Unrestricted</a></li>
+ <li><a href="fll/specifications/iki/iki-0001.html" class="link">iki-0001: Basic</a></li>
+ <li><a href="fll/specifications/iki/iki-0002.html" class="link">iki-0002: Simple Script</a></li>
+ </ul>
+ </div>
+ </section>
+
+ <section id="completeness_theorem" class="section">
+ <header class="section-header header separate">
+ <h2 class="section-title h h2">Completeness Theorem</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ The <strong>Completeness Theorem</strong> represents an informal theory by Kevin Day focusing on how software should be complete. The theory has not been formalized and the following is a basic explanation. A formal definition may be provided in the future.
+ </p>
+ <p>
+ When developing software, one should not program for the minimum requirements. Instead, one should consider the scope of the project and its intended design. Taking that into consideration all functionality needed to achieve this should be considered and implemented.
+ </p>
+ <p>
+ The most common misconceptions about this theorem is that it is not about writing all possible combinations, permutations, possibilities, etc. In fact, it is more accurate to say the opposite. The key focus is figuring out what the scope and intended functionalities are and make sure to achieve those.
+ </p>
+ <p>
+ This does not conflict with <abbr title="Keep It Simple Stupid">KISS</abbr> but instead complements it.
+ </p>
+ <p>
+ If this is not clear, then consider thinking of things this way. The <abbr title="Keep It Simple Stupid">KISS</abbr> focuses on keeping the design and process simple. The <strong>Completeness Theorem</strong> focuses on making sure the design is complete.
+ </p>
+ <p>
+ Now if, say a car, is designed to follow <abbr title="Keep It Simple Stupid">KISS</abbr> but violates the <strong>Completeness Theorem</strong>, then that car could be built without doors. Not having doors simplifies the car. It is much simpler and easier to get in and out of.
+ </p>
+ <p>
+ Using that example, a car designed to follow both <abbr title="Keep It Simple Stupid">KISS</abbr> and the <strong>Completeness Theorem</strong> would have doors.
+ </p>
+ <p>
+ To better understand the <strong>Completeness Theorem</strong>, again take the car example. If the car is intended to be used only in say photo shoots and is not in any way intended ever to be used, then as per the <strong>Completeness Theorem</strong>, the car would not need an engine. Whereas a car designed and intended to be used that does not have an engine would fail to follow the <strong>Completeness Theorem</strong>.
+ </p>
+ <p>
+ The <strong>Completeness Theorem</strong> is subjective and is intended to be used as a guide.
+ </p>
+ <p>
+ The <strong>Completeness Theorem</strong> asserts that perfection is impossible and pointless and one must instead understand what is necessary to complete the project rather than to handle all possibilities. Simply because perfection isn't possible doesn't mean one must lower their standards or have no standards. Determine what is or is not needed to complete the project and meet that rather than meet less than that.
+ </p>
+ </div>
+ </section>
+
+ <section id="terminology" class="section">
+ <header class="section-header header separate">
+ <h2 class="section-title h h2">Terminology</h2>
+ </header>
+
+ <div class="section-content">
+ <dl class="dl">
+ <div class="di">
+ <dt class="dt"><abbr title="Application Binary Interface">ABI</abbr></dt>
+ <dd class="dd">An <em>Application Binary Interface</em> is a binary implementation of an <abbr title="Application Programming Interface">API</abbr> making it an implementation of a specification. An <abbr title="Application Binary Interface">ABI</abbr> is neither a specification nor a standard.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt"><abbr title="Application Programming Interface">API</abbr></dt>
+ <dd class="dd">An <em>Application Programming Interface</em> is a specification of some implementation of a standard be it a formally defined standard or an informally defined standard. This is in effect, documentation. Note that this is a specification of an implementation rather than a specification of a standard.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt">Implementation</dt>
+ <dd class="dd">Something that applies (implements) a standard or specification.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt">Protocol</dt>
+ <dd class="dd">In the context of computer software, this is a standard focused on communication between two parties (often referring to Internet communication). Web services often provide, use, and follow protocols. These web protocols are commonly incorrectly referred to as an <abbr title="Application Programming Interface">API</abbr>.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt"><abbr title="Software Binary Interface">SBI</abbr></dt>
+ <dd class="dd">A <em>Software Binary Interface</em> is a new term created so that this project can more appropriately communicate the concept of what is traditionally referred to as an <abbr title="Application Binary Interface">ABI</abbr>. A <em>Software Binary Interface</em> is a more semantically accurate term intended to fully replace the misnamed <abbr title="Application Binary Interface">ABI</abbr> term.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt">Service</dt>
+ <dd class="dd">Any action or labor performed by one party for another party (such as one person helping another person). In regards to computers and networking a <em>service</em> is often used to represent a web service often provided by a website. It is common for people to misrepresent a web service by saying they are using an <abbr title="Application Programming Interface">API</abbr> when, in fact, they are using a web service.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt">Specification</dt>
+ <dd class="dd">A specific interpretation or clarification of a standard, such as the documentation that describes how to use or follow a standard.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt"><abbr title="Software Source Interface">SSI</abbr></dt>
+ <dd class="dd">A <em>Software Source Interface</em> is a new term created so that this project can more appropriately communicate the concept of what is traditionally referred to as an <abbr title="Application Programming Interface">API</abbr>. A <em>Software Source Interface</em> is a more semantically accurate term intended to fully replace the misnamed <abbr title="Application Programming Interface">API</abbr> term.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt">Standard</dt>
+ <dd class="dd">A set of rules and guidelines.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt"><abbr title="Web Service Interface">WSI</abbr></dt>
+ <dd class="dd">A <em>Web Service Interface</em> is a new term created so that this project can more appropriately communicate the concept of a web service. A <em>Web Service Interface</em> describes the interface in which to communicate to and receive response from a web service and is described by or adheres to some web protocol.</dd>
+ </div>
+ </dl>
+ <p>
+ Based on this terminology, a standard is the representation of some set of rules and guidelines, however it is the specification that actually defines and describes those roles. The last '<em>S</em>' in <abbr title="Featureless Settings Specifications">FSS</abbr> can therefore be used to represent either "standard" or "specification" in casual speech. Given that an implementation is not a standard, an implementation can deviate from the standard (or the specification of some standard). Such deviations do not alter the standard nor do they alter the specification.
+ </p>
+ <p>
+ Good documentation practices suggest the documentation of an implementation. It is very easy to confuse the specification of an implementation of some standard with the specification of the standard itself. This has happened several times in history where some implementation violates the standard but despite being non-standard that implementation becomes popular. When the specification of that, now non-standard, implementation becomes popularized, those properly following the specification of the standard tend to suffer.
+ </p>
+ <p>
+ This project encourages deviations from the standards and such actions are allowed and protected by the copyright licenses. However, this project discourages communicating compliance of some standard when something is, in fact, not compliant. Problems in the interpretation of a standard fall under communication problems and are not considered deviations from the standard even though it may technically be a deviation. It is for these reasons that the terminology has been explicitly defined, clarified, and presented on this page.
+ </p>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-0000 (Basic)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-0000, basic">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-0000.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0000.html#fss-0000" class="nav-text link"><div>FSS-0000</div><div>(Basic)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-0000.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-0000.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-0000" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-0000 (Basic)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ Each Object starts at the beginning of a line and white space to the left of the Object is not treated as part of the object.
+ White space separates an Object from the Content.
+ An Object may be preceded by a newline, in which case means that the Object has no Content.
+ If only printing white space follows a valid Object, that Object is considered to have no Content.
+ </p>
+ <p>
+ Content exists on the same line as the Object.
+ Content is represented as a single Content column terminated by a newline.
+ Content column consists of everything following the first non-white space character until the newline.
+ Content column includes trailing white space before newline is reached.
+ Content column does not include any of the leading white space.
+ No delimits are supported in the Content.
+ </p>
+ <p>
+ Key:
+ </p>
+ <ul>
+ <li><code class="code">\s</code> = white space, except newline.</li>
+ <li><code class="code">\b</code> = either white space or printable, except newline.</li>
+ <li><code class="code">\q</code> = non-white space or quoted white space with no white space outside of the quotes.</li>
+ <li><code class="code">\n</code> = newline.</li>
+ <li><code class="code">*</code> = zero or more occurrences.</li>
+ <li><code class="code">+</code> = one or more occurrences.</li>
+ </ul>
+ <p>
+ Before Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Structure:
+ </p>
+ <ul>
+ <li><code class="code">\s*\q+\s+\b*\n</code></li>
+ </ul>
+ <p>
+ After Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# fss-0000
+# valid comments are ignored.
+"The Object" Content until newline.
+Second object set.
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve">
+Object would be:
+1) The Object
+2) Second
+
+Content would be:
+1.1) Content until newline.
+2.1) object set.
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-0001 (Extended)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-0001, extended">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-0001.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0001.html#fss-0001" class="nav-text link"><div>FSS-0001</div><div>(Extended)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-0001.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-0001.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-0001" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-0001 (Extended)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ Each Object starts at the beginning of a line and white space to the left of the Object is not treated as an object.
+ White space separates an Object from the Content.
+ An Object may be followed by a newline, in which case means that the Object has no Content.
+ If only printing white space follows a valid Object, that Object is considered to have no Content.
+ </p>
+ <p>
+ Content exists on the same line as the Object.
+ Content is represented as multiple Content columns.
+ Content columns are white space separated parts within the Content and terminated by a newline.
+ Any number of Content columns may exist in the Content until the newline is reached.
+ </p>
+ <p>
+ Key:
+ </p>
+ <ul>
+ <li><code class="code">\s</code> = White space, except newline.</li>
+ <li><code class="code">\b</code> = Either white space or printable, except newline.</li>
+ <li><code class="code">\q</code> = Non-white space or quoted white space with no white space outside of the quotes.</li>
+ <li><code class="code">\n</code> = Newline.</li>
+ <li><code class="code">*</code> = Zero or more occurrences.</li>
+ <li><code class="code">+</code> = One or more occurrences.</li>
+ <li><code class="code">()*</code> = Grouping that repeats 0 or more times.</li>
+ </ul>
+ <p>
+ Before Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Structure:
+ </p>
+ <ul>
+ <li><code class="code">\s*\q+\s+(\s*\q+)*\s*\n</code></li>
+ </ul>
+ <p>
+ After Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# fss-0001
+# valid comments are ignored.
+"The Object" Content "content 2" content_3.
+Second object set.
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve">
+Objects would be:
+ 1) The Object
+ 2) Second
+
+Contents would be:
+ 1.1) Content
+ 1.2) content 2
+ 1.3) content_3.
+
+ 2.1) object
+ 2.2) set.
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-0000 (Basic List)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-0002, basic list">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-0002.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0002.html#fss-0002" class="nav-text link"><div>FSS-0002</div><div>(Basic List)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-0002.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-0002.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-0002" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-0002 (Basic List)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ Each Object starts at the beginning of a line and white space to the left of the Object is not treated as an object.
+ A colon followed by any white space until a newline terminates a valid Object.
+ Non-white space may not follow the colon of a valid Object.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ There is no single-quote or double-quote delimitation in this specification.
+ Only the colon that would result in a valid Object can be delimited.
+ </p>
+ <p>
+ Empty Objects are allowed, that is, the length of the object may be zero.
+ </p>
+ <p>
+ Key:
+ </p>
+ <ul>
+ <li><code class="code">\s</code> = White space, except newline.</li>
+ <li><code class="code">\o</code> = Any printable character, except unescaped ':'.</li>
+ <li><code class="code">\l</code> = Any printable character or white space, except unescaped ':'.</li>
+ <li><code class="code">\c</code> = either white space or printable, including newline, that not interpretable as an Object.</li>
+ <li><code class="code">\n</code> = Newline.</li>
+ <li><code class="code">*</code> = Zero or more occurrences.</li>
+ </ul>
+ <p>
+ Before Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Structure:
+ </p>
+ <ul>
+ <li><code class="code">\s*\o\l*:\s*\n\c*\n*</code></li>
+ </ul>
+ <p>
+ After Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# fss-0002
+# valid comments are ignored.
+"The Object":
+ Does not need to be quoted.
+ This: does not need to be delimited.
+ This Does\:
+Second:
+ Continues until EOS/EOF.
+ All white space, including newline (and leading white space) is "part of content."
+ # Valid comments are still ignored.
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve">
+ Objects would be:
+ 1) "The Object"
+ 2) Second
+
+ Contents would be:
+ 1.1) Does not need to be quoted.
+ This: does not need to be delimited.
+ This Does:
+ 2.1) Continues until EOS/EOF.
+ All white space, including newline (and leading white space) is "part of content."
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-0000 (Extended List)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-0003, extended list">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-0003.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0003.html#fss-0003" class="nav-text link"><div>FSS-0003</div><div>(Extended List)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-0003.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-0003.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-0003" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-0003 (Extended List)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ Each Object starts at the beginning of a line and white space to the left of the Object is not treated as an object.
+ An open-brace <code class="code">{</code> followed by any white space until a newline terminates a possible valid Object.
+ An Object is not considered fully valid until a valid close-brace <code class="code">}</code> is found, designating the end of the Content.
+ Non-white space may not follow the open-brace of a valid Object.
+ </p>
+ <p>
+ Content is represented as a single Content column of every line following a valid object until the end of file (or string) or until a non-delimited close-brace <code class="code">}</code>.
+ 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.
+ </p>
+ <p>
+ There is no single-quote or double-quote 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.
+ Likewise, the close-brace may only be delimited if it is within any potentially valid Content.
+ </p>
+ <p>
+ Each delimit slash in a delimitable open-brace is treated as a potential delimit such that two slashes represents a single delimited slash (<code class="code">\\{</code> would represent <code class="code">\{</code>).
+ Only the first delimit slash in a delimitable close-brace is treated as a potential delimit (<code class="code">\\\}</code> would represent <code class="code">\\}</code>).
+ </p>
+ <p>
+ Empty Objects are allowed, that is, the length of the object may be zero.
+ <p>
+ Key:
+ </p>
+ <ul>
+ <li><code class="code">\s</code> = White space, except newline.</li>
+ <li><code class="code">\o</code> = Any printable character, except unescaped <code class="code">{</code>.</li>
+ <li><code class="code">\l</code> = Any printable character or white space, except unescaped <code class="code">}</code>.</li>
+ <li><code class="code">\c</code> = Either white space or printable, including newline, that is not interpretable as an Object.</li>
+ <li><code class="code">\n</code> = Newline.</li>
+ <li><code class="code">*</code> = Zero or more occurrences.</li>
+ </ul>
+ <p>
+ Before Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Structure:
+ </p>
+ <ul>
+ <li><code class="code">\s*\o\l*{\s*\n\c*\n\s*}\s*\n</code></li>
+ </ul>
+ <p>
+ After Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# fss-0003
+# valid comments are ignored.
+"The Object" {
+ Does not need to be quoted.
+ This: does not need to be delimited.
+ \}
+}
+
+Second {
+ Continues until EOS/EOF.
+ All white space, including newline (and leading white space) is "part of content."
+ # Valid comments are still ignored.
+}
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve">
+Objects would be:
+ 1) "The Object"
+ 2) Second
+
+Contents would be:
+ 1.1) Does not need to be quoted.
+ This: does not need to be delimited.
+ }
+ 2.1) Continues until EOS/EOF.
+ All white space, including newline (and leading white space) is "part of content."
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-0004 (Very Basic List)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-0004, very basic list">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-0004.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0004.html#fss-0004" class="nav-text link"><div>FSS-0004</div><div>(Very Basic List)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-0004.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-0004.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-0004" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-0004 (Very Basic List)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ This is a <code class="code">fss-0002 (Basic List)</code> whose Content is then processed as <code class="code">fss-0000 (Basic)</code>.
+ </p>
+ <p>
+ All <code class="code">fss-0002 (Basic List)</code> escapes are applied before any <code class="code">fss-0000 (Basic)</code> is identified.
+ </p>
+ <p>
+ See the <a href="fll/specifications/fss/fss-0000.html" class="link">fss-0000 (Basic)</a> and <a href="fll/specifications/fss/fss-0002.html" class="link">fss-0002 (Basic List)</a> specifications for details on the syntax rules.
+ </p>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# fss-0004
+# valid comments are ignored.
+"The Object":
+ Does not need to be quoted.
+ This: does not need to be delimited.
+ This Does\:
+Second:
+ Continues until EOS/EOF.
+ All white space, including newline (and leading white space) is "part of content."
+ # Valid comments are still ignored.
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve">
+Outer Objects would be:
+ 1) "The Object"
+ 2) Second
+
+Inner Objects would be:
+ 1.1) Does
+ 1.2) This:
+ 1.3) This
+
+ 2.1) Continues
+ 2.2) All
+
+Inner Contents would be:
+ 1.1.1) not need to be quoted.
+ 1.2.1) does not need to be delimited.
+ 1.3.1) Does:
+
+ 2.1.1) until EOS/EOF.
+ 2.2.1) white space, including newline (and leading white space) is "part of content."
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-0005 (Somewhat Basic List)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-0005, somewhat basic list">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-0005.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0005.html#fss-0005" class="nav-text link"><div>FSS-0005</div><div>(Somewhat Basic List)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-0005.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-0005.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-0005" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-0005 (Somewhat Basic List)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ This is a code"fss-0002 (Basic List)" whose Content is then processed as <code class="code">fss-0001 (Extended)</code>.
+ </p>
+ <p>
+ All <code class="code">fss-0002 (Basic List)</code> escapes are applied before any <code class="code">fss-0001 (Extended)</code> is identified.
+ </p>
+ <p>
+ See the <a href="fll/specifications/fss/fss-0001.html" class="link">fss-0001 (Extended)</a> and <a href="fll/specifications/fss/fss-0002.html" class="link">fss-0002 (Basic List)</a> specifications for details on the syntax rules.
+ </p>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# fss-0005
+# valid comments are ignored.
+"The Object":
+ Does not need to be quoted.
+ This: does not need to be delimited.
+ This Does\:
+Second:
+ Continues until EOS/EOF.
+ All white space, including newline (and leading white space) is "part of content."
+ # Valid comments are still ignored.
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve">
+Outer Objects would be:
+ 1) "The Object"
+ 2) Second
+
+Inner Objects would be:
+ 1.1) Does
+ 1.2) This:
+ 1.3) This
+
+ 2.1) Continues
+ 2.2) All
+
+Inner Contents would be:
+ 1.1.1) not
+ 1.1.2) need
+ 1.1.3) to
+ 1.1.4) be
+ 1.1.5) quoted.
+
+ 1.2.1) does
+ 1.2.2) not
+ 1.2.3) need
+ 1.2.4) to
+ 1.2.5) be
+ 1.2.6) delimited.
+
+ 1.3.1) Does:
+
+ 2.1.1) until
+ 2.1.2) EOS/EOF.
+
+ 2.2.1) white space,
+ 2.2.2) including
+ 2.2.3) newline
+ 2.2.4) (and
+ 2.2.5) leading
+ 2.2.6) white space)
+ 2.2.7) is
+ 2.2.8) part of content.
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-0006 (Somewhat Extended List)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-0006, somewhat extended list">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-0006.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0006.html#fss-0006" class="nav-text link"><div>FSS-0006</div><div>(Somewhat Extended List)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-0006.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-0006.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-0006" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-0006 (Somewhat Extended List)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ This is a <code class="code">fss-0003 (Extended List)</code> whose Content is then processed as <code class="code">fss-0000 (Basic)</code>.
+ </p>
+ <p>
+ All <code class="code">fss-0003 (Extended List)</code> escapes are applied before any <code class="code">fss-0000 (Basic)</code> is identified.
+ </p>
+ <p>
+ See the <a href="fll/specifications/fss/fss-0000.html" class="link">fss-0000 (Basic)</a> and <a href="fll/specifications/fss/fss-0003.html" class="link">fss-0003 (Extended List)</a> specifications for details on the syntax rules.
+ </p>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# fss-0006
+# valid comments are ignored.
+"The Object" {
+ Does not need to be quoted.
+ This: does not need to be delimited.
+ \}
+}
+
+Second {
+ Continues until EOS/EOF.
+ All white space, including newline (and leading white space) is "part of content."
+ # Valid comments are still ignored.
+}
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve">
+Outer Objects would be:
+ 1) "The Object"
+ 2) Second
+
+Inner Objects would be:
+ 1.1) Does
+ 1.2) This:
+ 1.3) }
+
+ 2.1) Continues
+ 2.2) All
+
+Inner Contents would be:
+ 1.1.1) not need to be quoted.
+ 1.2.1) does not need to be delimited.
+ 1.3.1)
+
+ 2.1.1) until EOS/EOF.
+ 2.2.1) white space, including newline (and leading white space) is "part of content."
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-0007 (Very Extended List)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-0007, very extended list">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-0007.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0007.html#fss-0007" class="nav-text link"><div>FSS-0007</div><div>(Very Extended List)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-0007.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-0007.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-0007" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-0007 (Very Extended List)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ This is a <code class="code">fss-0003 (Extended List)</code> whose Content is then processed as <code class="code">fss-0001 (Extended)</code>.
+ </p>
+ <p>
+ All <code class="code">fss-0003 (Extended List)</code> escapes are applied before any <code class="code">fss-0001 (Extended)</code> is identified.
+ </p>
+ <p>
+ See the <a href="fll/specifications/fss/fss-0001.html" class="link">fss-0001 (Extended)</a> and <a href="fll/specifications/fss/fss-0003.html" class="link">fss-0003 (Extended List)</a> specifications for details on the syntax rules.
+ </p>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# fss-0007
+# valid comments are ignored.
+"The Object" {
+ Does not need to be quoted.
+ This: does not need to be delimited.
+ \}
+}
+
+Second {
+ Continues until EOS/EOF.
+ All white space, including newline (and leading white space) is "part of content."
+ # Valid comments are still ignored.
+}
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve">
+Outer Objects would be:
+ 1) "The Object"
+ 2) Second
+
+Inner Objects would be:
+ 1.1) Does
+ 1.2) This:
+ 1.3) }
+
+ 2.1) Continues
+ 2.2) All
+
+Inner Contents would be:
+ 1.1.1) not
+ 1.1.2) need
+ 1.1.3) to
+ 1.1.4) be
+ 1.1.5) quoted.
+
+ 1.2.1) does
+ 1.2.2) not
+ 1.2.3) need
+ 1.2.4) to
+ 1.2.5) be
+ 1.2.6) delimited.
+
+ 1.3.1)
+
+ 2.1.1) until
+ 2.1.2) EOS/EOF.
+
+ 2.2.1) white space,
+ 2.2.2) including
+ 2.2.3) newline
+ 2.2.4) (and
+ 2.2.5) leading
+ 2.2.6) white space)
+ 2.2.7) is
+ 2.2.8) part of content.
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-0008 (Embedded List)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-0008, embedded list">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-0008.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0008.html#fss-0008" class="nav-text link"><div>FSS-0008</div><div>(Embedded List)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-0008.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-0008.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-0008" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-0008 (Embedded List)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ This is a <code class="code">fss-0003 (Extended List)</code> whose Content is then recursively processed as <code class="code">fss-0003 (Extended List)</code>.
+ </p>
+ <p>
+ See the <a href="fll/specifications/fss/fss-0003.html" class="link">fss-0003 (Extended List)</a> specification for details on the syntax rules.
+ </p>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# fss-0008
+# valid comments are ignored.
+"The Object" {
+ Does not need to be quoted.
+ This: does not need to be delimited.
+ \}
+}
+
+Second {
+ Nested Example.
+
+ Third {
+ Fourth {
+ This is nested Content.
+ }
+ }
+}
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve">
+Outer Objects would be:
+ 1) "The Object"
+ 2) Second
+
+Inner Objects (depth 1) would be:
+ 2.1) Third
+
+Inner Objects (depth 2) would be:
+ 2.1.1) Fourth
+
+Inner Contents (depth 0) would be:
+ 1.1.1) Does not need to be quoted.
+ This: does not need to be delimited.
+ }
+
+ 2.1.1) Nested Example.
+
+ Third {
+ Fourth {
+ This is nested Content.
+ }
+ }
+
+Inner Contents (depth 1) would be:
+ 2.1.1.1) Fourth {
+ This is nested Content.
+ }
+
+Inner Contents (depth 2) would be:
+ 2.1.1.1.1) This is nested Content.
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-0009 (Reverse Mapping)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-0009, reverse mapping">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-0009.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-0009.html#fss-0009" class="nav-text link"><div>FSS-0009</div><div>(Reverse Mapping)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-0009.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-0009.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-0009" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-0009 (Reverse Mapping)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ This is based off of <code class="code">fss-0000 (Basic)</code>, except the Object is at the end of the line.
+ </p>
+ <p>
+ Each Object starts at the end of a line and white space to the left of the Object is not treated as part of the object.
+ White space separates an Object from the Content.
+ An Object may be preceded by a newline, in which case means that the Object has no Content.
+ If only printing white space precedes a valid Object, that Object is considered to have no Content.
+ </p>
+ <p>
+ Content exists on the same line as the Object.
+ Content is represented as a single Content column that begins at a newline.
+ Content column consists of everything following the first non-white space character at the start of the line until the Object is reached.
+ Content column includes trailing white space before newline is reached.
+ Content column does not include any of the white space between the last non-white space character and the start of the Object.
+ No delimits are supported in the Content.
+ </p>
+ <p>
+ Key:
+ </p>
+ <ul>
+ <li><code class="code">\s</code> = white space, except newline.</li>
+ <li><code class="code">\b</code> = either white space or printable, except newline.</li>
+ <li><code class="code">\q</code> = non-white space or quoted white space with no white space outside of the quotes.</li>
+ <li><code class="code">\n</code> = newline.</li>
+ <li><code class="code">*</code> = zero or more occurrences.</li>
+ <li><code class="code">+</code> = one or more occurrences.</li>
+ </ul>
+ <p>
+ Before Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Structure:
+ </p>
+ <ul>
+ <li><code class="code">\s*\b*\s+\q+\s*\n</code></li>
+ </ul>
+ <p>
+ After Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# fss-0009
+# valid comments are ignored.
+Content from newline. "The Object"
+object set. Second
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve">
+Object would be:
+ 1) The Object
+ 2) Second
+
+Content would be:
+ 1.1) Content from newline.
+ 2.1) object set.
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-000A (Extended Reverse Mapping)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-000a, extended reverse mapping">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-000a.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-000a.html#fss-000a" class="nav-text link"><div>FSS-000A</div><div>(Extended Reverse Mapping)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-000a.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-000a.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-000a" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-000A (Extended Reverse Mapping)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ This is based off of <code class="code">fss-0001 (Extended)</code>, except the Object is at the end of the line.
+ </p>
+ <p>
+ Each Object starts at the end of a line and white space to the left of the Object is not treated as an object.
+ White space separates an Object from the Content.
+ An Object may be followed by a newline, in which case means that the Object has no Content.
+ If only printing white space follows a valid Object, that Object is considered to have no Content.
+ </p>
+ <p>
+ Content exists on the same line as the Object.
+ Content is represented as multiple Content columns.
+ Content columns are white space separated parts within the Content is terminated by the start of the Object.
+ Any number of Content columns may exist in the Content until the Object is reached.
+ </p>
+ <p>
+ Key:
+ </p>
+ <ul>
+ <li><code class="code">\s</code> = White space, except newline.</li>
+ <li><code class="code">\b</code> = Either white space or printable, except newline.</li>
+ <li><code class="code">\q</code> = Non-white space or quoted white space, no white space outside of quotes.</li>
+ <li><code class="code">\n</code> = Newline.</li>
+ <li><code class="code">*</code> = Zero or more occurrences.</li>
+ <li><code class="code">+</code> = One or more occurrences.</li>
+ <li><code class="code">()*</code> = Grouping that repeats 0 or more times.</li>
+ </ul>
+ <p>
+ Before Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Structure:
+ </p>
+ <ul>
+ <li><code class="code">\s*(\s*\q+)*\s+\q+\s*\n</code></li>
+ </ul>
+ <p>
+ After Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# fss-000a
+# valid comments are ignored.
+Content "content 2" content_3. "The Object"
+object set. Second
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve">
+Objects would be:
+ 1) The Object
+ 2) Second
+
+Contents would be:
+ 1.1) Content
+ 1.2) content 2
+ 1.3) content_3.
+
+ 2.1) object
+ 2.2) set.
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+ <!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-000B (Simple List)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-000b, simple list">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-000b.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-000b.html#fss-000b" class="nav-text link"><div>FSS-000B</div><div>(Simple List)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-000b.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-000b.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-000b" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-000B (Simple List)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ This might be similar to <code class="code">fss-0008 (Embedded List)</code>, except it is an <code class="code">fss-0003 (Extended List)</code> with a (non-recursive) <code class="code">fss-0002 (Basic List)</code> inside the Content.
+ </p>
+ <p>
+ See the <a href="fll/specifications/fss/fss-0002.html" class="link">fss-0002 (Basic List)</a> and <a href="fll/specifications/fss/fss-0003.html" class="link">fss-0003 (Extended List)</a> specifications for details on the syntax rules.
+ </p>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# fss-000b
+# valid comments are ignored.
+"The Object" {
+ Does not need to be quoted.
+ This: does not need to be delimited.
+ \}
+}
+
+Second {
+ Nested Example.
+
+ Third:
+ Fourth:
+ There is parallel to Second rather than nested within Second.
+}
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve">
+Outer Objects would be:
+ 1) "The Object"
+ 2) Second
+
+Inner Objects (depth 1) would be:
+ 2.1) Third
+ 2.2) Fourth
+
+Inner Contents (depth 0) would be:
+ 1.1.1) Does not need to be quoted.
+ This: does not need to be delimited.
+ }
+
+ 2.1.1) Nested Example.
+
+ Third:
+ Fourth:
+ There is parallel to Second rather than nested within Second.
+
+Inner Contents (depth 1) would be:
+ 2.1.1.1)
+ 2.2.1.1) There is parallel to Second rather than nested within Second.
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-000C (IKI Text)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-000c, iki text">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-000c.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-000c.html#fss-000c" class="nav-text link"><div>FSS-000C</div><div>(IKI Text)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-000c.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-000c.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-000c" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-000C (IKI Text)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ The IKI specifications are separate specifications from the <abbr title="Featureless Settings Specifications">FSS</abbr>.
+ This is simply a more formal way to designate that this format utilizes IKI syntax.
+ </p>
+ <p>
+ The IKI syntax may be used in any <abbr title="Featureless Settings Specifications">FSS</abbr>.
+ The IKI format may be added to the.
+ </p>
+ <p>
+ See the file:"iki.txt" specification for details on the IKI specifications.
+ </p>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# fss-000c iki-0000
+
+This is a emphasis:"formal example" utilizing the FSS headers.
+</pre>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# iki-0000
+
+This is an emphasis:"informal example" utilizing the IKI headers.
+ </pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-000D (Basic Rule)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-000d, basic rule">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-000d.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-000d.html#fss-000d" class="nav-text link"><div>FSS-000D</div><div>(Basic Rule)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-000d.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-000d.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-000d" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-000D (Basic Rule)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ This is a special case that follows <code class="code">fss-0002 (Basic List)</code>, and different <abbr title="Featureless Settings Specifications">FSS</abbr> formats inside this <code class="code">fss-0002 (Basic List)</code>.
+ This <code class="code">fss-0002 (Basic List)</code> is considered the "Outer List" and the Content of this Outer List is considered the "Inner Content".
+ </p>
+ <p>
+ The Inner Content may be any of the following <abbr title="Featureless Settings Specifications">FSS</abbr> formats: <code class="code">fss-0000 (Basic)</code>, <code class="code">fss-0001 (Extended)</code>, and <code class="code">fss-0003 (Extended List)</code>.
+ The way in which each format is determined is first to see if the Inner Content Object would be a valid Extended List Object.
+ If the Inner Content Object is not a valid <code class="code">fss-0003 (Extended List)</code> Object, then check to see if it is an <code class="code">fss-0000 (Basic)</code> or <code class="code">fss-0001 (Extended)</code> Object.
+ </p>
+ <p>
+ The <code class="code">fss-0000 (Basic)</code> and <code class="code">fss-0001 (Extended)</code> Objects have the same format for Object names but the <code class="code">fss-0003 (Extended List)</code> Object is slightly different.
+ Anything that would match an <code class="code">fss-0003 (Extended List)</code> Object must therefore be an <code class="code">fss-0003 (Extended List)</code> Object.
+ </p>
+ <p>
+ This supports the use of <code class="code">iki-0000 (Unrestricted)</code> but only within the Content of the outermost <code class="code">fss-0002 (Basic List)</code>.
+ That is to say, the IKI is only processed once.
+ Additional restrictions on the use of IKI syntax is allowed if explicitly defined in the implementing specification.
+ This additional restriction may also include using a more restrictive IKI syntax, such as <code class="code">iki-0001 (Basic)</code>.
+ </p>
+ <p>
+ Anything implementing this specification may impose its own restrictions on when to determine if the Inner Content is what <abbr title="Featureless Settings Specifications">FSS</abbr> format, based on Object names.
+ </p>
+ <p>
+ See the <a href="fll/specifications/fss/fss-0000.html" class="link">fss-0000 (Basic)</a>, <a href="fll/specifications/fss/fss-0001.html" class="link">fss-0001 (Extended)</a>, and <a href="fll/specifications/fss/fss-0003.html" class="link">fss-0003 (Extended List)</a> specifications for details on the syntax rules.
+ </p>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# fss-000d
+main:
+ name "Boot Devices"
+
+script:
+ start {
+ ip addr add 127.0.0.1/8 label lo dev lo;
+ ip link set lo up;
+ }
+
+ stop {
+ ip link set lo down;
+ }
+
+command:
+ start mount -a -O no_netdev
+ stop umount -arf -O no_netdev
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve">
+Outer List Objects would be:
+ 1) main
+ 2) script
+ 3) command
+
+Outer List Contents would be:
+ 1.1) name "Boot Devices"
+
+ 2.1) start {
+ ip addr add 127.0.0.1/8 label lo dev lo;
+ ip link set lo up;
+ }
+
+ stop {
+ ip link set lo down;
+ }
+
+ 3.1) begin mount -a -O no_netdev
+ end umount -arf -O no_netdev
+
+Inner Content Objects would be:
+ 1.1.1) name
+ 2.1.1) start
+ 2.1.2) stop
+ 3.1.1) begin
+ 3.1.2) end
+
+Inner Content Contents would be (without breaking Content into its individual parts):
+ 1.1.1) Boot Devices
+ 2.1.1) ip addr add 127.0.0.1/8 label lo dev lo;
+ ip link set lo up;
+ 2.1.2) ip link set lo down;
+ 3.1.1) mount -a -O no_netdev
+ 3.1.2) umount -arf -O no_netdev
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-000E (Payload)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-000e, payload">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-000e.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-000e.html#fss-000e" class="nav-text link"><div>FSS-000E</div><div>(Payload)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-000e.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-000e.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-000e" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-000E (Payload)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ This is a <code class="code">fss-0002 (Basic List)</code> with two required objects:
+ </p>
+ <ol>
+ <li><em>header</em>.</li>
+ <li><em>payload</em>.</li>
+ </ol>
+ <p>
+ The <em>header</em>:
+ </p>
+ <ul>
+ <li>The <em>header</em>'s Content is of type <code class="code">fss-0001 (Extended)</code>.</li>
+ <li>The <em>header</em> is recommended to have the Objects <em>length</em>, <em>status</em>, <em>part</em>, and <em>total</em>.</li>
+ <li>The recommended <em>length</em> represents the size of the <em>payload</em>.</li>
+ <li>The recommended <em>part</em> represents a single part of a set of packets for when the data being transmitted is split across multiple payloads.</li>
+ <li>The recommended <em>total</em> represents the total number of parts representing a complete data transmitted across multiple payloads.</li>
+ <li>The recommended <em>status</em> represents status codes (such as success or failure) and multiple.</li>
+ <li>The Content for the recommended <em>length</em> and <em>status</em> are positive whole numbers (including zero) that may be in <em>binary</em>, <em>octal</em>, <em>decimal</em>, <em>duodecimal</em>, or <em>hexidecimal</em> numerical format.</li>
+ </ul>
+ <p>
+ The <em>payload</em>:
+ </p>
+ <ul>
+ <li>The <em>payload</em>'s Content may contain anything, including raw binary data.</li>
+ <li>The <em>payload</em> is <em>required</em> to be the last list Object in the file.</li>
+ <li>The <em>payload</em> is recommended to have its size designated in some manner in the <em>header</em> (such as with the recommended <em>length</em>).</li>
+ <li>The <em>payload</em> is terminated by the <abbr title="End of File">EOF</abbr> character or by the recommended <em>length</em> header.</li>
+ <li>The <em>payload</em> may be empty (length may be zero), but the list Object <em>payload</em> must still exist.</li>
+ <li>Nothing in the <em>payload</em> may be considered a valid list Object by the outer <code class="code">fss-0002 (Basic List)</code> and therefore escaping is unnecessary (No further processing by the outer <code class="code">fss-0002 (Basic List)</code> is allowed at this point).</li>
+ <li>Comments in the <em>payload</em> are not considered comments and are instead considered part of the payload, as-is.</li>
+ <li>Essentially, the <em>payload</em> should be treated as binary data embedded in a text file.</li>
+ </ul>
+ <p>
+ The recommended <em>length</em> <em>header</em> Object used to designate the <em>payload</em> size does not necessarily have to be defined in the <em>header</em>.
+ That is to say, if the <em>payload</em> is expected to be of some pre-defined or static length then a length does not need to be provided in the <em>header</em>.
+ </p>
+ <p>
+ The recommended <em>status</em> <em>header</em> Object may be a string, such as <code class="code">F_none</code>, or a positive whole number.
+ What the status code represents is application specific (or specific to a sub-standard) but may often be used to represent <abbr title="Featureless Linux Library">FLL</abbr> status code.
+ </p>
+ <ul>
+ <li>The <abbr title="Featureless Linux Library">FLL</abbr> status code is a 16-bit digit whose first two high-order bits represent <em>error</em> and <em>warning</em> ( representing <em>signal</em>).</li>
+ <li>The <abbr title="Featureless Linux Library">FLL</abbr> status code as a number is binary sensitive and may not be portable across binaries or systems.</li>
+ <li>For best portability, consider using status as a name string to ensure cross-system or cross-binary compatibility.</li>
+ </ul>
+ <p>
+ Example:
+ </p><pre class="preserve">
+# fss-000e
+# valid comments are ignored.
+header:
+ type error
+ status 296
+ length 30
+
+payload:
+The program is out of memory.
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve">
+Outer Objects would be:
+ 1) header
+ 2) payload
+
+"header" Objects would be:
+ 1.1) type
+ 1.2) status
+ 1.3) length
+
+"header" Contents would be:
+ 1.1.1) error
+ 1.2.1) 296
+ 1.3.1) 30
+
+The payload would be:
+ 2) The program is out of memory.
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - FSS-000F (Simple Packet)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, fss-000f, simple packet">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/fss/fss-000f.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">FSS</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/fss/fss-000f.html#fss-000f" class="nav-text link"><div>FSS-000F</div><div>(Simple Packet)</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/fss/fss-000f.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/fss/fss-000f.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="fss-000f" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">FSS-000F (Simple Packet)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ This is a network packet format that contains <code class="code">fss-000e (Payload)</code> within it.
+ </p>
+ <p>
+ The Simple Packet structure is described in blocks, of which are structured in bytes.
+ </p>
+ <p>
+ There are only three blocks in this format:
+ </p>
+ <ol>
+ <li>Control Block.</li>
+ <li>Size Block.</li>
+ <li>Payload Block.</li>
+ </ol>
+ <p>
+ The Control Block is the first block in the packet and is considered endianless.
+ There exists only a single byte within the Control Block.
+ Regardless of the endianness of the packet, the leftmost bit is always the <em>string</em> or <em>binary</em> bit.
+ The second bit following that bit represents the endianness bit.
+ </p>
+ <p>
+ The <em>string</em> or <em>binary</em> bit, a value of 0 designates that the packet is in string format and a value of 1 designates that the packet is in binary format.
+ While the packet might be considered to be in string format, it is technically always in binary format due to the Control Block and Size Block.
+ This means that the bit designating the packet as a <em>string</em> packet or a <em>binary</em> packet is referring to whether or not the Payload Block is in <em>string</em> format or is in <em>binary</em> format.
+ </p>
+ <p>
+ The endianness bit designates whether or not the packet is in big endian or little endian format.
+ A bit value of 0 designates that this packet is in little endian and a value of 1 designates that this packet is in big endian format.
+ All binary data within this packet, following the Control Block, must respect this endianness bit (including the Size Block).
+ </p>
+ <p>
+ The remaining bits are not defined by this standard and are expected to be 0.
+ Non-formal or local uses may utilize these remaining 6 bits as desired.
+ However, there may be additional standards that expand upon this and utilize these remaining Control bits.
+ Anything that utilizes these unused Control bits may add or remove additional Blocks after the Control Block as they see fit.
+ </p>
+ <p>
+ The Size Block is an unsigned 32-bit integer representing the size of the entire packet, including the Control Block and Size Block.
+ This size must exactly match the packet to be a valid packet.
+ The size represents number of bytes in the file.
+ The Control Block is 1 byte long and the Size Block is 4 bytes long and so the maximum available size is (2^32)-6.
+ </p>
+ <p>
+ The Payload Block is not defined by this standard of that that it exists and should be in <code class="code">fss-000e (Payload)</code> format.
+ The <code class="code">fss-000e (Payload)</code> may be represented in either string format or binary format.
+ The <code class="code">fss-000e (Payload)</code> may contain multiple <em>header</em>(s) but may only contain a single <em>payload</em>.
+ With this in mind, it is recommended that only a single <em>header</em> be supported in the Payload Block.
+ </p>
+ <p>
+ See the <a href="fll/specifications/fss/fss-000e.html" class="link">fss-000e (Payload)</a> specification for details on the syntax rules for the Payload Block.
+ </p>
+ <p>
+ Example Packet Structure:
+ </p><pre class="preserve">
+[ Control Block ] [ Size Block ] [ Payload Block ]
+[ 0b10000000 ] [ 0b00000000 0b00000000 0b00000100 0b11010010 ] [ size: 1229 (1234 - 5) ]
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - IKI-0000 (Unrestricted)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, iki-0000, unrestricted">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/iki/iki-0000.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">IKI</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/iki/iki-0000.html#iki-0000" class="nav-text link"><div>IKI-0000</div><div>(Unrestricted)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/iki/iki-0000.html#common" class="nav-text link">Common Specification Rules</a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/iki/iki-0000.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/iki/iki-0000.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="iki-0000" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">IKI-0000 (Unrestricted)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ This specification provides no restrictions on the vocabulary.
+ </p>
+ </div>
+ </section>
+
+ <section id="common" class="section">
+ <header class="section-header header separate">
+ <h2 class="section-title h h2">Common Specification Rules</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ IKI is a minimally structured WIKI-like syntax meant to be simpler than WIKI syntax.
+ </p>
+ <p>
+ The IKI syntax provides a vocabulary name (with specific context associated with it) followed by quoted code that is associated with the given vocabulary name.
+ The vocabulary represents a list of allowed variable names that may also have specific contextual meaning defined by a given IKI specification.
+ The variable name is considered the <em>Object</em>.
+ The variable value is considered the <em>Content</em>.
+ </p>
+ <p>
+ The IKI format will use <code class="code">iki-0000</code> to represent an IKI with no explicitly defined vocabulary.
+ Whereas <code class="code">iki-0001</code> and beyond represent a specific IKI vocabulary.
+ </p>
+ <p>
+ A potential IKI variable name starts on word (or <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code>) characters.
+ White space and non-word (and non <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code>) 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 (<code class="code">U+2010</code> and <code class="code">U+2011</code>).
+ </p>
+ <p>
+ Any valid IKI data may be escaped to make it treated as non-IKI data by prepending a backslash <code class="code">" before the colon code:</code>:" that is before the opening quote (single or double).
+ </p>
+ <p>
+ Unicode punctuation connector characters are supported just like <code class="code">_</code>, except when they connect outside the current line (such as <code class="code">U+FE33</code> <code class="code">︳</code>).
+ Unicode invisible punctuations (such as invisible plus: <code class="code">U+2064</code>) are not considered a punctuations in this standard (because they a zero-width characters), therefore they are not to be considered a valid <code class="code">_</code>, <code class="code">-</code>, or <code class="code">+</code> Unicode equivalents.
+ </p>
+ <p>
+ Key:
+ </p>
+ <ul>
+ <li><code class="code">\o</code> = any printable word character, including <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code> (and Unicode equivalents).</li>
+ <li><code class="code">\c</code> = 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.</li>
+ <li><code class="code">\q</code> = either a single quote <code class="code">'</code> or a double quote <code class="code">"</code>.</li>
+ <li><code class="code">\x</code> = any character.</li>
+ <li><code class="code">\W</code> = any non-word character, discluding <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code> (and Unicode equivalents).</li>
+ <li><code class="code">\e</code> = an optional escape sequence of any number of backslashes, such as <code class="code">\</code>.</li>
+ <li><code class="code">*</code> = 0 or more occurrences.</li>
+ <li><code class="code">~</code> = one or more occurrences, or 0 if at start of file.</li>
+ </ul>
+ <p>
+ Before Structure:
+ </p>
+ <ul>
+ <li><code class="code">\x*\W~\*:*</code></li>
+ </ul>
+ <p>
+ Structure:
+ </p>
+ <ul>
+ <li><code class="code">\o\e:\q\c\q</code></li>
+ </ul>
+ <p>
+ After Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Example File:
+ </p><pre class="preserve">
+# fss-000c iki-0000
+
+This is my sentence, anything can go here but sometimes I want to emphasis:"emphasize some text".
+
+Other times I want to render a url such as this example url: url:'http://www.example.com/url with space/'.
+
+There are no comments, except for maybe the FSS header (which would not resolve to any IKI syntax anyway).
+
+Quotes may be included, such as: code:"const char *string = \"My \\\"quoted\\\" C string.\";".
+
+The following emphasis\:"is escaped to not be treated as IKI data".
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve margin-below">
+Objects would be:
+ 1) emphasis
+ 2) url
+ 3) code
+
+Contents would be:
+ 1.1) emphasize some text
+ 2.1) http://www.example.com/url with space/
+ 3.1) const char *string = "My \"quoted\" C string.";
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - IKI-0001 (Basic)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, iki-0001, basic">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/iki/iki-0001.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">IKI</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/iki/iki-0001.html#iki-0001" class="nav-text link"><div>IKI-0001</div><div>(Basic)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/iki/iki-0001.html#common" class="nav-text link">Common Specification Rules</a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/iki/iki-0001.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/iki/iki-0001.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="iki-0001" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">IKI-0001 (Basic)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ This specification provides a small set of vocabulary names meant to be associated with common uses, such as e-mail addresses and <abbr title="Uniform Resource Locator">URL</abbr>s.
+ </p>
+ <p>
+ Vocabulary:
+ </p>
+ <dl class="dl">
+ <div class="di">
+ <dt class="dt">address</dt>
+ <dd class="dd">Any mailing address, except for e-mail and <abbr title="Uniform Resource Identifier">URI</abbr>.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt">code</dt>
+ <dd class="dd">All text contained within represent code and should be presented as such.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt">email</dt>
+ <dd class="dd">Any valid e-mail address.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt">phone</dt>
+ <dd class="dd">Any valid phone number.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt">quote</dt>
+ <dd class="dd">All text within represents some quote.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt">uri</dt>
+ <dd class="dd">Any valid <abbr title="Uniform Resource Identifier">URI</abbr> (allows <abbr title="Uniform Resource Locator">URL</abbr> and <abbr title="Uniform Resource Name">URN</abbr>).</dd>
+ </div>
+ <div class="di">
+ <dt class="dt">url</dt>
+ <dd class="dd">Any valid <abbr title="Uniform Resource Locator">URL</abbr>.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt">urn</dt>
+ <dd class="dd">Any valid <abbr title="Uniform Resource Name">URN</abbr>.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt">var</dt>
+ <dd class="dd">All text contained within represents some sort of variable.</dd>
+ </div>
+ </dl>
+ </div>
+ </section>
+
+ <section id="common" class="section">
+ <header class="section-header header separate">
+ <h2 class="section-title h h2">Common Specification Rules</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ IKI is a minimally structured WIKI-like syntax meant to be simpler than WIKI syntax.
+ </p>
+ <p>
+ The IKI syntax provides a vocabulary name (with specific context associated with it) followed by quoted code that is associated with the given vocabulary name.
+ The vocabulary represents a list of allowed variable names that may also have specific contextual meaning defined by a given IKI specification.
+ The variable name is considered the <em>Object</em>.
+ The variable value is considered the <em>Content</em>.
+ </p>
+ <p>
+ The IKI format will use <code class="code">iki-0000</code> to represent an IKI with no explicitly defined vocabulary.
+ Whereas <code class="code">iki-0001</code> and beyond represent a specific IKI vocabulary.
+ </p>
+ <p>
+ A potential IKI variable name starts on word (or <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code>) characters.
+ White space and non-word (and non <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code>) 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 (<code class="code">U+2010</code> and <code class="code">U+2011</code>).
+ </p>
+ <p>
+ Any valid IKI data may be escaped to make it treated as non-IKI data by prepending a backslash <code class="code">" before the colon code:</code>:" that is before the opening quote (single or double).
+ </p>
+ <p>
+ Unicode punctuation connector characters are supported just like <code class="code">_</code>, except when they connect outside the current line (such as <code class="code">U+FE33</code> <code class="code">︳</code>).
+ Unicode invisible punctuations (such as invisible plus: <code class="code">U+2064</code>) are not considered a punctuations in this standard (because they a zero-width characters), therefore they are not to be considered a valid <code class="code">_</code>, <code class="code">-</code>, or <code class="code">+</code> Unicode equivalents.
+ </p>
+ <p>
+ Key:
+ </p>
+ <ul>
+ <li><code class="code">\o</code> = any printable word character, including <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code> (and Unicode equivalents).</li>
+ <li><code class="code">\c</code> = 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.</li>
+ <li><code class="code">\q</code> = either a single quote <code class="code">'</code> or a double quote <code class="code">"</code>.</li>
+ <li><code class="code">\x</code> = any character.</li>
+ <li><code class="code">\W</code> = any non-word character, discluding <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code> (and Unicode equivalents).</li>
+ <li><code class="code">\e</code> = an optional escape sequence of any number of backslashes, such as <code class="code">\</code>.</li>
+ <li><code class="code">*</code> = 0 or more occurrences.</li>
+ <li><code class="code">~</code> = one or more occurrences, or 0 if at start of file.</li>
+ </ul>
+ <p>
+ Before Structure:
+ </p>
+ <ul>
+ <li><code class="code">\x*\W~\*:*</code></li>
+ </ul>
+ <p>
+ Structure:
+ </p>
+ <ul>
+ <li><code class="code">\o\e:\q\c\q</code></li>
+ </ul>
+ <p>
+ After Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Example File:
+ </p><pre class="preserve">
+# fss-000c iki-0001
+
+This is my sentence, anything can go here but sometimes I want to emphasis:"emphasize some text".
+
+Other times I want to render a url such as this example url: url:'http://www.example.com/url with space/'.
+
+There are no comments, except for maybe the FSS header (which would not resolve to any IKI syntax anyway).
+
+Quotes may be included, such as: code:"const char *string = \"My \\\"quoted\\\" C string.\";".
+
+The following emphasis\:"is escaped to not be treated as IKI data".
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve margin-below">
+Objects would be:
+ 1) emphasis
+ 2) url
+ 3) code
+
+Contents would be:
+ 1.1) emphasize some text
+ 2.1) http://www.example.com/url with space/
+ 3.1) const char *string = "My \"quoted\" C string.";
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>FLL - Specifications - IKI-0002 (Simple Script)</title>
+
+ <base href="../../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Featurless Linux Library Specifications">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, specification, standard, iki-0002, simple script">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="fll/specifications/iki/iki-0002.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="fll/specifications.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">FLL Specification</div>
+ <div class="nav-text unlink">IKI</div>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/iki/iki-0002.html#iki-0002" class="nav-text link"><div>IKI-0002</div><div>(Simple Script)</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="fll/specifications/iki/iki-0002.html#common" class="nav-text link">Common Specification Rules</a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="fll/specifications/iki/iki-0002.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="fll/specifications/iki/iki-0002.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Featureless Linux Library Specification</h1>
+ </header>
+
+ <section id="iki-0002" class="section">
+ <header class="section-header header">
+ <h2 class="section-title h h2">IKI-0002 (Simple Script)</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ This specification provides a small set of vocabulary names meant to be used for substitution in simple scripts.
+ </p>
+ <p>
+ This specification only loosely defines the vocabulary context.
+ This vocabulary may be further extended but must at least support the taxonomy defined here.
+ Flexibility on interpretation is intended so that the context can be more fine-tuned and customized.
+ </p>
+ <p>
+ The taxonomy for the emphasis:"context", emphasis:"define", and emphasis:"parameter" are intentionally not defined here and left open.
+ One utilizing this should document the taxonomy for each of these as desired.
+ </p>
+ <p>
+ Vocabulary:
+ </p>
+ <dl class="dl">
+ <div class="di">
+ <dt class="dt">context</dt>
+ <dd class="dd">Intended to be used for printing (or tagging) context codes before and after text, such as with color context.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt">define</dt>
+ <dd class="dd">Intended to be used for global properties, much like a C/C++ <code class="code">#define</code>.</dd>
+ </div>
+ <div class="di">
+ <dt class="dt">parameter</dt>
+ <dd class="dd">Intended to be used for parameters or variables.</dd>
+ </div>
+ </dl>
+ </div>
+ </section>
+
+ <section id="common" class="section">
+ <header class="section-header header separate">
+ <h2 class="section-title h h2">Common Specification Rules</h2>
+ </header>
+
+ <div class="section-content">
+ <p>
+ IKI is a minimally structured WIKI-like syntax meant to be simpler than WIKI syntax.
+ </p>
+ <p>
+ The IKI syntax provides a vocabulary name (with specific context associated with it) followed by quoted code that is associated with the given vocabulary name.
+ The vocabulary represents a list of allowed variable names that may also have specific contextual meaning defined by a given IKI specification.
+ The variable name is considered the <em>Object</em>.
+ The variable value is considered the <em>Content</em>.
+ </p>
+ <p>
+ The IKI format will use <code class="code">iki-0000</code> to represent an IKI with no explicitly defined vocabulary.
+ Whereas <code class="code">iki-0001</code> and beyond represent a specific IKI vocabulary.
+ </p>
+ <p>
+ A potential IKI variable name starts on word (or <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code>) characters.
+ White space and non-word (and non <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code>) 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 (<code class="code">U+2010</code> and <code class="code">U+2011</code>).
+ </p>
+ <p>
+ Any valid IKI data may be escaped to make it treated as non-IKI data by prepending a backslash <code class="code">" before the colon code:</code>:" that is before the opening quote (single or double).
+ </p>
+ <p>
+ Unicode punctuation connector characters are supported just like <code class="code">_</code>, except when they connect outside the current line (such as <code class="code">U+FE33</code> <code class="code">︳</code>).
+ Unicode invisible punctuations (such as invisible plus: <code class="code">U+2064</code>) are not considered a punctuations in this standard (because they a zero-width characters), therefore they are not to be considered a valid <code class="code">_</code>, <code class="code">-</code>, or <code class="code">+</code> Unicode equivalents.
+ </p>
+ <p>
+ Key:
+ </p>
+ <ul>
+ <li><code class="code">\o</code> = any printable word character, including <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code> (and Unicode equivalents).</li>
+ <li><code class="code">\c</code> = 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.</li>
+ <li><code class="code">\q</code> = either a single quote <code class="code">'</code> or a double quote <code class="code">"</code>.</li>
+ <li><code class="code">\x</code> = any character.</li>
+ <li><code class="code">\W</code> = any non-word character, discluding <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code> (and Unicode equivalents).</li>
+ <li><code class="code">\e</code> = an optional escape sequence of any number of backslashes, such as <code class="code">\</code>.</li>
+ <li><code class="code">*</code> = 0 or more occurrences.</li>
+ <li><code class="code">~</code> = one or more occurrences, or 0 if at start of file.</li>
+ </ul>
+ <p>
+ Before Structure:
+ </p>
+ <ul>
+ <li><code class="code">\x*\W~\*:*</code></li>
+ </ul>
+ <p>
+ Structure:
+ </p>
+ <ul>
+ <li><code class="code">\o\e:\q\c\q</code></li>
+ </ul>
+ <p>
+ After Structure:
+ </p>
+ <ul>
+ <li><code class="code"></code></li>
+ </ul>
+ <p>
+ Example File:
+ </p><pre class="preserve">
+# fss-000c iki-0000
+
+This is my sentence, anything can go here but sometimes I want to emphasis:"emphasize some text".
+
+Other times I want to render a url such as this example url: url:'http://www.example.com/url with space/'.
+
+There are no comments, except for maybe the FSS header (which would not resolve to any IKI syntax anyway).
+
+Quotes may be included, such as: code:"const char *string = \"My \\\"quoted\\\" C string.\";".
+
+The following emphasis\:"is escaped to not be treated as IKI data".
+</pre>
+ <p>
+ Example Results:
+ </p><pre class="preserve margin-below">
+Objects would be:
+ 1) emphasis
+ 2) url
+ 3) code
+
+Contents would be:
+ 1.1) emphasize some text
+ 2.1) http://www.example.com/url with space/
+ 3.1) const char *string = "My \"quoted\" C string.";
+</pre>
+ </div>
+ </section>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
<div id="nav-expanded" class="nav-block">
<nav id="kevux-document-nav" class="nav-menu">
<div class="nav-item block">
+ <div class="nav-text notice">2022 / 05 / 16</div>
+ <a href="news/2022_05_16-fll_specifications_added.html" class="nav-text link">FLL Specifications Added</a>
+ </div>
+ <div class="nav-item block">
<div class="nav-text notice">2022 / 05 / 06</div>
<a href="news/2022_05_06-basic_program_documentation.html" class="nav-text link">Basic Program Documentation</a>
</div>
<article class="article">
<header class="article-header header">
+ <h2 class="article-title h h2">2022 / 05 / 16 - FLL Specifications Added</h2>
+ </header>
+
+ <div class="article-content">
+ <p>
+ Updated the <abbr title="Featureless Linux Library">FLL</abbr> specifications and made them available on the website.
+ </p>
+ <p>
+ Basic styling is applied to make the specifications reasonably readable on a website. I avoided doing any complicated designs so that I can focus on other tasks (such as making a stable release). I took a shortcut on the example results by using the <code class="code"><pre></code> tag.
+ </p>
+ <p>
+ <a href="news/2022_05_16-fll_specifications_added.html" class="content link">Continue reading…</a>
+ </p>
+ </div>
+ </article>
+
+ <article class="article">
+ <header class="article-header header separate">
<h2 class="article-title h h2">2022 / 05 / 06 - Basic Program Documentation</h2>
</header>
+
<div class="article-content">
- <p>
- Update the website, bringing in my initial pass at the documentation for each of the programs provided by the <abbr title="Featureless Linux Library">FLL</abbr> project. Most of this documentation is copied from the help of each program and any improvements or deviations are incidental.
- </p>
- <p>
- While working on the documentation, I discovered and fixed random problems. In particular, the <strong>iki_read</strong> program in the release candidate has a major regression where it doesn't do anything. This is the result of a very minor mistake in passing the wrong size variable to the file read functions. Essentially, the <strong>iki_read</strong> program is only processing files of length 0 and as a result never produces any output. This is now fixed upstream and I am even happier with the practice of using release candidates.
- </p>
+
Update the website, bringing in my initial pass at the documentation for each of the programs provided by the <abbr title="Featureless Linux Library">FLL</abbr> project. Most of this documentation is copied from the help of each program and any improvements or deviations are incidental.
+ </p>
+ While working on the documentation, I discovered and fixed random problems. In particular, the <strong>iki_read</strong> program in the release candidate has a major regression where it doesn't do anything. This is the result of a very minor mistake in passing the wrong size variable to the file read functions. Essentially, the <strong>iki_read</strong> program is only processing files of length 0 and as a result never produces any output. This is now fixed upstream and I am even happier with the practice of using release candidates.
+ </p>
<p>
<a href="news/2022_05_06-basic_program_documentation.html" class="content link">Continue reading…</a>
</p>
<header class="article-header header separate">
<h2 class="article-title h h2">2022 / 05 / 01 - Website Redesign</h2>
</header>
+
<div class="article-content">
<p>
With a stable release of the Featureless Linux Library around the corner and the resuming of development of the Turtle Kevux Distribution, it is now time to refresh the website.
<!DOCTYPE html>
<html lang="en">
<head>
- <title>News - 2022/05/01 Website Re-design</title>
+ <title>News - 2022/05/01 - Website Re-design</title>
<base href="../">
<!DOCTYPE html>
<html lang="en">
<head>
- <title>News - 2022/05/06 Basic Program Documentation</title>
+ <title>News - 2022/05/06 - Basic Program Documentation</title>
<base href="../">
<meta charset="UTF-8">
<meta name="author" content="Kevin Day">
- <meta name="description" content="News post on 2022/05/01.">
+ <meta name="description" content="News post on 2022/05/06.">
<meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, News">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
<link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
- <link rel="canonical" href="news/2022_05_01-website_redesign.html">
+ <link rel="canonical" href="news/2022_05_06-basic_program_documentation.html">
<link type="image/x-icon" rel="icon" href="images/kevux.ico">
<link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
<link type="text/html" rel="license" href="licenses.html">
<div class="nav-text unlink">Basic Program Documentation</div>
</div>
<div class="nav-item block ellipses">
- <a href="news/2022_05_01-website_redesign.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
- <a href="news/2022_05_01-website_redesign.html" class="nav-text link close">Collapse Menu</a>
+ <a href="news/2022_05_06-basic_program_documentation.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="news/2022_05_06-basic_program_documentation.html" class="nav-text link close">Collapse Menu</a>
</div>
</nav>
</div>
While working on the documentation, I discovered and fixed random problems. In particular, the <strong>iki_read</strong> program in the release candidate has a major regression where it doesn't do anything. This is the result of a very minor mistake in passing the wrong size variable to the file read functions. Essentially, the <strong>iki_read</strong> program is only processing files of length 0 and as a result never produces any output. This is now fixed upstream and I am even happier with the practice of using release candidates.
</p>
<p>
- The website has been updated with an appropriate <code>.htaccess</code> file to better handle paths. I even decided to further emphasize the retro-internet feel by redirecting directory paths to html files, if they exist. I imagine this may annoy some of the people out there. Minor problems here and there have been addressed as I discovered them.
+ The website has been updated with an appropriate <code class="code">.htaccess</code> file to better handle paths. I even decided to further emphasize the retro-internet feel by redirecting directory paths to html files, if they exist. I imagine this may annoy some of the people out there. Minor problems here and there have been addressed as I discovered them.
</p>
<p>
This website is also designed to be fully downloadable and readable locally (and even offline). Whenever I have notable changes on the website, I will update the downloadable tarball of this website.
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>News - 2022/05/16 - FLL Specifications Added</title>
+
+ <base href="../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="News post on 2022/05/16.">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, News">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="news/2022_05_16-fll_specifications_added.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js news">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item active"><a href="index.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="index.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block unlink">
+ <div class="nav-text notice">2022 / 05 / 16</div>
+ <div class="nav-text unlink">FLL Specifications Added</div>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="news/2022_05_16-fll_specifications_added.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="news/2022_05_16-fll_specifications_added.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">2022 / 05 / 16 - FLL Specifications Added</h1>
+ </header>
+
+ <div class="main-content">
+ <p>
+ Updated the <abbr title="Featureless Linux Library">FLL</abbr> specifications and made them available on the website.
+ </p>
+ <p>
+ Basic styling is applied to make the specifications reasonably readable on a website. I avoided doing any complicated designs so that I can focus on other tasks (such as making a stable release). I took a shortcut on the example results by using the <code class="code"><pre></code> tag.
+ </p>
+ <p>
+ Only the main <abbr title="Featureless Linux Library">FLL</abbr> specification pages are updated. The specifications (or links to specifications) on the programs pages have not been updated. There is still quite a lot to do in regards to documenting the programs.
+ </p>
+ <p>
+ Several mistakes on the website, such as incorrect canonical addresses, are now fixed.
+ </p>
+ <p>
+ I have also added an informal definition of my <a href="fll/specifications.html#completeness_theorem" class="link">Completeness Theorem</a> that I always used for just about all of my personal work. This has been in use by the <abbr title="Featureless Linux Library">FLL</abbr> since I first started working on it. I believe that I just never formally (or informally) wrote down my theory (I believe that the concepts for this were touched on in my thesis).
+ </p>
+ <p>
+ <strong>Kevin Day</strong>
+ </p>
+ </div>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
</header>
<div class="article-content">
<p>
- This tool is a nifty way to get a <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> friendly <code>hexdump</code> alternative.<br>
+ This tool is a nifty way to get a <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> friendly <code class="code">hexdump</code> alternative.<br>
The output is intended to honor some of the feel of hexdump but do so in an <abbr title="Featureless Linux Library">FLL</abbr> way.
</p>
</div>
</p>
<p>
The goal of this is to provide task and service management similar to sysvinit, initng, and systemd.<br>
- This is designed to be used for booting the system as if it were <code>/sbin/init</code>.
+ This is designed to be used for booting the system as if it were <code class="code">/sbin/init</code>.
</p>
<p>
This should be controllable from user-space via the "Control" program.
The status codes are converted to or from a code and a label.
</p>
<p>
- This program handles more status codes that the <code>status_code</code> program.
+ This program handles more status codes that the <code class="code">status_code</code> program.
</p>
</div>
</article>
<p>
The IKI settings specification plays on how it is simpler than a Wiki syntax.<br>
The IKI could be used for anything from e-mails and text-messages to word-processors.<br>
- The goal with IKI is to be very easily readably by a human, such as: <code>iki:"example"</code> or <code>url:"https://sourceforge.net/projects/fll/"</code>.
+ The goal with IKI is to be very easily readably by a human, such as: <code class="code">iki:"example"</code> or <code class="code">url:"https://sourceforge.net/projects/fll/"</code>.
</p>
<p>
This program is a swiss army knife for reading files that contain IKI syntax.
<p>
The IKI settings specification plays on how it is simpler than a Wiki syntax.<br>
The IKI could be used for anything from e-mails and text-messages to word-processors.<br>
- The goal with IKI is to be very easily readably by a human, such as: <code>iki:"example"</code> or <code>url:"https://sourceforge.net/projects/fll/"</code>.
+ The goal with IKI is to be very easily readably by a human, such as: <code class="code">iki:"example"</code> or <code class="code">url:"https://sourceforge.net/projects/fll/"</code>.
</p>
<p>
This program is a swiss army knife for writing files that contain IKI syntax.
projects / kevux.org-website / commitdiff