Hello,
i have made a typescript which works. the only thing is that i have in my
typescript something like:
\startsetups [fallbackfonts]
…
\stopsetups
\starttypescript [bla]
\setups[fallbackfonts]
…
\stoptypescript
referring in my document to the typescriptfile with
On Sat, 29 May 2010 14:11:44 +0200 Alan BRASLAU wrote:
uname -suname -muname -p
Intel Q9400 (Core2 Quad):
FreeBSD amd64 amd64
GNU/kFreeBSDx86_64 amd64
Linux x86_64 unknown
32bit os
Am 30.05.10 01:33, schrieb Rogutės Sparnuotos:
Hello,
Could someone please confirm that it is ok to use \def like this:
\def\ru{\switchtobodyfont[cyr]\language[ru]}
\starttext
\item {\ru Эйхенбаум, Борис. {\it Теория «формального метода»}.}
Some other text in the main
Am 30.05.10 10:18, schrieb Bernhard Rosensteiner:
Hello,
i have made a typescript which works. the only thing is that i have in my
typescript something like:
\startsetups [fallbackfonts]
…
\stopsetups
\starttypescript [bla]
\setups[fallbackfonts]
…
\stoptypescript
referring in my document
ok i have boiled it down as minimal as possible (2 files in attachment). I have
commented out line 123 in my typescript:
%\definefontsynonym[SansSubhead-SemiBold]
[file:CronosPro-SemiboldSubh] [features=default]
so according to my \startsetups[font:optical:sans:fallback] (line
Michael Saunders wrote:
In addition, everything involving inferiors, superiors, numerators and
denominators is now broken. For example:
\definefontfeature[in][body][sinf=yes]%inferior
Cs{\setff{in}133}
has no effect.
This depends on whether the font supports the sinf feature. The
default
How is the [body] feature defined?
\definefontfeature[body][default][onum=yes,pnum=yes,calt=yes,protrusion=quality,expansion=quality]
\definefontfeature[in][body][sinf=yes]%inferior
\definefontfeature[su][body][sups=yes,ordn=yes]%superior
\definefontfeature[nu][body][numr=yes]%numerator
Hello,
What \stelinterliniein means in the following (taken from Skdk style).
\def\StartTitlePage%
{\startstandardmakeup[doublesided=no]
\setupbackgrounds[header][text][background=]
\switchtobodyfont[ss,18pt]
\setupalign[right]
\setupindenting[0pt]
\stelinterliniein
\vfil
Am 30.05.10 13:45, schrieb Vyatcheslav Yatskovsky:
Hello,
What \stelinterliniein means in the following (taken from Skdk style).
\def\StartTitlePage%
{\startstandardmakeup[doublesided=no]
\setupbackgrounds[header][text][background=]
\switchtobodyfont[ss,18pt]
\setupalign[right]
Thank you, Wolfgang, but I gen an error with this:
\setuphead
[Part]
[number=no,
style={\ss\bfd}]
%page=right]
\def\StartTitlePage
{\startstandardmakeup[doublesided=no,align=right,style={\switchtobodyfont[ss,18pt]}]
\setupbackgrounds[header][text][background=]
Am 30.05.10 14:56, schrieb Vyatcheslav Yatskovsky:
\setuphead
[Part]
[number=no,
style={\ss\bfd}]
%page=right]
\definehead[TitlePage][Part]
Use 'part' not 'Part'.
Wolfgang
___
If your question is of
On 29-5-2010 6:58, Yury G. Kudryashov wrote:
Hi!
Unicode subscripts do not work (at least, in math):
\starttext
$a₀₁₂₃₄₅₆₇₈₉₋₌₊$
\stoptext
prints only a. The file char-def.lua contains block like this:
[0x2080]={
category=no,
description=SUBSCRIPT ZERO,
direction=en,
Am 30.05.10 15:32, schrieb Vyatcheslav Yatskovsky:
Use part in both occasions?
It works, but gives blank page:
\setuphead
[part]
[number=no,
style={\ss\bfd}]
%page=right]
\def\StartTitlePage
{\startstandardmakeup[doublesided=no,align=right,style={\switchtobodyfont[ss,18pt]}]
Hans Hagen wrote:
On 29-5-2010 6:58, Yury G. Kudryashov wrote:
Hi!
Unicode subscripts do not work (at least, in math):
P.S.: Superscript digits work. Probably, the font contains ¹ but not ₁.
in which case ... do you expect that glyph? or maybe one special for
math? and does its size
On Sun, May 30, 2010 at 03:35:12PM +0200, Hans Hagen wrote:
On 29-5-2010 6:58, Yury G. Kudryashov wrote:
Hi!
Unicode subscripts do not work (at least, in math):
\starttext
$a₀₁₂₃₄₅₆₇₈₉₋₌₊$
\stoptext
prints only a. The file char-def.lua contains block like this:
[0x2080]={
On 30-5-2010 5:01, Khaled Hosny wrote:
Those characters are not intended for use as real sub/superscripts, they
are their for round trip compatibility (AKA the source of all Unicode
discrepancies).
indeed, which is why using them is on user's own risk
Hans
On 30-5-2010 4:52, Yury G. Kudryashov wrote:
Hans Hagen wrote:
On 29-5-2010 6:58, Yury G. Kudryashov wrote:
Hi!
Unicode subscripts do not work (at least, in math):
P.S.: Superscript digits work. Probably, the font contains ¹ but not ₁.
in which case ... do you expect that glyph? or maybe
Thank you, Wolfgang, with this correction it works fine!
A few questions, if you don't mind:
1) what \setupinterlinespace
\let\\=\blank
means? I thought this setup can accept only values in brackets; I don't
understand this construct.
2) Why I cannot use Part (with capital P)?
3) I
Thanks, I added the line to the \@@bk block in str-flt.mkiv, but I
don't know how to remake the formats. I tried:
mtxrun --script fonts --reload
luatools --generate
texexec --make --all
texexec --make --all --pdftex
texexec --make --all --xetex
luatools --generate
luatools --ini --compile
Am 30.05.10 18:45, schrieb Vyatcheslav Yatskovsky:
Thank you, Wolfgang, with this correction it works fine!
A few questions, if you don't mind:
1) what \setupinterlinespace
\setupinterlinespace comes in two version, with the complex version
you can change the values for the lineheight, e.g.
Hello everybody and esp. Mojca,
I started updating my Windows installer code to include --extras
switch. Unfortunately, I found that mtxrun.cmd does not exist anymore
and is replaced by mtxrun.exe. Moreover, mtxrun.exe is not working at
all, complaining mtxrun: unable to locate texlua.exe on
Michael Saunders wrote:
How is the [body] feature defined?
\definefontfeature[body][default][onum=yes,pnum=yes,calt=yes,protrusion=quality,expansion=quality]
Please add script=latn, that works for Palatino Nova, and I think
there possibly was in change in that a while back (some months).
Wolfgang, Vyatcheslav,
thank you for debugging my ancient Skdk style!
If you fix it in the wiki, please also remove all those broken links...
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
Please add script=latn, that works for Palatino Nova, and I think
there possibly was in change in that a while back (some months).
Thanks, I have added script=latn to \definefontfeature[body], but
those Open Type features still aren't back to normal. I should have
mentioned that I had:
Michael Saunders wrote:
Please add script=latn, that works for Palatino Nova, and I think
there possibly was in change in that a while back (some months).
Thanks, I have added script=latn to \definefontfeature[body], but
those Open Type features still aren't back to normal. I should have
There is no test file, and I still do not know which font you are
using. Attempting to find the problem is closer to tea-gazing
than to debugging at the moment. Font features cannot be debugged
independent of the actual font.
Thanks, I understand. I had been using GaramondPremrPro (which has
On 30 May 2010, at 10:18, Bernhard Rosensteiner wrote:
Hello,
i have made a typescript which works. the only thing is that i have in my
typescript something like:
\startsetups [fallbackfonts]
…
\stopsetups
\starttypescript [bla]
\setups[fallbackfonts]
…
\stoptypescript
On 30-5-2010 10:36, Michael Saunders wrote:
There is no test file, and I still do not know which font you are
using. Attempting to find the problem is closer to tea-gazing
than to debugging at the moment. Font features cannot be debugged
independent of the actual font.
Thanks, I understand. I
you can try
mtxrun --script font --list --info garamondpremrpr
...
to see what happens with features
Thanks. This seems to confirm that the features are there:
MTXrun | dnom cyrl dflt
MTXrun | grek dflt
MTXrun | latn aze crt deu dflt fra ita mol rom srb
On 30-5-2010 11:24, Michael Saunders wrote:
you can try
mtxrun --script font --list --info garamondpremrpr
to see what happens with features
Thanks. This seems to confirm that the features are there:
MTXrun | dnom cyrl dflt
MTXrun | grek dflt
MTXrun |
add mode=node to the 'body' feature definitions
I added it. I get the same results.
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
31 matches
Mail list logo
