I get this error when I try to compile a pdf with:
\setupbackend[
format=PDF/X-3:2003,
intent={ISO Coated v2 300\letterpercent\space (ECI)}
]
In log:
backend > profiles > setting format to 'PDF/X-3:2003'
backend > profiles > forcing pdf version 1.4.0, compression
level 3,
On 30.09.18 17:16, Henning Hraban Ramm wrote:
>
> Hi juh,
>
> you can define colors in several color models at once; CMYK makes most sense
> for professional printing.
>
> e.g. \definecolor[CompanyBlue][r=0,g=0,b=1,c=1,m=1,y=0,k=0]
>
> and see
On Mon, Oct 1, 2018 at 11:43 AM Ulrike Fischer wrote:
>
> I just got from Claudio Beccari (which seem to have complained to
> Luigi)
>
hm, not a complain, a simple "bug report". I always try to answer directly
to Claudio when/if I can,
but in this case, if I have understood correctly, you are
On 10/1/2018 9:23 AM, Jan U. Hasecke wrote:
On 30.09.18 17:16, Henning Hraban Ramm wrote:
Hi juh,
you can define colors in several color models at once; CMYK makes most sense
for professional printing.
e.g. \definecolor[CompanyBlue][r=0,g=0,b=1,c=1,m=1,y=0,k=0]
and see
On 9/30/2018 10:08 PM, Ulrike Fischer wrote:
The font Coelacanth (on CTAN) has glyphs in the private area.
Between 2/2017 (luaotfload in texlive 2017) and now the storing and
accessing of this glyphs has changed.
In the lua of the font of 2017 I find e.g.
[62860]={
Am 2018-10-01 um 09:23 schrieb Jan U. Hasecke :
> On 30.09.18 17:16, Henning Hraban Ramm wrote:
>
>>
>> Hi juh,
>>
>> you can define colors in several color models at once; CMYK makes most sense
>> for professional printing.
>>
>> e.g. \definecolor[CompanyBlue][r=0,g=0,b=1,c=1,m=1,y=0,k=0]
Am Mon, 1 Oct 2018 10:20:07 +0200 schrieb Hans Hagen:
> anyway, the problem, with these private areas is that they are also used
> by the loader (and context) so in order to avoid clashes we move all
> private chars in the font to a dedicated private range
This basically means that for every
On 01.10.18 10:11, Henning Hraban Ramm wrote:
> If you can ensure all RGB colors are tagged with the same profiles then it
> should work, as long as you only care about *same* colors and not
> (CMYK-defined) *specific* colors...
>
> Do your SVGs declare their RGB color space?
They start with:
Hi,
Thank you Aditya for the link. I knew that with natural tables, but I hoped
it could be done with xtables too.
Fabrice
Le lun. 1 oct. 2018 à 05:50, Aditya Mahajan a écrit :
> On Mon, 1 Oct 2018, Jeong Dal wrote:
>
> > What do you mean “does not typeset correctly as expected”?
>
> As I said,
Dear Aditya,
Thank you for the reply.
>
> As I said, I fixed the post.
I see why I have no problem.
Thank you for sharing your nice samples.
Best regards,
Dalyoung___
If your question is of interest to others as
On 10/1/2018 11:42 AM, Ulrike Fischer wrote:
Can you tell me when this change happend? Perhaps I can build an
older fontloader as a fall back.
no, probably a while ago when some other clash in private area use was
solved .. i'm not going to mess with the code now as 0xE000-0xEFFF is
used
Am Mon, 1 Oct 2018 19:29:40 +0200 schrieb Hans Hagen:
>> \DeclareTextGlyphY{LinBiolinum_K}{uniE18C}{57740}
>A funny definition ... is that access by name or number?
By number, it uses \char at the end to get the glyph.
> Anyway, for generic (so not for context) I can keep these glyphs in the
On Mon, 1 Oct 2018, Fabrice Couvreur wrote:
Hi,
Thank you Aditya for the link. I knew that with natural tables, but I hoped
it could be done with xtables too.
Almost the same code works with xtables as well (in your example, I don't
know the relationship between the columns)
\starttext
Hi Hans, hi all,
I think, that recent context has a problem with scaling included pdf files.
My minimal file:
\startMPpage
draw externalfigure "cow.pdf" ;
\stopMPpage
The resulting pdf is, as the original, 97x70.6 mm, all ok.
If I try to scale to the original size, i get arithmetic overflow
On Mon, Oct 1, 2018 at 7:56 PM Ulrike Fischer wrote:
>
> For what do you reserve the space in the PUA?
>
http://www.pragma-ade.nl/general/manuals/fonts-mkiv.pdf
page 32 of the document :
As we already mentioned in a previous chapter, in ConTeXt we use Unicode
internally.
This also means that
On Tue, Oct 2, 2018 at 7:03 AM Lutz Haseloff
wrote:
> Hi Hans, hi all,
>
> I think, that recent context has a problem with scaling included pdf files.
> My minimal file:
>
> \startMPpage
> draw externalfigure "cow.pdf" ;
> \stopMPpage
>
> The resulting pdf is, as the original, 97x70.6 mm, all
I looked at your example. I ran your example, and on my installation, it has
the same problem as I described. I have included a PDF file of my original
sample file, and also the PDF generated from your example. What version of
ConTeXt are you using?
On my installation of context, columns are
On Mon, 1 Oct 2018, David Walther wrote:
I looked at your example. I ran your example, and on my installation, it
has
the same problem as I described. I have included a PDF file of my original
sample file, and also the PDF generated from your example. What version
of
ConTeXt are you
On 10/1/2018 7:55 PM, Ulrike Fischer wrote:
Am Mon, 1 Oct 2018 19:29:40 +0200 schrieb Hans Hagen:
\DeclareTextGlyphY{LinBiolinum_K}{uniE18C}{57740}
A funny definition ... is that access by name or number?
By number, it uses \char at the end to get the glyph.
Anyway, for generic (so not
19 matches
Mail list logo
