[latex3-commits] [git/LaTeX3-latex3-latex2e] develop: ltpara: just one fix so far (fad42ce8)
Chris Rowley
car222222 at github.github.io
Thu Nov 11 06:13:41 CET 2021
Repository : https://github.com/latex3/latex2e
On branch : develop
Link : https://github.com/latex3/latex2e/commit/fad42ce8d8caba82059d86b253a6ea5b45f42617
>---------------------------------------------------------------
commit fad42ce8d8caba82059d86b253a6ea5b45f42617
Author: Chris Rowley <car222222 at users.noreply.github.com>
Date: Thu Nov 11 12:13:41 2021 +0700
ltpara: just one fix so far
Maybe some other small tweaks too
>---------------------------------------------------------------
fad42ce8d8caba82059d86b253a6ea5b45f42617
base/ltpara.dtx | 19 +++++++++++--------
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/base/ltpara.dtx b/base/ltpara.dtx
index 51bf9ce3..3a033f23 100644
--- a/base/ltpara.dtx
+++ b/base/ltpara.dtx
@@ -1035,14 +1035,17 @@
% it should get removed before the hook code gets added so we have
% to arrange for this removal.
%
-% TEMP NOTE: maybe a \cs{nobreak} should also be added?
-%
-% [FMi:]
-% sounds wrong to me, why?
-% [CCC:] See email: because the hook may add some material,
-% such as glue that might produce an unintended linebreak.
-% [FMi:]
-%
+% As in other simular cases, it maybe best to add here
+% a \cs{nobreak} in case the hook itself adds glue and thus
+% creates a non-explicit and unwanted potential breakpoont.
+% On the other hand (as has been argued) the code in the hook
+% should perhaps have the responsibility for adding such a
+% guard penalty in this casse.
+% This needs further analysis and decisions (as in emails).
+%
+% In either case, good documentation of these hooks is essential,
+% covering what the hook may or should provide and all
+% such related considerations convernimg the content.
%
% There is not much point in checking if there was really a glue
% item at the end of the horizontal list, instead we simply try to
More information about the latex3-commits
mailing list.