Options for pairing Concrete Roman with a .ttf font

[Will Robertson]

Hi all

Nothing has changed recently (I am quite sad that I haven’t been able to do new releases on my latex packages for some years now). You just need to load fontenc first with the necessary encodings and be careful about explicitly setting the encoding you want for each font you select. Note that fontspec patches commands like \rmfamily to include the encoding selection and it’s possible that I have neglected to add a command to change/customise this…

It would be great of course if the concrete fonts could see a Unicode release. Perhaps we should have lobbied GUST to make one. Mixing old and new font technologies is a bit awkward :-)

Will
(From phone) 

> On 19 Sep 2021, at 10:12, Bob Tennent <rdtennent at gmail.com> wrote:
> 
> 
> I'm forwarding this to Will Robertson.
> 
>> On Sat, Sep 18, 2021 at 7:29 PM Boris Veytsman <borisv at lk.net> wrote:
>> KB> Date: Fri, 17 Sep 2021 16:36:42 -0600
>> KB> From: Karl Berry <karl at freefriends.org>
>> 
>> >>> It looks like fontspec wants all fonts to be in TU encoding
>> 
>> KB> This seems like a compatibility bug in fontspec. Or somewhere.
>> KB> Since it worked in previous years. Just because all ttf/otf fonts are
>> KB> expected to be in TU, no reason to force that on other fonts. Not that
>> KB> it's anything I'm going to investigate or report :(. -k
>> 
>> Yes.  Looks like fontspec globally sets font encoding - something it
>> did not before.  Here seems to be the culprit in fontspec-xetex.sty:
>> 
>> \RequirePackage[\g_fontspec_encoding_tl]{fontenc}
>> 
>> -- 
>> Good luck
>> 
>> -Boris
>> 
>> There are two major products that come out of Berkeley: LSD and UNIX.
>> We don't believe this to be a coincidence.
>>                 -- Jeremy S. Anderson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/texhax/attachments/20210919/050661e9/attachment.html>