- ntg-context - NTG Mailing Lists

Empty heads after leading whitespace
by Maggyero 06 May '14

06 May '14

> after={\blank[0em]\blank[disable]}] Yes it also works, thank you Thangalin. So here is the final solution (I have added the 'nowhite' keyword in the second blank to kill whitespaces when they are active) to get real empty heads (sections here) in the document: \setupwhitespace[line] \setuphead [section] [placehead=empty, page=yes, after={\blank[none]\blank[nowhite, disable]}] \setuphead [subsection] [placehead=yes, before={\blank[line]}, after={\blank[line]}] \setupheadertexts[section] \showframe \starttext \completecontent \dorecurse{2} {\section{My section} \dorecurse{2} {\subsection{My subsection} \input knuth}} \stoptext

1 0

Calling fonts (was: Hebrew vowel placement in ConTeXt)
by Michael Ash 05 May '14

05 May '14

> > ... see message 56606 > <http://www.mail-archive.com/ntg-context%40ntg.nl/msg56606.html> in the > list archive. This is not the post-simplefonts solution, but the > pre-simplefonts solution. It does allow much better control over all of > the fonts that make up the typeface (using ConTeXt terminology). > If you set only some Hebrew/Aramaic/Arabic, and especially if you do not > need font variants (bold, italic, ...) you might prefer to define a > single font. Thank you very much again. This was helpful, and here is my minimal working example: \definefontfeature[hebrew][default][script=hebr,ccmp=yes] \definefont [myhebrew] [SILEOTSR.ttf*hebrew] \setupdirections[bidi=on,method=two] \starttext Here is the first line of the Bible. {\myhebrew בְּרֵאשִׁ֖ית בָּרָ֣א אֱלֹהִ֑ים אֵ֥ת הַשָּׁמַ֖יִם וְאֵ֥ת הָאָֽרֶץ׃ } \stoptext I still have some questions. It took me a long time to understand that \definefont [myhebrew] [SILEOTSR.ttf*hebrew] would use the fontfeature "hebrew" that I had defined together with the font file SILEOTSR.ttf and assign this pairing to the nickname "myhebrew". Rik's example also has "sa 1" which I do not understand. \definefontfeature [aramaic] [default][ccmp=yes,script=hebr] \definefont [aramaic] [KeterYG-Medium.ttf*aramaic sa 1] Is the syntax for definefont using "*" documented somewhere? Is it similar to definefontsynonym at http://wiki.contextgarden.net/Fonts_in_LuaTeX (and below)? I also do not understand the full syntax from the referenced message. Here is my best effort to annotate it, but I would appreciate corrections or additions %% The following defines the fontfeature "hebrew" %% which can then be applied to a font. %% definefontfeature is documented at %% http://wiki.contextgarden.net/Command/definefontfeature %% and the available features are specific to the font %% e.g. http://www.microsoft.com/typography/otspec/featurelist.htm \definefontfeature[hebrew][default][script=hebr,ccmp=yes,mark=yes] %% I am confused below. When was font:fallback:serif defined? %% Why file: but features= ? %% How will the fontsynonym "Serif" function? \starttypescript [serif] [ezrasil] \setups[font:fallback:serif] \definefontsynonym [Serif] [file:sileot] [features=hebrew] \stoptypescript %% Still confused \starttypescript [ezrasil] \definetypeface [ezrasil] [rm] [serif] [ezrasil] [default] \quittypescriptscanning \stoptypescript %% Sets the main body to the font %% that has been named and given features \setupbodyfont[ezrasil] %% Would an alternative at this point be to use %% \definefont [myezrasil] [ezrasil] %% to define a single font and then use {\myezrasil בְּרֵאשִׁ֖ית} for short passages \setupalign[r2l] \starttext בְּרֵאשִׁ֖ית בָּרָ֣א אֱלֹהִ֑ים אֵ֥ת הַשָּׁמַ֖יִם וְאֵ֥ת הָאָֽרֶץ׃ \stoptext Thank you again for your guidance. Best, Michael

4 3

linebreaks and cell width in xtables
by Pablo Rodriguez 05 May '14

05 May '14

Dear list, I have the following sample: \starttext \startxtable[option=stretch] \startxrow \startxcell One line And another \stopxcell \startxcell This breaks the following cell. \stopxcell \stopxrow \startxrow \startxcell This cell has multiple lines. Vertical spacing is wrong. \stopxcell \startxcell What am I missing? \stopxcell \stopxrow \stopxtable \stoptext I don’t know whether this is a bug. My question is the following: how can I get a new line inside a cell? I have another question: how can I force that both rows (in this case two) have the same width? Many thanks for your help, Pablo -- http://www.ousia.tk

4 7

Calling fonts (was: Hebrew vowel placement in ConTeXt)
by Michael Ash 05 May '14

05 May '14

Wolfgang and Rik Thank you very much. This was exactly what I needed. I'll add these to http://wiki.contextgarden.net/Fonts_in_LuaTeX Michael > You can find a description about the options in the old and new fonts > manuals: > > - http://pragma-ade.com/general/manuals/mfonts.pdf > - http://pragma-ade.com/general/manuals/fonts-mkiv.pdf > > Wolfgang > > > Font definition in ConTeXt allows extreme degrees of indirection. There > is a lot of flexibility that follows from this. By defining synonyms > such as serif and serifbold and using these in the document, the > document can be written independently of the actual fonts used. The > names are to some degree arbitrary, but used conventionally. There is > nothing stopping you from placing a sans font at the end of a chain of > serif references. > Rik >

1 0

Head titles and section blocks bug in s-pre-60.tex module
by Maggyero 05 May '14

05 May '14

Hans, I think there is a bug in your s-pre-60.tex module regarding the step mechanism interacting with section blocks: the head titles disappear each time ConTeXt starts a new section block. I have found a way to solve this problem by putting \StartSteps\StopSteps (empty pair, and it works also with \StartStep\StopStep empty pair) right after the start of each section block, like this for instance: \startbodymatter\StartSteps\Stopsteps blablabla \stopbodymatter. Could you correct this? Here is a minimal example illustrating the problem: \usemodule[pre-60] \setupinteraction[state=start] \starttext \startfrontmatter \startsection[title=My frontmatter section] % <-- Title displayed: fine. \StartSteps \startitemize \item my item\FlushStep \item my item\FlushStep \item my item\FlushStep \stopitemize \StopSteps \stopsection \stopfrontmatter \startbodymatter \startsection[title=My bodymatter section] % <-- Title NOT displayed: bug? \StartSteps \startitemize \item my item\FlushStep \item my item\FlushStep \item my item\FlushStep \stopitemize \StopSteps \stopsection \stopbodymatter \startbackmatter \startsection[title=My backmatter section] % <-- Title NOT displayed: bug? \StartSteps \startitemize \item my item\FlushStep \item my item\FlushStep \item my item\FlushStep \stopitemize \StopSteps \stopsection \stopbackmatter \startappendices \startsection[title=My backmatter section] % <-- Title NOT displayed: bug? \StartSteps \startitemize \item my item\FlushStep \item my item\FlushStep \item my item\FlushStep \stopitemize \StopSteps \stopsection \stopappendices \stoptext Regards.

1 0

Some problems with a new style for the sections
by Fabrice Couvreur 05 May '14

05 May '14

Hi, I encounter two problems : - Section numbers are not red ; - Calling the second section does not cause the creation of a new paragraph. Regards, Fabrice \setupcolors[state=start] \def\MySectionCommand#1#2% {\framed [frame=off, width=\textwidth, align={right}, background=color, backgroundcolor=lightgray] {#1\quad#2}} \setuphead[section][command=\MySectionCommand,numbercolor=red] \setupbodyfont[palatino,12pt] \starttext \MySectionCommand{A.}{Définitions} \input knuth \MySectionCommand{1.}{Propriétés} \input knuth

5 4

Empty heads after leading whitespace
by Maggyero 05 May '14

05 May '14

For those who are interested, I've finally solved my problem (the vertical space before a subsection which was not automatically swallowed at the top of a page when the page started with an empty section) by using the pair 'after={\vskip 0em\blank[disable]}' for sections: \setuphead [section] [placehead=empty, page=yes, after={\vskip 0em\blank[disable]}] \setuphead [subsection] [placehead=yes, before={\blank[line]}, after={\blank[line]}] \setupheadertexts[section] \showframe \starttext \completecontent \dorecurse{2} {\section{My section} \dorecurse{2} {\subsection{My subsection} \input knuth}} \stoptext

2 1

Re: [NTG-context] Proper setting of font features for protrusion/expansion
by Hans Hagen 04 May '14

04 May '14

On 5/4/2014 10:41 PM, Jan Tosovsky wrote: > On 2014-05-04 Wolfgang Schuster wrote: >> Am 04.05.2014 um 19:34 schrieb Jan Tosovsky: >> >>> In my code I use the following shortcut found somewhere: >>> >>> \definefontfamily[palatino][rm][Palatino Linotype][features={default, >>> quality}] >>> >>> Is there any description what that '[features={default, quality}]' >>> option really does? >> >> When you apply features to a font you can set a list of features and >> all of them will be applied. >> >> In the example below you can see both methods, the first text uses the >> new featurelist "testfeature" which uses "default" and extends it with >> "protrusion=quality". The second text applies the two predefined lists >> "default" and "quality" (which sets "protrusion=quality" >> and "expansion=quality"). >> >> \definefontfeature[testfeature][default][protrusion=quality] >> ... >> \startfont[Serif*testfeature] >> ... >> \startfont[Serif*default,quality] > > Aahh, thanks. > > So it is the preset name what confused me here... From my POV the 'quality' > should be replaced with the more specific label. I believe it will enhance > readability the code. I can imagine even 'microtypography' for this kind of > preset. quality is just a tag for a preset ... on can add his/her own btw, i have no clue what micro or typography is involved (esp when excessive values are used) ,,, using that term for a preset would be rather confusing > Jan > > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an entry to the Wiki! > > maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://tex.aanhet.net > archive : http://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > ___________________________________________________________________________________ > -- ----------------------------------------------------------------- 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] Proper setting of font features for protrusion/expansion
by Wolfgang Schuster 04 May '14

04 May '14

Am 04.05.2014 um 19:34 schrieb Jan Tosovsky <j.tosovsky(a)email.cz>: > Dear All, > > > e.g. in the last example at http://wiki.contextgarden.net/Protrusion there > is the following definition: > > \definefontfeature[default][default][expansion=quality,protrusion=quality] > > > I understand it overrides default settings and adds these two features. > > In my code I use the following shortcut found somewhere: > > \definefontfamily[palatino][rm][Palatino Linotype][features={default, > quality}] > > > Both features works, but I am not sure if I am getting the best quality. > > Is there any description what that '[features={default, quality}]' option > really does? When you apply features to a font you can set a list of features and all of them will be applied. In the example below you can see both methods, the first text uses the new featurelist “testfeature” which uses “default” and extends it with “protrusion=quality”. The second text applies the two predefined lists “default” and “quality” (which sets “protrusion=quality” and “expansion=quality”). \setupalign[hanging] \definefontfeature[testfeature][default][protrusion=quality] \showframe[text][text] \starttext \startfont[Serif*testfeature] \input knuth \stopfont \startfont[Serif*default,quality] \input knuth \stopfont \stoptext Wolfgang

2 1

Proper setting of font features for protrusion/expansion
by Jan Tosovsky 04 May '14

04 May '14

Dear All, e.g. in the last example at http://wiki.contextgarden.net/Protrusion there is the following definition: \definefontfeature[default][default][expansion=quality,protrusion=quality] I understand it overrides default settings and adds these two features. In my code I use the following shortcut found somewhere: \definefontfamily[palatino][rm][Palatino Linotype][features={default, quality}] Both features works, but I am not sure if I am getting the best quality. Is there any description what that '[features={default, quality}]' option really does? Thanks, Jan

1 0