For BLAST and SSAHA2, all non-alphanumeric characters were interpreted as a space for a total of alphabet size of 47, for Simrank no substitution for any of the 61 unique characters was performed.
A simple strategy is to just split on all non-alphanumeric characters, but while looks okay, looks intuitively bad.
The hyperlinks are tokenized after replacing all non-alphanumeric characters with space.
For the hyperlinks, terms are extracted by replacing all non-alphanumeric characters as token separator in the hyperlinks.
These two identifiers - the unique archive identifier and the unique record identifier - can then be concatenated (separated by any printable non-alphanumeric character) to form a unique full identifier (referred to as a fullID in the protocol documentation).
Base62x was first described in a paper[16] where it is proposed as an alternative approach to Base64 for non-alphanumeric characters and is intended to be an improved implementation of Base64.
A "word" means any string of alphanumeric characters bounded by non-alphanumeric characters or end-of-string.
For the tag markers, only non-alphanumeric characters are recognized for tags, with the exception of a few reserved characters used by the SQLite database (e.g., single quote, underscrore, percent sign, and ampersand).
Once a dataset is loaded, all variable labels are normalised in order to remove non-alphanumeric characters and certain words (e.g. articles, conjunctions), and to split numbers from letters (e.g. 'DTP-3 dose given to the infant' would be converted to 'DTP 3 dose given infant'; see 'fNormTxt.ado' in additional file 1).
If you upload files with non-alphanumeric characters in their filenames, the system will convert those characters into underscores.
If you use the hash mark or another single character, your tags cannot include spaces; however, if you use curly brackets or some other characters at the beginning and ending of the tag pattern, your tags can be strings that include spaces, hyphens, or other non-alphanumeric characters.
