Add numerous \DeclareFontSeriesChangeRule entries

[user227621]

LaTeX is currently missing some \DeclareFontSeriesChangeRule entries. Consider the following example:

\documentclass{article}

\begin{document}

\fontfamily{NotoSans-TLF}\selectfont

\fontseries{lsc}\selectfont This is light semicondensed.

\fontseries{b}\selectfont This should be bold semicondensed. %but you get bold regular

\end{document}

Furthermore, it is documented that not all widths are yet supported:

%    Also: while I did set up all nine standard weight values from
%    \texttt{ul} to \texttt{ub} I only bothered to provide entries for
%    \texttt{ec},  \texttt{sc}, \texttt{c} and \texttt{x}, because other levels of
%    compression/expansion are not in any real fonts that I know.
%
%    Could and perhaps should be eventually extended to cover the
%    whole set.

This PR adds rules so that the full range of weights (from ul to ub) and widths (from uc to ux) is covered. The entries are sorted first by weight (from ul to ub) and then by width (from uc to ux). (Perhaps this gives a little structure to the long list of entries.)

Internal housekeeping

Status of pull request

• Ready to merge
• rollback needed?
• test files needed?

Checklist of required changes before merge will be approved

• Test file(s) added
• Version and date string updated in changed source files
• Relevant \changes entries in source included
• Relevant changes.txt updated
• Rollback provided (if necessary)?
• ltnewsX.tex (and/or latexchanges.tex) updated

[FrankMittelbach]

I'm going to look at this once you say it is ready, but not before returning from Prague, ie not before August. Fixing the conflict is probably not sensible right now as it will conflict again during the next weeks.

[FrankMittelbach]

And it should get a (draft) entry in ltnews40, at least a placeholder so that it is not forgotten, thanks.

[user227621]

An incomplete sentence: "but on the other hand it doesn't change and accessing speed and it is fast this way." What was that originally supposed to mean?

[davidcarlisle]

@user227621

I assume the intended meaning is along the lines of this, which might be clearer?

this table is now rather large (1345 entries), but on the other hand, the table doesn't change and accessing rules is fast using a table implemented in this way.

[user227621]

I have rephrased the sentence accordingly.

[user227621]

Another incomplete sentence (a few lines further down, seems I can't comment there): "This file contains the implementation for handling extra axes splitting the series and the values into sub-categories. selection commands." What was that originally supposed to mean?

[user227621]

There are a number of entries of the form \DeclareFontSeriesChangeRule{...}{...}{bx}{b}. I suspect that they exist because for the Computer Modern fonts 'bold' is bx and not b, so that you have a reasonable substitution when bx is applied to another font. Wouldn't it be better if this was handled in a general way, e.g., in \merge@font@series@, instead of handling this case (incompletely) via random \DeclareFontSeriesChangeRule entries?

[user227621]

@FrankMittelbach I've added an entry in ltnews40. Minor open questions in the comments above, otherwise this PR is ready for review.

[cfr42]

Ignore this comment. It's only here because I can't figure out how to watch a PR. (If this gets merged, I can probably remove some code from nfssext-cfr-nnfss.sty.)

[user227621]

@cfr42 There is this button in the right-hand sidebar ;-):

(If you're opening GitHub on a mobile device, it's at the bottom of the page.)

[cfr42]

@cfr42 There is this button in the right-hand sidebar ;-):

Thanks! For some reason, I did not make that terminological connection, despite seeing the button. (I tried various other things, but not that one.)