June 2017 - ntg-context - NTG Mailing Lists

Module for Markdown: any volunteer to make a ConTeXt interface?
by Mojca Miklavec 24 Dec '17

24 Dec '17

Hi, There's a really nice module for processing markdown: https://github.com/Witiko/markdown that has been presented during the TUG meeting and is included in TeX Live. It theoretically works for ConTeXt (the output is perfectly usable), but it needs a cleanup of the user interface to turn the options on and off. For example, it would be nice to use something like \setupmarkdown [fencedCode=true] rather than \def\markdownOptionFencedCode{true} Is anyone willing to look into the code and help the author fix the interface? (I can add it to our distribution if needed.) Mojca

11 13

Modern CV like cover letter example
by Jonas Baggett 02 Dec '17

02 Dec '17

Hello everyone, As suggested by Wolfgang Schuster here : https://mailman.ntg.nl/pipermail/ntg-context/2016/087113.html , I have added on the wiki an example of a cover letter that has a similar style to Modern CV. You will find it here : http://wiki.contextgarden.net/Letter_style#Modern_CV_like_cover_letter . I hope it can help. Cheers, Jonas Baggett

4 9

Missing Chapter Numbers
by Thangalin 22 Oct '17

22 Oct '17

\setuphead[chapter][number=yes,] \setuphead[section][number=no,] \setuphead[subsection][placehead=hidden,] \definehead[scenesubsection][subsection] \starttext \dorecurse{5}{ \chapter{Chapter Name} \section{Section Name} \startscenesubsection \input tufte \stopscenesubsection } \stoptext The chapter headings should be enumerated 1 through 5, but some chapter numbers are either hidden or enumerated incorrectly. Using "placehead=no" causes the spacing to change when framing an entire section. Related: https://github.com/contextgarden/context-mirror/blob/b14f992ef5f4e868c9959b… Any ideas on how to work around this issue? Thank you!

2 2

Expandable \doifelse tests
by Henri Menke 08 Sep '17

08 Sep '17

Dear list, Motivated by this question on TeX.SX https://tex.stackexchange.com/questions/370868 I was fiddling around with the \doifelse conditionals. I noticed that most of them are not expandable, which makes it very difficult to concatenate them. Here a simple example \starttext \doifelse{a}{% \doifelse{x}{x}{a}{b}% <- evaluates to "a" but not expandable }{yes}{no} \stoptext This outputs "no" even though "a" is equal to "a". Would it be possible to substitute these conditionals by expandable ones? I would volunteer to help make them expandable. Cheers, Henri

3 2

BUG: Colour spilling in btxrendering
by Henri Menke 09 Aug '17

09 Aug '17

Dear list, I reported this already some time ago but apparently it went unnoticed. https://mailman.ntg.nl/pipermail/ntg-context/2016/086227.html When you place hyperlinks in the bibliography the colour »spills over«, see MWE below. The link is only on the string `Phys. Rev. 140 A1133–A1138 (1965)` but the whole line is coloured. Cheers, Henri --- \startbuffer[references] @article{Kohn1965, title = {Self-Consistent Equations Including Exchange and Correlation Effects}, author = {Kohn, W. and Sham, L. J.}, journal = {Phys. Rev.}, volume = {140}, issue = {4A}, pages = {A1133--A1138}, numpages = {0}, year = {1965}, month = {Nov}, publisher = {American Physical Society}, doi = {10.1103/PhysRev.140.A1133}, url = {https://link.aps.org/doi/10.1103/PhysRev.140.A1133} } \stopbuffer \setupinteraction[state=start] \usebtxdataset[references.buffer] \usebtxdefinitions[aps] \starttext \nocite{Kohn1965} \placelistofpublications \stoptext

5 6

Creating SVG: using MetaFun, exporting proper units, conversion to DXF
by Mojca Miklavec 27 Jul '17

27 Jul '17

Hi, I want to play with CNC and don't yet have any experience with CAD software (nor the licence for the expensive ones) other than perhaps some Blender, so I decided to try to use the super ugly route with metapost -> svg -> dxf -> g-code for the first time. I have a few questions. (1) I love Hans' shortcuts in metafun, but I seem to remember that things like input metafun; or perhaps input mp-tool; used to work, so that I don't have to remember to use mpost -mem=metafun my-drawings.mp when compiling the graphics. Did the method with "input" ever work (or is it supposed to work)? Now I'm getting a bunch of weird errors. I would love to specify everything in the source file and then just call mpost. If that doesn't work, that's fine, I can still add "-mem=metafun", but ... (2) I guess that using "raw metapost" is the only sane way to generate SVG. If I use metapost inside ConTeXt that's probably not going to work, right? (3) Is there any way to convince the SVG output mode to generate something like <svg ... width="100.0mm" height="100.0mm" ... > rather than <svg ... width="283.46456692913387" height="283.46456692913387" ... > because the program I use to convert SVG to DXF has troubles interpreting "points" properly. I read somewhere that they assume 90 points per inch because that's Inkskape's default. (4) Does anyone have a better proposal for conversion into DXF (or G-code)? I'm currently playing with FreeCAD and I've seen some tutorials showing that AutoCAD can open PDF directly, but I don't want to buy AudoCAD just for the sake of converting files. (Not to mention that FreeCAD's SVG importer crashes when reading output from MetaPost unless I manually remove parts of the SVG, but that's an unrelated problem that I'm somehow able to overcome.) Thank you, Mojca

4 9

synctex
by Hans Hagen 19 Jul '17

19 Jul '17

Hi, For those using synctex, an alternative method is: \setupsynctex[state=start] It is tuned for use in a more complex setup where one wants access to source files (with content) and not to e.g. styles in a tex tree. It also works reasonable well with (also included) xml files. Personally I never use synctex but for some projects it came in handy for authors (think of proofing xml files with hundreds of nested inclusions and files in a rather branched tree.) Of course you can expect a similar performance hit as normal synctex but commenting the above line in production results in zero overhead. Using the syntex flag on the command line (--synctex=context will work) can be messy. This currently only works with the windows binaries version on the garden (as we need luatex 1.0.5). 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 -----------------------------------------------------------------

2 4

Re: [NTG-context] next beta
by Jeong Dal 10 Jul '17

10 Jul '17

Dear Hans, I updated ConTeXt beta today and run your sample for long formula. It works nice and it is the feature what many math people want I think. Thank you for your concern. One thing that I’d like say is that a new line in the splitted long formula usually starts with operations in many math books. But, in the ourput of your example, every line ends with ‘+’ sign and begin a new line with a ‘number’. Would you please check it once more? Thank you again for your work, and have a nice weekend. Best regards, Dalyoung

5 6

Problem with columns and footnotes
by Henri Menke 05 Jul '17

05 Jul '17

Dear list, motivated by a question on TeX.SX I wanted to typeset multicolumn text with multicolumn footnotes. However, on the first page the distance between the columns and the footnote area is way too large. Occurs in TL2017 and latest beta. Also, is there something to influence the alignment inside the footnotes more aggressively. There are a couple of bad boxes. Is it possible to turn of balancing for the footnote columns? Cheers, Henri --- \setupnote [footnote] [n=4, rule=no, frame=on, frameoffset=1ex] \setupnotation [footnote] [alternative=hanging, align={raggedright,verytolerant}] \setupcolumns [rule=on] \starttext \startcolumns[n=2] \input Knuth\footnote{FreeBSD tire ses origines de l'UNIX de Berkeley.} \input ward\footnote{This does not seem to be implemented yet.} \input hawking\footnote{Left, right (raggedleft, raggedright).} \input Knuth\footnote{Distance between columns bad hyphenation.} \input ward\footnote{Draw a line between the columns. Default is off.} \input Knuth\footnote{FreeBSD tire ses origines de l'UNIX de Berkeley.} \input ward\footnote{Draw a line between the columns. Default is off.} \input hawking\footnote{Left, right (raggedleft, raggedright).} \input Knuth\footnote{Distance between columns bad hyphenation.} \input ward\footnote{Draw a line between the columns. Default is off.} \input ward\footnote{Draw a line between the columns. Default is off.} \stopcolumns \stoptext

2 3

Adjusting column width dynamically to get rid of orphans and widows
by Thomas Widmann 03 Jul '17

03 Jul '17

Hello, I recently started experimenting with using ConTeXt (mkiv) for dictionary typesetting. It's a much more attractive option than plain TeX or LaTeX because of the support for typesetting on a grid. However, grid typesetting can easily result in a large number of orphans and widows, which really doesn't look good in a dictionary. In an ideal world, I'd want to alter the column width slightly to prevent them (because most dictionaries aren't justified, this wouldn't be very noticeable). Would it be possible to use LuaTeX to achieve this? I.e., could one write some code that gets triggered by orphans and widows and then alters the current column width slightly until the problem disappears? Has somebody already done this? Or have the relevant TeX internals not been Luafied yet? I'd also be interested in other ways to solve this issue – for instance changing the looseness dynamically instead of the column width. Thanks a lot, Thomas -- Thomas Widmann Director Complexli Limited +44 789 444 3009

3 15