-
-
Notifications
You must be signed in to change notification settings - Fork 275
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'develop' into ltmarks-enhance
# Conflicts: # base/changes.txt # base/doc/ltnews39.tex # base/ltmarks.dtx
- Loading branch information
Showing
206 changed files
with
23,802 additions
and
7,460 deletions.
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
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 |
---|---|---|
|
@@ -75,10 +75,6 @@ regard to this policy. | |
|
||
## Code contributions | ||
|
||
If you want to discuss a possible contribution before (or instead of) | ||
making a pull request, drop a line to | ||
[the team](mailto:[email protected]). | ||
|
||
The stability of LaTeX is very important and this means that change in | ||
the kernel is necessarily very conservative. It also means that a lot of | ||
discussion happens before any changes are made. If you do decide to post | ||
|
@@ -87,10 +83,24 @@ cannot always integrate them into the kernel. | |
|
||
If you are submitting a pull request, notice that | ||
|
||
- The first line of commit messages should be a short summary (up to about | ||
50 chars); leave a blank line then give more detail if required | ||
- We use Travis-CI for (light) testing so add `[ci skip]` to documentation-only | ||
commit messages | ||
- The first line of commit messages should be a short summary (up to about 50 | ||
chars); leave a blank line then give more detail if required | ||
- We use GitHub Actions for testing; you can run the test suite locally using | ||
`l3build` | ||
- We favour a single linear history so will rebase accepted pull requests | ||
- Where a commit fixes or closes an issue, please include this information | ||
in the first line of the commit message [`(fixes #X)` or similar] | ||
- Where a commit fixes or closes an issue, please include this information in | ||
the first line of the commit message [`(fixes #X)` or similar] | ||
- There is a checklist in the [pull request | ||
template](.github/pull_request_template.md) for the various bit of admin that | ||
are needed: the key points are | ||
- Almost all changes should be listed in the relevant `changes.txt` file | ||
- The date in the `\ProvidesPackage` (or similar) line should be updated | ||
whenever the file changes | ||
- The version in the `\ProvidesPackage` (or similar) should be incremented | ||
whenever the code changes | ||
- The LaTeX sources include `\changes` that are typeset | ||
- Almost always, a code change should be accompanied by a matching test file | ||
- More significant changes will need an entry in _LaTeX News_ | ||
- Pull requests that are intended for the next major release of LaTeX should be | ||
made against `develop`; if you feel the change is urgent and requires a patch | ||
level, the pull request should be made against `main` |
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 |
---|---|---|
|
@@ -6,20 +6,68 @@ to completeness or accuracy and it contains some references to files that are | |
not part of the distribution. | ||
================================================================================ | ||
|
||
2024-01-27 Frank Mittelbach <[email protected]> | ||
|
||
* lttextcomp.dtx (section{Font family sub-encodings setup}): | ||
Adjusted/corrected TS1 sub-encoding declarations for various families. | ||
Some families have changed their names (due to licensing issues), | ||
some got new glyphs added, and some were simply incorrectly categorized | ||
(gh/1257) | ||
|
||
* lttextcomp.dtx (section{The \texttt{checkencodingsubset.tex} file}): | ||
Added check file for encoding subset | ||
|
||
2024-01-03 Phelype Oleinik <[email protected]> | ||
* lthooks.dtx: | ||
Correct expansion of \@@_print_args:nn argument (gh/1221). | ||
|
||
2023-12-30 Frank Mittelbach <[email protected]> | ||
* doc.dtx (subsection{Macros surrounding the `definition parts'}): | ||
Use \@noligs from the LaTeX kernel, so that the upquote | ||
package can add its patch (gh/1230) | ||
|
||
2023-12-26 Yukai Chou <[email protected]> | ||
* ltproperties.dtx: | ||
Correct typo (gh/1223) | ||
* doc.dtx, ltfntcmd.dtx, lthooks.dtx | ||
Correct similar typos of missing backslashes | ||
* ltfilehook.dtx | ||
Change flag markup in macro env | ||
|
||
2023-12-07 Ulrike Fischer <[email protected]> | ||
* ltproperties.dtx: use \protected@write, (gh1200) | ||
|
||
2023-12-02 Frank Mittelbach <[email protected]> | ||
* doc.dtx (subsection{API creation}): | ||
Provide \ProvideDocElement for use cases where files are processed | ||
individually as well as together, e.g., the LaTeX kernel documentation. | ||
|
||
2023-12-01 Joseph Wright <[email protected]> | ||
* ltcmd.dtx (subsection{Declaring commands and environments}): | ||
Optimize creation of simple document commands (gh/1189) | ||
* usrguide.tex (subsection{Performance}): | ||
Document efficiency of ltcmd definitions | ||
|
||
2023-11-16 Frank Mittelbach <[email protected]> | ||
* ltpara.dtx (subsection{Providing hooks for paragraphs}): | ||
Correct error message: hook left horizontal not vertical mode (gh/1182) | ||
|
||
2023-11-15 Joseph Wright <[email protected]> | ||
* ltfiles.dtx (subsection{Listing files}): | ||
Extend \listfiles to optionally include file sizes and hashes | ||
* usrguide.tex | ||
Re-introduce \listfiles (extended) description | ||
|
||
2023-11-14 Frank Mittelbach <[email protected]> | ||
|
||
* ltmarks.dtx: | ||
Some internal commands renamed and extended. | ||
|
||
Generalized the support for extracting marks to cover cases like multicols. | ||
|
||
Some internal commands renamed and extended. | ||
Renamed \__mark_update_structure:nn to \__mark_update_structure_from_material:nn | ||
|
||
Added \__mark_get_marks_for_reinsertion:nNN | ||
|
||
Added \ShowMarksAt for debugging (might not stay this way) | ||
|
||
|
||
2023-11-09 Yukai Chou <[email protected]> | ||
* clsguide-historic.tex, usrguide.tex: | ||
Replace quotation with quote envs for zero para indent | ||
|
@@ -44,6 +92,14 @@ not part of the distribution. | |
All changes above are only part of the development branch for the next release. | ||
================================================================================ | ||
|
||
######################### | ||
# 2023-11-01 PL1 Release | ||
######################### | ||
|
||
2024-01-13 Jonathan P. Spratte <[email protected]> | ||
* ltkeys.dtx: | ||
Trim spaces off key names taken from the raw-lists (gh1238) | ||
|
||
######################### | ||
# 2023-11-01 Release | ||
######################### | ||
|
@@ -169,7 +225,7 @@ All changes above are only part of the development branch for the next release. | |
* ltfiles.dtx | ||
Allow for pipes in \input, etc. | ||
|
||
2023-06-16 Phelype Oleinik <Joseph.Wright@latex-project.org> | ||
2023-06-16 Phelype Oleinik <phelype.oleinik@latex-project.org> | ||
|
||
* lthooks.dtx, ltcmdhooks.dtx | ||
Correct some rollback labels and dates. | ||
|
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
Oops, something went wrong.