Ken wrote:
> Ken, thank you!
> (You might probably have more experience with XeTeX than me. Is XeTeX
> dying? The last bugfix was in March, months ago, and apart from A.R.
> nobody seems to work on it anyway...)
No, I don't think XeTeX is dying. A look at its git repository shows lots of
comm
Ken wrote:
> Would this solution affect the compilation processes of lualatex
> (which does compile the file in question) or pdflatex?
No. lualatex and pdftex don't use fontconfig.
By the way, I've filed a bug report about this problem:
https://sourceforge.net/p/xetex/bugs/131/
Ke
References:
Ken Brown wrote:
Based on that, you can work around the problem by commenting out the type1
fonts in /usr/share/fontconfig/conf.avail/09-texlive.conf, like this:
$ cat /usr/share/fontconfig/conf.avail/09-texlive.conf
/usr/share/texmf-dist/fonts/opentype
/usr/share/texmf-d
--- Andrey wrote:
> Btw., the web page http://cygwin.com/ml/cygwin/2016-06/msg00197.html is
> displaying the cyrillic capital first letter of the cyrillic alphabet
> wrongly. The file has U+0410 internally, not a stroke D. Don't ask me why
> the web browser and web server are acting this way.
Tha
A more minimal non-working example:
[
\documentclass{article}
\usepackage{fontspec}
\setmainfont{CMU Serif}
%\setmainfont{cmunrm.otf}
\begin{document}
А
\end{document}
]
If you comment the first \setmainfont line and uncomment the second one, the
file compiles. Rerunning /usr/bin/texlive-enabl
Btw., the web page http://cygwin.com/ml/cygwin/2016-06/msg00197.html is
displaying the cyrillic capital first letter of the cyrillic alphabet wrongly.
The file has U+0410 internally, not a stroke D. Don't ask me why the web
browser and web server are acting this way.
--
Problem reports: h
Consider the following LaTeX file q.tex:
[
\documentclass{article}
\usepackage{fontspec}
\setmainfont{CMU Serif}
\usepackage[russian,american]{babel}
\begin{document}
\foreignlanguage{russian}{А}.
\end{document}
]
The letter А is a cyrillic one, U+0410. Running xelatex on it results in the
mess
Ken wrote:
> I obtained the output in the attachment, which looks good. Are you saying
> that the message is bogus and no action is needed?
Yes.
Ok, thanks! It is nice to know than nothing is broken in this respect. But it
would be also nice to get less bogus messages.
--
Problem repo
Ken wrote:
The exit code is the number of font caches that fontconfig thinks it failed to
write.
In fact, I'm pretty sure it actually did successfully write the cache, and the
error message is bogus. You can test this by adding the -v flag to the fc-cache
invocation in zp_fontconfig_cache
... and after one more installation, I get exit code 1. Don't ask me why. Here
is a relevant portion of the log for the following installation:
[
...
2016/06/12 23:23:38 running: C:\cygwin64\bin\dash.exe
"/etc/postinstall/0p_update-info-dir.dash"
Rebuilding info directory
install-info: /usr/shar
...
Some prior post http://cygwin.com/ml/cygwin/2016-05/msg00264.html said this
message might be innocuous, but there the exit code was 1, not 2.
...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/do
After a today update I got a postinstall script error from the setup-x86_64
program:
[
Package: z/Perpetual
zp_fontconfig_cache_1.sh exit code 2
]
Here are some relevant parts of /var/log/setup.log.full:
[
...
2016/06/12 22:30:56 running: C:\cygwin64\bin\dash.exe
"/etc/postinstall/0p_up
12 matches
Mail list logo
