From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/104584 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Thangalin Newsgroups: gmane.comp.tex.context Subject: Re: =?utf-8?q?Typesetting_Markdown_=E2=80=93_Part_5=3A?= =?utf-8?q?_Interpolation?= Date: Tue, 9 Jul 2019 11:06:19 -0700 Message-ID: References: Reply-To: mailing list for ConTeXt users Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9076903554166918550==" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="168695"; mail-complaints-to="usenet@blaine.gmane.org" To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Tue Jul 09 20:07:30 2019 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hkuWW-000he3-Pr for gctc-ntg-context-518@m.gmane.org; Tue, 09 Jul 2019 20:07:28 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id A71841525C6; Tue, 9 Jul 2019 20:06:41 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KHzR6_rJcIXj; Tue, 9 Jul 2019 20:06:36 +0200 (CEST) Original-Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 6C6DA1525BA; Tue, 9 Jul 2019 20:06:36 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 373A71525BA for ; Tue, 9 Jul 2019 20:06:35 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iDF2Lx519ufp for ; Tue, 9 Jul 2019 20:06:33 +0200 (CEST) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.167.194; helo=mail-oi1-f194.google.com; envelope-from=thangalin@gmail.com; receiver= Original-Received: from mail-oi1-f194.google.com (mail-oi1-f194.google.com [209.85.167.194]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id 41995152364 for ; Tue, 9 Jul 2019 20:06:33 +0200 (CEST) Original-Received: by mail-oi1-f194.google.com with SMTP id s184so16047384oie.9 for ; Tue, 09 Jul 2019 11:06:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=+S/Oaj7QCAe3RXcI08NkYOzjVePv9C3W3LLb4Pw6+YQ=; b=XVc1ZbeIF/9aSnLbOWtH+gFN8vVxSScl7kaK7YRAQiDojaKzAfRb1RKgB7JRWtG5d7 Zf2/tiqarly58ohDr0UnpJYO/9S0OjlSEx8A0K949uZylP4apPzfunDItxM0xhfo/MbM 7sfSoxffm1JfJNoeWtBE+sZiAaeYj6Rdw7QflxJGkld3wfrGGX8YzLDExx9OMR0z5ob4 MMpdUStN30rf++pCMHkhYJA7OheR780ZFMADplBCUxeuYPTw48K2CxS/7025dQ2oDS16 jMWydH3zFr4QoJxsotq3tnJvdMJSn5ZV7b9P6PfwJCPvYhtOncaK0V7wp8jx0SnK9z/q DHWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=+S/Oaj7QCAe3RXcI08NkYOzjVePv9C3W3LLb4Pw6+YQ=; b=pnC+S8eUEUhi0wlFsJWw7YpvkV4hPeH19+YzKbJw9ml3vgKjEsqtkOZa/R8zOi0e3y 2ly/Qep2scg0eMncmRnWQQwV5sLPgiPjzoYDN9xUasqpoHrN1IAqZknGR4ZBm8Pq1QGf s5GEeFL8YiGGL336YhihNqQ9VVRa/YQFWG611jAyJciYjQP0fnDm5QtV2de7nC+gr/Kg YWUap+HMUhqwbhd9Mk+lKS3v847QncIIUJxzkdbMcawTQgyd38v4D2Wpx5HbWdUn7s/X 6u4gjuCxGk5oReO62EoXMo21QVGd9jAHeUPlOmXWQWG4vWGINlEmcw6wlYIBGSR2tA9m WIZg== X-Gm-Message-State: APjAAAX9HM6jfFEjWsDad+zuR3gqZ+2HkNSphHbtxtPpHU+Ey5a2mHIJ ROzEhv5GsIokExBt7awU3SXeBnX4BSAUa/wxFcIEN990 X-Google-Smtp-Source: APXvYqynpZ+Oe1XxLdDiWZdpV36Je5kkJ5rWhpmZmG9cAHcU7bniwJpq4o2j/PBhFFxIpx1O/vV7MNVP6eddxcuSpF4= X-Received: by 2002:aca:ad0f:: with SMTP id w15mr834712oie.58.1562695590822; Tue, 09 Jul 2019 11:06:30 -0700 (PDT) In-Reply-To: X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.26 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: "ntg-context" Xref: news.gmane.org gmane.comp.tex.context:104584 Archived-At: --===============9076903554166918550== Content-Type: multipart/alternative; boundary="0000000000009545bb058d436b41" --0000000000009545bb058d436b41 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable That's another intriguing approach, Andr=C3=A9s, thank you. The approach faces some hurdles. First, the template file (main.tex) is written in ConTeXt, so it never sees the YAML variables, nor can it be used to interpret pandoc's conditional expressions. Second, moving the \completecontent macro out of main.tex and into Markdown (e.g., 01.md, being the first chapter) so that the conditional expression can be evaluated using pandoc mixes content with presentation logic. Modes are a good approach in this case because the "context" command can take a "mode" command-line argument. This provides presentation controls that neither the YAML nor the Markdown need consider. Adding presentation logic to the ConTeXt template (i.e., introducing \startmode and \startnotmode into main.tex) is acceptable because ConTeXt is wholly responsible for the appearance of the final document. See: https://wiki.contextgarden.net/Modes This then allows development of command-line arguments from shell scripts to control how the document is presented when built, which is a little bit more flexible than maintaining YAML variables. Also, ideally, the YAML variables would be used for controlling only content, not presentation logic. Thanks again, Andr=C3=A9s. On Mon, Jul 8, 2019 at 11:27 AM Andres Conrado wrote: > You can do it on the template... you can use a yaml variable to determine > if the toc should be printed or not. Like so: > > yaml file: > --- > toc: true > ... > > template file: > %%%%%%% > $if(toc)$ > \completecontent > $endif$ > %%%%%%% > > > Andr=C3=A9s Conrado Montoya > http://chiquitico.org > > > El lun., 8 jul. 2019 a las 2:52, escribi=C3= =B3: > >> Send ntg-context mailing list submissions to >> ntg-context@ntg.nl >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://mailman.ntg.nl/mailman/listinfo/ntg-context >> or, via email, send a message with subject or body 'help' to >> ntg-context-request@ntg.nl >> >> You can reach the person managing the list at >> ntg-context-owner@ntg.nl >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of ntg-context digest..." >> >> >> Today's Topics: >> >> 1. Re: Typesetting Markdown =E2=80=93 Part 5: Interpolation >> (Aditya Mahajan) >> 2. Re: Typesetting Markdown =E2=80=93 Part 5: Interpolation (Thangal= in) >> 3. Re: Typesetting Markdown =E2=80=93 Part 5: Interpolation >> (Aditya Mahajan) >> 4. request for \definefontfamily and \definefallbackfamily >> (Pablo Rodriguez) >> 5. Re: crappy names in the fontloader (Hans Hagen) >> 6. problems with images, layers and crop marks (Henning Hraban Ramm) >> 7. Re: problems with images, layers and crop marks (Hans Hagen) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sun, 7 Jul 2019 10:17:31 -0400 (EDT) >> From: Aditya Mahajan >> To: mailing list for ConTeXt users >> Subject: Re: [NTG-context] Typesetting Markdown =E2=80=93 Part 5: >> Interpolation >> Message-ID: >> Content-Type: text/plain; charset=3DUS-ASCII; format=3Dflowed >> >> On Sat, 6 Jul 2019, Thangalin wrote: >> >> > Hello again! >> > >> > This part of the series describes how to reference *interpolated* >> strings >> > inside Markdown documents. >> > https://dave.autonoma.ca/blog/2019/07/06/typesetting-markdown-part-5/ >> > >> > There's a section at the end about eliminating the table of contents >> from a >> > reusable document template. I would have preferred using setups, rathe= r >> > than redefining the \completecontent macro, but didn't see an obvious >> way >> > to do so. >> >> Why not simply omit \compltecontent from the pandoc template? >> >> Aditya >> >> >> >> ------------------------------ >> >> Message: 2 >> Date: Sun, 7 Jul 2019 11:58:12 -0700 >> From: Thangalin >> To: mailing list for ConTeXt users >> Subject: Re: [NTG-context] Typesetting Markdown =E2=80=93 Part 5: >> Interpolation >> Message-ID: >> > g@mail.gmail.com> >> Content-Type: text/plain; charset=3D"utf-8" >> >> Thank you Aditya. >> >> The main.tex file is meant to be reusable for different document styles. >> By >> removing \completecontent altogether from the main template, it would >> preclude a different document from reusing the main.tex template with a >> table of contents. I'd like the template to be "reusable"; making >> modifications to "main.tex" --- or creating a copy --- would subvert tha= t >> goal. >> >> On Sun, Jul 7, 2019 at 7:17 AM Aditya Mahajan wrote: >> >> > On Sat, 6 Jul 2019, Thangalin wrote: >> > >> > > Hello again! >> > > >> > > This part of the series describes how to reference *interpolated* >> strings >> > > inside Markdown documents. >> > > https://dave.autonoma.ca/blog/2019/07/06/typesetting-markdown-part-5= / >> > > >> > > There's a section at the end about eliminating the table of contents >> > from a >> > > reusable document template. I would have preferred using setups, >> rather >> > > than redefining the \completecontent macro, but didn't see an obviou= s >> way >> > > to do so. >> > >> > Why not simply omit \compltecontent from the pandoc template? >> > >> > >> > >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> http://mailman.ntg.nl/pipermail/ntg-context/attachments/20190707/25ca621= 5/attachment-0001.html >> > >> >> ------------------------------ >> >> Message: 3 >> Date: Sun, 7 Jul 2019 15:17:50 -0400 (EDT) >> From: Aditya Mahajan >> To: mailing list for ConTeXt users >> Subject: Re: [NTG-context] Typesetting Markdown =E2=80=93 Part 5: >> Interpolation >> Message-ID: >> Content-Type: text/plain; charset=3DUS-ASCII; format=3Dflowed >> >> >> On Sun, 7 Jul 2019, Thangalin wrote: >> >> > Thank you Aditya. >> > >> > The main.tex file is meant to be reusable for different document >> styles. By >> > removing \completecontent altogether from the main template, it would >> > preclude a different document from reusing the main.tex template with = a >> > table of contents. I'd like the template to be "reusable"; making >> > modifications to "main.tex" --- or creating a copy --- would subvert >> that >> > goal. >> >> Pandoc allows that. For example, see line 140 of the default context >> template: >> >> https://github.com/jgm/pandoc-templates/blob/master/default.context >> >> I don't remember the exact command line parameters for pandoc that set >> the toc flag to true. >> >> An equivalent method will be to control this using a ConTeXt mode. >> Redefining \completecontent to \empty seems too drastic. >> >> Aditya >> >> >> >> ------------------------------ >> >> Message: 4 >> Date: Sun, 7 Jul 2019 21:29:49 +0200 >> From: Pablo Rodriguez >> To: mailing list for ConTeXt users >> Subject: [NTG-context] request for \definefontfamily and >> \definefallbackfamily >> Message-ID: <857b6e26-0b65-c2a4-6569-e664f0111d1e@gmx.es> >> Content-Type: text/plain; charset=3Dutf-8 >> >> Hi Wolfgang, >> >> I have two requests to be implemented in \definefontfamily. >> >> The first one is that is able to load fonts not defined as entries in >> the font database. >> >> Here you have a minimal sample: >> >> \definefont[Test][file:texgyrepagella-regular.otf at 10pt] >> \definefont[TestOne][file:texgyrepagella-regular-500.otf at 10pt] >> >> \definefontfamily [mainface] [rm] [Pagella] >> [tf=3D{file:texgyrepagella-regular.otf}, >> bf=3D{file:texgyrepagella-regular-500.otf}] >> >> \setupbodyfont[mainface] >> \starttext >> normal\\ >> \bf bold not working\\ >> >> \Test this works >> \TestOne this works >> \stoptext >> >> The second one would be to allow method=3Duppercase to >> \definefallbackfamily, so it could be used to fake small caps (such as >> in https://mailman.ntg.nl/pipermail/ntg-context/2018/092878.html. >> >> Many thanks for your help, >> >> Pablo >> -- >> http://www.ousia.tk >> >> >> ------------------------------ >> >> Message: 5 >> Date: Sun, 7 Jul 2019 23:42:11 +0200 >> From: Hans Hagen >> To: ntg-context@ntg.nl >> Subject: Re: [NTG-context] crappy names in the fontloader >> Message-ID: >> Content-Type: text/plain; charset=3Dutf-8; format=3Dflowed >> >> On 7/6/2019 6:36 PM, Marcel Fabian Kr=C3=BCger wrote: >> > Hi everyone, >> > >> > under default settings, the fontloaders discards all glyph names which >> > are considered "crappy", meaning matching the "p_crappyname" pattern i= n >> > "font-oup.lua". For some names this makes a lot of sense. For example >> > the name "uni0303" is considered "crappy" and it really provides no >> > useful information. Then there are other names like "t_uni0303" which >> > are still considered "crappy" while they actually aren't completely >> > useless. So I think there would be some value in preserving them. Of >> > course, you can always enable "otf.keepnames" if you need names like >> > this. >> > >> > But I actually want to talk about another class of names: Look at >> > "Udotbelow". This is IMHO a perfectly normal and useful name, but the >> > fontloader still considers it "crappy" because it starts with a "U" >> > followed by a letter which could be a hexadecimal number. >> > >> > I think this is a bit over-agressive. Maybe the "p_crappyname" pattern >> > could be changed to only look for "u" if followed by >> > "p_done", marking the end of a component? >> i'll look into it (irr in generic mode (latex etc) one can disable that >> 'feature' which i thought happened) >> >> 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 >> ----------------------------------------------------------------- >> >> >> ------------------------------ >> >> Message: 6 >> Date: Sun, 07 Jul 2019 23:06:56 +0000 >> From: Henning Hraban Ramm >> To: ntg-context@ntg.nl >> Subject: [NTG-context] problems with images, layers and crop marks >> Message-ID: >> <20190707230656.Horde.IVjTQk9tNtFVGH0IBsHNXDk@webmail.fiee.net> >> Content-Type: text/plain; charset=3Dutf-8; format=3Dflowed; DelSp=3DYes >> >> Hi all, >> I=E2=80=99m quite quiet at the moment, because I can access my mailing l= ist >> address only via inconvenient webmail; since I updated MacOS, neither >> Apple Mail nor Thunderbird will take my password anymore... :-(( >> Besides, I=E2=80=99m currently well paid for working with LaTeX, and my = other >> projects get less time. >> >> >> Anyway, one of our authors finally submitted her final corrections, >> and "of course" my ConTeXt setup that still worked well in May doesn=E2= =80=99t >> behave any more: >> >> * stacked layers won=E2=80=99t work on the first page (there should be a= title >> bar above an image; it works on the back cover, but not on the front; >> but I can enable one of both layers) >> >> That might be related to: >> >> * on some right pages, including p.1 (cover), crop marks are shifted >> one page width to the right. >> >> * on some pages, crop marks are shifted vertically; might be related >> to using \offset for image placement. >> >> I=E2=80=99m trying to cook up MWEs, but the behaviour is so strange and >> irregular, that I don=E2=80=99t know if I can reproduce it in a simpler >> environment... I suspect my combined use of postponing, makeups, >> layers and \offset might have grown side effects since May. >> >> Any ideas? >> >> >> Greetlings, Hraban >> >> >> Greetlings, Hraban >> Gr=C3=BC=C3=9Flinge, Hraban >> --- >> https://www.fiee.net >> http://wiki.contextgarden.net >> https://www.dreiviertelhaus.de >> GPG Key ID 1C9B22FD >> >> >> >> ------------------------------ >> >> Message: 7 >> Date: Mon, 8 Jul 2019 09:52:51 +0200 >> From: Hans Hagen >> To: mailing list for ConTeXt users , Henning >> Hraban Ramm >> Subject: Re: [NTG-context] problems with images, layers and crop marks >> Message-ID: <26b17c1c-04b7-7398-4c5f-f514c942671e@xs4all.nl> >> Content-Type: text/plain; charset=3Dutf-8; format=3Dflowed >> >> On 7/8/2019 1:06 AM, Henning Hraban Ramm wrote: >> > Hi all, >> > I=E2=80=99m quite quiet at the moment, because I can access my mailing= list >> > address only via inconvenient webmail; since I updated MacOS, neither >> > Apple Mail nor Thunderbird will take my password anymore... :-(( >> > Besides, I=E2=80=99m currently well paid for working with LaTeX, and m= y other >> > projects get less time. >> > >> > >> > Anyway, one of our authors finally submitted her final corrections, an= d >> > "of course" my ConTeXt setup that still worked well in May doesn=E2=80= =99t >> > behave any more: >> > >> > * stacked layers won=E2=80=99t work on the first page (there should be= a title >> > bar above an image; it works on the back cover, but not on the front; >> > but I can enable one of both layers) >> > >> > That might be related to: >> > >> > * on some right pages, including p.1 (cover), crop marks are shifted >> one >> > page width to the right. >> > >> > * on some pages, crop marks are shifted vertically; might be related t= o >> > using \offset for image placement. >> > >> > I=E2=80=99m trying to cook up MWEs, but the behaviour is so strange an= d >> > irregular, that I don=E2=80=99t know if I can reproduce it in a simple= r >> > environment... I suspect my combined use of postponing, makeups, layer= s >> > and \offset might have grown side effects since May. >> > >> > Any ideas? >> afaik nothing fundamental changed in these areas (ok, maybe you operate >> out of the formal functionality) ... of course, if you're using lmtx it >> might be that something got fixed in there, as at that moment it was >> more experimental than it is now >> >> 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 >> ----------------------------------------------------------------- >> >> >> ------------------------------ >> >> Subject: Digest Footer >> >> >> ________________________________________________________________________= ___________ >> If your question is of interest to others as well, please add an entry t= o >> the Wiki! >> >> maillist : ntg-context@ntg.nl / >> http://www.ntg.nl/mailman/listinfo/ntg-context >> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net >> archive : https://foundry.supelec.fr/projects/contextrev/ >> wiki : http://contextgarden.net >> >> ________________________________________________________________________= ___________ >> >> >> ------------------------------ >> >> End of ntg-context Digest, Vol 181, Issue 8 >> ******************************************* >> > > _________________________________________________________________________= __________ > 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 > > _________________________________________________________________________= __________ > --0000000000009545bb058d436b41 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
That's another intriguing approa= ch, Andr=C3=A9s, thank you.

The approach faces som= e hurdles. First, the template file (main.tex) is written in ConTeXt, so it= never sees the YAML variables, nor can it be used to interpret pandoc'= s conditional expressions. Second, moving the \completecontent macro out of= main.tex and into Markdown (e.g., 01.md, being the first chapter) so that = the conditional expression can be evaluated using pandoc mixes content with= presentation logic.

Modes are a good approach in = this case because the "context" command can take a "mode&quo= t; command-line argument. This provides presentation controls that neither = the YAML nor the Markdown need consider. Adding presentation logic to the C= onTeXt template (i.e., introducing \startmode and \startnotmode into main.t= ex) is acceptable because ConTeXt is wholly responsible for the appearance = of the final document. See: https://wiki.contextgarden.net/Modes

This th= en allows development of command-line arguments from shell scripts to contr= ol how the document is presented when built, which is a little bit more fle= xible than maintaining YAML variables. Also, ideally, the YAML variables wo= uld be used for controlling only content, not presentation logic.
=

Thanks again, Andr=C3=A9s.

On Mon, Jul 8, 2019 at = 11:27 AM Andres Conrado <elandi= @chiquitico.org> wrote:
You can do it on the template... you c= an use a yaml variable to determine if the toc should be printed or not. Li= ke so:

yaml file:
---
toc: true
...

template= file:
%%%= %%%%
$if(toc)$
\completecontent
$endif$
%%%%%%%


<= /div>
Andr=C3=A9s Conrado Montoya


El lun., 8 jul. 2019 a las 2:52, <ntg-context-request@ntg.nl> esc= ribi=C3=B3:
Send= ntg-context mailing list submissions to
=C2=A0 =C2=A0 =C2=A0 =C2=A0 ntg-context@ntg.nl

To subscribe or unsubscribe via the World Wide Web, visit
=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://mailman.ntg.n= l/mailman/listinfo/ntg-context
or, via email, send a message with subject or body 'help' to
=C2=A0 =C2=A0 =C2=A0 =C2=A0 ntg-context-request@ntg.nl

You can reach the person managing the list at
=C2=A0 =C2=A0 =C2=A0 =C2=A0 ntg-context-owner@ntg.nl

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ntg-context digest..."


Today's Topics:

=C2=A0 =C2=A01. Re:=C2=A0 Typesetting Markdown =E2=80=93 Part 5: Interpolat= ion
=C2=A0 =C2=A0 =C2=A0 (Aditya Mahajan)
=C2=A0 =C2=A02. Re:=C2=A0 Typesetting Markdown =E2=80=93 Part 5: Interpolat= ion (Thangalin)
=C2=A0 =C2=A03. Re:=C2=A0 Typesetting Markdown =E2=80=93 Part 5: Interpolat= ion
=C2=A0 =C2=A0 =C2=A0 (Aditya Mahajan)
=C2=A0 =C2=A04. request for \definefontfamily and \definefallbackfamily
=C2=A0 =C2=A0 =C2=A0 (Pablo Rodriguez)
=C2=A0 =C2=A05. Re: crappy names in the fontloader (Hans Hagen)
=C2=A0 =C2=A06. problems with images, layers and crop marks (Henning Hraban= Ramm)
=C2=A0 =C2=A07. Re: problems with images, layers and crop marks (Hans Hagen= )


----------------------------------------------------------------------

Message: 1
Date: Sun, 7 Jul 2019 10:17:31 -0400 (EDT)
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [NTG-context]=C2=A0 Typesetting Markdown =E2=80=93 Part 5:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Interpolation
Message-ID: <nycvar.YAK.7.76.1907071012590.13567@nqv-guvaxcnq>
Content-Type: text/plain; charset=3DUS-ASCII; format=3Dflowed

On Sat, 6 Jul 2019, Thangalin wrote:

> Hello again!
>
> This part of the series describes how to reference *interpolated* stri= ngs
> inside Markdown documents.
> https://dave.autonoma.ca/b= log/2019/07/06/typesetting-markdown-part-5/
>
> There's a section at the end about eliminating the table of conten= ts from a
> reusable document template. I would have preferred using setups, rathe= r
> than redefining the \completecontent macro, but didn't see an obvi= ous way
> to do so.

Why not simply omit \compltecontent from the pandoc template?

Aditya



------------------------------

Message: 2
Date: Sun, 7 Jul 2019 11:58:12 -0700
From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [NTG-context]=C2=A0 Typesetting Markdown =E2=80=93 Part 5:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Interpolation
Message-ID:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <CAANrE7qd81BudwSHBWufu=3DMpDDUPn5fh8ZBM63qL= VZ160gZH=3Dg@mail.gma= il.com>
Content-Type: text/plain; charset=3D"utf-8"

Thank you Aditya.

The main.tex file is meant to be reusable for different document styles. By=
removing \completecontent altogether from the main template, it would
preclude a different document from reusing the main.tex template with a
table of contents. I'd like the template to be "reusable"; ma= king
modifications to "main.tex" --- or creating a copy --- would subv= ert that
goal.

On Sun, Jul 7, 2019 at 7:17 AM Aditya Mahajan <adityam@umich.edu> wrote:

> On Sat, 6 Jul 2019, Thangalin wrote:
>
> > Hello again!
> >
> > This part of the series describes how to reference *interpolated*= strings
> > inside Markdown documents.
> > https://dave.autonoma= .ca/blog/2019/07/06/typesetting-markdown-part-5/
> >
> > There's a section at the end about eliminating the table of c= ontents
> from a
> > reusable document template. I would have preferred using setups, = rather
> > than redefining the \completecontent macro, but didn't see an= obvious way
> > to do so.
>
> Why not simply omit \compltecontent from the pandoc template?
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ntg.nl/pipermail/ntg-context/attachments/20190707/25ca621= 5/attachment-0001.html>

------------------------------

Message: 3
Date: Sun, 7 Jul 2019 15:17:50 -0400 (EDT)
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [NTG-context]=C2=A0 Typesetting Markdown =E2=80=93 Part 5:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Interpolation
Message-ID: <nycvar.YAK.7.76.1907071512000.13567@nqv-guvaxcnq>
Content-Type: text/plain; charset=3DUS-ASCII; format=3Dflowed


On Sun, 7 Jul 2019, Thangalin wrote:

> Thank you Aditya.
>
> The main.tex file is meant to be reusable for different document style= s. By
> removing \completecontent altogether from the main template, it would<= br> > preclude a different document from reusing the main.tex template with = a
> table of contents. I'd like the template to be "reusable"= ;; making
> modifications to "main.tex" --- or creating a copy --- would= subvert that
> goal.

Pandoc allows that. For example, see line 140 of the default context
template:

https://github.com/jgm/pandoc-tem= plates/blob/master/default.context

I don't remember the exact command line parameters for pandoc that set =
the toc flag to true.

An equivalent method will be to control this using a ConTeXt mode.
Redefining \completecontent to \empty seems too drastic.

Aditya



------------------------------

Message: 4
Date: Sun, 7 Jul 2019 21:29:49 +0200
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] request for \definefontfamily and
=C2=A0 =C2=A0 =C2=A0 =C2=A0 \definefallbackfamily
Message-ID: <857b6e26-0b65-c2a4-6569-e664f0111d1e@gmx.es> Content-Type: text/plain; charset=3Dutf-8

Hi Wolfgang,

I have two requests to be implemented in \definefontfamily.

The first one is that is able to load fonts not defined as entries in
the font database.

Here you have a minimal sample:

=C2=A0 =C2=A0 \definefont[Test][file:texgyrepagella-regular.otf at 10pt] =C2=A0 =C2=A0 \definefont[TestOne][file:texgyrepagella-regular-500.otf at 1= 0pt]

=C2=A0 =C2=A0 \definefontfamily [mainface] [rm] [Pagella]
=C2=A0 =C2=A0 =C2=A0 =C2=A0 [tf=3D{file:texgyrepagella-regular.otf},
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0bf=3D{file:texgyrepagella-regular-500.otf= }]

=C2=A0 =C2=A0 \setupbodyfont[mainface]
=C2=A0 =C2=A0 \starttext
=C2=A0 =C2=A0 normal\\
=C2=A0 =C2=A0 \bf bold not working\\

=C2=A0 =C2=A0 \Test this works
=C2=A0 =C2=A0 \TestOne this works
=C2=A0 =C2=A0 \stoptext

=C2=A0The second one would be to allow method=3Duppercase to
\definefallbackfamily, so it could be used to fake small caps (such as
in https://mailman.ntg.nl/pipermail/ntg= -context/2018/092878.html.

Many thanks for your help,

Pablo
--
http:/= /www.ousia.tk


------------------------------

Message: 5
Date: Sun, 7 Jul 2019 23:42:11 +0200
From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg= .nl
Subject: Re: [NTG-context] crappy names in the fontloader
Message-ID: <ea884d13-5c0e-9772-8f69-c2f13ddb224e@xs4all.nl= >
Content-Type: text/plain; charset=3Dutf-8; format=3Dflowed

On 7/6/2019 6:36 PM, Marcel Fabian Kr=C3=BCger wrote:
> Hi everyone,
>
> under default settings, the fontloaders discards all glyph names which=
> are considered "crappy", meaning matching the "p_crappy= name" pattern in
> "font-oup.lua". For some names this makes a lot of sense. Fo= r example
> the name "uni0303" is considered "crappy" and it r= eally provides no
> useful information. Then there are other names like "t_uni0303&qu= ot; which
> are still considered "crappy" while they actually aren't= completely
> useless. So I think there would be some value in preserving them. Of > course, you can always enable "otf.keepnames" if you need na= mes like
> this.
>
> But I actually want to talk about another class of names: Look at
> "Udotbelow". This is IMHO a perfectly normal and useful name= , but the
> fontloader still considers it "crappy" because it starts wit= h a "U"
> followed by a letter which could be a hexadecimal number.
>
> I think this is a bit over-agressive. Maybe the "p_crappyname&quo= t; pattern
> could be changed to only look for "u<hexadecimal>" if = followed by
> "p_done", marking the end of a component?
i'll look into it (irr in generic mode (latex etc) one can disable that=
'feature' which i thought happened)

Hans

-----------------------------------------------------------------
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0Hans Hagen | PRAGMA ADE
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Ridderstraat 27 | 80= 61 GH Hasselt | The Netherlands
=C2=A0 =C2=A0 =C2=A0 =C2=A0 tel: 038 477 53 69 | www.pragma-ade.nl | www.= pragma-pod.nl
-----------------------------------------------------------------


------------------------------

Message: 6
Date: Sun, 07 Jul 2019 23:06:56 +0000
From: Henning Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg= .nl
Subject: [NTG-context] problems with images, layers and crop marks
Message-ID:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <20190707230656.Hord= e.IVjTQk9tNtFVGH0IBsHNXDk@webmail.fiee.net>
Content-Type: text/plain; charset=3Dutf-8; format=3Dflowed; DelSp=3DYes

Hi all,
I=E2=80=99m quite quiet at the moment, because I can access my mailing list= =C2=A0
address only via inconvenient webmail; since I updated MacOS, neither=C2=A0=
Apple Mail nor Thunderbird will take my password anymore... :-((
Besides, I=E2=80=99m currently well paid for working with LaTeX, and my oth= er=C2=A0
projects get less time.


Anyway, one of our authors finally submitted her final corrections,=C2=A0 <= br> and "of course" my ConTeXt setup that still worked well in May do= esn=E2=80=99t=C2=A0
behave any more:

* stacked layers won=E2=80=99t work on the first page (there should be a ti= tle=C2=A0
bar above an image; it works on the back cover, but not on the front;=C2=A0=
but I can enable one of both layers)

That might be related to:

* on some right pages, including p.1 (cover), crop marks are shifted=C2=A0 =
one page width to the right.

* on some pages, crop marks are shifted vertically; might be related=C2=A0 =
to using \offset for image placement.

I=E2=80=99m trying to cook up MWEs, but the behaviour is so strange and=C2= =A0
irregular, that I don=E2=80=99t know if I can reproduce it in a simpler=C2= =A0
environment... I suspect my combined use of postponing, makeups,=C2=A0
layers and \offset might have grown side effects since May.

Any ideas?


Greetlings, Hraban


Greetlings, Hraban
Gr=C3=BC=C3=9Flinge, Hraban
---
https= ://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD



------------------------------

Message: 7
Date: Mon, 8 Jul 2019 09:52:51 +0200
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>, Henning
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Hraban Ramm <texml@fiee.net>
Subject: Re: [NTG-context] problems with images, layers and crop marks
Message-ID: <26b17c1c-04b7-7398-4c5f-f514c942671e@xs4all.nl= >
Content-Type: text/plain; charset=3Dutf-8; format=3Dflowed

On 7/8/2019 1:06 AM, Henning Hraban Ramm wrote:
> Hi all,
> I=E2=80=99m quite quiet at the moment, because I can access my mailing= list
> address only via inconvenient webmail; since I updated MacOS, neither =
> Apple Mail nor Thunderbird will take my password anymore... :-((
> Besides, I=E2=80=99m currently well paid for working with LaTeX, and m= y other
> projects get less time.
>
>
> Anyway, one of our authors finally submitted her final corrections, an= d
> "of course" my ConTeXt setup that still worked well in May d= oesn=E2=80=99t
> behave any more:
>
> * stacked layers won=E2=80=99t work on the first page (there should be= a title
> bar above an image; it works on the back cover, but not on the front; =
> but I can enable one of both layers)
>
> That might be related to:
>
> * on some right pages, including p.1 (cover), crop marks are shifted o= ne
> page width to the right.
>
> * on some pages, crop marks are shifted vertically; might be related t= o
> using \offset for image placement.
>
> I=E2=80=99m trying to cook up MWEs, but the behaviour is so strange an= d
> irregular, that I don=E2=80=99t know if I can reproduce it in a simple= r
> environment... I suspect my combined use of postponing, makeups, layer= s
> and \offset might have grown side effects since May.
>
> Any ideas?
afaik nothing fundamental changed in these areas (ok, maybe you operate out of the formal functionality) ... of course, if you're using lmtx it=
might be that something got fixed in there, as at that moment it was
more experimental than it is now

Hans

-----------------------------------------------------------------
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0Hans Hagen | PRAGMA ADE
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Ridderstraat 27 | 80= 61 GH Hasselt | The Netherlands
=C2=A0 =C2=A0 =C2=A0 =C2=A0 tel: 038 477 53 69 | www.pragma-ade.nl | www.= pragma-pod.nl
-----------------------------------------------------------------


------------------------------

Subject: Digest Footer

___________________________________________________________________________= ________
If your question is of interest to others as well, please add an entry to t= he Wiki!

maillist : ntg-cont= ext@ntg.nl / http://www.ntg.nl/mailman/listinfo/nt= g-context
webpage=C2=A0 : http://www.pragma-ade.nl / http://tex.aanhet.net
archive=C2=A0 : https://foundry.supelec.fr/projects/c= ontextrev/
wiki=C2=A0 =C2=A0 =C2=A0: http://contextgarden.net
___________________________________________________________________________= ________


------------------------------

End of ntg-context Digest, Vol 181, Issue 8
*******************************************
___________________________________________________________________________= ________
If your question is of interest to others as well, please add an entry to t= he Wiki!

maillist : ntg-cont= ext@ntg.nl / http://www.ntg.nl/mailman/listinfo/nt= g-context
webpage=C2=A0 : http://www.pragma-ade.nl / http://context.aanhet.net=
archive=C2=A0 : https://bitbucket.org/phg/context-m= irror/commits/
wiki=C2=A0 =C2=A0 =C2=A0: http://contextgarden.net
___________________________________________________________________________= ________
--0000000000009545bb058d436b41-- --===============9076903554166918550== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv IGh0dHA6Ly9jb250ZXh0LmFhbmhldC5uZXQKYXJjaGl2ZSAgOiBodHRwczovL2JpdGJ1Y2tldC5v cmcvcGhnL2NvbnRleHQtbWlycm9yL2NvbW1pdHMvCndpa2kgICAgIDogaHR0cDovL2NvbnRleHRn YXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg== --===============9076903554166918550==--