While these are not in a release yet (they are in the master and devel branches), inspired by some new features of gforth 1.0 I have added to zeptoforth "foo\r\nbar" string literals with support for escapes, 'x' character literals with support for UTF-8, backtick-prefix execution token literals, double backtick-prefix name token literals, and 0xDEADBEEF integer hex prefixes.
I have also extended char and [char] to support UTF-8, and added ansi-term::get-unicode-from-utf-8 to get a Unicode code point read from console input as UTF-8 and ansi-term::emit-unicode-as-utf-8 to emit a Unicode code point to console output as UTF-8.
There is validation of UTF-8 to prevent overlong encodings and to limit code points to a maximum of $10FFFF, with U+FFFD being used to replace invalid Unicode. Also, when parsing UTF-8 read from console input, if there is a saved byte it is used, and if there is an error in the UTF-8 and the byte read from console input is a valid beginning to another code point is saved to be read by a subsequent call to ansi-term::get-unicode-from-utf-8 or ansi-term::get-key.
Note that I have not yet implemented literals of the form 7k4 or 3M4 for floating-point numbers. Also, I do not plan on implementing <baz> or <quux+$10> type literals, as execution tokens in zeptoforth are already the address of the first byte of the code of a word, and <quuux> is already established by convention to be how classes are named.
I also have no current plans to implement recognizers, as for most purposes zeptoforth already has extensible literal parsing and name looking-up, and implementing recognizing would require significantly more redesign than I am planning on doing at the present.
For the record, if you are looking for the repository, it is at https://github.com/tabemann/zeptoforth/ .