- ntg-context - Mailing Lists

Defining a title font.
by john Culleton 04 Oct '12

04 Oct '12

Trying to use an OTF font just for the title page. Ran mkluatexfontdb Used the name as defined in ../otfl-names.lua Here is my actual code: -------------------------- \usemodule[simplefonts] \definefont [titlefont][MyriadPro-Bold at 50bp] \startstandardmakeup \titlefont \centerline{Scribus} \centerline {for} \centerline{Book Covers} \centerline{Free Publishing Software Series} \rm \stopstandardmakeup -------------------------- And here are the pertinent error messages: ------------------------------ (title.tex resolvers > modules > loaded: 'simplefonts' (/home/safe/context/tex/texmf-modules/tex/context/third/simplefonts/t-simplefonts.mkiv loading > ConTeXt User Module / Simplefonts <+ /home/safe/context/tex/texmf-modules/tex/context/third/simplefonts/t-simplefonts.lua>) fonts > defining > font with asked name 'MyriadPro-Bold' is not found using lookup 'file' fonts > defining > unknown font MyriadPro-Bold, loading aborted fonts > defining > unable to define MyriadPro-Bold as [titlefont--0] ) ----------------------------------------------------------------------- Clearly I don't know what I am doing. Can someone help? -- John Culleton Wexford Press Free list of books for self-publishers: http://wexfordpress.net/shortlist.html PDF e-book: "Create Book Covers with Scribus" available at http://www.booklocker.com/books/4055.html

2 3

Issues with the legend mechanism
by Marco Patzer 04 Oct '12

04 Oct '12

Hi, I discovered some issues with the legend mechanism. 1) A newline after \startplacelegend fails: \starttext \startplacelegend \startcontent Foo \stopcontent \startcaption Bar \stopcaption \stopplacelegend \stoptext 2) location != top | bottom throws “Infinite glue shrinkage found in a paragraph”: \starttext \startplacelegend [location=left] \startcontent Foo \stopcontent \startcaption Bar \stopcaption \stopplacelegend \stoptext 3) tabulate inside the content fails when not boxed: \starttext \startplacelegend [location=left] \startcontent \starttabulate \NC Alpha \NC Beta \NC\NR \stoptabulate \stopcontent \startcaption Bar \stopcaption \stopplacelegend \stoptext Just reporting, nothing which needs to be fixed before EuroTeX. Marco

2 1

Math and units
by Procházka Lukáš Ing. - Pontex s. r. o. 04 Oct '12

04 Oct '12

Hello, which is the most correct way to display units (here: kN) in math formula? ---- \starttext \startformula a = 210 kN % "kN" is shown like a variable (here: like 'a'), which is unwanted \stopformula \startformula a = 210 \unit{kN} % No unit is displayed (?!) \stopformula \startformula a = 210 \text{~kN} % '~' required?, ugly way \stopformula \stoptext ---- TIA. Best regards, Lukas -- 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

3 4

punctuation vs font switch
by Andreas Mang 03 Oct '12

03 Oct '12

Dear all, at the risk of being met with an incredulous shake of the head: I am using xits as math font and pagella as main font (for several reasons). Obviously, the punctuation (in particular "comma") does not match. Is there an easy and quick global fix!? Your help is very much appreciated. Cheers, Andreas % minimal example \starttypescript [myface] \definetypeface [\typescriptone] [rm] [serif] [pagella] [default] \definetypeface [\typescriptone] [ss] [sans] [helvetica] [default] \definetypeface [\typescriptone] [tt] [mono] [modern] [default] \definetypeface [\typescriptone] [mm] [math] [xits] [default] \stoptypescript \setupbodyfont[myface,11pt] \starttext $1{,}2$ 1,2 % difference $1\text{,}2$ % not so nice work around and problematic since the font size does not change (superscript, subscript,...) \stoptext % stop minimal example P.S. Clearly, this does not matter for formulas but its different for inline (in text) math expressions.

2 1

Alignment in combination
by Marco Patzer 03 Oct '12

03 Oct '12

Hi, how to left align the elements of a combination? \useMPlibrary [dum] \setupexternalfigures [height=2cm] \starttext %% does nothing: \setupcombinations [align=flushleft] \startcombination [2*2] {\externalfigure[dummy][width=2cm]} {} {\externalfigure[dummy][width=2cm]} {} {\externalfigure[dummy][width=4cm]} {} {\externalfigure[dummy][width=3cm]} {} \stopcombination \blank[2cm] %% desired: \startcombination [2*2] {\kern-2cm\externalfigure[dummy][width=2cm]} {} {\kern-1cm\externalfigure[dummy][width=2cm]} {} {\externalfigure[dummy][width=4cm]} {} {\externalfigure[dummy][width=3cm]} {} \stopcombination \stoptext Marco

2 1

Strange behaviour by processing a project file
by pavel＠hanak.name 03 Oct '12

03 Oct '12

Hello, I have the following file structure: * file "my-project.tex" contains: \environment my-environment \startproject my-project \product my-product1 \product my-product2 \stopproject * file "my-environment.tex" contains: ... font definitions, style definitions etc. * file "my-product1.tex" contains: \project my-project \startproduct my-product1 ... \stopproduct * file "my-product2.tex" contains: \project my-project \startproduct my-product2 ... \stopproduct Now, when I process the product1 with "context my-product1.tex" I get the output in my-product1.pdf as expected. But when I try to process the whole project with "context my-project.tex", the file is processed but I get no pdf output, which surprise me, because in the reference manual contextref.pdf I read: "In principal a project file contains only a list of products and environments. If you would process the project file all products will be placed in one document. This is seldom wanted." So I would expect to get one pdf outputfile with all products. Could anyone explain me, why I don't get any pdf output? Best regards Pavel

2 1

TABLE and row/column align settings
by Procházka Lukáš Ing. - Pontex s. r. o. 03 Oct '12

03 Oct '12

Hello, I have a complicated TABLE, but I simplified it to the following example: ---- \def\DoTable#1{% \bTABLE \setupTABLE[width=2cm] \setupTABLE[column][#1][align=flushright] % ....................................................... [1] \setupTABLE[row][1][align=middle] % Settings for ALL columns in the row 1 should be overwritten ... [2] \bTABLEhead \bTR \bTH a\eTH \bTH b\eTH \eTR \eTABLEhead \bTABLEbody \bTR \bTD a\eTD \bTD b\eTD \eTR \eTABLEbody \eTABLE } \starttext No column specification: \DoTable{} With column specification: \DoTable{2} \stoptext ---- The problem is that row #1 should be mid-aligned in all columns. So I wrote: ---- \setupTABLE[column][2][align=flushright] % Column #2 has its own alignment... \setupTABLE[row][1][align=middle] % ... but overwrite here for the whole row #1 (including column #2) ---- But column #2 keeps the previously assigned alignment. The situation doesn't change even if I swap [1] and [2] (for the case "the earlier setting, the higher priority"). Moreover, if the column number if not specified (\DoTable{}), the row setting overwrites setting for ALL columns; so only if the column is specified precisely, its setting is kept. So how to overwrite row #1 setting globally? And how setting priorities are evaluated? I guessed the later specification, the higher weight (which would allow overwriting)... Note that in the example it would be possible to specify settings for each row/column, but it not useful way in the case of more/very complicated tables. TIA. Best regards, Lukas -- 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 4

Problem with new version
by pavel＠hanak.name 03 Oct '12

03 Oct '12

Hello, yesterday I upgraded my debian and I found out that my previsously prepared publication cannot be compiled with the new version of ConTeXt. The publication looks like: * main file "ausgewaehlte.tex" \startproject ausgewaehlte \environment ausgewaehlte_environment \startfrontmatter \setuppagenumbering[state=stop] \product titelpage \stopfrontmatter \startbodymatter \setuppagenumbering[state=start] \product first \product second ... \stopbodymatter \stopproject * environment file "ausgewaehlte_environment.tex" \startenvironment ausgewaehlte_environment \usemodule[typo-krn] \usemodule[letterspace] \setupoutput[pdftex] \enableregime[utf] \mainlanguage[cz] \definefontfeature[hz][default][protrusion=punctuation,expansion=quality, mode=node] \definefontfeature[oldnumbers][language=DFLT,script=latn,onum=yes] \setupfonthandling [hz][min=20, max=20, step=5] \setupalign[hz,hanging] ... ... \stopenvironment This publication I could compile without problem with context having these debian packages: luatex 0.70.1-1+b1 next generation TeX engine texlive-luatex 2009-15 TeX Live: LuaTeX packages context 2011.05.18.20110627-1 powerful TeX format context-modules 20110701-1 additional ConTeXt modules After upgrading debian to: luatex 0.70.1.20120524-3 amd64 next generation TeX engine texlive-luatex 2012.20120611-4 all TeX Live: LuaTeX packages context 2012.05.30.20120611-1 all powerful TeX format context-modules 20120611-1 all additional ConTeXt modules I get these error by compiling the above source: This is LuaTeX, Version beta-0.70.2-2012070300 (TeX Live 2012/Debian) \write18 enabled. (ausgewaehlte.tex jobcontrol > version mismatch with jobfile: 1.14 <> 1.19 ConTeXt ver: 2012.05.30 11:26 MKIV fmt: 2012.9.28 int: english/english system > cont-new.mkiv loaded (/usr/share/texmf/tex/context/base/cont-new.mkiv system > beware: some patches loaded from cont-new.mkiv ) system > ausgewaehlte.top loaded (ausgewaehlte.top) fonts > latin modern fonts are not preloaded languages > language en is active {/usr/share/texmf/fonts/map/pdftex/context/mkiv-base.map} fonts > preloading latin modern fonts (second stage) fonts > typescripts > unknown: library 'loc' {/usr/share/texmf/fonts/map/dvips/lm/lm-math.map}{/usr/share/texmf/fonts/map/dvips/lm/lm-rm.map} fonts > virtual math > unable to resolve name mapsfromchar fonts > fallback modern rm 12pt is loaded (ausgewaehlte_environment.tex resolvers > modules > loaded: 'typo-krn' (/usr/share/texmf/tex/context/base/typo-krn.mkiv loading > ConTeXt Typesetting Macros / Kerning <+ /usr/share/texmf/tex/context/base/typo-krn.lua> system > duplicate core namespace 'characterkerning' \wait = Could anyone explain me what happened? Why the new context version complains about "duplicate core namespace" when the previous version worked without problems? Any help will be appreciated. Best regards Pavel

2 1

Split \starttabulates
by Malte Stien 03 Oct '12

03 Oct '12

Dear all, I have a number of tables defined like this: \placetable[here][tab:some-table]{Some Table} \starttabulate[|w(.30\textwidth)p|w(.70\textwidth)p|] \HL \NC {\bf Animal} \NC {\bf Comment} \NC\FR \HL \NC Cat \NC Pretty cool \NC\MR \NC Bear \NC Kind of lazy \NC\MR \NC Sheep \NC Always hungry \NC\MR \HL \stoptabulate However, I need one of these tables to split over adjacent pages, which according to the documentation should be achievable with \setuptabulate[split=yes] However, that does not seem to work in connection with the \placetable line. That is, if I put that last line in front of the block mentioned above, the table does still not split across adjacent pages. I have to remove the \placetable line for the \setuptabulate line to have any effect, except then I loose my caption and can no longer cross-reference to table either. Any clues? Thank you, Malte.

2 1

xits font: some spacing and scaling problems
by Andreas Mang 02 Oct '12

02 Oct '12

Hi there, Not quite sure if this is the right place. I wanted to send this directly to Khaled Hosny, but then I thought it might be good to have some additional opinion on some of these issues (I am not quite sure if some of this is intended behaviour). I have collected some examples for which I think there are some scaling and spacing problems in xits. Also, small caps are not supported. Is this intended?! Thanks for your help. Cheers, Andreas %%%%%%%%%%%% MINIMAL EXAMPLE %%%%%%%%%%%% \setupbodyfont[xits,11pt] \starttext $\diamond$ % too small?! $\square$ % OK?! $\blacktriangleright$ % too big?! $\blacktriangleleft$ % too big?! $\blacktriangle$ % too big?! $\blacktriangledown$ % too big?! {\sc Word} % not supported ?! $\tilde{W}^i$ $W^i$ % using a superscript in case % an accent is used results in % a too small distance between letter % and superscript $f^i$ % distance too small (seems to be just the case for $f$, see e.g. $h^i$ $t^i$) \stoptext %%%%%%%%%%%% MINIMAL EXAMPLE %%%%%%%%%%%%

3 4