- 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