October 2016 - ntg-context - NTG Mailing Lists

Parsing ConTeXt errors
by Nicola 13 Oct '16

13 Oct '16

Hello, I'm trying to parse ConTeXt errors. TeX and Lua errors seem easy to parse (search for 'tex error' and 'lua error', respectively), but I have a couple of problems with MetaPost messages. First, when there are MetaPost errors, context/mtxrun exits with a zero exit code. Is that intentional? Second, as far as I see, there is no way to locate the error in the source from the log. I can only retrieve the file causing the error (by searching for an 'open source' line - very useful, btw), but no line number. Am I missing something? I think it would be very useful to have at least an approximate indication of the position of a MetaPost error. Nicola

3 6

Changes in hyphenations with 2016-10-12 beta
by josephcanedo＠gmail.com 13 Oct '16

13 Oct '16

Dear list, After ugrading to latest beta (to test typesetting with it for now), I noticed that some words that used to be hyphenated with previous versions are no longer hyphenated in the output, especially when the word break used to happen at a ligature (for example ‘st’ or ‘ct’). I had a quick look to the différences in files in tex/texmf-context/tex/context/base directory and I see some changes to font handling. Is this expected ? Or is there any mechanism to get the old behaviour ? I’ll try to build a MWE to show this if that’s required. Thanks a lot, Best regards Joseph Canedo

3 4

ConTeXt Garden Articles Site
by Taco Hoekwater 13 Oct '16

13 Oct '16

Hi all, At the recent 10th ConTeXt meeting, we also had the 6th members meeting of the ConTeXt Group. The ConTeXt Group uses the annual members meeting to keep track of the activities that are deployed by and for our members as well as ConTeXt users in general. One item on the agenda this year was the Electronic publication of the CG Journal. The assembly agreed that in the future we would publish the table of contents of the CG Journal as quickly as possible, and the PDFs of actual articles therein six months after appearance of the printed version of an issue. The table of contents of the 2016 journal issue is still undecided at this moment, we have to wait and see how many articles we will actually receive before the deadline of November 15. The PDFs of the 2015 journal issue will become available in March 2017, because it was released on paper during the 10th meeting. But the PDFs of previous issues’ articles can now be downloaded from: http://articles.contextgarden.net/journal While setting up this new site, I purposely used /journal for the CG Journal, so that there is room for other articles from other sources besides the ConTeXt Group. If you have written an article --or know of an article by someone else— that you believe would be interesting to add to the site, please send me an email message with the details and (link to) the PDF. But note that we will only consider articles that can technically and legally be hosted on articles.contextgarden.net itself (no external links). Best wishes, Taco -- The item(s) mentioned in this message are only part of the activities undertaken by the ConTeXt Group. The ConTeXt Group is a non-profit organisation set up for and by ConTeXt users, with its purpose being promoting and facilitating the use of the ConTeXt typesetting system developed by Pragma ADE. We can always use more volunteers and members, so please think about joining in! See http://group.contextgarden.net/ for more information.

2 1

Ideas for improving documentation of ConTeXt
by Jonas Baggett 13 Oct '16

13 Oct '16

Hello everyone, I am new to new to ConTeXt and I was thinking about how to improve documentation to help users and then make ConTeXt more appealing. Because, if there is one weak point in my eyes with ConTeXt, it is the lack of documentation, which is too bad because ConTeXt seems to be really great. And google search is also a little tricky, since context is a common name. On the other hand, most of the help I found was on the wiki, the mailing list, TeX Stack Exchange and some pdf documentations. Sometimes, I also faced the problem about the documentation being outdated and when I am trying to find the solution on the internet, I may have a hard time finding solutions that aren't outdated too. The worse is maybe when a command option isn't working anymore with not even a warning. The basic idea I have is a database of ConTeXt documents, where everyone can add his own documents. We have also to make it easy to find there insightful examples in ConTeXt that will help someone to achieve what he is trying to do. Then users, especially beginners, will less likely be stuck at one point and looking for hours for a solution and less help will be asked on the mailing list too. Here are the basic concepts about the database : - When someone adds a document, he can specify the type of the document like e.g. report, letter, CV, book, etc. Subcategories could be a good idea too, e.g. letters can have a subcategory called cover letters. Some extra tags could also be useful, like e.g.: math, luatex, tables, positioning, etc when there is some use of the preceding, maybe not necessarily essential when the use is only basic. - If some extra fonts or modules are needed to be installed in order to make the example fully work, this could also be specified. - Search could be done by specifying one or more categories and tags. It will also be possible to search all the occurrences in the database of a command with optionally a command parameter. - It will be like a wiki so that everyone could improve the existing examples. - It can be also useful to allow comments, because it is possible that an example is close to what someone is trying to do, in which case he will look on the comments hoping that there was already someone who asked there the question and got answered. - In order to mitigate the problem with deprecation stuffs after some language changes, we could have all the commands and their options listed somewhere in the database, then when a command or command parameter is getting deprecated, it will be possible to mark it as so and provide some hints on how to fix it. After that, all the examples that use the deprecated stuffs will get a warning and hints will be showed about how to fix them. And since that examples are editable by anyone, there won't be hopefully very much of outdated documents. Here some are possible scenarios about searching in the database : - Someone is writing a letter and is trying to move one element (e.g. date, his address, receiver address) in another location without any success so far. Then he will go to this database, choose letter as category and positioning as extra tag and launch the search. Maybe he will get about 20 results, then chances are that some of the found examples will be doing something close enough to what he's trying to do, so that he could analyse the source and understand what he needs to do in his case. - Someone is looking about how to set the background color of a framed box. Then he will search occurrences of the uses of the \framed command which have color in their arguments. Then by looking at the found examples, he will find out that the color is set with the backgroundcolor argument and that the background argument need to be set to "color" too. What do you think about the idea ? I believe this could be a good complement to the existing ressources. Have a nice sunday, Jonas

12 30

Deleted modules (fixme, games, lilypond, sgf)
by Mojca Miklavec 12 Oct '16

12 Oct '16

Hi, The following modules disappeared from Taco's server: - t-fixme - t-games - t-lilypond - t-sgf Can you please confirm that all four modules should be removed from CTAN & TeX Live as well as from the ConTeXt distribution? Thank you, Mojca

3 2

position of linenumbering
by Thomas A. Schmitz 12 Oct '16

12 Oct '16

Hi all, consider this example: \setuppapersize [A6] \starttext \startlinenumbering [location=text,distance=0.5cm] \dorecurse{2}{\input tufte} \stoplinenumbering dummy \stoptext on the second page, the position of the linenumbering changes and does not follow the "distance" setting. Can this be fixed? And if yes, how? Thanks and best wishes Thomas

5 8

context xml manual
by Meer, Hans van der 12 Oct '16

12 Oct '16

Did a small disaster happen in typesetting the XML manual? I find "MISSING SETUP"s all over the place. See the sample page. This is ConTeXt ver: 2016.10.08 00:11 MKIV beta Hans van der Meer

2 2

new beta
by Hans Hagen 12 Oct '16

12 Oct '16

Hi, I uploaded a new beta. There is a new command \setextrafontkerns which is described in the fonts-mkiv manual section 8.12. probably not that useful but kind of fun. 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 -----------------------------------------------------------------

1 0

How to use "fontsampler example" with Persian font
by Mingranina Gingranina 12 Oct '16

12 Oct '16

Dear All, Hello, I am trying to use "fontsampler example" with Persian fonts (please see below or "http://wiki.luatex.org/index.php/Fontsampler" for fontsampler codes). The problem is that Persian words apears as a string of separate glyphs, for example I get "ح‌س‌ن" instead of "حسن". Do I have to use commands like the followings inside \directlua or tex.tprint to fix the problem? If yes, how can I do that? \installlanguage [fa][default=pe,date=\longjalalidatefmt] \mainlanguage[fa] \definefontfeature[tlig][tlig=yes] \definefontfeature[slanted][slant=.2] \definefontfeature[dlang][language=dflt] \definefontfeature[flang][language=far] Thanks Mingranina fontsampler.tex ========================================================================================================= \input luaotfload.sty \overfullrule 0pt \font\mono = {file:lmmono8-regular.otf} at 6pt \parindent 0pt \def \samplestring {Sphinx of black quartz, judge my vow. 1234567890 äÄöÖüÜ ß !"§\$\%\&()=?} \directlua{ dofile("fontsampler.lua") fontsampler(arg[2]) } \bye ========================================================================================================= End Of fontsampler.tex fontsampler.lua ========================================================================================================= function dirtree(dir) assert(dir and dir ~= "", "directory parameter is missing or empty") if string.sub(dir, -1) == "/" then dir=string.sub(dir, 1, -2) end local function yieldtree(dir) for entry in lfs.dir(dir) do if not entry:match("^%.") then entry=dir.."/"..entry if not lfs.isdir(entry) then coroutine.yield(entry,lfs.attributes(entry)) end if lfs.isdir(entry) then yieldtree(entry) end end end end return coroutine.wrap(function() yieldtree(dir) end) end function fontsampler( dir ) for entry in dirtree(dir) do if entry:match(".otf","-4") then tex.tprint({[[\mono ]]},{-2,entry},{[[ (]]},{-2,fontloader.info(entry).fontname},{[[)\par\penalty 10000\font\sample={file:]]},{-2,entry},{[[} at 12pt\sample\samplestring\par\penalty 10000\vrule width \hsize height 0.25pt depth 0pt\par]]}) end end end ========================================================================================================= End Of fontsampler.lua

3 8

Paranormal bug in TL 2016
by Henri Menke 12 Oct '16

12 Oct '16

Dear list, at some point my document started throwing an error ! error: (nodes): trying to delete an attribute reference of a non attribute node I managed to extract a minimal example which shows the error (below). However, the error only occurs when the filename of the document contains a hyphen! When I save the document as `test-error.tex' the error comes up, when I save it as `testerror.tex' it typesets smoothly. Unfortunately, I currently cannot update to latest beta because I have an important document where I cannot afford any regressions. Cheers, Henri --- \version[temporary] \definebreakpoints[hyphen] \definebreakpoint [hyphen] [-] [nleft=3,nright=3,type=6,range=yes] \setbreakpoints[hyphen] \setuppagenumbering [alternative=doublesided] \starttext \startstandardmakeup \stopstandardmakeup {\em Detailtypografie} by Friedrich Frossman \stoptext

7 15