but it includes tex-prefix.xml, which has infodir...
So modify tex-prefix.xml so that it is more generic.
also modify the typography to have individual parameters, in order to
facilitate the automatic detection of wrong option vs parameter
tags.
This resulted in the currency script returning a new version, while also
being inconsistent (the title says 1.2.0, but we're offering 1.1.0 for
download)
it is in instructions that are not guarded by role="nodump"...
Note that now that vim gets several updates a day, I am not sure
we use the right way to update runtime files!
TTF-and-OTF-fonts - make CJK fonts a section2 so that it is
slightly bigger than the other items. Everything after it, either
re languages or specific fonts, is logically part of CJK fonts.
No change in indexing (i.e. CJK fonts itself is not indexed).
I reworked the paragraph about Unicode coverage, but left the
original in place while working on it, and then forgot to remove
it, causing an almost duplicate paragraph.
Explain that some recent fonts have TTF files with hinting, and
OTF files without. Expand the comment in TTF-and-OTF-fonts to
explain why OTF should be preferred, and link to previous page
for why hinting can be undesirable or unusable.
Rework second fc-match example:
'fcmatch -a TYPE | less' is useless: -a functions similarly to
fc-list, any following parameter is ignored. So the example listed
all installed font-style-weight combinations for all three TYPEs.
Replace by plain fc-match TYPE.
Remove TYPE specification from introductory paragraph, it is only
used for the replacement command here. Use the same markup for the
command and in the explanations, so that a capital TYPE in the
explanations is replaced by a smaller slanted TYPE.
The command after this shows a fuller variant with the type, lang
and weight being specified.
Typos, rewordings, put the conf file edits in <screen> blocks to
stand out, add details re GNOME Tweaks and Thunderbird.
I think I made a slight change to one of the wordings, but I now
forget which.
Outstanding item: 'fc-match -a Type | less' wording made me unsure
of exactly which variants of Sans Sasn-serif would be accepted.
Trying to test this (I have far too many fonts on current system)
appeared to act as if hte Type was being ignored. Need to think
about this.
