Re: [NTG-context] CMYK Color profile
Am 30.05.19 um 23:34 schrieb Benjamin Koppe:
> Hello everyone,
>
> I'm about creating a DIN Lang Folder brochure with ConTEXt. I got
> everything set up the way I'd like it to. Now that I'm done with the
> work, I've been told the output pdf should have a CMYK Color profile
> embedded for the on demand printing service to be able to deal with the
> file...
>
> I am unsure what steps I have to take to make my output pdf compliant
> with CMYK. I don't even know how I could verify it does indeed have
> CMYK. Evince doesn't seem to show that info...
>
> So if anybdy of you could give me some hints, that's be wonderful.
>
> Cheers
> De Benny
Hi Benny,
if you can read German you might find some hints in my articles about
creating din lang folders
https://www.hasecke.eu/post/werbemittel-mit-context-gestalten/
On colors read the second part:
https://www.hasecke.eu/post/wie-wir-bei-hostsharing-mit-context-arbeiten/
Search the mailing list for color profile questions because I had to ask
often to make my things work. ;-)
The wiki contains some hints, too.
What you can do is to create a mode like this:
\startmode[fogra39]
\doiffileelse{CoatedFOGRA39.icc}{}{\farbprofilnichtgefunden}
% This will be printed in log if context does not find the profile for
% some reason
\definecolor [hs-logoblau] [c=1.000, m=0.735, y=0.279, k=0.160]
\definecolor [hs-dunkelblau] [c=0.844, m=0.544, y=0.070, k=0.000]
\definecolor [hs-hellblau] [c=0.468, m=0.220, y=0.086, k=0.002]
\definecolor [hs-orange] [c=0.127, m=0.832, y=1.000, k=0.042]
\setupcolors[cmyk=yes,rgb=no,]
\setupbackend[
format=PDF/X-3:2003,
intent={Coated FOGRA39 (ISO 12647-2:2004)},
]
\stopmode
If you call context with --mode=fogra39 you will get these color
definitions and the defined pdf format with the right profile (intent).
If you download additional icc profiles (eg. the fogra one is missing in
the context distribution) put them here:
context/tex/texmf-local/colors/icc
In this folder they won't be overwritten by an update.
There are some limitations in ConTeXt concerning colors as embedded
images are not converted, so RGB images are converted only by the print
shop during printing, which can lead to strange results. I think the
only way to control the output is to convert all images to CMYK by hand.
By doing this you can modify them to get the best results.
I hope that helps
juh
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Extend figure to margin, or extend figure from margin to text
Dear Wolfgang,
I've made an MWE. It seems that once I changed the layout, the output would be
a little strange:
* The edgefigure (default=outer) on the odd pages can't be moved to the margin.
Those on the even pages are fine as long as I use
"leftmargindistance=-\innercombitotal"
* the marginfigure (default={outermargin, hanging}) on the odd pages are fine,
but those on the even pages have a weird offset.
* by the way, the offset of the marginfigure on the even pages are the same as
the edgefigure on the even pages if I set "leftmargindistance=-\outercombitotal"
I managed to make the marginfigure work by adding (just in this case)
leftmargindistance=\dimexpr\outercombitotal-\innercombitotal\relax,
rightmargindistance=0pt
But I could never make edgefigure work. Its different behavior on odd and even
pages really bothers me.
Although the output is acceptable now, I'm still concerned that the settings
are not logical (to a human being). I'm afraid that one day it won't work out
like that.
Here's the MWE:
===
\showframe
\setuppagenumbering
[alternative=doublesided]
\definepapersize
[911]
[width=9in,
height=11in]
\setuppapersize
[911]
\setuplayout
[backspace=1in%
,leftmargin=.5in%
,leftmargindistance=0.25in%
,width=5.5in%
,rightmargindistance=0.25in%
,rightmargin=2in%
]
\definefloat
[edgefigure]
[figure]
\setupfloat
[edgefigure]
[rightmargindistance=-\outercombitotal
,leftmargindistance=-\innercombitotal
,default={outer,low,high,none}]
\definefloat
[marginfigure]
[figure]
\setupfloat
[marginfigure]
[default={outermargin,hanging,none}]
\startbuffer[fitframe]
\framed[width=\rightmarginwidth,height=.6\rightmarginwidth,framecolor=darkgreen]{\tt
width=rightmarginwidth}
\stopbuffer
\startbuffer[wideframe]
\framed[width=2\rightmarginwidth,height=.6\rightmarginwidth,framecolor=darkred]{\tt
width=2*rightmarginwidth}
\stopbuffer
\starttext
\chapter{edge}
\dorecurse{10}{
\startplaceedgefigure
\getbuffer[fitframe]
\stopplaceedgefigure
\input knuth
}
\chapter{margin}
\dorecurse{10}{
\startplacemarginfigure
\getbuffer[fitframe]
\stopplacemarginfigure
\input knuth
}
\dorecurse{10}{
\startplacemarginfigure
\getbuffer[wideframe]
\stopplacemarginfigure
\input knuth
}
\stoptext
===
--
From:Wolfgang Schuster
Sent At:2019 May 29 (Wed.) 17:55
To:陈之初 ; mailing list for ConTeXt users
Subject:Re: [NTG-context] Extend figure to margin, or extend figure from margin
to text
Zhichu schrieb am Mi., 29. Mai 2019, 10:30:
Hi everyone,
I am writing a book, in which all figures are placed in the margin. But some
graphics are too big to fit in the margin. I was wondering whether there's an
elegant way to use some room of the text body?
Take a look into the Details manual: http://www.pragma-ade.nl/show-man-15.htm
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Typesetting Markdown -- Part 2
>
> sense to check all these mappings onto context, for instance I think
> that pandoc uses \section and such while in fact it should use
> \startsectionlevel[title={}] ... \stopsectionlevel so that one can embed
> documents in other documents.
>
https://github.com/jgm/pandoc/issues/5539
Feel free to add comments to the issue.
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] CMYK Color profile
Hello everyone, I'm about creating a DIN Lang Folder brochure with ConTEXt. I got everything set up the way I'd like it to. Now that I'm done with the work, I've been told the output pdf should have a CMYK Color profile embedded for the on demand printing service to be able to deal with the file... I am unsure what steps I have to take to make my output pdf compliant with CMYK. I don't even know how I could verify it does indeed have CMYK. Evince doesn't seem to show that info... So if anybdy of you could give me some hints, that's be wonderful. Cheers De Benny ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Typesetting Markdown -- Part 2
https://github.com/Witiko/markdown is forked from https://github.com/jgm/lunamark. Github user "jgm" is John MacFarlane, the creator of pandoc, and pandoc itself is hosted on github under "jgm" as well: https://github.com/jgm/pandoc. So, it seems a good bet that https://github.com/Witiko/markdown supports pandoc markdown. Regards, David. Excerpts from Saša Janiška's message of May 30, 2019 7:48 pm: Hans Hagen writes: just test it and tell me what needs to be fixed / added I'm looking at https://github.com/Witiko/markdown and wondering which flavour of Markdown this package does support? By reading https://github.com/Witiko/markdown/issues/25 it could mean it could be Pandoc's one, but not sure? ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Wiki update
> On 30 May 2019, at 12:07, Taco Hoekwater wrote: > […] > > For example, > > section > > outputs a table with the formal calling convention(s) for the \section > command. Multiple tables actually, as it also outputs the alternative calls > with different arguments, and it outputs the definition of the internal > \*section* command, of which \section is an instance. (The parents of > instances are printed in a slanted font). This is absolutely magic and extremely useful! Thank you, Wolfgang, Taco and Hans! I wonder whether the magic behind the scenes would allow some day to say \syntax[section] within a ConTeXT document… :-) Best regards, and again many many thanks: OK ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Wiki update
On 5/30/2019 12:07 PM, Taco Hoekwater wrote: I have not auto-replaced any of the handcrafted command page syntax tables in the existing wiki pages, because quite often the current syntax table has manual additions explaining various options. In the formal version these are obviously not present, and I did not want to remove any of that extra information. maybe at some point we can have extra xml files that explain some of that (after all there is a 'xml path' to such an entry ... something to discuss at a meeting Anyway, the nice thing about this new wiki plugin is that if you want to create a page for a specific command that is not in existence right now, it is a simple matter of going to the expected url, and creating a page with just a Syntax heading and a tag. For example (created a minute ago): url: https://wiki.contextgarden.net/Command/setupdescription content: == Syntax == setupdescription Thanks go to Wolfgang for all the hard work! And you too! Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Lua error using module pgfplots and shader=interp
On Thu, May 30, 2019 at 11:00 AM Hans Hagen wrote: > On 5/29/2019 10:36 PM, Luca Donetti wrote: > > Dear all, > > > > The following example using module pgfplots does not work in an updated > > context standalone nor with the texlive 2019 version. > fixed in next beta > Thank you. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Typesetting Markdown -- Part 2
On 5/30/2019 12:18 PM, Saša Janiška wrote:
Hans Hagen writes:
just test it and tell me what needs to be fixed / added
I'm looking at https://github.com/Witiko/markdown and wondering which
flavour of Markdown this package does support?
By reading https://github.com/Witiko/markdown/issues/25 it could mean it
could be Pandoc's one, but not sure?
I don't know as I never use these coding methods. But it might make
sense to check all these mappings onto context, for instance I think
that pandoc uses \section and such while in fact it should use
\startsectionlevel[title={}] ... \stopsectionlevel so that one can embed
documents in other documents.
(An option is to look into mappings onto xml.)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Wiki update
Hello Taco,
From now on, when you are editing the wiki (especially the /Command/CMD pages), you can use
CMD to output the formal table of arguments
for that CMD (omit the backslash)
For example,
section
outputs a table with the formal calling convention(s) for the \section command.
Multiple tables actually, as it also outputs the alternative calls with
different arguments, and it outputs the definition of the internal \*section*
command, of which \section is an instance. (The parents of instances are
printed in a slanted font).
this is really great!
This gives idea what syntax "sugars" (alternatives) are possible and what args
may be used! This lacked for years!
===
I have not auto-replaced any of the handcrafted command page syntax tables in
the existing wiki pages, because quite often the current syntax table has
manual additions explaining various options. In the formal version these are
obviously not present, and I did not want to remove any of that extra
information.
Anyway, the nice thing about this new wiki plugin is that if you want to create a
page for a specific command that is not in existence right now, it is a simple matter
of going to the expected url, and creating a page with just a Syntax heading and a
tag.
For example (created a minute ago):
url:
https://wiki.contextgarden.net/Command/setupdescription
content:
== Syntax ==
setupdescription
My suggestions is to add an auto-generated-command-syntax wiki-page-section,
too.
I find it very useful - just now one can see what are possibilities!
I added the following code into wiki page - just for testing purposes, anyone
can alter the page:
https://wiki.contextgarden.net/Command/section#Syntax
== [[Help:Reference|Syntax (generated automatically from ConTeXt definition)]]
==
section
And just now I can see that \section accepts syntax of the forms:
\section[MyRef]{My title}
\section[MyRef]{4.0}{My title}
\section[reference=MyRef,ownnumber=4.0,title={My title}]
So better for us if we find a way to COMBINE command descriptions already existing on wiki
WITH those generated via command injection.
Thanks again for the great job.
Best regards,
Lukas
Thanks go to Wolfgang for all the hard work!
Best wishes,
Taco
--
Ing. Lukáš Procházka | mailto:l...@pontex.cz
Pontex s. r. o. | mailto:pon...@pontex.cz | http://www.pontex.cz | IDDS:
nrpt3sn | IČO: 40763439
Bezová 1658
147 14 Praha 4
Mob.: +420 702 033 396
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Wiki update
Am 30.05.19 um 12:07 schrieb Taco Hoekwater: > url: > https://wiki.contextgarden.net/Command/setupdescription > > content: > == Syntax == > > setupdescription Brilliant! Thanks a lot! juh ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Typesetting Markdown -- Part 2
Hans Hagen writes: > just test it and tell me what needs to be fixed / added I'm looking at https://github.com/Witiko/markdown and wondering which flavour of Markdown this package does support? By reading https://github.com/Witiko/markdown/issues/25 it could mean it could be Pandoc's one, but not sure? Sincerely, Gour -- As the embodied soul continuously passes, in this body, from boyhood to youth to old age, the soul similarly passes into another body at death. A sober person is not bewildered by such a change. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] Wiki update
Hi all, Not sure how many of you remember this, but at the Kalenberg meeting in 2016 there was this talk: === Setups Wolfgang Schuster (and Hans Hagen) The user interface is described in xml files but the actual descriptions lagged behind development. Wolfgang spent a considerable amount of time to describe all commands in detail and we updated the descriptive format in the process. The rendering was partly redone, as was the help system and scripts that use this information. === Since then, nothing much had been done with those updated xml files, which is a big shame considering the enormous amount of work that went into the process. But recently we have been discussing the wiki and (especially) the sorry state of the reference portion of that. At some point, I realised that we could rather easily combine the new xml interface files with a small wiki extension, such that the wiki has easy access to the latest and greatest command list. === From now on, when you are editing the wiki (especially the /Command/CMD pages), you can use CMD to output the formal table of arguments for that CMD (omit the backslash) For example, section outputs a table with the formal calling convention(s) for the \section command. Multiple tables actually, as it also outputs the alternative calls with different arguments, and it outputs the definition of the internal \*section* command, of which \section is an instance. (The parents of instances are printed in a slanted font). There are 2035 normal commands and 373 instances in the database, essentially covering all the style- and document-level commands in ConTeXt. I’ve decided not to add the low-level system commands because (apart from perhaps a few special cases) these do not belong in general user documentation. === I have not auto-replaced any of the handcrafted command page syntax tables in the existing wiki pages, because quite often the current syntax table has manual additions explaining various options. In the formal version these are obviously not present, and I did not want to remove any of that extra information. Anyway, the nice thing about this new wiki plugin is that if you want to create a page for a specific command that is not in existence right now, it is a simple matter of going to the expected url, and creating a page with just a Syntax heading and a tag. For example (created a minute ago): url: https://wiki.contextgarden.net/Command/setupdescription content: == Syntax == setupdescription Thanks go to Wolfgang for all the hard work! Best wishes, Taco ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Typesetting Markdown -- Part 2
On 5/29/2019 11:54 PM, Thangalin wrote: Hi all, The second part describes how to create a PDF file from a Markdown file using pandoc and ConTeXt: https://dave.autonoma.ca/blog/2019/05/29/typesetting-markdown-part-2/ If anyone has suggestions to improve the ConTeXt-related portions, please pass them along. I've considered using ConTeXt's Markdown module, but I'm not sure how much of Pandoc's enhanced Markdown it supports. just test it and tell me what needs to be fixed / added Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Lua error using module pgfplots and shader=interp
On 5/29/2019 10:36 PM, Luca Donetti wrote: Dear all, The following example using module pgfplots does not work in an updated context standalone nor with the texlive 2019 version. fixed in next beta - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
