[NTG-context] problems with images, layers and crop marks
Hi all, I’m 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’m 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’t behave any more: * stacked layers won’t 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’m trying to cook up MWEs, but the behaviour is so strange and irregular, that I don’t 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üßlinge, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD ___ 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 ___
Re: [NTG-context] crappy names in the fontloader
On 7/6/2019 6:36 PM, Marcel Fabian Krüger wrote: Hi everyone, under default settings, the fontloaders discards all glyph names which are considered "crappy", meaning matching the "p_crappyname" pattern in "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 - ___ 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 ___
[NTG-context] request for \definefontfamily and \definefallbackfamily
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={file:texgyrepagella-regular.otf},
bf={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=uppercase 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
___
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
___
Re: [NTG-context] Typesetting Markdown – Part 5: Interpolation
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 ___ 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 ___
Re: [NTG-context] Typesetting Markdown – Part 5: Interpolation
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. 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 obvious way > > to do so. > > Why not simply omit \compltecontent from the pandoc template? > > > ___ 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 ___
Re: [NTG-context] Typesetting Markdown – Part 5: Interpolation
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 obvious way to do so. Why not simply omit \compltecontent from the pandoc template? Aditya ___ 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 ___
[NTG-context] crappy names in the fontloader
Hi everyone, under default settings, the fontloaders discards all glyph names which are considered "crappy", meaning matching the "p_crappyname" pattern in "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? Best regards, Marcel Krüger ___ 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 ___
