On Sun, 14 Apr 2019 18:30:11 +0300
Dmitry Starostin wrote:
> To cite like [1, p. 101]
>
> \cite[righttext={\nbsp p.~101}][Hankins:2014]
>
> works, but has no comma
>
> \cite[righttext={, p.~101}][Hankins:2014]
>
> produces no page
>
> \cite[righttext={,\nbsp p.~101}][Hankins:2014]
>
>
Am 2019-04-14 um 21:34 schrieb Wolfgang Schuster
:
> Henning Hraban Ramm schrieb am 14.04.2019 um 21:11:
>> Hi,
>> on the last page of my index, there are two entries printed over each other,
>> see attached screenshot.
>>
>> How can this happen? Any hints how to avoid it?
>>
>> Sorry, no MWE
Henning Hraban Ramm schrieb am 14.04.2019 um 21:11:
Hi,
on the last page of my index, there are two entries printed over each
other, see attached screenshot.
How can this happen? Any hints how to avoid it?
Sorry, no MWE yet, probably hard to reproduce...
Latest, i.e. yesterday’s beta with
Hi,
on the last page of my index, there are two entries printed over each other,
see attached screenshot.
How can this happen? Any hints how to avoid it?
Sorry, no MWE yet, probably hard to reproduce...
Latest, i.e. yesterday’s beta with LuaTeX; the same with the previous version.
Also the
Dear list,
With latest ConTeXt beta (13-04-2019) I notice that font features seem ignored
in page header rendering. (missing kern between Ps in « Psalme » and different
Th in « Thimothee ».
Anything I am doing wrong ?
Rendering is fine if \headerok is used.
Any help would be appreciated.
To cite like [1, p. 101]
\cite[righttext={\nbsp p.~101}][Hankins:2014]
works, but has no comma
\cite[righttext={, p.~101}][Hankins:2014]
produces no page
\cite[righttext={,\nbsp p.~101}][Hankins:2014]
gives no page at all
\cite[righttext={\nbsp, p.~101}][Hankins:2014]
gives no page at all.
On 4/14/2019 4:31 PM, Peter Rolf wrote:
Thanks for the quick reply. I have to wait for Akira then or install
Linux in a VM and cross compile from the sources. I guess I will wait a
bit more...
It depends what binaries you use. The default garden installation ships
Akira's binaries (32 bit
Am 14.04.2019 um 15:44 schrieb Hans Hagen:
> Hi,
>
> Forwarded ... gmx.* mail accounts bounce here (always have) so i cc to
> the list.
>
>
> Forwarded Message
> Subject: Re: Already new binaries?
> Date: Sun, 14 Apr 2019 15:25:02 +0200
> From: Hans Hagen
> To: Peter Rolf
>
>
On 4/14/2019 2:55 PM, Wolfgang Schuster wrote:
Lutz Haseloff schrieb am 14.04.2019 um 13:57:
Hi Hans, hi all,
my fresh installation of lmtx for win64 on Win 10 seems to have a
problem with the Windows font cambria. I get no readeable text in the
pdf. Other fonts work o.k.
It's a problem
Hi,
Forwarded ... gmx.* mail accounts bounce here (always have) so i cc to
the list.
Forwarded Message
Subject: Re: Already new binaries?
Date: Sun, 14 Apr 2019 15:25:02 +0200
From: Hans Hagen
To: Peter Rolf
On 4/14/2019 2:13 PM, Peter Rolf wrote:
Hi Hans,
does the
Lutz Haseloff schrieb am 14.04.2019 um 13:57:
Hi Hans, hi all,
my fresh installation of lmtx for win64 on Win 10 seems to have a
problem with the Windows font cambria. I get no readeable text in the
pdf. Other fonts work o.k.
It's a problem with fonts which use the ttc format.
\starttext
Hi Hans, hi all,
my fresh installation of lmtx for win64 on Win 10 seems to have a problem with
the Windows font cambria. I get no readeable text in the pdf. Other fonts work
o.k.
Greetings Lutz
test.pdf
Description: Adobe PDF document
test.tuc
Description: Binary data
test.log
12 matches
Mail list logo