TI Toolkit Token Sheets

Here, you can find token sheets for the TI-83/84-series calculators to include in external projects. The sheets contain detailed information about every token in a simple XML format. Basic scripts for parsing the sheets are also included.

How to Use

To include the token sheets in your next project, add them to your repository as a Git submodule via the git submodule command. You can target the built branch to clone just the sheets without any of the scripts or config files. Check out this project for an example.

You can also manually include a download of the sheets and/or scripts as needed.

XML Format

The XML format for 8X.xml is outlined below.

Tokens

Each token is stored in a <token> tag (perhaps within a <two-byte> parent, if the token is two bytes) containing one or more <version> tags, which detail the history of the token across OS versions.

<tokens>
	...
	<token value="$BA">
		<version>...</version>
		<version>...</version>
	</token>
	<two-byte value="$BB">
		<token value="$00">
			<version>...</version>
		</token>
	</two-byte>
	...
</tokens>

Versions

The token sheet forces the calculator operating system versions into a clean, linear timeline spanning over 30 years. Four essential patterns allow for this:

1. Newer calculators in the lineage generally get their token table's first version directly from their immediate predecessor's last version.
2. Older calculators do not receive patches after a newer model is introduced.
3. Changes from version to version (we treat calculator-to-calculator changes as version-to-version changes, given the previous points) are usually limited to addition, renaming, and omission.
   • Basically, we don't see dramatic reorganization of the token data.
4. Critically, the current system handles any violation of these patterns (that we have encountered) nicely.

We can then track the history of any token with a series of half-open ranges placed on this timeline. We use [since, until) (i.e. both since and until are versions where changes happened).

Versions are written as major.minor or major.minor.patch.

For our timeline, we define an ordering of calculator models here. Versions are compared first by model, then by major OS version, then by minor OS version, then by patch OS version, if present.

Each version includes a <since> tag, the first OS with that version of the token, and an optional <until> tag. The remaining tags are translations of that token into available languages.

<version>
	<since>
		<model>TI-82</model>
		<os-version>1.0</os-version>
	</since>
	<until>
		<model>TI-83</model>
		<os-version>0.0103</os-version>
	</until>
	<lang code="en">...</lang>
</version>

Translations

Each language translation contains a number of different ways that token is represented on- and off-calc in that language:

• ti-ascii: The font bytes corresponding to the token's characters on-calc
• display: A Unicode approximation of the token's on-calc appearance. These are meant only for display; they are not unique and may contain characters not found on most keyboards.
• <accessible>: A representation of the token meant to be easy to type for speakers of the language. For en, this means ASCII and Latin-1.
• <variant>: Any other name commonly used to represent the token (optional and repeatable).

accessible and variant entries are guaranteed to be unique within their version and translation, and there must not be any overlapping names between them. This is vital for tokenization tasks.

<lang code="en" ti-ascii="7528012D3229" display="u(𝑛-2)">
	<accessible>u(n-2)</accessible>
	<variant>u(𝒏-2)</variant>
</lang>

Warning

Currently, only English translations are supported. See our contribution guidelines for details on adding new translations.

The default translation is en. If a translation is not specified for a token, it is the same as the en translation.

Other Formats

Alternative token sheet formats, such as JSON, can be found in the built branch. These formats are automatically generated whenever an XML sheet is updated, and thus only the XML sheets should be targeted by PR's.

If there's a format you want supported, feel free to open an issue.

Scripts

The scripts package contains Python scripts for parsing and manipulating the token sheets.

• build.py: Helper script to generate the built branch
• formats.py: Convert an XML sheet to another format, e.g. JSON (see above)
• parse.py: Load a sheet or individual tokens into Python objects
• tokenide.py: Create or update token files used by TokenIDE
• trie.py: Create a trie from a sheet for use in tokenization

Contributions welcome!