Proposal: version names for Tcekitaujau dialects

From Lojban
Revision as of 17:14, 16 September 2016 by Krtisfranks (talk | contribs) (Created page with "Tcekitaujau is a proposal and family of dialects of Lojban which, when implemented/activated, swaps some cmavo (and rafsi) pairs' with respect to their CLL 1...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Tcekitaujau is a proposal and family of dialects of Lojban which, when implemented/activated, swaps some cmavo (and rafsi) pairs' with respect to their CLL 1.1 meaning. Unfortunately, there are very many possibilities for which words are swapped. Thus, it is necessary, in order to avoid confusion (and, technically, ambiguity/breaking of the language in any text which employs any of the words which any dialect of Tcekitaujau would swap), to implement naming in order to identify which dialect is in use.

This is done by using "jo'au". This word specifies the Lojban version being activated for thefollowing text (until the next "jo'au" is uttered). The default version, modulo culture and implicit social conventions, is CLL 1.1, which is officially implemented. In order to acivate (some dialect of) Tcekitaujau, utter "jo'au tcekitaujau".

Without any further specification, this implies only that some dialect of Tcekitaujau is being used, not which - it is a vague flag/warning to the audience.

What follows is a series of proposals, possibly mutually contradictory, for how to further specify which dialect, exactly, is being used. Note that if any given dialect is ever incorporated into the default implementation of Lojban (some CLL v. ), then this manual and explicit activation via "jo'au" - for that specific dialect - is automatic and therefore unnecessary.

"kyfy" version naming schema

This is a proposal by lai .krtisfranks. (Hence "kyfy"). It is designed to be inclusive of and general for any dialect of Tcekitaujau. It should be easy to understand, craft, and express; the general principles should be easy to remember. However, it is also clunky and arbitrary, making its practical usage somewhat difficult to memorize.

All versions are specified by "jo'au tcekitaujau kyfy pi'e" which is immediately followed by a two-digit number or a QWERTY letter in standard lerfu form for Lojban (this string is the mode specifier), which may then be immediately followed by "pi'e" and then immediately by a number (this is the tier specifier), which will be immediately followed by "pi'e" and then immediately by some ASCII string (which is called the version specifier). If a tier specifier is used, then both a mode and a version specifier must be used. The whole string is called the specification.

First, there are 2n+1 modes; currently n = 1.

They are currently assigned mode specifiers "0", "1", and ".a'y". Mode ".a'y" is the only one of these which must not have a tier specifier; all of the others requir tier specifiers. Mode ".a'y" is an elliptical version name which just means that some dialect of Tcekitaujau is in usage, but which is not specified; it is, in a sense, equivalent to "xo'ei", except for the fact that no additional strings may be concatenated to its end; ".a'y" as a mode specifier cannot be followed by any nonempty string.

Each version specification literally encodes the swaps as an ordered string of bits; how this works will be explained below. If the mode is "0", then "on" bits are denoted by "0"'s and the "off" bits are denoted by "1"'s - this is exactly opposite to typical computer notation, but it has its perks. If the mode is "1", then the "on" bits are denoted by "1"'s and the "off" bits are denoted by "0"'s - exactly as is standard in computer science. That is for n being 0 or 1, mode "n" has "n" representing "on" bits and its bit-complement representing "off" bits. Thus the version specifications (but not the tier specifications) for modes "0" and "1" are exact bit-complements of each other before rendering/being 'encrypted'.

If two specifications are connected by "ce'o", then they left-group but in cases of conflict, the latter one prevails. They can compound so that if the first-mentioned version swaps X and Y while the latter-mentioned version swaps X and Z such that they do not really conflict, then the swaps happen in left-to-right order so that new-X is old-Z, new-Y is old-X, and new-Z is old-Y. The whole specification must be uttered when "ce'o"-connected.

Tier "1": the primary/basic dialect