From: "Jaakov Jaakov" <j_k_v@ro.ru>
To: "Cygwin" <cygwin@cygwin.com>
Subject: Re: The font "TeX Gyre Termes" cannot be found.
Date: Sat, 28 May 2016 21:35:00 -0000 [thread overview]
Message-ID: <1464386580.116151.17141.14977@mail.rambler.ru> (raw)
Ken wrote:
> On 5/13/2016 9:26 PM, Jaakov Jaakov wrote:
>
>
> (/usr/share/texmf-dist/tex/latex/fontspec/fontspec.cfg)))kpathsea:make_tex:
> Invalid fontname `TeX Gyre Termes', contains ' '
>
>
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !
> ! fontspec error: "font-not-found"
> ! ! The font "TeX Gyre Termes" cannot be found.
> ! ! See the fontspec documentation for further information.
> ! ! For immediate help type H <return>.
> !...............................................
> l.9
> \setromanfont[Ligatures=TeX]{TeX Gyre Termes}
> ?
> ]
>
> executing fc-cache -f won't help. Any way to repair the system?
>
>
>
> Did you run /usr/bin/texlive-enable-fontconfig? (See the release announcement for TeX Live 2015 or /usr/share/doc/texlive/README.Cygwin.)
> Ken
Dear Ken:
Thank you for the notice. In fact, I had expected xelatex to work "out of the box", but I see now that I was wrong. Probably I should read those announcements regularly. In any case: yes, your script takes several minutes (somewhere between 5 and 10 on my system) to run, but after that xelatex detects TeX Gyre Termes like a charm. Thanks again!
Best regards,
Jaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2016-05-27 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 21:35 Jaakov Jaakov [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-14 1:27 Jaakov Jaakov
2016-05-14 11:17 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1464386580.116151.17141.14977@mail.rambler.ru \
--to=j_k_v@ro.ru \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).