>> Does compilation of this small plain TeX test document
>>
>> ```
>> \font\lh = latt1095
>> \lh ^^c1
>> \bye
>> ```
>>
>> with `xetex` actually work?
>
> Since this short file didn't run,
Well, this explains what's going on.
> I will run the test file. But since you suggested this problem,
Forwarding to list
-- Forwarded message -
From: Carl Sorensen
Date: Fri, Jan 26, 2024 at 6:34 PM
Subject: Re: Error with texi2pdf on MacOS
To: Werner LEMBERG
On Fri, Jan 26, 2024 at 3:28 PM Werner LEMBERG wrote:
>
> >> Please also check whether the two TFM files from the L
Forwarding to list
-- Forwarded message -
From: Carl Sorensen
Date: Fri, Jan 26, 2024 at 6:44 PM
Subject: Re: Error with texi2pdf on MacOS
To: Werner LEMBERG
On Fri, Jan 26, 2024 at 3:28 PM Werner LEMBERG wrote:
>
> >> Please also check whether the two TFM files from the LH
Here is the current countdown report.
The next countdown will begin on 2024-01-29
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
No patches in Push at this time.
Countdown:
!2245 NR: Add index entries for
>> Please also check whether the two TFM files from the LH fonts are
>> actually valid (for example, by testing with `tftopl `).
>
> I tested this and got no errors. [...]
OK, thanks. AFAICS, the `xetex` binary finds file `latt1095.tfm` but
`xdvipdfmx` (which convert's `xetex`'s output to PDF
> So: Wouldn't it be more consistent to turn those context properties
> that (to the user) create "one-time only effects" into persistent
> ones (so forceClef = ##t _would_ actually create a clef at each
> timestep forward) and instead create dedicated user interfaces using
> music functions, like
