- ntg-context - Mailing Lists

Where to put icc color profiles
by Jan U. Hasecke 04 Feb '19

04 Feb '19

Hi all, I downloaded some color profiles and stored them in: /context/tex/texmf-context/colors/icc/profiles But they get overwritten, when I update context. Can I put color profiles in the working folder of my project. And how do I access them with setupbackend? TIA juh -- Software-Dokumentation mit Sphinx http://www.amazon.de/dp/1497448689/ Paperback: 224 Seiten

2 2

Re: [NTG-context] About the macro path intersectionpoint path with Metapost
by Jeong Dal 04 Feb '19

04 Feb '19

Dear Fabrice, Metapost is great for drawiang figures but it is not easy for me to use it. > b:= fullcircle scaled 2cm shifted (0,-3cm); > pair A, B ; > A:= p intersectionpoint r ; > B:= p intersectionpoint r ; > path u ; > u:= A--B--cycle ; A and B are the same point. One of “r” should be changed to “q” or “b”. Then you can have a line. I also made similar errors many times too. Btw, is there any reason to add “—cycle”? Enjoy the drawing. Best regards, Dalyoung

1 0

problem with \sym?
by Alan Bowen 03 Feb '19

03 Feb '19

Processing a table of contents with the latest standalone (ConTeXt ver: 2019.01.28 16:58 MKIV beta fmt: 2019.2.3) fails with the following message: luatex warning > hpack filter: error: ...eXt/tex/texmf-context/tex/context/base/mkiv/typo-dua.lua:422: attempt to compare number with nil tex error > tex error on line 18 in file c_Contents.tex: ? \strc_itemgroups_make_symbol_box ...mbol \fi \fi } \let \strc_itemgroups_extr... \strc_itemgroups_insert_item ...s_make_symbol_box \strc_itemgroups_make_dest... \strc_itemgroups_start_item ...groups_insert_item \dostoptagged \ifcondition... <to be read again> \dotagsetitem \sym ..._symbol \startitemgroupitem \dotagsetitem \s!symbol l.18 \sym{0.} Prolegomena to the Study of Hellenistic Astronomy This worked with the previous standalone. Alan

2 1

Title from setupinteraction used in header
by Jan U. Hasecke 03 Feb '19

03 Feb '19

Hi all, it is quite easy to have chapters in headers and footers as shows this example. \setuppagenumbering[location=] \setupheadertexts [text] [chapter] [] [] [chapter] \setupinteraction [title={foo}, subtitle={bar}, author={Peter}, keyword={context}] \starttext \startchapter[title={chapter title},] \input lorem \stopchapter \startchapter[title={another chapter title},] \input lorem \stopchapter \stoptext How can I insert title, subtitle and author from setupinteraction into headertexts? Background: authors shall define title, subtitle etc in the product file with setupinteraction (or a better method if available). In the environment file I want to insert theses informations into headers and footers. TIA juh

2 2

Color profile not found
by Jan U. Hasecke 03 Feb '19

03 Feb '19

I get an error when I use. \setupbackend[ format=PDF/X-3:2003, intent={Coated FOGRA39 (ISO 12647-2:2004)}, ] backend > profiles > profile specification 'Coated FOGRA39 (ISO 12647-2:2004)' loaded from '/home/juh/context/tex/texmf-context/colors/icc/context/colorprofiles.xml' backend > profiles > error, couldn't locate profile 'CoatedFOGRA39.icc' backend > profiles > invalid output intent 'Coated FOGRA39 (ISO 12647-2:2004)' I copied the file CoatedFOGRA39.icc to context/tex/texmf-context/colors/icc/profiles My setup worked before. Using the intent "ISO Coated v2 300\letterpercent\space (ECI)" I get no error. TIA juh

1 1

Restarting with different engine fails
by Henri Menke 01 Feb '19

01 Feb '19

Dear list, ConTeXt allows to select the engine in the preamble with a “magic comment”. The preamble is parsed and the engine restarted with new options. The following MWE fails in the latest beta % engine=luajittex \starttext Fail \stoptext with the error message texmf-context/scripts/context/lua/mtx-context.lua:427: attempt to call a nil value (global 'restart') If I uncomment the restart function and its helpers around line 110 it works. Please fix. Cheers, Henri

2 1

getting ConTeXt results back to Lua (for typesetting solutions at end of document)
by Sanjoy Mahajan 01 Feb '19

01 Feb '19

Dear List, I'm trying to have problem solutions automatically collected, each with its corresponding problem number, e.g. 2.3, and then typeset at the end of a document. Thus, I imagine something like \startproblem{A problem title} % Problem 1.1 A question \startsolution An answer \stopsolution \stopproblem And then the solution(s) would appear at the end (with the "1.1" remembered from when the problem was typeset): Solution to Problem 1.1. An answer It seems that buffers are the way to do this. But I cannot quite get the automatic numbering to work. The delayed evaluation and information passing between lua and ConTeXt has me confused and tangled in a knot. Below is a minimal almost-working example. The issue is in the line {\ctxlua{userdata.addTempToBuffer('#1', [==[\getnumber[problem]]==])}} which ends up putting the verbatim string "\getnumber[problem]" into the temp buffer, rather than the typeset result, which would be something like 1.1 or 1.2. I've read the cld-mkiv.pdf manual, but I must be missing a simple solution to getting ConTeXt to send back the result of \getnumber[problem]. I've also tried the analogous context.getnumber({"problem"}), though without success. Does anyone see what I am missing? Many thanks! -Sanjoy \defineenumeration[problem] [title=yes, text=Problem, way=bychapter, prefix=chapter] \defineenumeration[solution][problem] \setupenumeration [solution][text={Solution to problem}, number=no] \def\test#1{[#1]} % appendbuffer modified from Sietse Brouwer's on mailing list (Jan 15, 2013) \startluacode userdata = userdata or { } function userdata.addTempToBuffer(buffername, problem) buffers.append( buffername, '\\startsolution{' .. problem .. '}\n' .. buffers.getcontent('APPENDTEMP') .. '\n\\stopsolution\n\n' ) end \stopluacode \def\startappendbuffer[#1]% {\def\stopappendbuffer% {\ctxlua{userdata.addTempToBuffer('#1', [==[\getnumber[problem]]==])}} \dostartbuffer[APPENDTEMP][startappendbuffer][stopappendbuffer]} \starttext \chapter{One} \startproblem{Test} Test problem \startappendbuffer[soln] Solution \stopappendbuffer \stopproblem \startproblem{Test} Test problem \startappendbuffer[soln] Solution \stopappendbuffer \stopproblem \typebuffer[soln] \stoptext

8 10

Headings vs. enumerations
by Clyde Johnston 01 Feb '19

01 Feb '19

I have a document that contains a numbered enumeration that spans 107 pages - it's a legal document where \items are clauses. I would like to put level one of the enumeration in a table of contents. I have read the available documentation but I am not clear whether I should make level one headers, whether I can utilise the \starthead in \startitemize or whether I can create a list from the level one headings to create the table of contents. How is best to tackle this problem? Thanks, Clyde MWE #1: \starttext \placecontent[alternative=c] \startitemize[n,repeat] \starthead{A heading}\stophead \startitemize[n,repeat,2*broad] \starthead{A sub-heading}\stophead \startitemize[n,repeat,3*broad] \item \input knuth \stopitemize \stopitemize \stoptext MWE #2: \starttext \placecontent[alternative=c] \chapter{A heading} \startitemize[n,repeat,2*broad] \starthead{A sub-heading}\stophead \startitemize[n,repeat,3*broad] \item \input knuth \stopitemize \stopitemize \stoptext

2 2

New logo proposal
by Paul Schalck 31 Jan '19

31 Jan '19

Dear ConTeXt users and developers, I want to submit a new ConTeXt logo to you (link to GitLab project): https://gitlab.com/schickele/new-context-logo I made this logo in February 2018. At the time, I was planning to do some video tutorials on ConTeXt (still work in progress), and I wanted a nice looking visual clue for the thumbnails. Recently, I made a few minor tweaks and thought it would be the right time to put it out there. The logo comes in two different layouts (hexagonal and horizontal), and each layout comes in two color variations (multicolored and blue). The hexagonal layout is borrowed from the unofficial ConTeXt logo that has been around for some time. I like the idea of a clean geometrical form, and the hexagon reminds me of chemistry formulas -- one of the many application fields of ConTeXt. The seven colors have mainly an esthetic purpose. They also denote the flexibility of ConTeXt. I've added a monochromatic blue version because shiny, saturated colors are not suitable for every case, and blue is strongly associated with ConTeXt to me. Blue is also a reminder of Mark IV and LuaTeX. The letters are set in Din17 EF, which I've licensed. I like its simple shapes combined with a round and soft touch. It avoids consciously the very connoted Computer Modern and can be seen as a modernized and also Europeanized interpretation of the TeX tradition. This logo is just a humble proposal. Perhaps it is of some use to someone. It could also make someone else want to create and share his or her logo -- that would be great. I'm using ConTeXt since 2006/07 for almost everything that contains text: letters, presentations, invitations, résumés, certificates, manuals, reports, flyers, university papers, book typesetting, exercise sheets, song sheets, and I'm still amazed by how powerful, flexible and reliable it is. Thanks to the whole community -- and particularly to the Dutch wizard -- for making this possible! Greetings from Leimen, Germany Paul Schalck

10 11

New logo proposal
by Paul Schalck 30 Jan '19

30 Jan '19

Hello again, as many critics go towards "I don't see any coherence" or "to me it's just a random bunch of colored letters" or "it's hard to read the word CONTEXT", some afterthoughts in that regard (difficulty, randomness). Personally, I like visual material that catches my attention, but does not give all away at first glance. For example a good poster or book cover. It invites me to spend time on it. And I don't have the feeling that the designer thinks I'm stupid. ConTeXt is quite sophisticated, its logo can also be a little bit more complicated than your average sportswear brand. Any color choice is arbitrary to some extend. The colors I've used cover the entire hue range and are at equal distance apart (common in multicolored designs). This denotes to me not only the flexibility, and the fun of using it, but also the comprehensiveness of ConTeXt. Not only can you use ConTeXt in very different situations, you can use it in every situation (that requires typesetting). My 2c! Greetings, Paul

2 1