Path: ...!3.eu.feeder.erje.net!feeder.erje.net!fu-berlin.de!uni-berlin.de!not-for-mail From: Jens-Olaf Lindermann Newsgroups: comp.text.tex Subject: Re: aunclfamily and fontspec Date: Wed, 24 Jul 2024 02:33:09 +0200 Organization: Freie Universitaet Berlin Lines: 29 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: news.uni-berlin.de sCD4BzJWzz+3KY9pEvQxWghNyGN9mqlC6evu9/fQBFaAyV8IhF6/R41ruu Cancel-Lock: sha1:vw1YUdtf1zcbtwQ5nzYC2f7mWo0= sha256:dWxsJG+jzcoPIT9UBHhiOcSEBgxy7OEiUvU4CpAjGoI= User-Agent: Mozilla Thunderbird Content-Language: de-DE In-Reply-To: Bytes: 1928 Maybe I should have mentioned, that indeed I have read the documentation of auncial, and having tried to solve the problem alone in many ways like \textuncl{text} or \aunclfamily{}, also having put the [B1]{fontenc} package. This would have given a bunch of MWEs. And yes, the files b1enc.def, b1cmr.fd and TeXB1.enc are in my texlive directory too. But never mind: I have realized the task with the package uncial (not the uncial A I want but alas – I have to edit a Latin text. PS: If you have one day a question about a Latin phrase or problem in old Greek, feel free to ask me – I will certainly not insist that you have to learn Latin first (on my level naturally). > I'm always again surprised how many people nowadays ignore the > documentation of a package. I suggest that you do texdoc auncial and > then read section 2. (Put the fontenc command then before fontspec, > to avoid side-effects on the main text encoding.) > > > -- PGP-Key available 8923 F718 CFC1 9490 6711 0D3B 17A5 0634 6B71 A0DF