From a4c1d1a1e418ee73c93150594d94bb80c5455ec8 Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Wed, 14 Feb 2024 21:31:38 +0000 Subject: optex (14feb24) git-svn-id: svn://tug.org/texlive/trunk@69861 c570f23f-e606-0410-a88d-b1316a301751 --- Master/texmf-dist/tex/optex/base/fonts-preload.opm | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'Master/texmf-dist/tex/optex/base/fonts-preload.opm') diff --git a/Master/texmf-dist/tex/optex/base/fonts-preload.opm b/Master/texmf-dist/tex/optex/base/fonts-preload.opm index 8562da786c6..82387970e68 100644 --- a/Master/texmf-dist/tex/optex/base/fonts-preload.opm +++ b/Master/texmf-dist/tex/optex/base/fonts-preload.opm @@ -24,14 +24,14 @@ \_endcode %--------------------------------------------------- The format in Lua\TeX/ can download only non-Unicode fonts. Latin Modern EC is -loaded here. These fonts are totally unusable in LuaTeX when languages with out +loaded here. These fonts are totally unusable in \LuaTeX/ when languages with out of ASCII or ISO-8859-1 alphabets are used (for example Czech). We load only a few 8bit fonts here especially for simple testing of the format. But, if the user needs to do more serious work, he/she can -use `\fontfam` macro to load a selected font family of Unicode fonts. +use \^`\fontfam` macro to load a selected font family of Unicode fonts. We have a dilemma: when the Unicode fonts cannot be preloaded in the format then the basic -font set can be loaded by `\everyjob`. But why to load a set of fonts at the +font set can be loaded by \^`\everyjob`. But why to load a set of fonts at the beginning of every job when it is highly likely that the user will load something completely different. Our decision is: there is a basic 8bit font set in the format (for testing purposes only) and the user should load -- cgit v1.2.3