April 2013 - ntg-context - NTG Mailing Lists

flushfootnotes
by Meer H. van der 11 Apr '13

11 Apr '13

The contextgarden mentions a command flushfootnotes, however \starttext \flushfootnotes \stoptext results in an error: ! Undefined control sequence. log system > tex > error on line 2 in file sectioning.tex: Undefined control sequence ... l.2 \flushfootnotes ConTeXt ver: 2013.03.20 10:34 MKIV fmt: 2013.3.20 int: english/english Hans van der Meer

1 0

SVG with \externalfigure and http:// handler
by Marco Patzer 11 Apr '13

11 Apr '13

Hi, Including local SVG graphics works, so does including remote PNGs. Remote SVGs are not displayed, however. Example: \starttext \externalfigure[http://www.gnu.org/graphics/gnu2.svg] \stoptext Is this not supported or am I missing a required option? Marco

1 0

Number of pages by Lua of a figure to be inserted?
by Procházka Lukáš Ing. - Pontex s. r. o. 11 Apr '13

11 Apr '13

Hello, I need to identify number of pages by Lua of an image which is to be inserted. The image can be of all various types supported by Ctx - e.g. .png, .pdf. I've been using the following code so far (based on a mailing thread in the past): ---- function nOfPages(fn) local fig = figures.push{name = fn} local info = figures.identify() figures.check() local n = fig.used.pages figures.pop() return n end ---- But the code above break Ctx in the case that the image doesn't exist. I'd need to modify the solution somehow so to return 'nil' or 'false' (or a error message) in the case the file was not found. How to do it? TIA. Best regards, Lukas (NB: Still "ConTeXt ver: 2012.11.26 13:31 MKIV fmt: 2012.11.27 int: english/english".) -- Ing. Lukáš Procházka [mailto:LPr@pontex.cz] Pontex s. r. o. [mailto:pontex@pontex.cz] [http://www.pontex.cz] Bezová 1658 147 14 Praha 4 Tel: +420 244 062 238 Fax: +420 244 461 038

2 2

Re: [NTG-context] Hanging and Protrusion with Typescript
by "H. Özoguz" 10 Apr '13

10 Apr '13

> Can you add “mode=node” to \definefontfeature in the typescript based solution. Ok, now the kerning is exactly the same, what does mode=node do? Huseyin

3 2

hyperlink bug in \cite
by Alan BRASLAU 10 Apr '13

10 Apr '13

Hello, \cite[A] can yield a hyperlink to the bibliography. However, \cite[A,B] does not (and should). I suppose that this could be a bit complicated when using numbered references (rather than Author, year), in the particular case where one collapses the list of numbers, in which case the hyperlink could naturally point to the first numbered reference of the list. Alan

2 2

markdown: referencing tables
by Xenia 10 Apr '13

10 Apr '13

Dear context list, I love simple tables in markdown like this one \startmarkdown Right Left Center Default ------- ------ ---------- ------- 12 12 12 12 123 123 123 123 1 1 1 1 Table: Demonstration of simple table syntax. \stopmarkdown Is there a way to reference this table? With \starttabulate (\stoptabulate) tables can be referenced with \placetable, but \placetable just creates another (empty) table in case of a markdown table. Thanks, Xenia

3 5

Re: [NTG-context] New user of ConTeXt
by "H. Özoguz" 10 Apr '13

10 Apr '13

Am 10.04.2013 15:29, schrieb ntg-context-request(a)ntg.nl: > \setupbodyfont[11pt] > \enableregime[utf-8] > \mainlanguage[fr] > \starttext > > \setMPtext {1} {C'est le titre} > \startMPcode > pickup pencircle scaled .5mm ; > pair a; a :=(0.2cm,.5cm); > label.rt("\MPtext {1}",a); > draw (0cm,0cm)--(8cm,0cm); > draw (8cm,0cm)..(8.15cm,0.08cm)..(8.2cm,0.18cm); > draw (8.2cm,0.18cm)--(8.7cm,1.7cm); > \stopMPcode > > \stoptext > ---------------------------------------- > > How can I avoid these symbols? > > Thanks for your help, > Tristan lorino Here your code does not generate these space-symbols, maybe an editor-issue? Huseyin

1 0

Blanks instead of indented paragraphs
by "H. Özoguz" 10 Apr '13

10 Apr '13

Hi there, I have here an book, where I want to have empty lines between paragraphs, not only indenting. Of course I could write always ++++ Para 1 \blank Para 2 ++++ but it would be easiest, if empty lines in the editors would be automatically interpreted as "\blank" – and then without indenting of course. How to get that? Regards. Huseyin

2 1

Re: [NTG-context] Hanging and Protrusion with Typescript
by "H. Özoguz" 10 Apr '13

10 Apr '13

Am 10.04.2013 11:27, schrieb ntg-context-request(a)ntg.nl: > This is no problem because they have different names, you can try the following example: > > \usemodule[simplefonts] > > \setmainfont[Garamond] > %\setmainfont[Adobe Garamond Pro] > %\setmainfont[AGaramondPro] > %\setmainfont[EBGaramond] > %\setmainfont[Stempel Garamond] > > \starttext > Regular, \it Italic, \bf Bold and \bi Bolditalic. > \stoptext With \setmainfont[AGaramondPro] it works! The first and second does not work. > >> >Another interesting question: I compared the results using the Simplefont solution and your Typescript solution, both with hanging. Both works, but it is not the same output. It seems, that with Simplefont it is "nicer", in the following sence: The distance between a capital of a beginning word to the next letter it better typed, f.e. in "Hans Meier" the distance of "H" to "ans" could be too much in the typescript example, but is perfect with Simplefont. >> > >> >Where does this difference in typography between Typescript and Simplefont comes from? > Maybe a kerning issue, you can add \showfontkerns at the begin of your document to visualize the kerning. > > Wolfgang \showfontkerns works with Simplefont, but not with Typescript. More precisely: This shows kerning: +++++++++++++ \showfontkerns \usemodule[simplefonts] \setmainfont[AGaramondPro][boldfont=AGaramondPro-Bold, italicfont=AGaramondPro-Italic, bolditalicfont=AGaramondPro-BoldItalic, protrusion=quality, expansion=quality] \setupalign[hz, hanging] \starttext \input tufte \stoptext ++++++++++++++ But this one not: +++++++++++++ \showfontkerns \starttypescript [serif] [nimbus] \definefontsynonym [Serif] [file:AGaramondPro-Regular.otf] \definefontsynonym [SerifBold] [file:AGaramondPro-Bold.otf] \definefontsynonym [SerifItalic] [file:AGaramondPro-Italic.otf] \definefontsynonym [SerifBoldItalic] [file:AGaramondPro-BoldItalic.otf] \stoptypescript \definefontfeature[default][default][protrusion=quality,expansion=quality] \definetypeface [nimbus] [rm] [serif] [nimbus] [default] [features=default] \setupbodyfont[nimbus,rm,12pt] \setupalign[hz,hanging] \starttext \input tufte \stoptext ++++++++++++++++ Where the mistake? And independent from that: That the kerning is different, is for sure (by visual inspection). How can the showing in numbers (showkerning) help to understand the reason for this difference? (Just interested to learn more about ConTeXt, of course I am not able to fix anything or understand it by myself). Huseyin

2 1

Re: [NTG-context] Hanging and Protrusion with Typescript
by "H. Özoguz" 10 Apr '13

10 Apr '13

Am 10.04.2013 10:29, schrieb ntg-context-request(a)ntg.nl: > mtxrun --script font --list --all --pattern=*garamond* I got this: +++++++++++++++++++++++ adobegaramondpro agaramondprobold c:/windows/fonts/AGaramondPro-Bold.otf adobegaramondprobold agaramondprobold c:/windows/fonts/AGaramondPro-Bold.otf adobegaramondproitalic agaramondprobolditalic c:/windows/fonts/AGaramondPro-BoldItalic.otf adobegaramondpronormal agaramondproitalic c:/windows/fonts/AGaramondPro-Italic.otf adobegaramondproregular agaramondprobold c:/windows/fonts/AGaramondPro-Bold.otf agaramondprobold agaramondprobold c:/windows/fonts/AGaramondPro-Bold.otf agaramondprobolditalic agaramondprobolditalic c:/windows/fonts/AGaramondPro-BoldItalic.otf agaramondproitalic agaramondproitalic c:/windows/fonts/AGaramondPro-Italic.otf agaramondproregular agaramondproregular c:/windows/fonts/AGaramondPro-Regular.otf ebgaramond ebgaramond08regular c:/windows/fonts/EBGaramond08-Regular.otf ebgaramond08regular ebgaramond08regular c:/windows/fonts/EBGaramond08-Regular.otf ebgaramond08regularsmallcaps ebgaramond08sc c:/windows/fonts/EBGaramond08-SC.otf ebgaramond08sc ebgaramond08sc c:/windows/fonts/EBGaramond08-SC.otf ebgaramond12allsc ebgaramond12allsc c:/windows/fonts/EBGaramond12-AllSC.otf ebgaramond12allscnormal ebgaramond12allsc c:/windows/fonts/EBGaramond12-AllSC.otf ebgaramond12italic ebgaramond12italic c:/windows/fonts/EBGaramond12-Italic.otf ebgaramond12regular ebgaramond12regular c:/windows/fonts/EBGaramond12-Regular.otf ebgaramond12regularallsmallcaps ebgaramond12allsc c:/windows/fonts/EBGaramond12-AllSC.otf ebgaramond12regularsmallcaps ebgaramond12sc c:/windows/fonts/EBGaramond12-SC.otf ebgaramond12sc ebgaramond12sc c:/windows/fonts/EBGaramond12-SC.otf ebgaramondinitials ebgaramondinitials c:/windows/fonts/EBGaramond-Initials.otf ebgaramondinitialsf1 ebgaramondinitialsf1 c:/windows/fonts/EBGaramond-InitialsF1.otf ebgaramondinitialsf2 ebgaramondinitialsf2 c:/windows/fonts/EBGaramond-InitialsF2.otf ebgaramondinitialsfill1 ebgaramondinitialsf1 c:/windows/fonts/EBGaramond-InitialsF1.otf ebgaramondinitialsfill1normal ebgaramondinitialsf1 c:/windows/fonts/EBGaramond-InitialsF1.otf ebgaramondinitialsfill1regular ebgaramondinitialsf1 c:/windows/fonts/EBGaramond-InitialsF1.otf ebgaramondinitialsfill2 ebgaramondinitialsf2 c:/windows/fonts/EBGaramond-InitialsF2.otf ebgaramondinitialsfill2normal ebgaramondinitialsf2 c:/windows/fonts/EBGaramond-InitialsF2.otf ebgaramondinitialsfill2regular ebgaramondinitialsf2 c:/windows/fonts/EBGaramond-InitialsF2.otf ebgaramondinitialsnormal ebgaramondinitials c:/windows/fonts/EBGaramond-Initials.otf ebgaramondinitialsregular ebgaramondinitials c:/windows/fonts/EBGaramond-Initials.otf ebgaramonditalic ebgaramond12italic c:/windows/fonts/EBGaramond12-Italic.otf ebgaramondnormal ebgaramond08regular c:/windows/fonts/EBGaramond08-Regular.otf ebgaramondregular ebgaramond08regular c:/windows/fonts/EBGaramond08-Regular.otf ebgaramondsc ebgaramond08sc c:/windows/fonts/EBGaramond08-SC.otf garamond garamond c:/windows/fonts/GARA.TTF garamondantiqua garamondantiqua c:/windows/fonts/91545.ttf garamondbold garamondbold c:/windows/fonts/GARABD.TTF garamondhalbfett garamondhalbfett c:/windows/fonts/91547.ttf garamonditalic garamonditalic c:/windows/fonts/GARAIT.TTF garamondkursiv garamondkursiv c:/windows/fonts/91546.ttf garamondkursivhalbfett garamondkursivhalbfett c:/windows/fonts/91548.ttf garamondnormal garamondantiqua c:/windows/fonts/91545.ttf stempelgaramondbold stempelgaramondbold c:/windows/fonts/11547.ttf stempelgaramondbolditalic stempelgaramondbolditalic c:/windows/fonts/11548.ttf stempelgaramonditalic stempelgaramonditalic c:/windows/fonts/11546.ttf stempelgaramondroman stempelgaramondroman c:/windows/fonts/11545.ttf stempelgaramondromanbold stempelgaramondbold c:/windows/fonts/11547.ttf stempelgaramondromanbolditalic stempelgaramondbolditalic c:/windows/fonts/11548.ttf stempelgaramondromanitalic stempelgaramonditalic c:/windows/fonts/11546.ttf stempelgaramondromannormal stempelgaramondroman c:/windows/fonts/11545.ttf ++++++++++++++++++++++ Maybe too many different garamonds? Another interesting question: I compared the results using the Simplefont solution and your Typescript solution, both with hanging. Both works, but it is not the same output. It seems, that with Simplefont it is "nicer", in the following sence: The distance between a capital of a beginning word to the next letter it better typed, f.e. in "Hans Meier" the distance of "H" to "ans" could be too much in the typescript example, but is perfect with Simplefont. Where does this difference in typography between Typescript and Simplefont comes from? Huseyin

2 1