- ntg-context - Mailing Lists

(critical edition) compressseparatorbefore and compressseparatorafter
by Pablo Rodriguez 18 Nov '13

18 Nov '13

Dear Thomas, Luigi and Hans, code first: \definepapersize[mine][width=3in,height=2in] \setuppapersize[mine] \definelinenote[Variant] \setupnote[Variant][paragraph=yes, inbetween=\hskip2.5em] \setupnotation[Variant][alternative=serried,distance=1em,compress=yes, width=broad] \starttext \startlinenumbering This\Variant{That} context\Variant{document} is\Variant{was} a sample\Variant{an example} that I\Variant{she} want\Variant{didn’t want} to show\Variant{publish}\stoplinenumbering \stoptext With compressed linenotes (when compressseparator isn’t set to none), I think is important to have the ability to specify different lengths for the compressseparator than for the linenotes. If neither of them is defined, compressseparatorbefore should have the same value as inbetween from setupnote and compressseparatorafter should take its value from distance in setupnotation. But with the sample above, I think that the spacing that can make sense for line numbers might be visually misleading for separators. Here I’m only an amateur, Thomas, you are the professional. What do you think of this feature? Many thanks for your help, Pablo -- http://www.ousia.tk

1 0

Re: [NTG-context] ToC - right-alignment of roman numerals
by Jan Tosovsky 18 Nov '13

18 Nov '13

> On 2013–06–03 honyk wrote: > in fresh MkIV I use the following commands for building ToC, but I > have no idea how to align the label (roman numeral) to the right. I am almost there, but things get complicated when chapters are combined with preface/index titles without numbering and thus aligned improperly: \setupcombinedlist[content][list=chapter, alternative=c] \setupcombinedlist[chapter][ distance=1em, width=1cm, numbercommand={\simplealignedbox{\listparameter{width}}{flushright}}, ] \starttext \completecontent \startfrontmatter \chapter{Preface}text \stopfrontmatter \startbodymatter \chapter{Chapter}text\index{primary} \stopbodymatter \startbackmatter \completeindex \stopbackmatter \stoptext Is there any way how to indent these non-numbered titles so that they start where the chapter title starts? Thanks, Jan

1 0

(critical edition) not hyphenated body with linenotes
by Pablo Rodriguez 18 Nov '13

18 Nov '13

Dear Thomas, Luigi and Hans, here is my first sample to the critical edition project of Thomas. I think it is a bug. This is the code: \setuppapersize[A8] \starttext \startlinenumbering This text shows a \startlinenote[one]{bariant H} variant \stoplinenote[one]. This text shows a \startlinenote[two]{bariant H}variant\prewordbreak\stoplinenote[two]. \stoplinenumbering \stoptext Last word from body text from linenote isn’t hyphenated unless \prewordbreak is added. Could you add this internally, so it isn’t required to add it to every linenote? Many thanks for your help, Pablo -- http://www.ousia.tk

1 0

Re: [NTG-context] ToC - right-alignment of roman numerals
by Jan Tosovsky 18 Nov '13

18 Nov '13

On 2013-11-17 Jan Tosovsky wrote: > On 2013-06-03 Marco Patzer wrote: > > On 2013–06–03 honyk wrote: > > > > > in fresh MkIV I use the following commands for building ToC, but I > > > have no idea how to align the label (roman numeral) to the right. > > > > The width setting needs to be applied to the chapter list, not the > > content list, see example > > > > \setuphead[chapter][conversion=Romannumerals] > > \setupheadnumber[chapter][48] > > > > \setupcombinedlist > > [content] > > [alternative=c] > > > > \setupcombinedlist > > [chapter] > > [distance=1em, > > width=1cm, > > numbercommand={\simplealignedbox{\listparameter{width}}{flushright}} > > ] > > > > \starttext > > \completecontent > > \chapter{Foo} > > \chapter{Bar} > > \stoptext > > > > Whereas this works for basic test cases, in my document it ends with an > error: > > structure > sectioning > title @ level 2 : 0.0 -> \headtext > {content} > ! Argument of \147>flushright has an extra }. There was a missing comma after the numbercommand parameter! Strange... Jan

1 0

Re: [NTG-context] Chapter numbering - applying several commands at once
by Wolfgang Schuster 17 Nov '13

17 Nov '13

Am 17.11.2013 um 20:02 schrieb Jan Tosovsky <j.tosovsky(a)tiscali.cz>: > Dear All, > > in my book I'd like to precede my titles with the number formated as > 'CHAPTER I.', e.g. roman numeral and all this small caped and also in bold > as the title itself. > > In the following definition I can use either: > (1) \sc + \setcharactercasing - small caps + lowercased number (but not > bold) > (2) \smallcaps - bold small caps (but not lowercased number) > (3) \setcharactercasing - lowercased number (but not small caps) > > Idealy I'd like to combine \smallcaps + \setcharactercasing, but this throws > an error. > > I am also considering using just smaller font, but I am facing similar > problems as I cannot combine both the casing conversion and e.g. \bfb in > single \groupedcommand. > > I prefer setting the upercased version of Romannumerals as I do not want > small roman literals in the TOC or bookmarks. Are there better ways to > accomplish this? > > \definefontfamily[palatino][rm][Palatino Linotype][features={default, > quality}] > \setupbodyfont[palatino] > > \setuplabeltext[en][chapter=chapter~] > > \setuphead[chapter][ > alternative=middle, > style=\bfc, > conversion=Romannumerals, > numbercommand=\groupedcommand{\sc > \setcharactercasing[word]}{.\blank[0.4cm]}, > ] Inestead of small capitals for the chapter number you can use capitals in combination with a smaller font size. \setuplabeltext[en][chapter=Chapter~] \setuphead [chapter] [alternative=middle, style=\bfc, numberstyle={\setcharactercasing[WORD]\kerncharacters[0.125]\bfa}, numbercommand=\groupedcommand{}{\blank[4mm]}, sectionstopper={.}, inbetween={\blank[4mm]}, conversion=Romannumerals] Wolfgang

2 1

Re: [NTG-context] ToC - right-alignment of roman numerals
by Marco Patzer 17 Nov '13

17 Nov '13

On 2013–06–03 honyk wrote: > in fresh MkIV I use the following commands for building ToC, but I have no > idea how to align the label (roman numeral) to the right. \setuphead[chapter][conversion=Romannumerals] \setupheadnumber[chapter][48] \setupcombinedlist [content] [alternative=c] \setupcombinedlist [chapter] [distance=1em, width=1cm, numbercommand={\simplealignedbox{\listparameter{width}}{flushright}}] \starttext \completecontent \chapter{Foo} \chapter{Bar} \stoptext > In addition, the specified width and distance seem to be somehow > ignored so that label interferes with the title. The width setting needs to be applied to the chapter list, not the content list, see example above. Marco

3 2

Chapter numbering - applying several commands at once
by Jan Tosovsky 17 Nov '13

17 Nov '13

Dear All, in my book I'd like to precede my titles with the number formated as 'CHAPTER I.', e.g. roman numeral and all this small caped and also in bold as the title itself. In the following definition I can use either: (1) \sc + \setcharactercasing - small caps + lowercased number (but not bold) (2) \smallcaps - bold small caps (but not lowercased number) (3) \setcharactercasing - lowercased number (but not small caps) Idealy I'd like to combine \smallcaps + \setcharactercasing, but this throws an error. I am also considering using just smaller font, but I am facing similar problems as I cannot combine both the casing conversion and e.g. \bfb in single \groupedcommand. I prefer setting the upercased version of Romannumerals as I do not want small roman literals in the TOC or bookmarks. Are there better ways to accomplish this? \definefontfamily[palatino][rm][Palatino Linotype][features={default, quality}] \setupbodyfont[palatino] \setuplabeltext[en][chapter=chapter~] \setuphead[chapter][ alternative=middle, style=\bfc, conversion=Romannumerals, numbercommand=\groupedcommand{\sc \setcharactercasing[word]}{.\blank[0.4cm]}, ] \setupcombinedlist[content][list=chapter, alternative=c] \starttext \completecontent \chapter{Foo}text \chapter{Bar}text \stoptext Thanks, Jan

1 0

Re: [NTG-context] Support for Bold Small Caps font alternative
by Wolfgang Schuster 17 Nov '13

17 Nov '13

Am 17.11.2013 um 15:33 schrieb honyk <j.tosovsky(a)email.cz>: > Other OTF features needs to be declared though: > \definefontfeature[f:superscript][sups=yes] > > and then used as written above: > 25 m{\feature[+][f:superscript]2} > > But it is not so big deal. When you use this for units you can use the \unit command: \starttext \unit{25 square meter} \stoptext > <joke>I suggest removing all font styles related descriptions in manuals, wiki pages to some special place marked as obsolete and replace it with this simple approach ending with a small note that if this is not applicable, there are other, but deprecated, ways - with the appropriate hyperlink.</joke>. Not all font provide small caps as font feature, there is still many (older and newer) which use a separate file for them. Wolfgang

1 0

Re: [NTG-context] Support for Bold Small Caps font alternative
by Wolfgang Schuster 17 Nov '13

17 Nov '13

Am 17.11.2013 um 13:23 schrieb honyk <j.tosovsky(a)email.cz>: > On 2013-11-17 Wolfgang Schuster wrote: >> Am 17.11.2013 um 11:04 schrieb honyk <j.tosovsky(a)email.cz>: >>> >>> in my document I combine both regular and bold small caps. >>> As there is no predefined alternative for bold small caps variant, >>> moreover, combining bold style and small caps has no effect, I've >>> had to override an unused one: >>> >>> \definefontsynonym[SerifCaps][file:pala.ttf][features=small-caps] >>> \definefontsynonym[SerifBoldSlanted][file:palab.ttf][features=small- >>> caps] % bold caps >>> >>> Now I can switch styles using \sc and \bs. >>> >>> It would be nice to have a dedicated alternative for this. Or am I >>> missing something? >> >> When you use a opentype font you can enable the small caps feature >> with the \feature command, there is no need for an additional font >> synonym. >> >> \setupbodyfont[pagella] >> >> \starttext >> >> Text {\feature[+][f:smallcaps]Text} {\bf Text >> {\feature[+][f:smallcaps]Text}} >> >> Text \smallcaps{Text} \bold{Text \smallcaps{Text}} >> >> \stoptext > > Thanks for pointing me to this nice feature! This is even more robust. > > All my font definitions are based on this example > http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV You can save a few lines in the font setup when you the new simplefonts code (works only with a recent beta). \definefontfamily[mainface][rm][Palatino Linotype][features={default,quality}] \setupbodyfont[mainface] \setupalign[hanging,hz] \starttext How you, O Athenians, have been affected by my accusers, I cannot tell; but I know that they almost made me forget who I was—so persuasively did they speak; and yet they have hardly uttered a word of truth. Ὅτι μὲν ὑμεῖς, ὦ ἄνδρες Ἀθηναῖοι, πεπόνθατε ὑπὸ τῶν ἐμῶν κατηγόρων, οὐκ οἶδα· ἐγὼ δ' οὖν καὶ αὐτὸς ὑπ' αὐτῶν ὀλίγου ἐμαυτοῦ ἐπελαθόμην, οὕτω πιθανῶς ἔλεγον. \stoptext Wolfgang

2 1

Re: [NTG-context] Support for Bold Small Caps font alternative
by Wolfgang Schuster 17 Nov '13

17 Nov '13

Am 17.11.2013 um 11:04 schrieb honyk <j.tosovsky(a)email.cz>: > Dear All, > > in my document I combine both regular and bold small caps. As there is no > predefined alternative for bold small caps variant, moreover, combining bold > style and small caps has no effect, I've had to override an unused one: > > \definefontsynonym[SerifCaps][file:pala.ttf][features=small-caps] > \definefontsynonym[SerifBoldSlanted][file:palab.ttf][features=small-caps] % > bold caps > > Now I can switch styles using \sc and \bs. > > It would be nice to have a dedicated alternative for this. Or am I missing > something? When you use a opentype font you can enable the small caps feature with the \feature command, there is no need for an additional font synonym. \setupbodyfont[pagella] \starttext Text {\feature[+][f:smallcaps]Text} {\bf Text {\feature[+][f:smallcaps]Text}} Text \smallcaps{Text} \bold{Text \smallcaps{Text}} \stoptext Wolfgang

2 1

Palatino patch for the current ConTeXt version
by honyk 17 Nov '13

17 Nov '13

Hello Everyone, I am trying to fix a Palatino small caps issue using the procedure explained here: http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV That fix seems to be obsolete nowadays and returning errors. I've changed fonts.otf.enhancers.patches["^pala"] to fonts.handlers.otf.enhancers.patches["^pala"] which compiles, but it does nothing. I've also tried this variant, but that 'patch' function is never called even though I clear my font cache every run: \startluacode local fonts = fonts local otf = fonts.handlers.otf local patches = otf.enhancers.patches local register = patches.register local report = patches.report function patch (data,filename) report("I am here") report("processing data %s", table.serialize(data)) end register("after","prepare glyphs","^pala", patch) \stopluacode Any idea? Thanks, Jan

1 0

Support for Bold Small Caps font alternative
by honyk 17 Nov '13

17 Nov '13

Dear All, in my document I combine both regular and bold small caps. As there is no predefined alternative for bold small caps variant, moreover, combining bold style and small caps has no effect, I've had to override an unused one: \definefontsynonym[SerifCaps][file:pala.ttf][features=small-caps] \definefontsynonym[SerifBoldSlanted][file:palab.ttf][features=small-caps] % bold caps Now I can switch styles using \sc and \bs. It would be nice to have a dedicated alternative for this. Or am I missing something? Regards, Jan

1 0

Re: [NTG-context] PDF bookmarks - missing interactivity of some items
by Hans Hagen 16 Nov '13

16 Nov '13

On 11/16/2013 3:41 PM, honyk wrote: > Dear All, > > when bookmarks are placed to my file, only several of them are interactive. > I cannot find any rule for this behaviour nor to reproduce it on a > simplified example. > > \setupinteraction[state=start] > \placebookmarks[chapter] > \setupinteractionscreen[option=bookmark] > > .... > \chapter{Chapter A} > .... > \chapter{Chapter B} > .... > > Is there any known issue related to this? > ConTeXt 2013.11.14 (Mark IV), Windows 7 64-bit. > > I can provide my file for testing (off the list). indeed .. without a minimal test i won't look into it Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Re: [NTG-context] PDF bookmarks - missing interactivity of some items
by Alan Braslau 16 Nov '13

16 Nov '13

On Sat, 16 Nov 2013 15:41:12 +0100 honyk <j.tosovsky(a)email.cz> wrote: > Dear All, > > when bookmarks are placed to my file, only several of them are > interactive. I cannot find any rule for this behaviour nor to > reproduce it on a simplified example. Indeed, I find that the interaction does not always work on some bookmarks. My impression was that, for example, a chapter title might not be interactive whereas its first section title would be interactive. However, I have not been able to produce a minimal example demonstrating the behavior (nor have I really tried very hard yet). Alan

1 0

Index entries - custom font size
by honyk 16 Nov '13

16 Nov '13

Hello Everyone, there are lot of index entries in my document and with the standard body font size they occupy too much space. I've tried to decrease the size by the textstyle parameter. It works, but it is applied recursively to every nested level: secondary items are smaller twice and tertiary items three times... \setupregister[index][command=\Word, textstyle=small] \starttext \index{primary}\index{primary+secondary}\index{primary+secondary+tertiary}Te xt \completeindex \stoptext How can I set the same value to all the levels? Thanks, Jan

1 0

announcement and call
by Thomas A. Schmitz 16 Nov '13

16 Nov '13

Dear list, today, I have an announcement to make and a call for contributions. We have obtained a medium-sized grant at my university to further development of ConTeXt. Specifically, our project wants to facilitate typesetting critical editions after the TEI xml standard and bibliographical data. Luigi will be employed as a full-time developer for the next 6 months (he signed his contract today); Hans will coordinate the work flow. So this is good news. Now for the call for contributions: we invite you to send in examples in those two areas (critical editions, i.e. linenotes cum suis, and bibliographical data, aka bib-module) which show where ConTeXt could be developed. So please send examples to the list that show limitations or bugs, ask for new features, etc. If you want new features in the bibliography department, please do not send vague requests ("it would be nice if we could have hungarian reference systems") but small examples which show a precise feature and a possible syntax for it. Of course, I can't promise that we will be able to act on all your submissions, but I'm optimistic that this project will make our favorite software better! All best Thomas

5 10

PDF bookmarks - missing interactivity of some items
by honyk 16 Nov '13

16 Nov '13

Dear All, when bookmarks are placed to my file, only several of them are interactive. I cannot find any rule for this behaviour nor to reproduce it on a simplified example. \setupinteraction[state=start] \placebookmarks[chapter] \setupinteractionscreen[option=bookmark] ... \chapter{Chapter A} ... \chapter{Chapter B} ... Is there any known issue related to this? ConTeXt 2013.11.14 (Mark IV), Windows 7 64-bit. I can provide my file for testing (off the list). Thanks, Jan

1 0

how to reduce \lineskiplimit in ConTeXt grid layout
by Lars Huttar 15 Nov '13

15 Nov '13

As you know, in plain TeX, \lineskiplimit tunes the vertical glue algorithm by specifying the minimum amount of space between the bottom edge of one line and the top edge of the following line. But in ConTeXt, it appears that \lineskiplimit is set to zero, at least in grid mode. We're using grid mode, and we have some occasional high ascenders, e.g. capital letters with diacritics on top. We have bodyfont size 8.1pt, and interlinespace = 9.3pt. We realize this is less than the recommended ratio of 1.2. Understandably, when those tall characters occur, we sometimes get a blank line above them. It looks like the \lineskiplimit would be violated if the 9.3pt interlinespace were enforced, so ConTeXt adds some space (analogous to \lineskip in TeX?). But since we're on a grid, more space has to be added in order to conform to the grid. All that makes sense, but we would like to be able typeset the lines closer together, and judge for ourselves whether it looks too bad. (When we used to typeset the same text at 8.1pt/9.3pt using mkii, blank lines did not occur.) Is there something similar to \lineskiplimit that we can tweak? I've been reading section 5.5 Line Spacing in the context ref manual, but I don't see anything there about changing a threshold analogous to \lineskiplimit. I tried setting \lineskiplimit=-2pt, but that caused a worse problem: a blank line across both columns, instead of just one. Thanks, Lars Version: mkiv luatex in Tex Live 2013.

2 5

simplefonts: defining a fallback for a non-main font
by Lars Huttar 15 Nov '13

15 Nov '13

Hi again, I'm using simplefonts (TeX Live 2013 version) and I have a main font: \setmainfont[Gentium Book Basic] and I can set a fallback for it, \setmainfontfallback[Gentium Plus][range={ipaextensions}, force=yes, rscale=auto] and that works. But then I have another font for the title: \definesimplefont[titleface][Gentium Basic][size=40pt] How do I set a fallback for it? After looking at the source code for simplefonts, I tried: % undefined cs: \definesimplefontfallback[titleface][Gentium Plus][range={ipaextensions}, force=yes, rscale=auto] % undefined cs: \fontfallback[titleface][Gentium Plus][range={ipaextensions}, force=yes, rscale=auto] % undefined cs: \definefallbackfont[titleface][Gentium Plus][range={ipaextensions}, force=yes, rscale=auto] But they all gave "undefined control sequence" errors. I can work around the problem by setting the main font before the title, using the main font for the title, and then changing the main font after the title is done. But that seems kludgy. Thanks, Lars

3 5

Re: [NTG-context] Index - ranges
by honyk 15 Nov '13

15 Nov '13

On 2013-11-15 honyk wrote: > On 2013-11-12 honyk wrote: > > On 2013-11-07 honyk wrote: > > > > > > 1) when a range for my subject index entry is specified and the > > > text between doesn't overflow to the next page, even in this case > > > the range of pages 1-1 is created. Is there any option to normalize > > > it to a single page number? > > > > > > \startregister[index][range_01]{primary} > > > Dummy text. > > > \stopregister[index][range_01] I've finally found it is caused by this logic: if first == last then if first.references.lastrealpage then -- IMHO this could be optional pagerange(first,first,true,prefixspec,pagespec) else pagenumber(first,prefixspec,pagespec) end elseif last.references.lastrealpage then pagerange(first,last,true,prefixspec,pagespec) else pagerange(first,last,false,prefixspec,pagespec) end Even after normalization, if there is a range, it is preserved regardless it spans multiple pages or not. The fix is quite easy. But whether to convert these single page ranges into a single value or not could be optional, or applied according to the compress parameter (both 'yes' and 'all' would collapse the range). Jan

1 0

Win64 Version of ConTeXt Standalone?
by Bill Meahan 15 Nov '13

15 Nov '13

I'm curious (not complaining). Does a Win64 version of the Standalone suite exist? Certainly the 32-bit binary works fine (the exigencies of WOW64 notwithstanding) but it seems odd to me 64-bit versions for Mac, Linux, FreeBSD or FreeBSD/Debian exist but not a 64-bit Windows version. This seems particularly odd given most laptops/desktops the last few years have been 64-bit with a 64-bit OS even the cheap consumer-grade laptop I bought my wife. Is there a technical reason or simply lack of a maintainer? -- Bill Meahan, Westland, Michigan “Writing is like getting married. One should never commit oneself until one is amazed at one's luck.” —Iris Murdoch

2 1

Is it OK to release the source files of fonts-mkiv.pdf?
by seasoul 15 Nov '13

15 Nov '13

Recently I encountered to the new font manual in mkiv. http://www.pragma-ade.com/general/manuals/fonts-mkiv.pdf I really like the document style: the structure, the page and section design. where could I find the source files, if it is ok to be released to the public. Thanks.

1 0

Re: [NTG-context] Handling index entries with many references
by honyk 15 Nov '13

15 Nov '13

On 2013-06-09 honyk wrote: > > in my book I want to place the index (aka register) of places. > Some of them are mentioned very often (>10). > > In one old book I've found the following solution for this: > in the index there are first three page references listed for > that index entry followed by 'and many' phrase. > > Can something like this be done in the ConTeXt (MkIV)? I found an elegant way for this: \defineprocessor[many][right= and many] This processor is then applied just for the last index entry page reference: \index[many->]{primary} This can be automated in my system. Wow, great! Jan

1 0

"no format found" only with "--jit" option
by stephleg＠free.fr 15 Nov '13

15 Nov '13

Hello, For the same ConTeXt file, if i use the "--jit" option i get the following error: mtx-context | error, no format found with name: cont-en, aborting But when i use no option, there is no error and the PDF is ok. This is with ConTeXt version "2013.11.14 23:22". Regards, Stéphane.

1 0

Re: [NTG-context] Index - ranges
by honyk 15 Nov '13

15 Nov '13

On 2013-11-12 honyk wrote: > On 2013-11-07 honyk wrote: > > > > 1) when a range for my subject index entry is specified and the text > > between doesn't overflow to the next page, even in this case > > the range of pages 1-1 is created. Is there any option to normalize > > it to a single page number? > > > > \startregister[index][range_01]{primary} > > Dummy text. > > \stopregister[index][range_01] > > > I've found a promising option compress=no|yes|all in an experimental > test case located in the strc-reg.mkiv file. The corresponding lua > code seems to be performing some cleanup of page ranges, but when > I define it same way, there is no difference in my output (still 1-1). Looking into the lua code this one is an edge case as normalization is performed if #pages > 1 which is not achieved here. No problem. But I've encountered more serious issue now: When original pages are 'compressed' for the index 114, 117, 119, 122, 130-132, 135, 135-139, 188-204, 321-321 The incorrect result is returned: 114, 117, 119, 122, 130-135, 135-321 I'd expect: 114, 117, 119, 122, 130-132, 135-139, 188-204, 321 Debugging it roughly I've noticed unsorted page numbers before compressing (in collapsedpage function in strc-reg.lua), which leads to unexpected result from first/second comparison. Some kind of page entries sorting might help here. Regards, Jan

1 0