[latex3-commits] [git/LaTeX3-latex3-latex3] text-map: Clarify documentation (47099cc2d)

Joseph Wright joseph.wright at morningstar2.co.uk
Mon Aug 8 15:05:47 CEST 2022


Repository : https://github.com/latex3/latex3
On branch  : text-map
Link       : https://github.com/latex3/latex3/commit/47099cc2dba83aaa7e7c40aa346840f1d7aa86b4

>---------------------------------------------------------------

commit 47099cc2dba83aaa7e7c40aa346840f1d7aa86b4
Author: Joseph Wright <joseph.wright at morningstar2.co.uk>
Date:   Mon Aug 8 14:05:47 2022 +0100

    Clarify documentation


>---------------------------------------------------------------

47099cc2dba83aaa7e7c40aa346840f1d7aa86b4
 l3kernel/l3text.dtx | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/l3kernel/l3text.dtx b/l3kernel/l3text.dtx
index 570cf8942..3cd8668bd 100644
--- a/l3kernel/l3text.dtx
+++ b/l3kernel/l3text.dtx
@@ -312,8 +312,10 @@
 %   the Unicode Consortium describe the decomposition of input to
 %   graphemes in depth, and the approach used here implements that
 %   algorithm. The \meta{function} should accept one argument as \meta{balanced
-%   text}: this may be a single codepoint, multiple codepoints (or with an
-%   $8$-bit engine bytes) or may be a control sequence.
+%   text}: this may be comprise codepoints or may be a control sequence.
+%   With $8$-bit engines, the codepoint(s) themselves may of course be
+%   made up of multiple bytes: the mapping will pass the correct codepoints
+%   independent of the engine in use.
 %   See also \cs{text_map_inline:nn}.
 % \end{function}
 %
@@ -329,8 +331,10 @@
 %   graphemes in depth, and the approach used here implements that
 %   algorithm. The \meta{inline function} should consist of code which
 %   receives the grapheme as \meta{balanced
-%   text}: this may be a single codepoint, multiple codepoints (or with an
-%   8-bit engine bytes) or may be a control sequence.
+%   text}: this may be comprise codepoints or may be a control sequence.
+%   With $8$-bit engines, the codepoint(s) themselves may of course be
+%   made up of multiple bytes: the mapping will pass the correct codepoints
+%   independent of the engine in use.
 %   See also \cs{text_map_function:nN}.
 % \end{function}
 %





More information about the latex3-commits mailing list.