April 2016 - ntg-context - NTG Mailing Lists

unwanted head behavior
by Zhichu Chen 09 Apr '16

09 Apr '16

Dear Hans and Wolfgang, The following code generates a pdf that I cannot understand. 1. Although "placehead" is set to "no," the \part macro still makes an empty line. 2. The first \chapter does not open a new page, but if we switch the first \title and the first \chapter, the result seems to be all right. Is there a simple fix? Thanks in advance. ================================== \setuphead [part,chapter,title,section] [continue=yes,page=yes,number=no] \setuphead[part][placehead=no] \showframe \starttext \input ward\page \part{TITLE}\input ward\par \title{Title} \chapter{Title} \chapter{Title} \title{Title} \chapter{Title} \stoptext ================================== ConTeXt minimal information: zhichu  ~  context -version mtx-context | ConTeXt Process Management 0.63 mtx-context | mtx-context | main context file: /opt/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2016.03.26 13:51 zhichu  ~  luatex -version This is LuaTeX, Version beta-0.90.0 (TeX Live 2016) Execute 'luatex --credits' for credits and version details. There is NO warranty. Redistribution of this software is covered by the terms of the GNU General Public License, version 2 or (at your option) any later version. For more information about these matters, see the file named COPYING and the LuaTeX source. LuaTeX is Copyright 2016 Taco Hoekwater and the LuaTeX Team. zhichu  ~  -- Best regards, ℤhichu ℂhen Shanghai Institute of Applied Physics No. 2019, Jialuo Road Jiading, Shanghai, P.R.China Tel: +86-21-39194888

2 6

breakpoints & dashes in recent betas
by Brian R. Landy 08 Apr '16

08 Apr '16

Hi, I noticed this behavior today (on 2016.03.13 and 2016.04.01): \starttext em-dash: 50---70\par em-dash: discussion---largest\par \setbreakpoints[compound] 3 hyphens: 50---70\par 1 hyphen and 1 en-dash: discussion---largest\par \stoptext After \setbreakpoints -- and --- are no longer interpreted properly. Best regards, Brian

2 1

Re: [NTG-context] Downloading ConTeXt standalone alternatively
by Hans Hagen 07 Apr '16

07 Apr '16

On 4/7/2016 9:04 PM, Jan Tosovsky wrote: > I don't have any computer outside the firewall to tunnel the port using 'nc' > program as described at http://wiki.contextgarden.net/ConTeXt_Standalone - > and I am on Windows so I don't have 'ssh' either. you have putty for ssh on windows ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1

Downloading ConTeXt standalone alternatively
by Jan Tosovsky 07 Apr '16

07 Apr '16

Dear All, I've tried to install ConTeXt at work, but it failed because of blocked 873 port used by rsync. Our admins aren't going to open that port in foreseeable future. I don't have any computer outside the firewall to tunnel the port using 'nc' program as described at http://wiki.contextgarden.net/ConTeXt_Standalone - and I am on Windows so I don't have 'ssh' either. Looking into the first-setup.bat and especially to mtx-update.lua all files seem to be picked up on demand and there isn't any repository for ConTeXt Standalone I could download directly (that syncing is not crucial now). Is there more efficient way than packing my home context folder and copying & unpacking it in my work? Thanks, Jan

1 0

MPinstance
by dr. Hans van der Meer 07 Apr '16

07 Apr '16

I do not understand the info in the ConTeXt wiki on setupMPinstance. The syntax is specified as \setupMPinstance[...][...,...=...,...0 [...] name format metafun mpost etc. I read this as: in the first argument one can specify a name presumably a name specified on \defineMPinstance. in the second argument [format=metafun] specifies the format. But then the example under Usage gives: \setupMPinstance[metafun][...] Why metafun in the first instead of the second argument as implied in the syntax description? I get confused here. Also in the description \startMPextensions and \startMPinitializations are mentioned, but their descriptions are missing from the list given in the page MetaPost in ConTeXt. How are these described and what is the specific purpose of \startMPextensions compared to \startMPinitializations? What is the recommended use for them? Hans van der Meer

4 3

server
by Thomas A. Schmitz 07 Apr '16

07 Apr '16

Hi Mojca, is the server working again? I just wanted to mention that the garden hasn't picked up the latest beta yet, so if it's online again, maybe the syncing process needs to be triggered? All best Thomas

4 6

combining itemize and starttabulate
by Jan Willem Flamma 07 Apr '16

07 Apr '16

Dear members, The following combination of itemize and starttabulate is numbered from 'd. to f.' instead of from 'a. to c.' \starttext \startitemize[a] \starttabulate[|l|p|] \item \NC column1 \NC column2 \NC \NR \item \NC column1 \NC column2 \NC \NR \item \NC column1 \NC column2 \NC \NR \stoptabulate \stopitemize \stoptext I'm unable to figure out why this occurs and also how to get the following desired result: a. tekst tekst b. tekst tekst c. tekst tekst Kind regards, Jan Willem

3 2

On LuaTeX beta-0.95.0
by luigi scarso 07 Apr '16

07 Apr '16

Hi all, we have put beta-0.95.0 on the luatex svn already from while, but the tag is not frozen because: 1) Hans is working on the manual, 2) I keep source/ in sync with TeXLive (kpathsea files etc ), 3) we fix bugs, of course --- the building process not always goes well on every the platforms that we support. The initial plan was to put 0.90.0 for TeXLive, but now we are pretty confident that 0.95.0 is ok, and we have no plan to touch the codebase in source/ (bug fixing apart). (@Karl: I can keep Master/texmf-dist/doc/luatex/base in sync, if it's ok for you) For those that build from source: A. Kakuto keeps the TeXLive repo aligned with the luatex repo, assuring that the windows binaries are ok. It's clear that, having two repos with the same program, is a bit hard to decide which program is the latest one, so when I import from TeXLive in the commit message I specify the revision (e.g. "sync with TL rev. 40299." ); in the luatex repo, trunk and tags/beta-0.95.0 are always aligned, always first trunk and immediately after beta-0.95.0. I found more simple to have both the repos (texlive and luatex) on my machine, but it's my choice. Unfortunately currently the contextgarden server has some problems, and perhaps not all context users have the latest luatex --- not a big problen, we are working on this. The formal announcement of Luatex 0.95.0 very likely will be when the TeXLive is frozen. around 4may. -- luigi

1 0

Re: [NTG-context] Microtypography in ConTeXt
by Hans Hagen 06 Apr '16

06 Apr '16

On 4/6/2016 9:03 PM, Jan Tosovsky wrote: >> the other things ... well, they are up to the macro package > > Indeed, you most likely figured the problem. They are mentioning luatex, while those features require ConTeXt 'preprocessing'. i didn't read that document but i assume it refers to latex which for sure will have some way to set up these feaures; i don't know about plain support in context protrusion and expansion is supported in mkii (pdftex) and mkiv (luatex) .. in mkiv there is a bit more control there is no preprocessing involved (these two features are just part of the par builder) extra kerning and so is done by manipulating node lists (so not an engine feature but a context one) >> i don't think that there are typographical advantages of using pdftex >> over luatex (at least not with context) > > Great, thanks! I am updating article with comparision of various engines, I'll reflect it. > > Jan > > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an entry to the Wiki! > > maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://tex.aanhet.net > archive : http://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > ___________________________________________________________________________________ > -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Re: [NTG-context] Microtypography in ConTeXt
by Hans Hagen 06 Apr '16

06 Apr '16

On 4/5/2016 11:51 PM, Jan Tosovsky wrote: > On 2016-04-05 Hans Hagen wrote: >> On 4/5/2016 10:55 PM, Jan Tosovsky wrote: >>> >>> according to http://texdoc.net/texmf- >>> dist/doc/latex/microtype/microtype.pdf >>> pdfTeX offers fine tuning of: >>> (1) Character protrusion >>> (2) Font expansion >>> (3) Tracking >>> (4) Additional kerning >>> (5) Interword spacing >>> >>> AFAIK ConTeXt covers 1+2+(3?) ... >>> Are there any plans to cover the rest? >> > > My concern was based on this introduction (on title page), especially on that sentence marked with asterisks: > > <cite> > Note that character protrusion requires pdfTeX (version 0.14f or later), LuaTeX, or > XeTeX (at least version 0.9997). Font expansion works with pdfTeX (version 1.20 for > automatic expansion) or LuaTeX. The package will by default enable protrusion and > expansion if they can safely be assumed to work. Disabling ligatures requires pdfTeX > (≥ 1.30) or LuaTeX, > > ************************************************ > while the adjustment of interword spacing > and of kerning only works with pdfTeX (≥ 1.40). > > ************************************************* > > Letterspacing is available with pdfTeX (≥ 1.40) or LuaTeX (≥ 0.62). > </cite> protrusion and expansion are supported at the luatex engine level but configuration is up to the macro packages and they can follow different approaches the other things ... well, they are up to the macro package > >> 3 - i have no clue what tracking is > > As explained in that document this seems to be a synonym for letter spacing, which is IMO supported. yes, context supports that (more than just letters) >> 4 - neither what additional kerning is (unless you mean (usually ugly) >> extra inter character kerning, which is supported) > > Rereading the description in that document there is no advanced processing behind it, so most likely just that ugly kerning, already available in ConTeXt. Just curious why not mentioned as supported on the title page. what title page? anyway, one can kick in extra font features to deal with kerns (although when a font is that bad i'd use another font) >> 5 - it being a rather core tex feature, normal interword spacing is >> supported > > This seems to be a standard glue with plus/minus value. Again, curious why not mentioned as supported on the title page. probably because it is so standard > Are you aware of any typographic feature which is available in pdfTeXt, but not in ConTeXt?-- pdftex is an engine so even if something is available it has to be supported by macros i don't think that there are typographical advantages of using pdftex over luatex (at least not with context) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1