- ntg-context - Mailing Lists

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