package nisaba

Get desktop application:
View/edit binary Protocol Buffers messages

An index containing, for each letter of a particular script, a list of languages using it. Next available ID: 3

• repeated string uname_prefix = 1

• repeated LetterLanguages.Item item = 2

  List of all the letters.

A mapping between single letter and the corresponding list of languages. Next available ID: 4

Used in: LetterLanguages

• optional UnicodeStrings.Item letter = 1

  Letter definition.

• repeated string language = 2

  A list of three-letter (`alpha-3`) language codes in ISO 639-2/3 format. See: https://iso639-3.sil.org/code_tables/639/data.

• repeated string region = 3

  A letter may or may not be specific to a particular region as well. This list specifies three-letter (`alpha-3`) country codes where this letter is used in ISO 3166-1/2/3 format. For example, according to Wikipedia, Chad has over 120 indigenous languages, a considerable number of which are written using either Latin or Arabic orthography (`L’Alphabet national tchadien`) developed by the ministry of education (see, e.g., https://unicode.org/L2/L2010/10288-arabic-proposal.pdf).

Next available ID: 4

A data item can represent a single item in a list of Unicode strings or an item in a mapping.

• repeated string uname_prefix = 1

  Default prefixes for the Unicode character names listed in the `uname` or 'to_uname' fields in `Item` messages in this file. This usually corresponds, but is not restricted, to the script name of these characters, e.g. "BENGALI", "GUJARATI". It could have multiple values like `["ARABIC", "ARABIC LETTER"]`. An empty prefix is assumed to be implicitly present. When joined with these prefixes, `uname` field in an `Item` should be equal to exactly one character name. If this field is set, these prefixes can be omitted from the names of the characters.

• repeated string to_uname_prefix = 3

  Default prefixes for the Unicode character names listed in the `to_uname` field in `Item` messages in this file. This usually corresponds, but is not restricted, to the script name for the text in `to_raw`, e.g. "BENGALI", "GUJARATI". It could have multiple values like `["ARABIC", "ARABIC LETTER"]`. An empty prefix is assumed to be implicitly present. When joined with these prefixes, `to_uname` field in an `Item` should match with exactly one character name. If this field is set, these prefixes can be omitted from the names of the characters. If it is not set, it defaults to `uname_prefix` field.

• repeated UnicodeStrings.Item item = 2

  A sequence of data items.

Next available ID: 5

Fields `uname` and `raw` are required for defining Unicode string lists (languages) or the source item in a mapping (relation). At least one of the two fields has to be set. If both fields are set, codepoint representation in `uname` must match the contents of `raw`, otherwise an error is raised.

Used in: LetterLanguages.Item, UnicodeStrings

• repeated string uname = 1

  Sequence of Unicode characters specified by their character names (e.g., `BENGALI VOWEL SIGN UU`) or name aliases (e.g., `KANNADA LETTER LLLA`), or sequence names (e.g., `TAMIL SYLLABLE NNNAI`). Example: [`BRAHMI LETTER AI`, `BRAHMI LETTER JA`].

• string raw = 2

  Raw Unicode string. Example: `𑀐𑀚`.

• repeated string to_uname = 3

  Destination sequence of Unicode characters or sequences specified by their character names (e.g., `BENGALI VOWEL SIGN UU`) or name aliases (e.g., `KANNADA LETTER LLLA`), or sequence names (e.g., `TAMIL SYLLABLE NNNAI`).

• string to_raw = 4

  Destination represented as verbatim string in UTF-8 format. Example: `ꯏꯑꯎ`.