Skip to content

Commit 0df6fc5

Browse files
committed
[lex.charset] Move reference to glyphs to appropriate place
The statement that glyphs are used to identify members of the basic character set does not belong separating two sentences introducing and then defining preprocessing tokens. Also, we do not *exlusively* use glyphs for this purpose but also directly call out Unicode code points too, so tone down the phrasing to glyphs are *often* used to ...
1 parent a1e1535 commit 0df6fc5

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

source/lex.tex

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -317,6 +317,8 @@
317317
\pnum
318318
The \defnadj{basic}{character set} is a subset of the translation character set,
319319
consisting of 99 characters as specified in \tref{lex.charset.basic}.
320+
In this document, glyphs are often used to identify elements of
321+
the basic character set.
320322
\begin{note}
321323
Unicode short names are given only as a means to identifying the character;
322324
the numerical value has no other meaning in this context.
@@ -549,9 +551,6 @@
549551
\pnum
550552
A preprocessing token is the minimal lexical element of the language in translation
551553
phases 3 through 6.
552-
In this document,
553-
glyphs are used to identify
554-
elements of the basic character set\iref{lex.charset}.
555554
The categories of preprocessing token are: header names,
556555
placeholder tokens produced by preprocessing \tcode{import} and \tcode{module} directives
557556
(\grammarterm{import-keyword}, \grammarterm{module-keyword}, and \grammarterm{export-keyword}),

0 commit comments

Comments
 (0)