Re: [NTG-context] Empty heads after leading whitespace
Avoid vskip. http://wiki.contextgarden.net/Command/vskip ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@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 ___
Re: [NTG-context] Some problems with a new style for the sections
Hi, Sorry, I posted a little too fast for my question I found the answer herehttp://wiki.contextgarden.net/Titleshttp://wiki.contextgarden.net/Titles. Nevertheless, thank you for your response speed. As I said before, I slowly migrates to ConTeXt (which I love!), Without abandoning LaTeX, which explains my confusion in the use of the command. Regards, Fabrice ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@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 ___
Re: [NTG-context] numerator is too high in \frac{3}{4}, in palatino
I just compared MkII and MkIV in this respect, and the MkII fraction
looks more symmetric (more correct) than the MkIV version.
Here is the MkII code:
\usetypescript[palatino][ec]
\setupbodyfont[palatino]
\starttext
\startformula
{3\over4}\quad {1\over2}
\stopformula
\stoptext
I've attached (cropped) images to show the difference.
Another difference is in the fonts. For the MkII version, pdffonts gives
IVJLXF+TeXGyrePagella-RegularType 1Custom yes
yes no 4 0
IVJLXF+TeXGyrePagella-RegularType 1Custom yes
yes no 5 0
For the MkIV version, pdffonts shows a math font (maybe for the
thicker fractional bar):
EUEJAR+TeXGyrePagella-RegularCID Type 0C Identity-H yes
yes yes 18 0
UPBTGS+TeXGyrePagellaMath-RegularCID Type 0C Identity-H yes
yes yes 19 0
If you have suggestions for how to change, slightly, the numerator and
denominator placement when using alatino, let me know.
Maybe the entire problem is that the division line is thicker in
Palatino math than in the text font, and maybe sits below the math axis
(so it gets too close to the denominator)?
-Sanjoy
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@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
___
[NTG-context] [Metapost] Using mkIV and metapost to produce SVG
Dear all,I would like to produce an svg file from a Metapost input file using some of ConTeXt's typesetting features (esp. using System OTF Fonts) using something like:\startbuffer[buffer:dummy] \start\startcolor[white]\framed[align=middle,width=28mm,frame=off]{ \SansBodyBold % Font definition done earlier Test to \par rendered \par}\stopcolor \stop\stopbuffer% \startuniqueMPgraphic{mp:margin} picture text; text := btex \getbuffer[buffer:dummy] etex; draw text shifted(-11.8mm,-4.8mm ); % Some more fancy drawing her\stopuniqueMPgraphicCan I render that with MetaPost to SVG?Is it possible to render text as paths not as referenced glyphs in MetaPost/ConTexT?Unfortunately I have to stick to SVG as the resulting output format.Converting from PDF to SVG is not an option at the moment due a) performance considerations and b) trouble with generated font names in the resulting ConTeXt PDF file (inkscape as well as pdf2svg produce real strange results).Please let me know, if you need furhter information.Thank you very much in advance.Kind regards,Ralf
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@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
___
[NTG-context] Empty heads after leading whitespace
Avoid vskip. Do you have a better solution? ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@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 ___
Re: [NTG-context] linebreaks and cell width in xtables
On 05/05/2014 12:20 AM, Rik Kabel wrote: [...] which shows a problem in row 2. When I add \\ to the first line of text in row 2 column 1, as shown here [...] which perhaps has some faults in the vertical spacing, but is much better than the original. The spacing can be improved by specifying [align=lohi] for that cell. Many thanks for your reply, Rik. Now I got what I was doing wrong. I get the same result with the other two methods I suggested. Is there a reason that you cannot use one of these methods in row 2 as you do in row 1? Well, that was a minimal sample. I have a document that has many over 50 tables. If that means that I have to add lines in every row that suffers from this feature, I think I might be doing something wrong. There is a more basic problem not shown in the samples: cells can contain paragraphs with multiple lines (such as \input zapf). Is the user supposed to insert line breaks manually in paragraphs containing multiple lines? Perhaps we would all benefit from an obeylines alignment option? Sorry, but I cannot refrain from asking: isn’t this a bug? Many thanks for your help, Pablo -- http://www.ousia.tk ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@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 ___
[NTG-context] Calling fonts (was: Hebrew vowel placement in ConTeXt)
... 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
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@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
___
Re: [NTG-context] Calling fonts (was: Hebrew vowel placement in ConTeXt)
Am 05.05.2014 um 17:29 schrieb Michael Ash m...@econs.umass.edu:
... 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)?
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
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@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
___
[NTG-context] Head titles and section blocks bug in s-pre-60.tex module
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. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@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 ___
Re: [NTG-context] Calling fonts (was: Hebrew vowel placement in ConTeXt)
On 2014-05-05 11:29, Michael Ash wrote:
... 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
Michael,
Wolfgang already answered most of your questions, at least by the
expedient means of teaching a man to fish. However, not all of the
questions are answered in the font manuals, and in particular your
question about the font fallbacks. (The word setups does not appear in
mfonts, and fallback appears once. In the MKIV font manual setups
appears once and fallback thrice. None provide your answer.)
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.
Setups are at their simplest a way to bundle other commands for reuse.
They also provide a namespace mechanism and a mechanism for group
setting and resetting of values.
The ConTeXt source file type-fbk.mkiv (and undoubtedly something similar
for MKII) defines a set of font name synonyms in a font:fallback:
namespace that is useful for gracefully substituting one font for
another when required, as when the document calls for a bold italic but
the font in use does not have that style. You can leave this out, or
define your own fallback hierarchy if you wish.
So, the first part of the typescript above defines ezrasil as a synonym
for the serif face and associates it with the file sileot and certain
otf features labeled hebrew. The file naming and search mechanism are
well described in the manuals. The setups brings in the standard set of
substitutions that will be applied when the document calls for serif
styles that the specific font does not offer.
The second part of the typescript defines another synonym (confusingly
also ezrasil) for the typeface and includes in it only a roman face
definition. In a latin script there would likely be another
definetypeface for the sans face, another for the mono face, and a
fourth for the math
Re: [NTG-context] linebreaks and cell width in xtables
On 5/5/2014 4:48 PM, Pablo Rodriguez wrote: On 05/05/2014 12:20 AM, Rik Kabel wrote: [...] which shows a problem in row 2. When I add \\ to the first line of text in row 2 column 1, as shown here [...] which perhaps has some faults in the vertical spacing, but is much better than the original. The spacing can be improved by specifying [align=lohi] for that cell. Many thanks for your reply, Rik. Now I got what I was doing wrong. I get the same result with the other two methods I suggested. Is there a reason that you cannot use one of these methods in row 2 as you do in row 1? Well, that was a minimal sample. I have a document that has many over 50 tables. If that means that I have to add lines in every row that suffers from this feature, I think I might be doing something wrong. There is a more basic problem not shown in the samples: cells can contain paragraphs with multiple lines (such as \input zapf). Is the user supposed to insert line breaks manually in paragraphs containing multiple lines? Perhaps we would all benefit from an obeylines alignment option? Sorry, but I cannot refrain from asking: isn’t this a bug? more a side effects of trying to find some optimal width automatically ... i've tried to 'fix' it in the next beta but who knows what else shows up - 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 - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@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 ___
[NTG-context] Calling fonts (was: Hebrew vowel placement in ConTeXt)
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 ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@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 ___
Re: [NTG-context] linebreaks and cell width in xtables
On 05/05/2014 08:45 PM, Hans Hagen wrote: On 5/5/2014 4:48 PM, Pablo Rodriguez wrote: [...] Sorry, but I cannot refrain from asking: isn’t this a bug? more a side effects of trying to find some optimal width automatically ... i've tried to 'fix' it in the next beta but who knows what else shows up Many thanks for your reply and the fix, Hans. Pablo -- http://www.ousia.tk ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@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 ___
Re: [NTG-context] Calling fonts
On 5/5/2014 8:37 PM, Rik Kabel wrote:
On 2014-05-05 11:29, Michael Ash wrote:
... 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
Michael,
Wolfgang already answered most of your questions, at least by the
expedient means of teaching a man to fish. However, not all of the
questions are answered in the font manuals, and in particular your
question about the font fallbacks. (The word setups does not appear in
mfonts, and fallback appears once. In the MKIV font manual setups
appears once and fallback thrice. None provide your answer.)
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.
Setups are at their simplest a way to bundle other commands for reuse.
They also provide a namespace mechanism and a mechanism for group
setting and resetting of values.
The ConTeXt source file type-fbk.mkiv (and undoubtedly something similar
for MKII) defines a set of font name synonyms in a font:fallback:
namespace that is useful for gracefully substituting one font for
another when required, as when the document calls for a bold italic but
the font in use does not have that style. You can leave this out, or
define your own fallback hierarchy if you wish.
So, the first part of the typescript above defines ezrasil as a synonym
for the serif face and associates it with the file sileot and certain
otf features labeled hebrew. The file naming and search mechanism are
well described in the manuals. The setups brings in the standard set of
substitutions that will be applied when the document calls for serif
styles that the specific font does not offer.
The second part of the typescript defines another synonym (confusingly
also ezrasil) for the typeface and includes in it only a roman face
definition. In a latin script there would likely be another
definetypeface for the sans face, another for the mono face, and a
fourth for the math face.
Re: [NTG-context] Empty heads after leading whitespace
\setuphead
[section]
[placehead=empty,
page=yes,
after={\blank[0em]\blank[disable]}]
That works for me. I don't know if it is better, but if it works for
you as well then it is probably the way to go.
mtx-context | current version: 2014.01.03 00:40
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@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
___
