Hello list,
I have an index which uses multilevel indexing (a+b+c) to insert entries
which contain snips of text. LMTX behaves differently from MkIV when
trimming that text, resulting in line wrapping which does not happen
with MKiV. I am not sure when this began -- I just picked up work
On 8/26/20 12:13 PM, jbf wrote:
> [...]
> Maybe, one of these days, someone with experience in both ConTeXt and
> InDesign (since InDesign is used by very many commercial publishers, but
> I am trying to convince one of them of the value of ConTeXt) could offer
> a comparison of the layout
On 8/26/2020 11:01 AM, Marcel Fabian Krüger wrote:
Hi,
I was playing with the variable font support of ConTeXt's font loader
and noticed some issues.
1. While parsing the LocalSubRS and GlobalSubRS Indices, ConTeXt tries
to use 16bit count fields as in CFF(1) instead of 32bit fields
Thank you. Let's see if the Quality Control person is convinced by what
she gets with the suggested measurements.
I usually set things up 'as if' they would be on A4, in this case,
\setuppapersize[ACN][A4] (ACN being the name I give to the 140x216mm
book in question).
And yes, I have looked
Hi,
I was playing with the variable font support of ConTeXt's font loader
and noticed some issues.
1. While parsing the LocalSubRS and GlobalSubRS Indices, ConTeXt tries
to use 16bit count fields as in CFF(1) instead of 32bit fields as in
CFF2, reducing the number of found
> Am 26.08.2020 um 08:44 schrieb jbf :
>
> Severe Covid-19 restrictions locally have left me out on a limb unable to be
> side-byside with people who can set me on track for a few things! Hence the
> bombardment of questions, for which I apologise. But almost there!
>
> The InDesign QC
Severe Covid-19 restrictions locally have left me out on a limb unable
to be side-byside with people who can set me on track for a few things!
Hence the bombardment of questions, for which I apologise. But almost there!
The InDesign QC individual (who accepts my ConTeXt-produced pdfs) wants
