-
-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correct handling of lost chars in boxes with LuaTeX #1691
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,6 +6,15 @@ to completeness or accuracy and it contains some references to files that are | |
not part of the distribution. | ||
================================================================================ | ||
|
||
2025-03-05 Joseph Wright <[email protected]> | ||
* ltplain.dtx | ||
Set \tracinglostchars to 4 for recent LuaTeX releases (gh/1687) | ||
Remove \tracinglostchars setting from \tracingall/\loggingall (gh/1687) | ||
|
||
* ltfssbas.dtx | ||
Set \tracinglostchars to 0 for all engines in \showhyphens | ||
|
||
|
||
2025-03-01 Frank Mittelbach <[email protected]> | ||
|
||
* ltexpl.dtx (section{Document-level command names for \pkg{expl3} functions}): | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
This is a generated file for the LaTeX2e validation system. | ||
Don't change this file in any respect. | ||
{vertical mode: \tracingrestores} | ||
{\tracingassigns} | ||
{into \tracingassigns=1} | ||
{select font nullfont} | ||
{changing current font=\OT1/cmr/m/n/10} | ||
{into current font=\nullfont} | ||
~.\a ->\b \relax | ||
~..\b ->\c \relax | ||
~...\c ->\d \relax | ||
~....\d ->\tracingnone \leavevmode \tracingall hi | ||
~.....\tracingnone ->\tracingassigns \z@ \tracingrestores \z@ \tracingonline \z@ \tracingcommands \z@ \showboxdepth \m@ne \showboxbreadth \m@ne \tracingoutput \z@ \errorcontextlines \m@ne \tracingstacklevels \z@ \tracingnesting \z@ \tracingscantokens \z@ \tracingifs \z@ \tracinggroups \z@ \tracingparagraphs \z@ \tracingmacros \z@ \tracingpages \z@ \tracingstats \z@ | ||
{\tracingassigns} | ||
{changing \tracingassigns=1} | ||
{\tracingrestores} | ||
{\tracingonline} | ||
{\tracingcommands} | ||
{horizontal mode: \tracingrestores} | ||
{\tracingassigns} | ||
{into \tracingassigns=1} | ||
{the letter h} | ||
Missing character: There is no h ("68) in font nullfont! | ||
{the letter i} | ||
Missing character: There is no i ("69) in font nullfont! | ||
{\relax} | ||
{\relax} | ||
{\relax} | ||
~.\tracingnone ->\tracingassigns \z@ \tracingrestores \z@ \tracingonline \z@ \tracingcommands \z@ \showboxdepth \m@ne \showboxbreadth \m@ne \tracingoutput \z@ \errorcontextlines \m@ne \tracingstacklevels \z@ \tracingnesting \z@ \tracingscantokens \z@ \tracingifs \z@ \tracinggroups \z@ \tracingparagraphs \z@ \tracingmacros \z@ \tracingpages \z@ \tracingstats \z@ | ||
{\tracingassigns} | ||
{changing \tracingassigns=1} | ||
{\tracingrestores} | ||
{\tracingonline} | ||
{\tracingcommands} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting XeTeX behaves differently than pdfTeX when
\tracinglostchars=2
, but the same with pdfTeX when\tracinglostchars=3
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, doubt it's deliberate - but I'm not sure there is much to be done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it isn't perfect but it isn't that much of a problem either (for us 1-2 extra tlg files due to the differences)