From 7bc7662f3cd1ceaf55e00f3d5f84e9772574afc8 Mon Sep 17 00:00:00 2001 From: Robin Haberkorn Date: Thu, 3 Jul 2025 15:21:37 +0200 Subject: implemented ^E string building constructs for embedding bytes and codepoints in a strtoul()-like manner --- doc/sciteco.7.template | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'doc') diff --git a/doc/sciteco.7.template b/doc/sciteco.7.template index 51a4da2..ba43ac2 100644 --- a/doc/sciteco.7.template +++ b/doc/sciteco.7.template @@ -1846,6 +1846,19 @@ Operations on registers (\fBEU\fP) similarily consult the register's encoding. Everything else expects Unicode codepoints. .TP +.SCITECO_TOPIC ^E< ^E<> +.BI ^E< code > +Expands to the character, specified by \fIcode\fP. +\# This is Video-TECO-like. TECO-11 only accepts octal codes AFAIK. +It is read in decimal by default, but can be given in hexadecimal if lead by \(lq0x\(rq +or octal if given with a leading \(lq0\(rq. +The current radix as specified by \fB^R\fP does not influence parsing. +These semantics are compatible with libc's +.BR stroull (3). +The sequence \(lq^E<0x41>\(rq for instance expands to the character \(lqA\(rq. +The interpretation of this code as bytes or Unicode codepoints depends on the context +just like for \fB^EU\fP. +.TP .SCITECO_TOPIC ^EQ ^EQq .BI ^EQ q Expands to the string contents of the Q-Register specified by -- cgit v1.2.3