September 2020 - ntg-context - NTG Mailing Lists

Can't output direct glyphs either in MKIV or LMTX
by Andres Conrado Montoya 07 Sep '20

07 Sep '20

Hello list. I'm trying to call a direct glyph from the Phaistos font, but it seems it doesn't work. The font is loaded, the log file says it so: system > 12: filename=/home/vantta/.fonts/Phaistos.otf format=otf foundname=/home/vantta/.fonts/Phaistos.otf fullname=/home/vantta/.fonts/Phaistos.otf usedmethod=direct However, the glyph is not displayed in the pdf. I've tried both in MKIV and LMTX with no luck. Maybe someone here will have a clue. MWE: %%%%%%%%%%%%%%%%%%%%%% \definesymbol[arbol] [\getnamedglyphdirect{phaistos}{u101F2}] \starttext \switchtobodyfont[72pt] \symbol[arbol] \stoptext %%%%%%%%%%%%%%%%%%%%%%% -- Andrés Conrado Montoya Andi Kú andresconrado(a)gmail.com http://sesentaycuatro.com http://messier87.com http://chiquitico.org ---------------------------------------- Los fines no justifican los medios, porque la medida verdadera de nuestro carácter está dada por los medios que estamos dispuestos a utilizar, no por los fines que proclamamos. ---------------------------------------- “You develop an instant global consciousness, a people orientation, an intense dissatisfaction with the state of the world, and a compulsion to do something about it. From out there on the moon, international politics look so petty. You want to grab a politician by the scruff of the neck and drag him a quarter of a million miles out and say, ‘Look at that, you son of a bitch.’” — Apollo 14 astronaut Edgar Mitchell

2 1

Problems with tikz plot file
by Christian Prim 06 Sep '20

06 Sep '20

Hi everyone Following MWE produces an error on newest lmtx (current version: 2020.09.03 20:03): \usemodule[tikz] \starttext \placefigure[here][]{}{\hbox{\starttikzpicture \draw plot file {data.table}; \stoptikzpicture}} \stoptext with data.table: 150 -0.102 150.1 -0.15 150.2 -0.389 150.3 -0.15 150.4 -0.389 150.5 -0.15 150.6 -0.293 150.7 -0.341 150.8 -0.485 150.9 -0.293 (data.table could be any x-y-pair) The error says: tex error on line 5 in file ./plot.tex: Argument of \pgf@parsexyline has an extra } It doesn't seem to be directly related to https://unix.stackexchange.com/questions/10267/how-to-find-unmatched-bracke… as I have tested to convert data.table to dos-Format with unix2dos. No success. I'm working on linux (debian). What am I missing? Or is this a bug? Many thanks Christian

2 2

\setupuserpagenumber not working as expected
by jbf 06 Sep '20

06 Sep '20

Am seeking to have frontmatter pages in roman numerals and from Chapter 1 onwards in arabic numerals. I have achieved something of the kind, but page 1 (arabic) is appearing on the last page of the frontmatter and not the first page of Chapter 1. I do not know why this is happening. My setup for page numbering is as follows (something I found somewhere - wiki? elsewhere? Not sure. I didn't make it up!): \definestructureconversionset[frontpart:pagenumber][][romannumerals] \definestructureconversionset[bodypart:pagenumber] [][numbers] \startsectionblockenvironment[frontpart] \setupuserpagenumber[numberconversion=romannumerals] \setuplist[chapter][pageconversionset=pagenumber] \setuppagenumber[number=1] \stopsectionblockenvironment \startsectionblockenvironment[bodypart] \setuppagenumber[number=1] \stopsectionblockenvironment The frontmatter is some 16 pages worth (ends on a verso page but that verso carries the arabic number 1 instead of page xvi which it should be, since the final paragraph on that page ends with \stopfrontmatter. That means Chapter 1 (immediately after \startbodymatter) is now page 2 instead of page 1! I tried a slightly simpler version of the above which I found on Stackexchange: |\definestructureconversionset[frontpart:pagenumber][][romannumerals]|| | |\startsectionblockenvironment[bodypart]| |\setcounter[userpage][1]\stopsectionblockenvironment| but it gave me the same result. Any idea how I can get the correct result? Julian

3 6

Combining modes and MetaFun
by Jan Willem Flamma 06 Sep '20

06 Sep '20

2 2

Typing efficiency
by Jan Willem Flamma 06 Sep '20

06 Sep '20

3 3

latest lmtx
by Alan Bowen 05 Sep '20

05 Sep '20

When I process \starttext Hello, world! \stoptext I get the following error message: /Users/bowen1/Library/TeXShop/Engines/LuaMetaTeX.engine:9: no such file or directory: /Users/bowen1/context-osx-64/tex/texmf-osx-64/bin/mtxrun resolvers | formats | executing runner 'run luametatex format': /Applications/LuaMetaTeX/tex/texmf-osx-64/bin/luametatex --jobname="Version" --fmt=/Applications/LuaMetaTeX/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt --lua=/Applications/LuaMetaTeX/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui cont-yes.mkiv --c:autogenerate --c:currentrun=1 --c:file-line-error --c:fulljobname="./Version.tex" --c:input="./Version.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:synctex="1" --c:texmfbinpath="/Applications/LuaMetaTeX/tex/texmf-osx-64/bin" mtx-context | fatal error: return code: 11 There is definitely a file /Users/bowen1/Library/TeXShop/Engines/LuaMetaTeX.engine. Previous versions of lmtx process without any problem. Alan

3 4

author in ToC and other design complications
by jbf 04 Sep '20

04 Sep '20

Very much at the conclusion of a complicated book where most if not all issues in the body of the text are resolved, but now comes the really difficult part: the Table of Contents. Here is what I am currently using (but it does not produce what I have been asked for, which is explained below this MWE): %------------------------------ \setuphead [subject] [incrementnumber=list] \setuphead [title] [incrementnumber=list] \setupcombinedlist [content] [list={chapter,title,section,subsection}]\switchtobodyfont[10.5pt] \setuplist[chapter][style=normal,alternative=b, before=] And then I place the ToC using: \definehead [tochead] [title] \starttochead[title={Contents}] \placecombinedlist[content] \stoptochead %----------------------------- The last bit ensures that I get the word 'Contents' as the toc title, and avoid then getting 'contents' listed as an item with its page number. And if I want a relatively straightforward Table of Contents, then this mostly works, giving me (e.g.): Foreword iii One Chapter title 1 Two Chapter title 10 etc. Of course, I would prefer it to say 'Chapter One' not just 'One', so that is a minor problem I still have to resolve. But in fact, the publisher wants something quite different and I really do not know how to go about it. I did look at 'Author in ToC' in the wiki, but that referred me to a somewhat complicated Proceedings style, and given that my Chapters are all set up anyway, I just couldn't follow that. Am hoping there is some other way I can achieve the design that follows: Foreword Author's name iii Chapter One Chapter title Author's name 1 Chapter Two 1820-1880 Chapter title Author's name 10 I need to add that the current setup to obtain Chapter Two is with \setuplabeltext[chapter={{Chapter },{:1820-1880}}] which gives me Chapter Two:1820-1880 I had thought that maybe I could get the author with something like \starttitle[title={\ss Foreword}][author={Author Name}] Foreword content.... \stoptitle But that does not produce any author name in the ToC, and in fact the Author's name in the Chapter opening page is simply placed manually as a right-aligned item in the position where I want it, nothing to do with the setup for \chapter (or \title in this case). Given the above complicated design (or so it seems to me) will I have to just set the ToC up manually with a table, or can it be achieved otherwise? Julian

2 3

Re: [NTG-context] defining font family for several options
by jbf 03 Sep '20

03 Sep '20

Thanks Otared. That clears up that little item :-) BTW I know how to reduce font size in the headers (chapter titles) that appear on the recto pages, which I can do with something like \setupheader [style={\ss\switchtobodyfont[10pt]}], but it doesn't seem to affect the header (title of the book) on the verso pages, which is drawn from the simple statement: \startdocument [metadata:title={Book title}] Shouldn't \setupheader affect both headers? Or is it possible I have left something out of my \setupheader declaration? Julian On 4/9/20 5:30 am, Otared Kavian wrote: > Hi Julian, > > The tilde ~ in {\bf\ss #1.~#2} is only there to have an unbreakable fixed space between the dot and the first character of the chapter title. Also in this way one can see that one has put a space there… :-) > > Best tegards: Otared > >> On 2 Sep 2020, at 23:29, jbf <roma83537(a)gmail.com> wrote: >> >> Thanks Otared, >> >> Still off list. You are very patient but also very thorough, and this is making a huge difference to what is in fact a considerable challenge for me, but one I am coming to grips with. I believe this aspect of things is now clear to me. No hurry, but when you have a moment can you explain the significance of the ~ in the {\bf\ss #1.~#2}}part of the definition, before the 2nd element? >> >> After this I'll go back on list! I still have a couple of other queries (not font related) about things that are not functioning as they ought at the moment, which means I'll need either some understanding or some tweaking, but as always there are people on the list like yourself who are prompt with their assistance. >> >> Kind regards, >> >> Julian >> >> On 3/9/20 12:34 am, Otared Kavian wrote: >>> Hi Julian, >>> >>> First of all, your definition of mychapterfont is incomplete: a font family should contain also math fonts, because even if you don't have mathematics in your text where you use that font, ConTeXt may pick some characters from math fonts. So in my opinion you should define a whole font family named mychapterfont, where in particular the sans serif comes from what you are indicating. >>> >>> The second point is that you should not setup bodyfont twice: when you say twice \setupbodyfont, ConTeXt will take the last one for the rest of your document… >>> So you say only once >>> \setupbodyfont[mainface] >>> and then only where you want to change the font you say >>> \start \switchtobodyfont[mychapterfont] \ss My special text. \stop >>> >>> By the way, as we said earlier, you can also use braces instead of \start\stop, and even better you can say >>> >>> \start \switchtobodyfont[mychapterfont,sans] My special text. \stop >>> >>> A third point is that if you are using mychapterfont only to set the titles of chapters, in my opinion it would be better to define a command which takes care of all the formatting you are wishing, and then use it in the chapter header. Something like >>> >>> \define[2]\MyChapterCommand{\switchtobodyfont[mychapterfont,12pt] {\bf\ss #1.~#2}} >>> \setuphead[chapter][command=\MyChapterCommand] >>> >>> In this way you can just say >>> >>> \startchapter[title={This is my first chapter}] >>> >>> \input ward.tex >>> >>> \stopchapter >>> >>> without the hassles of formatting each title. If only some chapters have the special font, then you can define a new family of chapters which may share the same counter as the rest of your chapters. >>> >>> Best regards: Otared >>> >>>> On 2 Sep 2020, at 03:30, jbf <roma83537(a)gmail.com> wrote: >>>> >>>> Otared, I thought I had it right - and it is partly right, but that newly declared font now applies to everything, not just the chapter title. So I haven't got it quite right! Maybe I shouldn't bother the list with these extra bits so am writing off list. Here is what my font definitions now look like (new one highlighted): >>>> >>>> \definefontfamily [mainface] [rm] [alegreya] [sc=file:alegreyasc-bold] >>>> \definefontfamily [mainface] [ss] [dax][tf=file:dax-regular,bf=file:dax-medium] >>>> \definefontfamily [mainface] [mm] [alegreya] >>>> \definefontfamily [mychapterfont] [ss] [itcavantgardepromd] [ss=file:itcavantgardepro-md] >>>> \setupbodyfont[mainface] >>>> \setupbodyfont[mychapterfont] >>>> >>>> I presumed I would have to \setupbodyfont[mychapterfont], but is this where I have gone wrong?. >>>> >>>> Then in the first chapter, I wrote as follows: >>>> >>>> \chapter{{\switchtobodyfont[mychapterfont] \ss Introduction to the BDACE Online Project}} and I am getting my AvanteGardePro-MD font alright, but it now applies to the whole document! >>>> >>>> I tried following title with \start switchtobodyfont[mainface] \rm and then my body text (followed by \stop obviously, at the end of the chapter). But this did not work. >>>> >>>> I then thought that I could use this [mychapterfont] and include it somehow in my \setuphead[chapter] so it would work for all chapter titles, along the lines of: \setuphead [chapter] [header=empty, {\switchtobodyfont[mychapterfont] \ss}] but that hasn't worked either - my body text throughout is still in the sans serif, not the usual [mainface] [rm] >>>> >>>> I think the problem is that if I define two or more \setupbodyfont items, it is the last of them that controls what happens. But if I don't set up the newly-defined [mychapterfont] then it is not recognised when I call it in. So what am I doing wrong? You see, I seem to back to the very first question I asked, which involved setting up two separate bodyfonts. So what is it I haven't understood? >>>> >>>> Julian >>>> >>>> >>>> >>>> On 2/9/20 9:59 am, Otared Kavian wrote: >>>>> Hi Julian, >>>>> >>>>> What Aditya means is that you define two (or more) font families: one is named mainface as yu have already done, the other named mychapterfont (for instance) where you attribute whatever fonts you wish to sans serif and else. Then when you want to use the special font in some of the titles you use >>>>> >>>>> {\switchtobodyfont[mychapterfont]\ss my text} >>>>> >>>>> You can use also >>>>> >>>>> \start \switchtobodyfont[mychapterfont] \ss my text \stop >>>>> >>>>> in case the braces are not convenient for a longer text. >>>>> >>>>> Best regards: Otared >>>>> >>>>> >>>>>> On 2 Sep 2020, at 01:22, jbf <roma83537(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>> I presume you mean, {\switchtobodyfont[itcavantgarde]\ss My text} for the case I mentioned? >>>>>> >>>>>> Because at no point in the example I gave of \definefontfamily[mainface] had I defined ss as an AvanteGarde typeface, and that is the heart of my question. Can I somehow define two kinds of sans serif for different uses? >>>>>> >>>>>> It was earlier suggested (Hraban) I might be able to do away with the serif font or use calligraphy, but I need the rm and I don't need cg (though, was the suggestion that I could use the initials cg but set up the typeface in fact as a sans serif, in this case AvantGarde? Is that possible? In which case I could also use hw as well for a different typeface as well?). As you can see, I am trying to get to grips with this whole typeface issue which I find a bit complicated. >>>>>> >>>>>> Julian >>>>>> >>>>>> >>>>>> On 2/9/20 9:08 am, Aditya Mahajan wrote: >>>>>> >>>>>>> On Tue, 1 Sep 2020, jbf wrote: >>>>>>> >>>>>>> >>>>>>>> Perhaps someone can assist me with the following query. I have a >>>>>>>> situation where I need to use more than one sans serif fonts (especially >>>>>>>> within complicated chapter heads). I currently have the following: >>>>>>>> >>>>>>>> \definefontfamily [mainface] [rm] [alegreya] >>>>>>>> \definefontfamily [mainface] [ss] [dax][tf= >>>>>>>> file:dax-regular >>>>>>>> ] >>>>>>>> \definefontfamily [mainface] [mm] [alegreya] >>>>>>>> \setupbodyfont[mainface] >>>>>>>> \setupbodyfont[11pt] >>>>>>>> >>>>>>>> But what if I need to have, in addition to the Dax sans serif typeface, >>>>>>>> an additional sans serif typeface such as ITCAvantGarde? How do I >>>>>>>> declare that? Do I just give it another name, e.g. >>>>>>>> \definefontfamily[chapter][itcavantgarde] etc? If I did that, how then >>>>>>>> do I refer to it? Obviously not just as {\ss my text} since that would >>>>>>>> call in the dax font. >>>>>>>> >>>>>>> {\switchtobodyfont[chapter]\ss my text} >>>>>>> >>>>>>> I tried to improve the explanation on the wiki: >>>>>>> https://wiki.contextgarden.net/Font_Switching#Switching_typefaces >>>>>>> >>>>>>> >>>>>>> Aditya >>>>>>> ___________________________________________________________________________________ >>>>>>> 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://context.aanhet.net >>>>>>> >>>>>>> archive : >>>>>>> https://bitbucket.org/phg/context-mirror/commits/ >>>>>>> >>>>>>> wiki : >>>>>>> http://contextgarden.net >>>>>>> >>>>>>> ___________________________________________________________________________________ >>>>>>> >>>>>> ___________________________________________________________________________________ >>>>>> 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://context.aanhet.net >>>>>> >>>>>> archive : >>>>>> https://bitbucket.org/phg/context-mirror/commits/ >>>>>> >>>>>> wiki : >>>>>> http://contextgarden.net >>>>>> >>>>>> ___________________________________________________________________________________ >>>>>> >>>>> ___________________________________________________________________________________ >>>>> 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://context.aanhet.net >>>>> >>>>> archive : >>>>> https://bitbucket.org/phg/context-mirror/commits/ >>>>> >>>>> wiki : >>>>> http://contextgarden.net >>>>> >>>>> ___________________________________________________________________________________ >>>>>

2 2

ebook
by Hans Hagen 03 Sep '20

03 Sep '20

Hi, Has anyone seen this device: https://www.pocketbook-int.com/nl/products/pocketbook-color-lux I wonder what the quality is (300 dpi bw, 100 dpi color overlayed). 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 1

packed items not working in latest from 2020.09.03 12:08
by Pablo Rodriguez 03 Sep '20

03 Sep '20

Dear list, I have the following sample: \starttext \startitemize[n] \startitem Item\stopitem \startitem Item\stopitem \startitem Item\stopitem \startitem Item\stopitem \stopitemize \startitemize[a, packed] \startitem Item\stopitem \startitem Item\stopitem \startitem Item\stopitem \startitem Item\stopitem \stopitemize \stoptext I’m afraid that packed item lists are misbehaving. Could anyone confirm this? Pablo -- http://www.ousia.tk

2 3