- ntg-context - Mailing Lists

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 05 May '14

05 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

Re: [NTG-context] Hebrew vowel placement in ConTeXt. (Rik Kabel)
by Michael Ash 04 May '14

04 May '14

Thank you very much for the reply. I switched to ConTeXt standalone and now it is working. Best, Michael This works: \usemodule[simplefonts] \definefontfeature[hebrew][default][script=hebr,ccmp=yes] \setmainfont[Ezra SIL SR][features=hebrew] \setupdirections[bidi=on] \starttext בְרֵאשִ֖ית בָרָ֣א אֱלֹהִ֑ים אֵ֥ת הַשָמַ֖יִם וְאֵ֥ת הָאָֽרֶץ \stoptext BTW what is the \definefontfamily syntax that would work with \setupbodyfont in the new post-simplefonts era? Best, Michael PS Just FYI here is what I had been working with: What platform are you using, what version of Ezra SIL SR (likely 2.51, > but worth asking)? I am using linux (ubuntu 14.04) fonts-sil-ezra package Package fonts-sil-ezra: i 2.51-8 trusty 500 (I presume this means version 2.51.) I am using the current ppa:reviczky/context-daily version of context: ConTeXt ver: 2014.03.25 16:58 MKIV beta fmt: 2014.5.1 int: english/english Here is the error message that I was receiving (when I include "script=hebr"): <+ /usr/share/texmf/tex/context/third/simplefonts/t-simplefonts.lua>)error: /usr/share/texmf/tex/context/base/font-otn.lua:805: attempt to call upvalue 'getprop' (a nil value) > > May I bump? > > > > The following code used to work, but now it gives an error: > > > > \usemodule[simplefonts] > > > \definefontfeature[hebrew][default][mode=node,script=hebr,language=dflt,mark=yes,ccmp=yes] > > \setmainfont[Ezra SIL SR][features=hebrew] > > \setupdirections[bidi=on] > > \starttext > > ?????????? ?????? ????????? ???? ?????????? ?????? ???????? > > \stoptext > > > > The following variant (without "script=hebr") compiles but the vowels > > are misplaced (not centered below the letters), which "ccmp=yes" (see > > http://www.microsoft.com/typography/otspec/features_ae.htm#ccmp) is > > supposed to request: > > > > \usemodule[simplefonts] > > > \definefontfeature[hebrew][default][mode=node,language=dflt,mark=yes,ccmp=yes] > > \setmainfont[Ezra SIL SR][features=hebrew] > > \setupdirections[bidi=on] > > \starttext > > ?????????? ?????? ????????? ???? ?????????? ?????? ???????? > > \stoptext > > > > The problem in definefontfeature seems to be that the feature > > "ccmp=yes" is not taking effect, and the feature "script=hebr" > > generates an error. > > > > Thank you very much for your advice. > > > > Michael > > Michael, > > Sorry to say, no problem here with your example, and trimming the second > line even further to > > \definefontfeature[hebrew][default][script=hebr,ccmp=yes] > > > still produces results with no errors and proper nikkud alignment (run > on a system running Windows 8.1 x64 and ConTeXt standalone 2014-04-28 > standard and jit). > > Similarly, no problem with traditional font definition without simplefonts. > >

2 1

Empty heads after leading whitespace
by Maggyero 04 May '14

04 May '14

Thanks Wolfgang. I could even have sections in the TOC with '\setuptexttexts[{\placerawheaddata[section]}]'. However, how can I start a new page at each new section? The 'page=yes' pair does no longer work with your solution 'placehead=hidden' (since the head is not placed I guess). I also tried 'before=\page' or 'after=\page' without more success. Here is a minimal example showing the absence of page breaks though I specified 'page=yes' (the section numbers are also mismatched but if one puts manual page breaks they match again, so it's not really a problem for me): \setupheadertexts[\namedstructurevariable{section}{title}][] \setuphead [section] [placehead=hidden, page=yes] % <-- This key does NOT work. \setuphead [subsection] [placehead=yes, before={\blank[line]}, after={\blank[line]}] \setuptexttexts[{\placerawheaddata[section]}] \showframe \starttext \completecontent \dorecurse{2} {\section{My section} \dorecurse{2} {\subsection{My subsection} \input knuth}} \stoptext

1 0