[NTG-context] [***SPAM***] Re: Summary of user wishes for streams
This reminds me. Two columns of text over three columns of footnotes. Is it possible? Hans Hagen pra...@wxs.nl: indeed, just multicolumns with page notes in 3 columns My footnotes all end up at the bottom of the last column. ___ 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] Summary of user wishes for streams (Salil Sayed)
This reminds me. Two columns of text over three columns of footnotes. Is it possible? ___ 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] \writetolist fails in footnotes when interaction is on
\setupinteraction[state=start,color=,contrastcolor=,option=fit]
\definelabel[demonum][text=,before=,after=,way=bytext]
\definelist[demos]
\setuplist[demos][interaction=all,alternative=b,after=]
\starttext
\footnote{\writetolist[demos]{\nextdemonum}{demo title}}
\stoptext
Is there a way around this?
___
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] can Context render complex scripts?
next time make a simple example .. you caniidentity features with
mtxrun --script font --info --list --file BNBDOT0N.ttf
anyhow, only one features is applied. It lookslike some gpos feature is not
used.
\usemodule[fnt-20]
\definefontfeature
[indic]
[mode=node,analyze=yes,
script=beng,language=dflt,
% gsub
abvs=yes,akhn=yes,blwf=yes,blws=yes,
half=yes,nukt=yes,pstf=yes,psts=yes,rphf=yes,
% gpos
blwm=yes,abvm=yes]
\definefontsynonym[dwbangla][file:BNBDOT0N.ttf]
\starttext
{\definedfont[dwbangla*indic] সত্যজিৎ রায় \par}
\showotfcomposition
{dwbangla*indic}
{0}
{সত্যজিৎ রায়}
\stoptext
I don't understand---are you saying this is supposed to work? Is the
trick supposed to be using fnt-20 or in being careful not to turn on
unused features? (To be on the safe side, since I was switching
between them in testing, I was turning on all the features Microsoft
calls Indic.) I tried your example and, yes, one shaping looks
correct, but there was no reordering and now some of the characters
print out on top of each other (which is incorrect). I tried the same
routine, using fnt-20 and commenting out unused features, for some
other fonts:
Akaash:
http://www.nongnu.org/freebangfont/downloads.html
Bangla, from the University of Chicago:
http://salrc.uchicago.edu/resources/fonts/available/bengali/
and Arial Unicode MS (standard on Windows),
and I got no improvement in their rendering in Context. They work
fine in Notepad, Firefox, and TexnicCenter though, for example.
What am I missing?
___
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] can Context render complex scripts?
As Khaled mentioned ... are these proper otf fonts or do they rely on specific features in the microsoft engine? They all carry the .ttf extender. Arial Unicode MS is clearly True Type. I've seen some of the free fonts widely described as Open Type, but they are all amateur products---maybe they don't comply with the standard properly. If True Type fonts won't work correctly without an external engine and Context can't harness an external engine, then it looks like I will just have to wait for a more modern font to come along. Thanks for the article, Khaled. ___ 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] can Context render complex scripts?
OpenType (just ignore file extension for the moment) is a rather dump standard in the sense that it requires the engine to have some knowledge about the writing system at hand. ... So, what we have here is that ConTeXt has no special knowledge about Indic scripts, and thus it will not apply the feature properly according the linguistic rules. It seems to me that, since Hans can't be expected to write special code for dozens of Indic scripts, let alone for every script in the world, the pragmatic solution would be a method for Context to harness external engines (ICU, Pango, Graphite, Uniscribe, or whatever). If that's not possible, or if he doesn't want to do it, or until he is able to work with scholars on each special case, programs like Notepad will be able to do something that Context can't. As a casual user, it's not an urgent need for me. I had read that Aleph functionality had been integrated into LuaTeX (though I never found anything very detailed about that) and thought that everything was okay. I assume that Luatex/Context or some future TeX will have this functionality someday, however it's implemented. I'll just keep watching. ___ 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] can Context render complex scripts?
My first experiments aren't going well. For example:
using the free font, BNBDOT0N.ttf, from Deutsche Welle here:
http://www.dw-world.de/dw/article/0,,3219221,00.html
and the following typescript, type-bidisha.tex:
\starttypescript [serif] [dwbangla]
\definefontsynonym[DWbangla][name:BNBIDISHAOpentypeNormal][features=body]
\stoptypescript
\starttypescript [serif] [dwbangla]
\definefontsynonym[Serif][DWbangla][features=body]
\stoptypescript
\starttypescript [dwbangla]
\definetypeface [dwbangla] [rm] [serif] [dwbangla] [default]
[script=beng,features=body]
\stoptypescript
I try the following test:
\definefontfeature[default][mode=node,language=dflt,script=latn,kern=yes,liga=yes,tlig=yes,trep=yes]
\definefontfeature[body][default][mode=node,script=latn,onum=yes,pnum=yes,calt=yes,protrusion=quality,expansion=quality]
%just to be sure:
\definefontfeature[indic][body][nukt=yes,akhn=yes,rphf=yes,blwf=yes,half=yes,pstf=yes,vatu=yes,pres=yes,blws=yes,abvs=yes,psts=yes,
haln=yes,blwm=yes,abvm=yes,dist=yes]
\usetypescriptfile[type-bidisha]
\starttypescript [MTbook]
\definetypeface [dwbangla] [rm] [serif] [dwbangla] [default]
[script=beng,language=ben,features=body]
\stoptypescript
\def\bengali#1{{\switchtobodyfont[dwbangla]\addff{indic}\language[ben]#1}}
\usetypescript[MTbook]
\starttext
\bengali{সত্যজিৎ রায়}
\stoptext
সত্যজিৎ isn't rendered correctly in the output---after a the first
two characters, things go wrong. Yet, with the same font, it is
rendered correctly everywhere else I look in windows---notepad,
Firefox, TexnicCenter, etc., etc. To see what a correct rendering
should look like, google সত্যজিৎ রায় or see here:
http://bn.wikipedia.org/wiki/%E0%A6%B8%E0%A6%A4%E0%A7%8D%E0%A6%AF%E0%A6%9C%E0%A6%BF%E0%A7%8E_%E0%A6%B0%E0%A6%BE%E0%A6%AF%E0%A6%BC
or here (first word in text, in bold):
http://i367.photobucket.com/albums/oo113/andbipul/All%20about%20JJ/JJ%20Torjoma%20Works/Work-11Post-1.jpg
I tried this with several other free and MS fonts (e.g., arial Unicode
MS) and got the same results. Am I doing something wrong?
___
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] \reference fails in the new beta
\starttext
\reference[test]{test}
\stoptext
Has the syntax of \reference changed?
___
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] ntg-context Digest, Vol 72, Issue 9
more acrobat and initialization and so ... some of these things change
per version; which version of acrobat? test file?
I have Adobe Reader 9.3.2, which I think is the latest. The following test:
\starttext
\dorecurse{1000}{\tooltip[middle]{test}{test}}
\stoptext
produces a pdf which opens up with the purple band at the top. There
is a button (which doesn't look much like a button) on the left of
this band that will hide it when pressed. Still I'd like to control
it.
I have a closely-related question. I'm preparing a document for
screen reading, and I always have to push the Adobe Read button click
to show one page at a time to make it behave nicely. I'm guessing
that the command to keep the purple band from my screen is similar to
the one that would push this button automatically and begin the
document in the one-page-at-a-time mode. I'm using:
\setupinteraction[state=start,color=,contrastcolor=,focus=???]
and I've tried every value I can think of for ???, but maybe that's
not the 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] Please fill out the following form
more acrobat and initialization and so ... some of these things change
per version; which version of acrobat? test file?
I have Adobe Reader 9.3.2, which I think is the latest. The following test:
\starttext
\dorecurse{1000}{\tooltip[middle]{test}{test}}
\stoptext
produces a pdf which opens up with the purple band at the top. There
is a button (which doesn't look much like a button) on the left of
this band that will hide it when pressed. Still I'd like to control
it.
I have a closely-related question. I'm preparing a document for
screen reading, and I always have to push the Adobe Read button click
to show one page at a time to make it behave nicely. I'm guessing
that the command to keep the purple band from my screen is similar to
the one that would push this button automatically and begin the
document in the one-page-at-a-time mode. I'm using:
\setupinteraction[state=start,color=,contrastcolor=,focus=???]
and I've tried every value I can think of for ???, but maybe that's
not the 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
___
[NTG-context] Please fill out the following form
I was creating a document with many hyperlinks and tooltips, and everything was working, until it reached a certain size. Two strange behaviors began: 1. At the top of Adobe Reader I get a purple band that says Please fill out the following form... 2. Tooltips no longer appear at the first rollover. Instead, a pale blue box with a checkmark pops up. On the second rollover, my tooltips appear as normal. Is this some limit inherent in Context, pdf, or Adobe Reader? Is there a way to work around it? ___ 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] LuaTeX error ... object in use
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
\definefontfeature[de][body][dnom=yes]%denominator
in{\addff{in}123}
su{\addff{su}123abc}
nu{\addff{nu}123}
de{\addff{de}123}
The numerals all come out as proportional oldstyle, but the letters work. So,
sinf, sups, numr, and dnom are failing but ordn works.
I was thinking---besides updating to 0.60 yesterday, I was also trying
to test Stix fonts, so I ran:
mtxrun --script fonts --reload
luatools --generate
Maybe a change in mtxrun or luatools broke these features?
About my other problem---the strange one that's hard to isolate, and
which appeared this way in 0.50:
! LuaTeX error ...imal/tex/texmf-context/tex/context/base/lpdf-ini.lua:345:
pdf.immediateobj() object in use
and this way in 0.60:
! Undefined control sequence.
argument \@@bklocation
\processaction ...- \expandaction \!!stringa{#1
} \ifx \!!stringa \empty \l...
I'm still having a very hard time isolating a short example---e.g., I
spent the evening discovering this: near the end of about seven pages
of typeset text, I have the following string in my input file:
become more obvious as we examine the phenomena
This works:
become more obvious as %we examine the phenomena
and this fails:
become more obvious as we %examine the phenomena
I know the word we isn't the problem. Maybe it has something to do
with the length of the text, but that doesn't seem quite right either.
___
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] LuaTeX error ... object in use
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 --verbose cont-en
none of which had any effect on the output. How do I remake the formats?
On Sun, May 30, 2010 at 6:35 AM, Hans Hagen pra...@wxs.nl wrote:
On 30-5-2010 1:24, Michael Saunders wrote:
! Undefined control sequence.
argument \@@bklocation
\processaction ...- \expandaction \!!stringa{#1
} \ifx \!!stringa \empty \l...
in str-flt.mkiv there is a section
\def\@@bknumbering {\floatsharedparameter\c!numbering } % global one
\def\@@bkspaceafter {\floatsharedparameter\c!spaceafter } % global one
\def\@@bkspacebefore{\floatsharedparameter\c!spacebefore} % global one
\def\@@bknbottom {\floatsharedparameter\c!nbottom } % global one
\def\@@bkntop {\floatsharedparameter\c!ntop } % global one
\def\@@bknlines {\floatsharedparameter\c!nlines } % global one
\def\@@bkmargin {\floatsharedparameter\c!margin } % global one
\def\@@bkcache {\floatsharedparameter\c!cache } % global one
can you add:
\def\@@bklocation {\floatsharedparameter\c!location }
and then remake the formats
the bk namespace has been replaced (and this section is a temporary solution
in the transition)
Hans
-
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
___
Re: [NTG-context] LuaTeX error ... object in use
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: \definefontfeature[default][mode=node,language=dflt,script=latn,kern=yes,liga=yes,tlig=yes,trep=yes] \definefontfeature[body][default][onum=yes,pnum=yes,calt=yes,protrusion=quality,expansion=quality] But I seem to remember when I set this up that argument 1 never actually inherited from argument 2 when I tested it. Don't be too sure they are related, they could be totally independent problems. Ahh, of course you are right. I see that: ! Undefined control sequence. argument \@@bklocation... must be related to the missing line from str-flt.mkiv. I have added it, though, and I _think_ I remade the formats, but I get no change in behavior. ___ 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] LuaTeX error ... object in use
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 all four features and worked with 0.50). You gave me the idea to try GillSansMTPro, which also has the four features. I got a very interesting result---for it, numr and dnom work, but sinf and sups do not. I don't know how I could prepare a test file for you short of sending you my fonts and typescripts (which I'd be willing to do). ___ 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] LuaTeX error ... object in use
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 trk
MTXrun | numr cyrl dflt
MTXrun | grek dflt
MTXrun | latn aze crt deu dflt fra ita mol rom srb trk
MTXrun | ordn cyrl dflt
MTXrun | grek dflt
MTXrun | latn aze crt deu dflt fra ita mol rom srb trk
MTXrun | sinf cyrl dflt
MTXrun | grek dflt
MTXrun | latn aze crt deu dflt fra ita mol rom srb trk
MTXrun | sups cyrl dflt
MTXrun | grek dflt
MTXrun | latn aze crt deu dflt fra ita mol rom srb trk
but still,
\definefontfeature[body][default][script=latn,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
\definefontfeature[de][body][dnom=yes]%denominator
in {\addff{in}123}
su {\addff{su}123}
nu {\addff{nu}123}
de {\addff{de}123}
produces only proportional oldstyle figures.
___
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] LuaTeX error ... object in use
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 / 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] LuaTeX error ... object in use
This problem we have seen before, and I think it was a luatex bug then.
Which luatex is this ? 0.60.1 ?
It was .50, so I updated to .60. I'm still getting errors with the
same behavior, e.g.:
% block of text
block of text
and
block of text
% block of text
work, but
block of text
block of text
doesn't. The difference is that now they are reporting differently:
! Undefined control sequence.
argument \@@bklocation
\processaction ...- \expandaction \!!stringa{#1
} \ifx \!!stringa \empty \l...
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.
Also, debugging this really needs a complete test input file.
I don't know how to make one.
___
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] LuaTeX error ... object in use
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 fonts do not.
Mine does. It worked in 0.50. Maybe the name of the feature sinf changed?
Well, if I literally run
\starttext
block of text
block of text
\stoptext
It works just fine, so I need a test file to debug your bug report.
It appears to depend on having a big enough, complicated enough text,
not a specific combination of commands, so it's hard to come up with
one, but I'll try. Thanks.
___
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] LuaTeX error ... object in use
I keep running into errors that look like this:
! LuaTeX error ...imal/tex/texmf-context/tex/context/base/lpdf-ini.lua:345:
pdf.immediateobj() object in use
I can't find anything specific that's causing them. For example:
input{chapter1}
input{chapter2}
fails, but:
%input{chapter1}
input{chapter2}
and
input{chapter1}
%input{chapter2}
work.
Or, I may make a small change, get the error, reverse the change, and
continue to get the error. Maybe I need to allocate more memory
somehow? what's wrong?
___
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] urls longer than 57 characters fail in the bibliography
\usemodule[bib]
\newcommand{\myurl}[2]{\useURL[#1][#2][][\hyphenatedurl{#2}]{\ss\from[#1]}}
\starttext
\cite[test]
\placepublications[criterium=all]
\stoptext
works with:
@BOOK{test,
title = {test title},
publisher = {test title},
year = {2010},
author = {test author},
note =
{\myurl{testurl}{123456789012345678901234567890123456789012345678901234567}}
}
but fails with:
note =
{\myurl{testurl}{1234567890123456789012345678901234567890123456789012345678}}
however, this \myurl statement works in the body.
___
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] index sorting and formatting mixed up
luigi scarso:
\setupregister[index][bd][pagestyle=bold]
\starttext
\index{bc}\index{be}
This is a \index[bd::]{test}test.
\page
This is a less important \index{test}test.
\page
\placeindex
\stoptext
Confirmed: mkiv is different from mkii.
How is it to be done in MKIV? I could find no docs about it, nor even
a comment in the code.
___
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] index sorting and formatting mixed up
\setupregister[index][bd][pagestyle=bold]
\starttext
\index{bc}\index{be}
This is a \index[bd::]{test}test.
\page
This is a less important \index{test}test.
\page
\placeindex
\stoptext
___
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] tooltips and glossary
Philipp:
Thank you---I appreciate your effort on glossarium.lua very much, but
I don't want to be dependent on you every time I want to tweek my
glossary. I find it difficult to change the appearance and behavior
of anything in Context, but I think my chances are better with it than
with trying to work in lua.
So, I have pursued the problem via the \definesynonyms approach. What
I have so far can do all the basic things I imagined, and only seems
to need some cosmetic work now. This is what I have:
In the preamble:
\definesynonyms[gentry][gentries][\infull][\inshort]
%to connect headwords to entries
\definesynonyms[gloss][glosses][\tttext][\ttkey]
%to make short glosses available for tooltips
\def\gldef#1#2#3{\gloss{#1}{#2}\gentry{#1}{#3 {(p.\at[g:#1])}}}
\def\hint#1{\tooltip[middle]{#1}{\tttext{#1}}}
\def\glref#1{\reference[g:#1]{}}
%to place at a substantive reference in the text
%then you have a file of definitions like this one:
\gldef{vibrato}{a periodic fluctuation in pitch}{A periodic
fluctuation of pitch, typically in the range 6--12~Hz.}
Then, in the text, when you use an unfamiliar word and the reader
could benefit from a quick, pop-up gloss:
\hint{vibrato} (I just need a more sophisticated version of this that
can deal with variants of the word).
And, when you are about to engage in a substantive discussion of a
word or phrase that appears in the glossary (for a given headword,
there might be zero, one, or several such points in the text):
\glref{vibrato} (This causes a page reference after the glossary entry.)
I have two questions remaining:
1. I was somehow able to guess that \definesynonyms[gentry][gentries]
creates a new command called \setupgentries[], and I imagine this
command must inherit its possible keys and values from another
command, but I don't know what. Where can I look it up?
2. How can I modify the appearance/location/behavior of tooltips? I
tried \setuptooltips, but apparently that's not it.
I'll tinker with this and test it for a while. Eventually I hope to
contribute a glossaries my way to the garden.
Hans:
No problem! I'm sure whatever I put in the Google translator was just
as articulate as what came out of it. Really, I think the mistake is
mine. All along I have been assuming that Context was like LaTeX: a
system for end-users, a language where an author could easily
manipulate the appearance of his document. Apparently, it's more like
a supporting infrastructure for that. Maybe it needs a layer of
macros sitting on top of it to make it accessible and friendly to
users/writers. I'm hoping Idris's book will shed light on this.
Thanks, everyone.
___
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] tooltips and glossary
Marius:
Try this one: http://www.tex.ac.uk/tex-archive/info/context-top-ten/cmds.pdf
- page 14
Thanks, but that looks like it's just some extracts from cont-eni
translated from Engijsh into Engrish along with a distracting
background that makes it hard to read. The stuff about the not very
useful abbreviation command is there again, but I'm drawn to the
section about building a dictionary that says it's not about building
a dictionary.It says:
All you have to do is inserting a \index at whatever the phrase you
want to index is, and placeing a \placeindex where you want the
glossary to be.
and then goes on to describe and index, not a glossary, which seems to
require commands that need a lot of redundant arguments. It also
contains this gem:
Like many other ConTeXt command, users can define their own series of
indexing, which pluses the default \index series are called register.
That's the most remarkable thing I've read today. Maybe I need to be
more clear. A glossary is like a little dictionary in the back of a
book that defines the specialized words and phrases that the book uses
that might not be known to the general reader. Here is a definition
of glossary:
A collection of glosses; a list with explanations of abstruse,
antiquated, dialectal, or technical terms; a partial dictionary.
(Glosses were little explanatory notes written in the margins of
medieval texts---the kind of thing I would do if Context's marginal
notes weren't incompatible with its columns.)
Ideally, I'd like a system where I could keep the entries in a bib
database or in a special .tex file. The records would include the
headword and the gloss, and maybe a cross reference to the point in
the text that dealt with the headword definitively---the point where
the term was explained. (A document that defines and explains the new
words and phrases it coins---imagine such a thing!) It would be nice
if there were a command that would automatically link this point in
the text with the glossary entry. LaTeX has several packages
(glosstex, gloss, glossary, glossaries) that do things like this.
To do this in Context, I will probably have to do it all manually,
defining a command to set an entry and then doing all the
alphabetization and cross-referencing by hand.
What I would really, really, like is to add short definitions to each
glossary record that could pop up as tooltips when the reader hovers
over an unfamiliar word. Since there is no mechanism for glossaries
in Context, there is no mechanism to build this into, but I'm still
interested in doing it. The idea is, I could write something like:
\gloss{strange word}{short definition}
The text would read strange word. When you hover over it with the
cursor, a tooltip would appear saying short definition. It would be
great if this were linked to a glossary mechanism so I wouldn't have
to keep writing the short definition---I could say something like:
\gloss{strange word}
and its short definition would be looked up automatically for the
tooltip. The automatic reference to the word might look like this, in
the text:
\gref{strange word}
which would cause the page number at that point to be printed at the
end of the glossary entry for strange word.
___
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] tooltips and glossary
(Preliminary remark to M.S.: please, please, configure your MUA to correctly reply to the current thread!) (What's wrong with my subject line? I'm merely hitting reply in gmail.) No, it's plain English. Unfamiliar phrases are just one consequence of a language becoming the world standard. Do you want to flame Italians or French for not adhering to the norms of classical Latin? You don't. There's no point at all in even mentioning somebody's stylistic idiosyncrasies on the internets. Just face it: the world won't adopt English as a global means of communication without interfering with its norms. If you don't understand something why don't you contact the author, his email adress is right there on the first page. I don't mind non-native speakers using bad grammar, strange usages, or odd constructions at all. Things like that are usually no problem for native speakers to understand, although the two sentences I quoted were not plain English at all---one was completely indecipherable. The biggest problem with the docs is far more basic---it's the most basic mistake a beginning writer can make. I'm sure documents like the ones I was shown on this thread make perfect sense to their authors---who already know what they mean---but they fail to communicate their message to anyone who doesn't already know it. The reader isn't being given enough information to decode the message and what he is given is in no particular order: it's whatever bits and pieces of the story the author thinks of in the order he happens to think of them. You can't tell the author this. It makes sense to him and he can't understand the criticism. He has to put himself in the place of the reader who doesn't already know the message. If he can't do that, he can't communicate. I'm sure that these documents would be just as bad in the native languages of the authors as they are in English. The fault is far deeper than bad translation. Increasingly, I'm wondering whether the problem with Context is just bad docs or bad language design (it's hard to control, it looks bad most of the time). I still don't know. I'm hoping that Idris's book will shed light on this. I append a snippet that should allow basic glossaries. It doesn't provide much functionality (capitalization might have to be implemented …) but you may fit it to your needs. ... (As for the code, it's certainly not context style, I'm aware of that but don't have the time to care.) Awaiting your feedback, Thank you. I'm not quite sure what to do with these files (the .lua file in particular). Unfortunately, I won't be able to get to them until tomorrow. As for the tooltips, unfortunately I don't know how to create them. The functionality would be nice, though, as long as no javascript is involved. It's not done with javascript. As I understand it, the usual way is to place an invisible pdf forms-style button over the word you want to gloss and then set its short description feature. I think context knows how to make such buttons and to set bounding boxes around words, so I think it should be possible, no? ___ 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] tooltips and glossary
About glossaries:
Thank you, everyone. I'm not much of a TeXpert and certainly not a
lua expert, but I'm trying to understand your different solutions and
integrate them into a working system. There seem to be three
approaches:
I. Willi Egger---synonym-based
II. Marius---modified index
III. Philipp Gesang---lua-based
I. So far, Willi's synonym-based solution looks simple and promising.
I imagine something like this:
\definesynonyms[gloss][glosses][\infull][\inshort]%to make short
glosses available for tooltips
\definesynonyms[gentry][gentries][\infull][\inshort]%to connect
headwords to entries
\def\gdef#1#2#3{\gloss{#1}{#2}\gentry{#1}{#3}}
\def\hint#1{\tooltip[middle]{#1}{\infull{#1}}}
%then you have a file of definitions like this one:
\gdef{vibrato}{a periodic fluctuation in pitch}{A periodic fluctuation
of pitch, typically in the range 6--12~Hz.}
%within the text, where you need a tooltip on a word, you can say:
... \hint{vibrato} ...
%at then end of the text, something like:
Glossary:
\placelistofgentries
I see three problems with this:
1. I don't know how to tell \hint to refer to the vibrato in
glosses and not in gentries.
2. There is no mechanism to refer to the page with a substantive
discussion of vibrato.
3. There is no way to handle cases where the string in the text is
some variation of vibrato (e.g., Vibrato, vibrati, vibrato's)
II. Marius's modified index solution is the only one to successfully
link the entry back to a point in the text, but the resulting
glossary really just looks like an index.
III. Philipp Gesang's lua-based solution connects headwords to
entries just as \definesynonyms[gentry][gentries][\infull][\inshort]
does, and it produces something that looks like a glossary, but the
entries have no link back to the text. Also, I don't see the point of
the \usegloss{word} command unless it references the substantive
discussion(s) of the word. I think that is what his
\usegloss[exp]{word} is for, but then there should be a reference to
it in the entry. Something like:
{\bd headword}---entry text, p.\at[g:headword]
There probably is some advantage in using the lua script for this, but
I don't know what it is.
About tooltips:
\tooltip surprised me, and I was impressed that it appears to typeset
the tooltip text with Context, but there are some problems with it:
1. It's stretched horizontally.
2. The active area begins at the baseline and stretches about 1 ex
_under_ the word.
3. It appears without a border and under the cursor.
I have seen tooltips in pdf files before, and they looked better than
this. I suspect the reason is that, as you say, \tooltip uses
Javascript, and the ones I saw use a different mechanism. I dug
around and found this reference which describes how it's done with
form fields and invisible buttons:
http://gilbertconsulting.com/pdf/Build_tool_tips_in_InDesign.pdf
(Notice how tidy the tooltips in it look.) That document describes
setting them up manually in a point-and-click interface, but surely
Context could automate this by putting an invisible frame around the
word and creating a form field/button over it?
And, correct me if I'm wrong, but that mechanism is not
Javascript-based at all, is it?
(by the way: I've not broken the thread again, have I?)
___
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] tooltips and glossary
Also, is there no Context method to produce a glossary? It might be enough to produce a secondary .bib file with special entries and to print this out as a secondary References section, but I don't know how to do this or how to control the appearance of the printed references. Wolfgang Schuster: http://wiki.contextgarden.net/Reference/en/definesynonyms If you read that page, you'll notice it doesn't say what the second and third arguments of \definesynonyms do, what the command \definesynonyms itself does, nor does it hint at what \infull is doing. There is certainly nothing there about using an external database. I don't see any way to use \definesynonyms for a glossary or any practical purpose for \definesynonyms at all, and the abbreviations example is obviously more trouble than it's worth. More to the point, there is nothing about tooltips. Is there a way for Context to produce tooltips in text (with invisible buttons, perhaps)? ___ 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] tooltips and glossary
Wolfgang Schuster: http://pragma-ade.com/general/manuals/cont-enp.pdf - page 159 That rambling entry is like the webpage but worse. It still doesn't say what arguments 2--4 do, why \infull is necesarry, or anything else with any clarity. It's just another bundle of bad writing concealing what may be (but probably isn't) something useful. I was thinking of something like GlossTeX: ftp://ftp.dante.de/tex-archive/support/glosstex/glosstex.pdf I accept that Context has nothing built-in that's useful for making glossaries. That's okay, I can come up with something on my own. How about tooltips, though? Does anyone do those with Context? ___ 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] tooltips and glossary
Does Context have a mechanism for placing tooltips on text? I think the usual PDF way is to put an invisible button over the test and set its short description. Does anyone know how to do this? Also, is there no Context method to produce a glossary? It might be enough to produce a secondary .bib file with special entries and to print this out as a secondary References section, but I don't know how to do this or how to control the appearance of the printed references. ___ 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] bibliography overprinting and out of order
For example, with this .bbl file:
\setuppublicationlist[samplesize={Gob06},totalnumber=3]
\startpublication[k=siBrochure,t=techreport,
a={{Gobel}},y=2006,
n=1,s=Gob06]
\author[]{E.}[E.]{}{Gobel}
\pubyear{2006}
\title{The international system of units}
\pubname{Organisation Intergouvernementale de la Convention}
\stoppublication
\startpublication[k=siNist,t=techreport,
a={{Taylor},{Thompson}},y=2008,
n=2,s=TT08]
\author[]{Barry~N.}[B.~N.]{}{Taylor}
\author[]{Ambler}[A.]{}{Thompson}
\pubyear{2008}
\title{The international system of units ({\addff{sc}si})}
\bibtype{{\addff{sc}nist} Special Publication}
\volume{330}
\city{Washington, {\addff{sc}dc}}
\pubname{The National Institute of Standards and Technology ({\addff{sc}nist}),
United States Department of Commerce}
\note{http://physics.nist.gov/Pubs/SP330/sp330.pdf}
\stoppublication
\startpublication[k=siGuide,t=techreport,
a={{Thompson},{Taylor}},y=2008,
n=3,s=TT08]
\author[]{Ambler}[A.]{}{Thompson}
\author[]{Barry~N.}[B.~N.]{}{Taylor}
\pubyear{2008}
\title{Guide for the use of the international system of units ({\addff{sc}si})}
\bibtype{{\addff{sc}nist} Special Publication}
\volume{811}
\city{Washington, {\addff{sc}dc}}
\pubname{The National Institute of Standards and Technology ({\addff{sc}nist}),
United States Department of Commerce}
\note{http://www.nist.gov/physlab/pubs/sp811/index.cfm}
\stoppublication
and these commands:
\usemodule[bib]
\setupbibtex[database=Mydatabase]
\setuppublications[numbering=yes,alternative=ams,setupinteraction=start]
\startext
\placepublications[criterium=all]
\stoptext
...I get 3 and 2 printing out on top of each other (text overprinting
text), and out of order. I'd like the references to be alphabetical
(so you can find them by looking in the bibliography), numbered in
order, and these numbers used to print the citations. I'd also like
to prevent text from printing on top of text (that's so you can read
it).
___
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] Unicode bibliography
Mojca Miklavec: Long ago (when I was still using JabRef) I was thinking about creating support for export into ConTeXt-specific format. What do you use now? Is there something better? ___ 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] Unicode bibliography
Mojca Miklavec: What still makes me wonder is tha fact that there are problems with Unicode. I don't remember any, though I admit that I'm not sure if I ever cited any non-English item. Well, using Taco's trick of surrounding every sting with braces, the record won't print out. If I surround only the non-ascii characters in braces, the record will print out, out of order and on top of other records. ___ 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] Unicode bibliography
I'm using JabRef to generate a .bib file in utf8. I'd like to use this with Context to typeset a bibliography. I'm running into a lot of problems with Bibtex's Unicode incompatibility. What is currently the best way to do this? Googling, I came across this tantalizing suggestion from Idris (in 2008): Can you port your database to bbl format -- \start-stoppublication -- and just use the bib module without bibtex? That sounds good, but how can I do it? ___ 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] basic \cite[]
Taco: \placepublications Please change the above line to \placepublications[criterium=all] Thanks, but that's what I was using already. To be clear, in Mk IV: \usemodule[bib] \setupbibtex[database=myProject] \setuppublications[alternative=num] ... \cite[myKey] ... \placepublications[criterium=all] The references in the back look okay, but at the point where \cite[myKey] occurs, I get empty brackets: [], not [1]. ___ 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] basic \cite[]
Taco: Try \setuppublications[alternative=num] Thank you, but using that I get the same result: \cite[myKey] prints out empty brackets [], not [1]. ___ 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] basic \cite[]
Michael Green: Mk II gets the desired result; Mk IV does not. Example: \usemodule[bib] \setuppublications[alternative=num,refcommand=num] ... That's it then. I'm using Mk IV. Is there a proper way to use it? By the way, the developers should know something: in English, a criterium is a kind of bicycle race. The key should be called criterion. ___ 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] grid in footnotes, was: Re: footnote marks fail
i was not even aware that \newcommand was there ... probably more a
catch for bibtex issues
I have been using it a lot since, although Context seems to use a lot
of brackets, it won't allow nested ones. For example, I have to use:
\newcommand{\hfstyle}{\switchtobodyfont[15pt]}
\setupheader[style=\hfstyle]
because I'll get an error from:
\setupheader[style=\switchtobodyfont[15pt]]
Is there an easier way?
\setupnote[footnote][location=columns,numbercommand=\fnmstyle,textcommand=\fntstyle,textstyle=\addff{su},align={normal,hanging},split=verystrict,interaction=yes]
I don't know quite why it works, but it works---except for one little
thing---there is a little vertical space between each footnote
(apparently because of the \switchtobodyfont[12pt]).
that will indeed define the interlinespace; also, the regular \high
command does some snapping while with the supp feature you're dependent
on what the fonts delivers as ht/dp of a glyph
I don't see how could you possibly use \high{} for the footnote marks
(\setupnote[footnote][?]). Besides, as I understand it, \high{} just
rescales the body font---which always looks bad. So, I don't want to
use \high{}. I use my numr feature which gives me exactly the right
shape and height, but I have a little space between the footnotes.
How do I eliminate the space? Maybe by setting a verytolerant grid
for the footnotes? I don't know how.
___
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] footnote marks fail
Taco Hoekwater wrote:
I may be missing something on my side, but I can't get sups=yes
to work at all.
\definefontfeature[default][default][mode=node,script=latn,sups=yes]
\switchtobodyfont[palatino,11pt]
It may well be that this palatino doesn't have the sups feature. Let
me put it this way:
\starttext
text1\footnote{1footnote}
\stoptext
This will produce four instances of the numeral '1'. Suppose I want
them all to look exactly alike. In other words, suppose I didn't want
either footnote mark to be rescaled or elevated at all. How could I
do that?
___
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] footnote marks fail
Taco Hoekwater wrote:
\setupfootnotes[textcommand=,numbercommand=,style=,bodyfont=]
Thanks, Taco. I tried the following:
\setupfootnotes[textcommand=,numbercommand=,style=,bodyfont=]
\starttext
text1\footnote{1footnote}
\stoptext
and it almost works. The third and fourth '1' look the same, but the
first and second '1' (those in the text) are different. The second is
on the baseline, but it has been scaled much smaller than the first.
I want to turn off even this scaling.
My eventual plan is to use my sups for this (they seem to work fine
for me), but for now I'd be content to turn the automatic scaling off.
By the way, of these four keys (textcommand, numbercommand, style,
bodyfont), it's not at all clear to me what each is supposed to
control.
___
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] grid in footnotes, was: Re: footnote marks fail
Peter M?nster wrote:
\setupfootnotes[numbercommand=, textcommand=, style=, textstyle=,
bodyfont=]
Thanks, Peter. With some experimentation I got what I wanted. For
the record, I'm using:
\definefontfeature[su][body][sups=yes,ordn=yes]%superior
\definefontfeature[nu][body][numr=yes]%numerator
\definefontfeature[po][body][pnum=yes,onum=yes]%proportional old style
\newcommand{\fnmstyle}{\addff{nu}\switchtobodyfont[12pt]}
\newcommand{\fntstyle}{\addff{po}}
\setupnote[footnote][location=columns,numbercommand=\fnmstyle,textcommand=\fntstyle,textstyle=\addff{su},align={normal,hanging},split=verystrict,interaction=yes]
I don't know quite why it works, but it works---except for one little
thing---there is a little vertical space between each footnote
(apparently because of the \switchtobodyfont[12pt]).
So I have one more question: is there a way to force the footnotes
onto their own grid to prevent this? I am already using
\setuplayout[...,grid=verytolerant], which I thought would take care
of it.
___
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] footnote marks fail
Sebastien Mengin: Sorry, a bit off topic, but: is \setupfootnotes[] a synonym for \setupnote[footnote][] ? Besides \setupfootnotes[] and \setupnote[footnote][] there are: \setupenumerations[footnote][] and \setupfootnotedefinition[] and maybe more. I have no idea how they are related or even how to find out the difference. ___ 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] no protrusion or hz
\definefontfeature[default][mode=node,language=dflt,script=latn,kern=yes,liga=yes,tlig=yes,trep=yes]
\definefontfeature[body][default][protrusion=quality,expansion=quality]
\starttypescript [test]
\definetypeface[test][rm][serif][palatino][default][features=body]
\stoptypescript
\usetypescript[test]
\setupalign[hanging,hz]
\setupbodyfont[test,12pt]%
\mainlanguage[en-us]
\showgrid
\starttext
\addff{body}
\input{knuth}
\stoptext
Results in no protrusion or hz. What's wrong?
___
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] bug/feature request tracker?
it's not that complex to deal with it (but i'd only do it in mkiv) gien time and motivation ... you can put a feature request in the tracker so that i can look at it when i'm reworking marging notes the mkiv way (first come floats) Where is this tracker? ___ 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] footnote marks fail
Footnotes are normally marked with superior figures both in the text
and before the footnote itself. Context's defaults prevent this, and
I can't figure out how to change the defaults.
1. The defaults
So that no imagination is necessary, here is a minimal example:
\starttext
text\footnote{footnote}
\stoptext
I have to guess what Context is doing. It looks like it's taking the
regular numbers from the font, shrinking them somehow and elevating
them. It does this in unequal amounts for the marks in text and the
marks before footnotes. In both cases, the number is so light it's
barely readable. In the case of the mark before the footnote, it's
raised much too high.
Normal, professional fonts have superior figures in them that are used
for footnote marks. It _should_ be possible to use them, that is.
All I want to do is turn off the default scaling and raising behavior
of Context footnote marks so I can do this, and finally get normal
looking footnotes. No doubt, people will object that they don't have
my font in the room with them, and it is therefore impossible to think
about the problem. So, I repeat myself: all I want to do is turn off
the default scaling and raising.
2. My first stab at correcting this.
WARNING: I have a font with the opentype features 'sups' and 'numr'.
You might not have this font, but it is still possible to think about
the problem: the problem is not my font, but Context's defaults.
\definefontfeature[su][default][sups=yes]%superior
\definefontfeature[nu][default][numr=yes]%numerator
\newcommand{\fnstyle}{\switchtobodyfont[12pt]\addff{su}}
\setupnote[footnote][numbercommand=\fnstyle,textcommand=\fnstyle\tfa]
(Note: my body font is 12pt.)
This is as close as I could get to correcting the problem. When I do
this, the marks in text look a little too low, too short and much too
bold. It looks like Context is still scaling and elevating on its
own. The marks before the footnotes are much too large and far, far
too high. Context seems to be trying to squeeze them between the
lines. This also seems to force extra space between the separate
footnotes, even though I have grid on.
If I try using numerators instead of superiors (they look the same but
are lower), the marks in text look too bold and far too low. The
marks before the footnotes are at the right height, but too big.
DISCLAIMER: it is not necessary to own my font in order to think
about this problem. The issue is the default scaling and raising that
Context applies to footnote marks. I want to turn it off.
___
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] minimal example of some problems
1. Leftward protrusion doesn't work.
2. I don't think hz is working in footnotes.
The font I'm using is Adobe Garamond Premiere Pro. If you think there
might be a problem with the typescript, I can show you that too.
These two are related to font. Either show that something is wrong with
default typescripts (lmodern, times, palatino, etc) else it means that
tosmething is wrong with your typescript. But first you have to narrow
down the problem
I take your word for it that it works for the default typescripts;
therefore, the problem must be somewhere in my typescript, but I have
no idea where. It is as follows:
I don't have the font, so I cannot test it.
I should not have been so fast to take your word for it. If I use the
default LM fonts, I get the same problems---no leftward protrusion and
no hz in the footnotes.
You can prevent notes from splitting across pages by
\setupenumerations[footnote]
[before=\vbox\bgroup, after=\egroup]
The footnote may still appear on a different page. If you want to prevent
that add
\setupfootnotes[split=verystrict]
This doesn't work. I'm still getting footnotes appearing on the wrong page.
4. Notice the overprinting near the top of p.2 c.1. That is a
marginal note that should go into the right margin.
\starttext
\startcolumns
\input knuth
\input tufte
\column
\input tufte
\inmargin{This is in wrong margin}
\input knuth
\stopcolumns
\stoptext
The marin note in 2nd column is displayed in the 1st column. This is
artifact of the way in which TeX constructs columns: first creating a
long and narrow page and then splitting it into two. I don't know at
what stage of the OTR are margin notes inserted, and if there is a
workaround. Maybe others can help.
this is the first time someone needs it so indeed there is no mechamism
it's not that complex to deal with it (but i'd only do it in mkiv) gien
time and motivation ... you can put a feature request in the tracker so
that i can look at it when i'm reworking marging notes the mkiv way
(first come floats)
Where is the tracker I should put this in?
I have found another problem which is probably related. In the same
sort of arrangement, two columns with margins on either side, I would
like to place floats like this:
1. If they appear on the left side, they should end at the right edge
of the left column.
2. If they appear on the right side, they should begin at the left
edge of the right column.
Using \placetable[inmargin] (my best guess), this works fine for case
(2), but case (1) begins at the left edge of the left column and can
overprint the right column.
___
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] The ConTeXt book
This is the project which has only 5 or 6 users. Who actually uses it? Use LaTeX! That's the feeling I'm getting. I'm finding it hard to do a lot of basic things in Context. Maybe Context can do them and maybe it can't, but there is no way to find out. If the claims that Context is better really aren't empty, I would expect a lot of people to switch, but I imagine 99% of them are in the same boat I'm in---trying to switch and finding it practically impossible. I imagine many people try, spend a week trying to get it to work and then give up and go back to LaTeX. Mojca's point, that Context is commercial, may be the key: it can be free in name only but if the means of using it are kept secret, it's only of benefit to Pragma. (Hans himself mentioned earlier that there are many undocumented options for use in-house only that outsiders see in the code and wonder about.) Taco's objection that no one helps with the community project to update the reference manual is reasonable, but also predictable: strangers cannot simply wander in and write the book. The knowledge is in Hans's head (and maybe a few others), and only they can communicate it. It's evident that they either can't or won't. I really would like to see the quality of computer typesetting advance, and I was hopeful at hearing about Luatex/Context. I'd love to see Context produce better output more easily than LaTeX, but so far I'm putting a lot of effort into it to get some very disappointing results. One might place some hope in a future (21st c.?) LaTeX 3 based on Luatex, but that would depend on Hans explaining how Luatex works, and it seems doubtful that would ever happen. For now I'm sticking with Context because I still hope there might be some value in it, but it's hard to find. ___ 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] The ConTeXt book
Taco: Some feedback on the quality other than 'it sucks' would have helped enormously. ... Over the past four years, it has been next to impossible to get people interested in the reference manual project, not even for something as simple as reading the rewritten chapters and telling me what they think about it. ... The near total lack of feedback had led me to believe that most complainers are in it just for the complaining. I've been trying to be more constructive than saying 'it sucks'. I'm not complaining just to complain---I want to get the most I can out of the software. Please point me to a rewritten chapter you would like me to look at and I will give it a try. ___ 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] The ConTeXt book
Wolfgang:
Thanks---I'll go over what I can of those this weekend and get back to
you and Taco about them in a few days.
Peter:
That's the feeling I'm getting. I'm finding it hard to do a lot of
basic things in Context. Maybe Context can do them and maybe it
can't, but there is no way to find out.
Could you please provide a typical example?
Here are ten:
1. columns and marginal notes conflict:
\setupcolumns[n=2,rule=off,distance=20pt]
\setupinmargin[style=\ss,align=outer]
\startcolumns
text text \inmargin{text} text
\stopcolumns
The marginal notes always print to the left of the column. This works
perfectly for the left column, but fails for the right column---they
overprint the text of the left column.
2. leftward protrusion fails
\definefontfeature[...][default][...,protrusion=quality,expansion=quality]
\setupalign[hanging,hz]
\showgrid % or \showframe
There is no leftward protrusion at all. Everything on the left edge
is flush with the margin, even 'T' and 'J'. Similarly:
3. protrusion fails in footnotes:
Even on the right edge. Hz isn't happening in them either.
4. interactive headers/footers
I'd like to make my header and footer texts hyperlinks to the head
that they point to. I'm trying this:
\setupinteraction[state=start,color=darkgreen,contrastcolor=darkred]
\setupinteractionscreen[option=fit,view=fit]
\newcommand{\gmpt}{\getmarking[pt]}
\newcommand{\swpt}{{\goto{\getmarking[part]}[\gmpt]}}
\setupfootertexts[margin][\rlap\swpt\hfill][\hfill\llap{\getmarking[chapter]}]
(By the way, I'm resorting to this misdirection with the \newcommands
only because Context gives me an error whenever it finds nested
brackets. E.g.,
\newcommand{\swpt}{{\goto{\getmarking[part]}[\getmarking[pt]]}}
would fail.)
Then, at the beginning of a part, I have to add the extra marking to
carry the reference in the 'pt' marker (right?), e.g.:
\part[pt:one]{One}\marking[pt]{pt:one}
But this does not work. (By the way, all of this \defineXYZ,
\setupXYZ, \XYZ stuff is confusing. It seems like there is some kind
of purpose to this pattern of naming, but I can't find what it is.)
So, I experimented:
{\about[pt:one]}
(a particular reference) works
{\about[\gmpt]}
(referring through the marking) fails---so I can find no automatic way
of doing it.
(By the way, why are my footnote markers all green---shouldn't they be
red? could I make them black? Why does clicking on them sometimes
send me to a random page?)
5. footnotes break between pages
How do I stop this?
6. hyphenation between pages.
How do I stop this?
7. opening state
I'd like my document to open in Adobe reader showing one page at a
time (as if click to open one page at at time had been pressed).
8. description
I spent the evening trying to get \definedescription to set a
description on a line of its own followed by an explanatory paragraph.
I tried most of the keys/values. I never got anything that looked
good, let alone close to what I wanted. Finally, I spent a few
seconds writing a humble LaTeX-esque line:
\newcommand{\defhead}{\switchtobodyfont[gillSB,12pt]\ss}
\newcommand{\desclist}[2]{\crlf{\noindent\defhead #1\emspace#2}\crlf}
that did the job.
9. \raisebox?
What is the proper way to raise or lower a bit of text? I just spent
a lot of trial and error to find this:
\inframed[frame=off,offset=.5pt,height=17.3pt]{--}
to raise my en-dashes a little when \setff{ac} (for all caps) didn't
work with one font.
10. problematic characters in grid typesetting.
Unless I set grid=verytolerant, my 'Q' knocks the next line down a
notch. Is there a better way to deal with this?
switch and finding it practically impossible. I imagine many people
try, spend a week trying to get it to work and then give up and go
back to LaTeX.
Why do you?
Because I think it might be possible to produce better output with
Context than with LaTeX (is this true?). My experience has been quite
different from yours. I got up an running with LaTeX in a week (in
1995), found the documentation clear and almost any effect I wanted
easy to achieve with well-documented packages that never seriously
conflicted. This, on the other hand, is a nightmare.
___
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] The ConTeXt book
1. columns and marginal notes conflict:
For some of the issues, it would be perhaps a good idea to make proper
bug-reports (with minimal example of course).
In some other venue?
P.S.: Please consider fixing or changing your email client: it breaks the
threads.
Gmail. This is broken?
2. leftward protrusion fails
\definefontfeature[...][default][...,protrusion=quality,expansion=quality]
\setupalign[hanging,hz]
\showgrid % or \showframe
There is no leftward protrusion at all. Everything on the left edge
is flush with the margin, even 'T' and 'J'. Similarly:
Don't know what you mean, works here.
\definefontfeature[default][default][protrusion=quality]
\usetypescript[modern]
\setupbodyfont[modern]
The only difference I see is that I'm trying to use a different font
than modern:
\usetypescriptfile[type-garamond]
\starttypescript [MTbook]
\definetypeface[MTbook][rm][serif][garamondMD][optical]
...
\stoptypescript
\usetypescript[MTbook]
\setupalign[hanging,hz]
\setupbodyfont[MTbook,12pt]
So, leftward protrusion only works with Latin Modern?
3. protrusion fails in footnotes:
Even on the right edge. Hz isn't happening in them either.
You have to enable it separate for notes.
\setupnote[footnote][align={normal,hanging}]
I got rightward protrusion with that, but it looks like no hz.
Why are the key-values different? I also tried {quality,quality} and
got nothing.
5. footnotes break between pages
How do I stop this?
No example, no help!
Imagine:
one page full of lorem ipsum... containing \footnote{half-page of
lorem ipsum...}
The footnote will begin on page one, break halfway through, and
continue on the following page. I want to prevent footnotes from
breaking in this way.
If you really need to see 1.5 pages of concrete lorem ipsum posted
to understand the problem, I can provide it.
9. \raisebox?
What is the proper way to raise or lower a bit of text? I just spent
...
\raisebox{1ex}{?}
When I try:
\raisebox{1ex}{--}
Context stops on the error:
A box was supposed to be here
\raisebox{1ex}{
--}
What should ConTeXt do when your font doesn't provide the allcaps feature.
Some of the punctuation (e.g., hyphens, en- and em-dashes) should be
raised slightly and perhaps given a little extra spacing. The feature
is in my serif font, but not in my sans, hence my effort to correct
this.
10. problematic characters in grid typesetting.
Unless I set grid=verytolerant, my 'Q' knocks the next line down a
notch. Is there a better way to deal with this?
You can change the height/depth ratio of a line.
\setupinterlinespace[height=0.6,depth=0.4]
I must remember to put that convenient command before every majescule Q.
By the way---I am thrilled to hear of and very eager to see Idris's book!
But maybe a select audience of test-able volunteers will be the way to go...
I volunteer to be testable.
Yep. But when you actually run into one of these problems in LaTeX, you
are often more or less left alone - unlike ConTeXt and this list.
I'm pursuing it with the hope of more beautiful results, but I'm not
getting my problems solved here so far.
___
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] minimal example of some problems
Aditya:
1. columns and marginal notes conflict:
For some of the issues, it would be perhaps a good idea to make proper
bug-reports (with minimal example of course).
In some other venue?
In a separate thread, with a minimal example, that one can copy-paste and
see the error. Trying to guess what is wrong is difficult.
I tried that several times and got no response. Since you insist on
seeing lots of lorem ipsum, the following example:
\definefontfeature[default][mode=node,language=dflt,script=latn,kern=yes,liga=yes,tlig=yes,trep=yes]
\definefontfeature[body][default][onum=yes,onum=yes,pnum=yes,calt=yes,protrusion=quality,expansion=quality]
\definefontfeature[su][body][sups=yes,ordn=yes]
\usetypescriptfile[type-garamond]
\starttypescript [MTbook]
\definetypeface[MTbook][rm][serif][garamondMD][optical]
\stoptypescript
\usetypescript[MTbook]
\setupalign[hanging,hz]
\setupbodyfont[MTbook,12pt]%
\mainlanguage[en-us]
\definepapersize[MTS][width=823pt,height=462pt]
\definepapersize[MTA][width=823pt,height=462pt]
\setuppapersize[MTA][MTS]
\setuplayout[width=604.46pt,height=462pt,%
topspace=3pt,bottomspace=0pt,lines=30,header=21.4pt,footer=21.4pt,%
headerdistance=7.2pt,footerdistance=7.2pt,%
leftedgedistance=0pt,rightedgedistance=0pt,%
leftmargin=95pt,rightmargin=95pt,%
leftmargindistance=10pt,rightmargindistance=10pt,%
leftedge=11.5pt,rightedge=11.5pt,%
cutspace=0pt,backspace=109.5pt,%
grid=verytolerant]
\showgrid
\setupcolumns[n=2,rule=off,distance=20pt]
\setupinmargin[style=\ss,align=outer]
\setupfootnotedefinition[location=serried,distance=0.5em]
\newcommand{\fnstyle}{\switchtobodyfont[12pt]\addff{su}}
\setupnote[footnote][location=columns,numbercommand=\fnstyle,textcommand=\fnstyle\tfa,align={normal,hanging},interaction=yes]
\setupinteraction[state=start,color=darkgreen,contrastcolor=darkred]
\setupinteractionscreen[option=fit,view=fit]
\setupcombinedlist[content][interaction=all,textcolor=black]
\showlayoutcomponents
\starttext
\startcolumns
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis aliquam
sapien nec ligula aliquam eu tempor quam elementum. Etiam tellus
justo, pellentesque non luctus a, adipiscing ac mi. Nulla nec lorem
quis ante blandit laoreet vitae sed purus. Donec quis quam nec massa
ullamcorper condimentum at sit amet ante. Quisque ac nisl nibh.
Aliquam pulvinar pharetra purus suscipit dictum. Cras adipiscing sem
id tortor commodo nec mattis felis ultricies. Sed eget neque eget arcu
dictum feugiat. Nulla at congue ligula. Aliquam a magna et erat
interdum auctor. Ut consectetur sem ac massa congue ut consequat sem
elementum. Quisque ac justo enim. Donec et enim eu risus fermentum
lacinia at a odio. Sed egestas ligula ullamcorper risus accumsan
hendrerit. Integer placerat lectus sed eros porta accumsan.
Pellentesque elementum, urna eu tincidunt mollis, elit dolor
scelerisque diam, sed commodo nisl odio sagittis erat. Ut consequat
dolor enim, eget euismod arcu. In hac habitasse platea dictumst. Cras
adipiscing erat eu enim hendrerit quis euismod orci vehicula.
Sed pharetra porta lacinia. Nullam at lacus et sem venenatis consequat
ut nec eros. Donec diam elit, malesuada nec aliquam in, elementum vel
mi. Etiam quis euismod dui. Nunc sit amet eros vel erat vehicula
accumsan. Cras vulputate magna vitae urna fermentum nec eleifend
tortor dignissim. Suspendisse at velit id turpis gravida commodo sed
quis nulla. Cras id urna vel dui facilisis convallis. Cum sociis
natoque penatibus et magnis dis parturient montes, nascetur ridiculus
mus. Pellentesque habitant morbi tristique senectus et netus et
malesuada fames ac turpis egestas. Phasellus pulvinar auctor metus,
non rutrum risus ornare a. Proin purus nisl, fringilla at congue ac,
imperdiet non velit. Sed magna libero, pellentesque ut vestibulum sit
amet, euismod ac nulla. Proin egestas, mi at convallis accumsan,
lectus erat tincidunt magna, quis ullamcorper arcu dolor et dui.
Maecenas iaculis erat aliquam augue pellentesque aliquam. Donec in
odio sapien, ac iaculis risus. In tempus nulla tristique ante dapibus
nec accumsan velit convallis. Sed imperdiet tincidunt turpis aliquam
porta.
Pellentesque\footnote{Integer libero velit, accumsan at porttitor et,
gravida et ligula. Maecenas vestibulum convallis metus, vitae
ullamcorper diam aliquet eget. Sed id lorem nec nibh dignissim
bibendum. Cum sociis natoque penatibus et magnis dis parturient
montes, nascetur ridiculus mus. Praesent in arcu a nunc rutrum
faucibus. Ut ornare, est vitae viverra luctus, sapien eros malesuada
felis, id facilisis ipsum ligula sit amet purus. Sed libero dui,
consectetur rhoncus laoreet non, faucibus quis est. Aenean non lacus
felis, sit amet tempor felis. Fusce gravida sem arcu, id hendrerit
est. Ut nec ligula nunc, sed pulvinar risus. Cras ac purus sem, eget
posuere enim. Quisque sem velit, accumsan sit amet interdum vitae,
laoreet ac tellus. Curabitur tempus, erat sed dapibus volutpat, dolor
lacus faucibus ante, ut iaculis nunc nisl in
Re: [NTG-context] minimal example of some problems
1. Leftward protrusion doesn't work. 2. I don't think hz is working in footnotes. The font I'm using is Adobe Garamond Premiere Pro. If you think there might be a problem with the typescript, I can show you that too. These two are related to font. Either show that something is wrong with default typescripts (lmodern, times, palatino, etc) else it means that tosmething is wrong with your typescript. But first you have to narrow down the problem I take your word for it that it works for the default typescripts; therefore, the problem must be somewhere in my typescript, but I have no idea where. It is as follows: \starttypescript [serif] [optical] [size] \definebodyfont [4pt,5pt,6pt,7pt,8pt,9pt,10pt] [rm] [tf=SerifCaption-Regular sa 1, it=SerifCaption-Italic sa 1] \definebodyfont [11pt,12pt,13pt,14pt,14.4pt] [rm] [tf=SerifRegular-Regular sa 1, it=SerifRegular-Italic sa 1] \definebodyfont [15pt,16pt,17pt,17.3pt,18pt,19pt,20pt,21pt,22pt] [rm] [tf=SerifSubhead-Regular sa 1, it=SerifSubhead-Italic sa 1] \definebodyfont [23pt,24pt,30pt,36pt,48pt,51pt,60pt] [rm] [tf=SerifDisplay-Regular sa 1, it=SerifDisplay-Italic sa 1] \stoptypescript %I don't know what this block is for, but I think it is needed only once. \starttypescript [serif] [garamond] \definefontsynonym [Serif] [SerifRegular-Regular] \definefontsynonym [SerifItalic] [SerifRegular-Italic] \stoptypescript %Garamond (Book)garamond \starttypescript [serif] [garamond] \definefontsynonym [SerifCaption-Regular] [file:GaramondPremrPro-Capt] [features=body] \definefontsynonym [SerifCaption-Italic] [file:GaramondPremrPro-ItCapt] [features=body] \definefontsynonym [SerifRegular-Regular][file:GaramondPremrPro] [features=body] \definefontsynonym [SerifRegular-Italic] [file:GaramondPremrPro-It] [features=body] \definefontsynonym [SerifSubhead-Regular] [file:GaramondPremrPro-Subh] [features=body] \definefontsynonym [SerifSubhead-Italic] [file:GaramondPremrPro-ItSubh] [features=body] \definefontsynonym [SerifDisplay-Regular] [file:GaramondPremrPro-Disp] [features=body] \definefontsynonym [SerifDisplay-Italic] [file:GaramondPremrPro-ItDisp] [features=body] \stoptypescript \starttypescript [garamond] \definetypeface [garamond] [rm] [serif] [garamond] [optical] \stoptypescript %Garamond MediumgaramondMD \starttypescript [serif] [garamondMD] \definefontsynonym [SerifCaption-Regular] [file:GaramondPremrPro-MedCapt] [features=body] \definefontsynonym [SerifCaption-Italic] [file:GaramondPremrPro-MedItCapt] [features=body] \definefontsynonym [SerifRegular-Regular] [file:GaramondPremrPro-Med][features=body] \definefontsynonym [SerifRegular-Italic] [file:GaramondPremrPro-MedIt] [features=body] \definefontsynonym [SerifSubhead-Regular] [file:GaramondPremrPro-MedSubh] [features=body] \definefontsynonym [SerifSubhead-Italic] [file:GaramondPremrPro-MedItSubh] [features=body] \definefontsynonym [SerifDisplay-Regular] [file:GaramondPremrPro-MedDisp] [features=body] \definefontsynonym [SerifDisplay-Italic] [file:GaramondPremrPro-MedItDisp] [features=body] \stoptypescript \starttypescript [garamondMD] \definetypeface [garamondMD] [rm] [serif] [garamondMD] [optical] \stoptypescript %Garamond Semi-Bold garamondSB \starttypescript [serif] [garamondSB] \definefontsynonym [SerifCaption-Regular] [file:GaramondPremrPro-SmbdCapt] [features=body] \definefontsynonym [SerifCaption-Italic] [file:GaramondPremrPro-SmbdItCapt] [features=body] \definefontsynonym [SerifRegular-Regular] [file:GaramondPremrPro-Smbd][features=body] \definefontsynonym [SerifRegular-Italic] [file:GaramondPremrPro-SmbdIt] [features=body] \definefontsynonym [SerifSubhead-Regular] [file:GaramondPremrPro-SmbdSubh] [features=body] \definefontsynonym [SerifSubhead-Italic] [file:GaramondPremrPro-SmbdItSubh] [features=body] \definefontsynonym [SerifDisplay-Regular] [file:GaramondPremrPro-SmbdDisp] [features=body] \definefontsynonym [SerifDisplay-Italic] [file:GaramondPremrPro-SmbdItDisp] [features=body] \stoptypescript \starttypescript [garamondSB] \definetypeface [garamondSB] [rm] [serif] [garamondSB] [optical] \stoptypescript %Garamond Bold garamondBD \starttypescript [serif] [garamondBD] \definefontsynonym [SerifCaption-Regular] [file:GaramondPremrPro-BdCapt] [features=body] \definefontsynonym [SerifCaption-Italic] [file:GaramondPremrPro-BdItCapt] [features=body] \definefontsynonym [SerifRegular-Regular] [file:GaramondPremrPro-Bd][features=body] \definefontsynonym [SerifRegular-Italic]
[NTG-context] footnote and hyphens splitting between pages
Is there any way to prevent footnotes splitting between pages? ?I thought the undocumented key, 'split' might control this (who knows?), but it has no effect on anything. Also, is there any way to prevent hyphenation between pages? luigi scarso: I'm completely ignorant about this subject. Do you have a pathological example to test ? Consider a page of Lorem ipsum dolor... containing within its first half, a half-page long footnote of Lorem ipsum dolor Context is likely to start the footnote on page one and continue it on page two. I want to forbid this. In the second case, imagine a very long book of Lorem ipsum dolor There are likely to be occasions where a word is hyphenated at the very end of the page, splitting a word between two pages. I want to forbid this too. ___ 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] footnote and hyphens splitting between pages
Is there any way to prevent footnotes splitting between pages? I thought the undocumented key, 'split' might control this (who knows?), but it has no effect on anything. Also, is there any way to prevent hyphenation between pages? ___ 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] Microtype in ConTeXt
On 27-3-2010 1:15, Yan Zhou wrote: As I can see now ConTeXt is indeed a far more advanced system than LaTeX. But I have one more query. Where can I find the documents. When following these replies and some other messages in the list, I find some commands not documented in the Manual or Reference Manual. In LaTeX, all commands are detailed documented in source2e.tex, in TeX, The TeXBook explains everything. So in ConTeXt, where can I find such detailed documents. I tried the documented source, but it is more like a PDF version or source with only a little documentation. as most of the functrionality does not change you can use older docs (website, wiki etc) for most cases newer things i.e. introduced in mkiv using luatex are described in for instance mk.pdf and articles of course the wiki is a good source as well Notice that Yan Zhou isn't complaining that the docs are old. Our problem is that they are sketchy and rambling, bits and pieces of this and that without any systematic explanations. Often they are just some unexplained code samples that communicate nothing (unless you happen to be the guy who invented the language). I can't think of one command that is fully explained along with all its possible parameters. The wiki is better written, but even less complete. It might not be possible to do better, but this is a huge obstacle to anyone who actually wants to use ConTeXt. The docs hint at a lot of features that sound better than LaTeX, but actually getting them to work is a different story. ___ 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] docs (was: Re: Microtype in ConTeXt)
Peter, that post of Hans's mainly argues that the old manual is good
enough and then goes on to talk about development. For example:
Even an old manual can quite well describe functionality as much
didn't change.
It can if it ever did. I don't think cont-eni.pdf etc., describe the
functionality well at all.
As one can visually get all kind of output and as
typographical elements can interfere the ultimate manual would
show $n!$ variants and become quite unreadable. There is no easy
way out of this.
There is: describe each option concisely and abstractly, then you
need only be concerned with $n$ elements. Almost every LaTeX package
manages to do this successfully, and they are very usable.
More documentation would not help all users.
There needn't be more. It needn't be lengthy, just clear, complete,
and concise.
There are quite some options that were never meant for
usage beyond our own, but as we ship the full product, they become
visible. No, they are not documented apart from the source. Yes,
if useful they should be documented but why by me?
Because you are probably the only person on earth who understands
them. Getting that knowledge out of your head and into others' will
require an act of communication.
I only work on a manual (or article or whatever) if it's fun to do.
That may be the problem!
Hans, Here are some constructive suggestions. I hope you take them seriously:
If you ever write another manual, perhaps when MKIV is complete,
1. Start from scratch. Throw away the old material.
2. Forbid yourself the use of code examples. They are a crutch which
impedes communication. First, write the whole manual with normal,
abstract, expository prose. When it's complete and explains
everything fully---when it {\em makes sense}--- {\em then} illustrate
it with as many code samples as you like.
3. Have a standard format, a sort of checklist, for what must be said
about each argument, parameter, command and group of commands:
---What is its function?
---How is it used?
---What is it used for (what effect is it supposed to achieve)?
---What are the options?
A regular format like this will make it much easier on you. You'll
have a regular structure that you simply have to fill in. It might
even make the task more fun.
4. Get someone to serve as an editor.
These will solve most of your writing problems. I look forward to a
new manual someday.
Thanks,
-- 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
___
[NTG-context] marginal note problems
I'm still trying to get marginal notes to work with columns. I've
been experimenting with columnsets, but I still get the marginal notes
popping up on the wrong side of their column, and overprinting the
other column, not printing in the margin.
I thought that this though, would be an opportunity to attempt two
column text with three column footnotes (I'd read of other people in
the archive who found this impossible in the past). I tried:
%columns
\definecolumnset[body][n=2,distance=20pt]
\definecolumnset[footnotes][n=3,distance=10pt]
%footnotes
\newcommand{\colprefoot}{\stopcolumnset\startcolumnset[footnotes]}
\newcommand{\colpostfoot}{\stopcolumnset\startcolumnset[body]}
\setupfootnotedefinition[location=serried,distance=0.5em]
\newcommand{\fnstyle}{\switchtobodyfont[12pt]\addff{su}}
\setupnote[footnote][numbercommand=\fnstyle,textcommand=\fnstyle\tfa,before=\colprefoot,after=\colpostfoot]
and variations on it, expecting to switch to three columns after the
balanced two column body and back again after the footnotes. The
results were very disappointing:
-- The footnotes are still in two columns.
-- At least, they now flow from one column to the next, though neither
they nor the body columns are balanced.
-- The hrule separating them from the body is now always absent---but
one appears at the top of the very first page!
I'm beginning to think that columns with marginal notes and footnotes
in a different number of columns can't be done.
If I have a two-column text with margins on either side, is there a
way for \inmargin{} or something like it to place text in the margin
next to the column where it occurs? I haven't been able to avoid it
overprinting the text in the opposite column.
I tried using margin blocks but I couldn't get anywhere with them. Even:
\startmarginblock
test
\stopmarginblock
produces no output. And there is a new wrinkle:
\setupinmargin[align=outer] ruins my footnotes. It causes the
footnote marks that occur before the notes themselves to appear one
margin-length left of where they should be, even if the overprint
text.
___
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] marginal note problems
Thank you for the help with headers---it worked. My marginal note
problems continue:
If I have a two-column text with margins on either side, is there a
way for \inmargin{} or something like it to place text in the margin
next to the column where it occurs? I haven't been able to avoid it
overprinting the text in the opposite column.
I tried using margin blocks but I couldn't get anywhere with them. Even:
\startmarginblock
test
\stopmarginblock
produces no output. And there is a new wrinkle:
\setupinmargin[align=outer] ruins my footnotes. It causes the
footnote marks that occur before the notes themselves to appear one
margin-length left of where they should be, even if the overprint
text.
___
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] three problems
1. central headers with margin overhanging:
I find that the following line:
\setupheadertexts[margin][\rlap{\getmarking[section]}\hfill][\hfill\llap{\getmarking[subsection]}]
will set up a header nicely, overhanging the margins. To be clear, I
meant that:
the left header text begins at the leftmost extreme of the left margin
and goes as far right as it needs to, even above the text area, and
the right header text begins whereever it has to, even above the text,
to end at the rightmost extreme of the right margin.
On the other hand, this code:
\setupheadertexts[\setups{text a}]
\startsetups[text a]
\rlap{\getmarking[section]}\hfill
\hfill
--center text here--
\hfill
\hfill\llap{\getmarking[subsection]}
\stopsetups
can place a center header text.
Is there a way to do both?
2. marginal notes with columns:
If I have a two-column text with margins on either side, is there a
way for \inmargin{} or something like it to place text in the margin
next to the column where it occurs?
I haven't been able to avoid it overprinting the text in the opposite column.
3. leftward protrusion:
When I look at my output with \showgrid, it's clear that there is no
leftward protrusion at all. Everything is flush with the margin, even
'T' and 'J'.
I'm using:
\definefontfeature[...][default][...,protrusion=quality,expansion=quality]
\setupalign[hanging,hz]
___
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] ntg-context Digest, Vol 69, Issue 95
Wolfgang Schuster:
\setupbodyfont[pagella]
\definefontfeature[smcp][smcp=yes]
\definefontfeature[frac][frac=yes]
\setuphead[chapter][textstyle=\addfs{frac}\addfs{smcp}]
...
This is just an example, but what I think you mean to say by it is
that the new command \addfs{} has the behavior I describe, but only
for otf features and not for things like switching to semibold or to
condensed (and, presumably, even if I'm able to define my own commands
for things like semibold, something like:
\sb ABC \it DEF
would set the DEF at regular weight).
Since I've never seen anyone talk about \addfs{}, but only give
examples, I'm guessing (but just guessing) that there exists somewhere
a list of what otf features are active at any given point, and that
this command can add to that list. That's great. I might not need it
anytime soon, but I'm just curious---are there other commands of this
kind? Maybe something to clear the list?
That leaves me the problem of installing sets with more than two
weights, more than one width and several design sizes, as we spoke
about earlier. It's late in the day here, but I hope to try that out
tomorrow. Just to make sure I understand the example you and Mojca
gave me:
\definebodyfont [default] [rm]
[tf=Serif sa 1,
bf=SerifBold sa 1,
it=SerifItalic sa 1,
sl=SerifSlanted sa 1,
bi=SerifBoldItalic sa 1,
bs=SerifBoldSlanted sa 1,
sc=SerifCaps sa 1]
You could add your
in=SerifYourFontVariantName sa 1,
bd=SerifYourOtherFontVariantName sa 1,
I think I can add this block to the top of my own typescript,
duplicate the existing definitions as shown, and, when making up my
own, I think I'm free to define font switches with more than two
characters, so, e.g.:
sbexit=SansSemiboldExtendedItalic sa 1
so, I won't be able to switch variants of this kind independently, but
at least I can get them installed.
After that, I'll move on to the optical examples and see what I can do
about that (I'm hoping they provide for automatic switching of design
size).
Thank you,
-- m
___
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] typescripts
I'm trying to follow the examples and getting surprising results:
\definefontfeature[default][mode=node,language=dflt,script=latn,kern=yes,liga=yes,tlig=yes,trep=yes]
\definefontfeature[body][default][onum=yes,pnum=yes,protrusion=quality,expansion=quality]
\definefontfeature[smallcaps][body][smcp=yes, onum=yes]
%I understood this to mean that body would inherit default and
smallcaps would inherit body.
\starttypescript [sans] [gillLT]
\definefontsynonym[Gill-Light][name:gillsansmtprolight][features=body]
\definefontsynonym[Gill-Light-Italic][name:gillsansmtprolightitalic][features=body]
\stoptypescript
\starttypescript [sans] [gillLT]
\definefontsynonym[Sans][Gill-Light][features=body]
\definefontsynonym[SansItalic][Gill-Light-Italic][features=body]
\stoptypescript
\starttypescript [gill]
\definetypeface [gillLT] [ss] [sans] [gillLT] [default]
[features=body,script=latn,script=grek]
\stoptypescript
\setupalign[hanging,hz]
\setupbodyfont[gillLT,12pt]
\ss
1:1234567890 fi fl ffi ffl\addff{smallcaps} test smallcaps
2:\addff{body} 1234567890 fi fl ffi ffl\addff{smallcaps} test smallcaps
In both 1 2, ligatures and small caps fail (though the glyphs are in
the font).
In 1, oldstyle fails.
___
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] typescripts
Wolfgang Schuster:
You can apply only *one* feature to \definefontfeatures.
I've seen examples like this:
\definefontfeature
[fea]
[mode=node,language=dflt,script=arab,
init=yes,medi=yes,fina=yes,isol=yes,
liga=yes,dlig=yes,rlig=yes,tlig=yes,
calt=yes,trep=yes,mark=yes,mkmk=yes,
kern=yes,curs=yes]
so I think you mean to say that I can apply only one feature to
\definefontsynonym or to \definetypeface. I tried this and it
checks out. Thanks---it's nice to see hz working. Protrusion is
only on the right margin?
2. As far as I can tell from trying to decode examples, there is some
hidden connection between the first arguments of the second typescript
block and the font switches. So, for example, a secret connection
between SerifBoldItalic and \bi seems to connect Junicode-BoldItalic
to \bi. Fine, but, in all the examples I've seen, there are no more
than two weights and no widths. In some cases, I have five weights
(light, book, medium, semi-bold, bold). How do I set up the
typescript for this and the switches in the text? Must I learn more
pairs like (SerifBoldItalic, \bi)?
You need more typefaces. One for light, another one for condensed etc.
--
Mojca Miklavec:
Must I learn more pairs like (SerifBoldItalic, \bi)?
Yes, but there are not many (tf, it, sl, bf, bi, bs, sc) and I assume
that they are extensible. See also below.
You need more typefaces. One for light, another one for condensed etc.
Maybe I'm wrong, but shouldn't it be possible (I didn't test) to
modify font-unk.mkiv and add a few extra definitions to the following?
(Maybe not modify font-unk itself, but just adding a couple of more
definitons to the typescript.)
\definebodyfont [default] [rm]
[tf=Serif sa 1,
bf=SerifBold sa 1,
it=SerifItalic sa 1,
sl=SerifSlanted sa 1,
bi=SerifBoldItalic sa 1,
bs=SerifBoldSlanted sa 1,
sc=SerifCaps sa 1]
You could add your
in=SerifYourFontVariantName sa 1,
bd=SerifYourOtherFontVariantName sa 1,
And then
\definefontsynonym[SerifYourFontVariantName][YourFontName]
It's true that most people don't do that, but I see no reason for not
extending the model for your particular needs.
Mojca
--
Wolfgang Schuster:
The last time i did this you needed for MkIV also
\definefontalternative[in]
\definefontalternative[bd]
but be carefull with the shortcuts, \in is already used (references).
Thank you both. I want to begin experimenting with this, but there's
one thing that still confuses me. If I have a font with say, forty different
combinations of weight/width/shape (5x4x2), I will need to come up with
forty different pairs like:
myNewFontSwitch=SerifMyFontVariantName sa 1,
a strain on the poetic imagination, but possible.
It would be nicer though, if I could change weight/width/shape independently
of each other (then I need have only 5+4+2 switches). For example, when
I see something like:
\rm\tf roman \it italic \bf bold
resulting in:
book roman book italic bold roman,
it's surprising to see that \bf has turned off the italic---you don't
expect a switch
of the weight to have a hidden switch of the shape in it. Could the typescript
be set up with fewer switches, so that:
\rm\tf roman \it italic \bf bold
would result in:
book roman book italic bold italic,
or, e.g.,
\rm\tf (regular book roman) \cd (condensed) \it (italic) \bf (bold)
would result in:
regular book roman condensed book roman condensed book italic
condensed bold italic?
(Also, I'm hoping that having a dozen different sets of font features won't
require twelve times as many switches and feature names as this. I think
there is some easier method for switching---Hans mentioned \addff{}, but
I can't find anything in the docs. If that works, that would make two kinds
of switches, one for some kinds of features and another for other kinds.)
___
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] typescripts
Wolfgang Schuster:
do you need all of your fonts at the same time in your document?
Most of the time, one serif and one sans. I'd be happy to get these
installed. Of course, High quality fonts often come in large sets.
The varying weights turn up most often in the variations between
different kinds of heads, occasionally in other things. Variations in
optical size occur more frequently, besides in heads, in things like
quotations, footnotes, and captions. Smallcaps (and sometimes,
all-caps environments) often turn up in headers. It's nice to be able
to switch easily between roman/italic and other things within
environments like that---it's very nice if things like shape, weight
and so on can be switched independently. It's also very nice if
optical design sizes switch automatically with the current size.
Consider, for example, something like this: a book on film with a header:
Fellini's Roma and 8 1/2. I'm used to setting something like this
in this way:
Fellini's \it{Roma} and \it{\cvfrac{8}{1}{2}}
(where \cvfrac{}{}{} is a macro that gives me a compound vulgar fraction).
The header is itself in smallcaps, so what comes out is:
Fellini's small caps
Roma italic small caps
and small caps
8 italic proportional lining (italic and lining (i.e., uppercase)
because it's a title)
1/2 italic numeratoritalicitalic denominator
all with minimal effort on the part of the writer. It seems natural that way.
Do you plan to switch between oldstyle and lining figures each sentence?
I've certainly done that before, with lining for quantities and
oldstyle for everything else (mostly chapter and page numbers). Of
course, other sorts of numerals turn up a lot too---the numerator and
denominator variants for fractions, the superiors for footnotemarks
and ordinals, and occasionally inferiors as well.
Do you need condensed and regular width together in the running text
or do you want one in the text and the other in the header?
The different widths of my sans is one thing I hadn't counted on using
much (I spend more time in serif) but, since I have the fonts, I
thought it would be nice to be able to use them. More than the
specific uses I've mentioned above, I'm used to the freedom of being
able to use what I have when the need arises.
ConTeXt is not a DTP program and has a completely different concept.
I'm aware of that. I've been using LaTeX for fifteen years now. I
keep hearing about Context and the work with Luatex and I want to try
it out to see whether I can get higher quality. Loading and switching
fonts is just the first hurdle. If it's too difficult to do this in
Context, that's okay. I realize that it's a work in progress and
these things may be improved someday. I just want to get as much
working as I can right now so I can try out more things. I have two
fonts to install. I've been at it for two weeks. I realize it might
take a few more weeks and a lot of work. I know it's not as easy as
dropping them in a folder. That's okay. I'll keep at it.
Before we can give you better answers think about what do want
to achieve and where do you need a certain font feature and style,
when you have a clear picture about this ty to describe it and we
try to help you.
___
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] typescripts
I have been earnestly trying to understand how they work by attempting a slightly more complex one. So far, I have: --- \definefontfeature[default][mode=node,language=dflt,script=latn,kern=yes,liga=yes,tlig=yes,trep=yes] \definefontfeature[body][onum=yes,pnum=yes,protrusion=quality,expansion=quality]%turn hz on %plus some I hope to use later \definefontfeature[tabular][sans=yes,tnum=yes,onum=yes]%turn hz off \definefontfeature[allcaps][cpsp=yes,case=yes,lnum=yes] \definefontfeature[smallcaps][smcp, onum=yes] \definefontfeature[swashes][swsh=yes] \definefontfeature[inferior][sinf=yes] \definefontfeature[superior][sups, ordn=yes] \definefontfeature[numerator][numr=yes] \definefontfeature[denominator][dnom=yes] \definefontfeature[prop-os][pnum=yes,onum=yes] \definefontfeature[prop-lin][pnum=yes,lnum=yes] \definefontfeature[tab-os][tnum=yes,onum=yes] \definefontfeature[tab-lin][tnum=yes,lnum=yes] \definefontfeature[ornaments][ornm=yes] \definefontfeature[lgc][script=latn,script=grek,script=cyrl] \starttypescript [serif] [junicode] \definefontsynonym[Junicode][name:junicode][features=default,features=body,features=lgc] \definefontsynonym[Junicode-Bold][name:junicodebold][features=default,features=body,features=lgc] \definefontsynonym[Junicode-Italic][name:junicodeitalic][features=default,features=body,features=lgc] \definefontsynonym[Junicode-BoldItalic][name:junicodebolditalic][features=default,features=body,features=lgc] \stoptypescript \starttypescript [serif] [junicode] \definefontsynonym[Serif][Junicode][features=default,features=body,features=lgc] \definefontsynonym[SerifBold][Junicode-Bold][features=default,features=body,features=lgc] \definefontsynonym[SerifItalic][Junicode-Italic][features=default,features=body,features=lgc] \definefontsynonym[SerifBoldItalic][Junicode-BoldItalic][features=default,features=body,features=lgc] \stoptypescript \starttypescript [junicode] \definetypeface [junicode] [rm] [serif] [junicode] [default] [features=default,features=body,features=lgc,features=hanging,features=hz] \stoptypescript \setupalign[hanging,hz] \setupbodyfont[junicode,12pt] - but, 1. tlig and trep aren't working, so evidently, features=default isn't getting through. No hanging or hz is happening either---probably the same problem. 2. As far as I can tell from trying to decode examples, there is some hidden connection between the first arguments of the second typescript block and the font switches. So, for example, a secret connection between SerifBoldItalic and \bi seems to connect Junicode-BoldItalic to \bi. Fine, but, in all the examples I've seen, there are no more than two weights and no widths. In some cases, I have five weights (light, book, medium, semi-bold, bold). How do I set up the typescript for this and the switches in the text? Must I learn more pairs like (SerifBoldItalic, \bi)? ___ 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] typescript
I am trying to get a minimal working example so that I have something to tinker with. C:\contextminimal\tex\texmf-local\type-garamondprem.tex contains only: \starttypescript [serif] [garamondprem] \definetypeface [garamondprem] [rm] [serif] [name:garamondpremrpromed] [default] \stoptypescript (garamondpremrpromed is a name returned by mtxrun --script fonts --list --all --pattern=*Garamond*.) I run: luatools --generate and texmf-local is found. In my preamble: \usetypescriptfile [type-garamondprem] \usetypescript [garamondprem] \setupbodyfont [garamondprem,12pt] When I run Context, the result contains only Latin Modern. ___ 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] simplefonts
Thomas A. Schmitz: Thank you, Thomas. I've been studying this closely. A typescript file can contain a series of typeface definitions, e.g., one for serif, one for sans, one for mono, one for math, etc. hence the syntax \starttypescript [typeface] [identifier] I see! So, I'm guessing that it is this typeface which connects the typescripts to the font switching commands like \rm. My guess is: typeface switch serif \rm sans \ss mono\tt math \mm ?? \hw ?? \cg and that Context only permits these six families? In the typography manual, Hans says, The third and fourth arguments to \definetypeface are pointers to already declared font sets; these are defined elsewhere. I think by font set he must mean a typescript like garamondprem, but I don't know where the font set (typescript?) serif is or why two font sets need to be pointed to. ??? That's how I feel. The command in question was: \definetypeface [GaramondPrem] [rm] [serif] [garamondprem] [default] The typography document says that the [serif] [garamondprem] are pointers to already declared font sets; these are defined elsewhere. I know now that [garamondprem] is the font set in your typescript. I don't know what font set [serif] points to or why. The same typography document goes on to explain the fifth argument: The fifth argument to \definetypeface specifies specific font size setups (if any), these will be covered in section ?? in the next chapter. This is getting scary, but I'm hoping putting [optical] there will solve everything. I don't follow. http://context.aanhet.net/svn/contextman/context-reference/en/co-typography.pdf says: The fifth argument to \definetypeface specifies specific font size setups (if any), these will be covered in section ?? in the next chapter. If this chapter were inserted into the manual, the next chapter would be about color and backgrounds, so, no luck searching there. But, I noticed that that fifth argument was filled by [optical] at the bottom of this page: http://wiki.contextgarden.net/Optical_Size so: \definetypeface [minion-pro] [rm] [serif] [minion-pro] [optical] I'm confused about how [GaramondPremUpper] and [garamondpremupper] seem to be getting associated with [rm] and [serif] after they were already associated with [GaramondPrem] and [garamondprem]. I don't see how, when I now use \rm, the machine is going to know whether I mean garamondpremupper or garamondprem. The rest of the file seems straightforward. In ConTeXt, you are always within a certain bodyfont (the one defined with the \definetypeface command). A switch like \it or \rm will thus take the italic/roman from this bodyfont. Meaning: when you say \setubodyfont[GaramondPrem], it will use normal Garamond Premier, if you use \switchtobodyfont[GaramondPremUpper], it will use the superior numbers variant. Ahhh, okay. It wasn't intuitive to me, as a user, that a relatively small change (from, say, oldstyle to superiors) would take a much bigger switch (of the whole bodyfont) than would a relatively big change (from, say, roman to italic, which only needs a little \it). I wrote a set of font switches once (in LaTeX) that were all little digraph codes (major axis: rm, it, sl, ui; minor axis: rg, ac, sc, sw, in, su, nu, de, po, pl, to, tl + ornaments, which handles all of the variations that Adobe makes, anyway). Maybe I'll be able to reproduce it once I get this working. I get the error: !undefined control sequence recently read \usetypescript l.12 \usetypescript [GaramondPrem] Then we will need your example - this is not normal behavior. okay: First, I put an almost exact copy of your file (with your comments commented out) in type-garamondprem.tex in C:\contextminimal\tex\texmf-local and ran luatools --generate, which seems to see the directory alright. Then I put the commands: \usetypescriptfile [type-garamondprem] \usetypescript [GaramondPremUpper] \usetypsecript [GaramondPrem] \setupbodyfont [GaramondPrem,12pt] in my preamble, with nothing else. When I try to run Context, the above error was returned. For the record, here is the exact contents of type-garamondprem.tex: %So we define a set of such features for the different font instances we want to define. %In my case, I want regular text with oldstyle figures, small caps with lining figures, and superior numerals. This goes into your typescript: \definefontfeature [myroman] [protrusion=pure,expansion=quality,script=latn,liga=yes,onum=yes,pnum=yes,kern=yes,tlig=yes,trep=yes] \definefontfeature [mysmcp] [mode=node,script=latn,language=dflt,liga=yes,onum=yes,pnum=yes,kern=yes,tlig=yes,trep=yes,smcp=yes] \definefontfeature [mysup] [mode=node,script=latn,onum=no,pnum=yes,sups=yes] %Next step: we set up the normal and smallcaps font: \starttypescript [serif] [garamondprem]
Re: [NTG-context] ntg-context Digest, Vol 69, Issue 77
Henning Hraban Ramm: \usetypsecript [GaramondPrem] Here's a typo. Yes, that was it, thank you. Now when I run it it gives me... ... Latin Modern. -- Hans Hagen: My guess is: typeface switch serif \rm sans \ss mono \tt math \mm ?? \hw ?? \cg and that Context only permits these six families? it can support as many as you want but only a few make sense If you say so! you can combine such combinations in typefaces and mix then any way and use multiple such mixtures in one document I'm sure it's easy if you know how. I'm just trying to find out how. (major axis: rm, it, sl, ui; minor axis: rg, ac, sc, sw, in, su, nu, de, po, pl, to, tl + ornaments, which handles all of the variations that Adobe makes, anyway). Maybe I'll be able to reproduce it once I get this working. sounds complex .. It's very easy to use, and it allows me to access any feature of my fonts with a digraph switch. Also, it keeps the different kinds of shapes on independent axes, so I can say: \it 123 \in 456 \bd 238 \rm 909 to get the numbers set in: italic; italic inferiors; bold italic inferiors; bold roman inferiors, because I also have the weight and width on separate axes. I can't imagine anything simpler to use. it's more like: [typefaceone|typefacetwo|...| [rm|ss|tt|..] [tf|it|..] That looks like a much more complicated font switch. What command are those arguments to? so if you want a smallcaps set, you'd best do something \definetypeface[Whatever] [] \definetypeface[WhateverSmallcaps][] and then switch the lot to smallcaps using a typeface switch (which is quite fast) instead of defining all kind of extra smallcaps instances within the main typeface You are saying that putting: \definetypeface[WhateverSmallcaps] [undocumented argument] [undocumented argument] [some other typescript somewhere] in one file and then invoking it in another with (I think maybe?): \usetypescript[that other typescript from somewhere] \usebodyfont[WhateverSmallcaps] is easier than saying: \sc ? ___ 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] simplefonts
Thomas A. Schmitz: That may be a lack of imagination on your part. If you want something that follows LaTeX rules, it might be a good idea to use LaTeX. It would have been a good idea to say so from the start instead of wasting my time. I'm going to try to go on using Context without wasting any more of your time. First, I have to figure out why your typescript gives me Latin Modern. -- m ___ 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] simplefonts
Aditya Mahajan:
Have you read the chapter on typography in the new manual
http://context.aanhet.net/svn/contextman/context-reference/en/co-typography.pdf
Yes. Several times. And I took notes.
--
Hans Hagen:
1. What the first two arguments do.
the mode=base|node determines if we use traditional tex mechanisms
(base) or let mkiv do all work itself (node)
2. What keys and values are available for the third, and what they mean.
Thank you, but by the first two arguments, I mean 1 and 2 of:
\definefontfeature [1][2][3]. For example, in
\definefontfeature[smallcaps][smallcaps][script=latn]
I don't know what [smallcaps][smallcaps] is doing.
3. Once I have composed a \definefontfeature command, how do I use it
in the text.
not in the text, only when defining fonts; although you can enable and
disable features in the running text (dynamicly) .. from the source:
% \startbuffer
% \definefontfeature[smallcaps][smallcaps][script=latn]
% \definefontfeature[oldstyle] [oldstyle] [script=latn]
%
% \definedfont[name:cambria at 15pt]
%
% Hello there {\setff{smallcaps}capped 123 \setff{oldstyle}123!}\blank
% Hello there {\addff{smallcaps}capped 123 \addff{oldstyle}123!}\blank
% Hello there {\addff{smallcaps}capped \subff{smallcaps}normal} \blank
% \stopbuffer
%
% \typebuffer \getbuffer
Naturally, I don't know what any of this code means (which is why I seek
a human language explanation), but I'm guessing that in
\definefontfeature[oldstyle] [oldstyle] [script=latn]
the first [oldstyle] creates a command or variable called oldstyle,
the second [oldstyle] relates this to something else (another command or
variable, maybe a font file) which is also called oldstyle, and
the key-value pair [script=latn]qualifies this, selecting the only the Latin
part of the second [oldstyle]. (And, by the way, my font has Greek and
Cyrillic as well---why disable oldstyle in them?) I think that leaves me with
a command or variable or something called oldstyle, which I could include
in the text. My first guess would have been that it's \oldstyle, but, later
in your code snippet, I see \setff{smallcaps} and \addff{smallcaps}.
There's no telling what the difference is. So, I'm left guessing that
\definefontfeature[oldstyle] [oldstyle] [script=latn]
creates a possible argument for \setff{} and \addff{}, whatever they are.
They might be the commands for font switching in the text.
Since the code snippet isn't a human explanation, however, I can't tell---
I can only make wild guesses.
4. For example, I gathered that I needed a [default] [default]
[...onum=yes...] to get oldstyle numerals by default, but what if I
want to use some lining numerals here and there?
\definefontfeature [lining] [lining] [...onum=no...]
{\lining 123}
doesn't do it.
lnum=yes
I tried this, and
\definefontfeature [lining] [lining] [lnum=yes]
{\lining 123}
still gives me undefined control sequence on \lining.
I also tried {\switchtobodyfont [lining] 123},
which had no effect.
5. How I could use the superior and inferior shapes in my font---like
for the footnotemarks, for example?
hm, with sups=yes,subs=yes i guess but better use \high{..} and \low{..}
as often such font features are rather limited and depend on the font
I'll have to try that out (since I know which fonts have them), but:
\definefontfeature [?] [?] [sups=yes,subs=yes] ?
--
Thomas A. Schmitz:
This is not to disparage Wolfgang's great simplefonts module, but I learnt
setting up fonts the old-fashioned way (with typescripts),
so I will give a few explanations about this approach. Most of what you want
can be achieved easily. I have Garamond Premier myself, and this is how I set
it up:
Thank you, this is very encouraging. I used to do this with otftotfm and .fd
files, so it's not totally alien to me. I just need to grasp the syntax of the
Context commands. I've been pouring over your example. There are a
few points I still don't understand.
...
Next step: we set up the normal and smallcaps font:
\starttypescript [serif] [garamondprem]
\definefontsynonym [Garamond-Roman] [name:garamondpremierpro]
[features=myroman]
\definefontsynonym [Garamond-Bold] [name:garamondpremierprobold]
[features=myroman]
\definefontsynonym [Garamond-Italic] [name:garamondpremierproitalic]
[features=myroman]
\definefontsynonym [Garamond-Bold-Italic]
[name:garamondpremierprobolditalicc] [features=myroman]
\definefontsynonym [Garamond-SmallCaps] [name:garamondpremierpro]
[features=mysmcp]
\stoptypescript
\starttypescript [serif] [garamondprem]
\definefontsynonym [Serif] [Garamond-Roman] [features=myroman]
\definefontsynonym [SerifItalic] [Garamond-Italic] [features=myroman]
\definefontsynonym [SerifBold] [Garamond-Bold] [features=myroman]
\definefontsynonym [SerifBoldItalic]
[NTG-context] simplefonts
Add \definefontfeature[default] [default] [mode=node,script=latn] \definefontfeature[smallcaps][smallcaps][mode=node,script=latn] before \setmainfont. Thank you, Wolfgang, but this has no effect. -- m ___ 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] simplefonts
This works
\definefontfeature[default] [default] [mode=node,script=latn]
\definefontfeature[smallcaps][smallcaps][mode=node,script=latn]
\usemodule[simplefonts]
\setmainfont[garamondpremrpro]
Thank you once again. That _did_ work, after I got rid of an \os (I
used it because I saw it in the manual).
The command \definefontfeature intrigues me greatly. I wonder if it
could solve all my problems. I'd love to understand it so that I
don't end up coming in here and asking you to write all my font setups
line by line. I Googled it and found only a few scattered examples
here and there, mostly from this list. I wish I could find an
explanation of it written down somewhere. For example, I would very
much like to know:
1. What the first two arguments do.
2. What keys and values are available for the third, and what they mean.
3. Once I have composed a \definefontfeature command, how do I use it
in the text.
4. For example, I gathered that I needed a [default] [default]
[...onum=yes...] to get oldstyle numerals by default, but what if I
want to use some lining numerals here and there?
\definefontfeature [lining] [lining] [...onum=no...]
{\lining 123}
doesn't do it.
5. How I could use the superior and inferior shapes in my font---like
for the footnotemarks, for example?
6. Could I use \definefontfeature to set up the different design sizes
of my font (I'm trying to use some standard Adobe fonts like Garamond
Premiere Pro, which have design sizes), as well as its other features?
7. Maybe \definefontfeature is how I should turn on hz?
I'm sure these things must be possible, but I'm stumped about how to
find them out.
-- m
___
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] stack overflow
can you run with --track=resolvers.* and see where it goes wrong It seems to get hung up looking for context.lua (which is there, in C:\contextminimal\tex\texmf-context\context\data\textadept). It ends up in an infinite loop, saying: context MTXrun | fileio: file '\context.lua' is not readable over and over. I tried updating context minimals by saying: first-setup.bat --keep but this didn't fix it. -- m ___ 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] simplefonts
I couldn't get Context running from within TexnicCenter again, so I'm running it from a batch file. After pouring over all the mentions of typescripts here and there, I can't make sense of them. For example, I used to be able to write font definition files that would automatically shift between different design sizes depending on what font size was called for. How to do that here? Not a clue. Finally I settled on trying simplefonts. The two lines of documentation in Context Garden are: \usemodule[simplefonts] % load the module \setmainfont[Delicious] % set Delicious as main (serif) font I tried this at home: \usemodule[simplefonts] \setmainfont[garamondpremrpro] and, indeed, it loads Garamond, but normal ligatures (e.g. ffi) are broken, TeX ligatures (e.g. ---) are broken, small caps are broken, etc. It doesn't even take advantage of the superior figures for the footnote marks, which are now tiny, spindly things. The documentation that comes with the module is one line long: \simplefont[font][..,..=..,..] followed by a list of OpenType features. So, I tried it: \simplefont[garamondpremrpro] [features=liga] It doesn't seem to do anything. Even standard ligatures don't work. -- m ___ 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] stack overflow
Thank you, Taco. I'm still going over the font docs. Today: \starttext test \stoptext results in: mtxrun.lua:2167: stack overflow It worked yesterday. ___ 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] using otf fonts with MKIV
I think this should be possible. I'm trying to follow: http://wiki.contextgarden.net/Fonts_in_LuaTex I have set OSFONTDIR and run mtxrun --script font --reload. The output looks like: MTXrun | fontnames: identifying tree font files with suffix otf MTXrun | fontnames: identifying tree font files with suffix OTF MTXrun | fontnames: 161 tree files identified, 0 hash entries added, runtime ... MTXrun | fontnames: 0 system files identified, 0 hash entries added, runtime 0.135 seconds MTXrun | fontnames: 60 files rejected due to clashes MTXrun | fontnames: 635 double lookups in mappings MTXrun | fontnames: 169 double lookups in fallbacks The next step, mtxrun --script fonts --list returns not supported. I supposed that the documentation was wrong and finally struck on mtxrun --script fonts --list --pattern=* which seems to know of only one font file, though I have over 1000 in the folder. ___ 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] ntg-context Digest, Vol 69, Issue 49
The question is: what have you set OSFONTDIR to, and does that location actually contain the system fonts? Thank you, Taco. Double checking, I find that I have set OSFONTDIR to C:\Windows\Fonts, which does indeed contain my 1074 system font files, 970 of them open type. The slightly different string you put on the webpage: mtxrun --script fonts --list --all --pattern=* now seems to find them. That was the problem. My next problem is to make sense of what lies under the heading The standard way: Typescripts. It's clear that the instructions don't mean typescript in the ordinary English sense of the word (a typewritten document), but some new, undefined thing. From other bits of documentation here and there, I've gotten the idea that typescripts are files that contain commands. I know that there are examples of typescripts given elsewhere, but without explanation, I couldn't decipher them. I don't suppose there is a syntax of the typescript language written down anywhere. The first instruction stymies me: 1. Copy the typescript files into either $TEXMF/tex/texmf-fonts/tex/context/user $TEXMF/tex/texmf-project/tex/context/user What typescript files? Where? Also, the two directories don't exist in my distribution of Context Minimals. Are we supposed to create them? I look ahead for clues as to where the typescripts for my fonts might be. A little farther down there is a heading, 'Where to find existing typescripts', but it doesn't talk about where to find typescripts. It does hint at what typescripts are though---it says, 'Each of the typescripts below...' and then, below, there is a list of lines like the following: Latin Modern (typescript name: modern; this is the default font set) Maybe a line like that is a typescript. Who knows? ___ 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] no output
I finally got Context to install (correctly, I think), and I'm trying to set up a profile for it in TeXnicCenter. When I run it, I get the promising message: TeXExec | processing document 'test.tex' TeXExec | no ctx file found TeXExec | tex processing method: context TeXExec | TeX run 1 TeXExec | writing option file test.top TeXExec | using randomseed 110 TeXExec | tex engine: luatex TeXExec | tex format: cont-en TeXExec | runtime: 0.08 LaTeX-Result: 0 Error(s), 0 Warning(s), 0 Bad Box(es), 0 Page(s) but no pdf file is output. My command looks something like this: texexec --lua --bat --nonstop --pdf --interface=en --color --language=en test.tex the tex file contains the lines: \starttext hello cruel world \stoptext What is wrong? ___ 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] no output
Thank you. I had never heard of luatex/mkiv format before---I have just been trying to follow the four or five conflicting pages about installation that I found at Context Garden. I did a Google search there for luatex format, which does not occur, and for mkiv format, which occurs once, under a heading about updating existing installations. It says: * For making MKIV format luatools --selfupdate mtxrun --selfupdate luatools --generate context --make I tried these commands and, indeed they ran. I also changed my command line to: context --interface=en --language=en test.tex I had been trying to follow the example on the Context Garden page, which contained the incorrect command and flags you saw. Now when I run context, I get less promising output than before: MTXrun | run 1: luatex --fmt=C:contextminimal/tex/texmf-cache/luatex-cache/context/d1d2ccfb3346ff481f4c4dab022cb26d/fomats/cont-en --lua=C:contextminimal/tex/texmf-cache/luatex-cache/context/d1d2ccfb3346ff481f4c4dab022cb26d/fomats/cont-en.lui --backen MTXrun | fatal error: no return code, message: luatex: No such file or directory ___ 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] suggestions for context documentation
The important thing is: is there _ever_ going to be a manual? I want to try Context, but I've been putting it off for years because it's not really practical without documentation. There must be many others in the same situation. ___ 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] suggestions for context documentation
You mean like the beginner's manual http://www.pragma-ade.com/general/manuals/ms-cb-en.pdf and the user manual http://www.pragma-ade.com/general/manuals/cont-eni.pdf ... amongst 46 others by Pragma No, not like those. I mean like a real manual. I read the book about Hasselt---a few examples without explanations. I've looked at most of the fifty or so documents over which this virtual manual is supposed to be spread. They are about as informative. Most of these documents seem to be 5--12 years old. The wiki is even more patchy. The idea that a computer manual is something that exists implicitly in the discussions of a mailing list is a new idea to me. You can't be serious about mk.pdf being a manual. Even it admits, This document is not so much a users manual as a history of the development. Little after that point is intelligible. Compared with the clear, abundant documentation of the LaTeX world, Context seems like a secret that a small club is trying to keep. It's not even clear from the manuals that development is ongoing, much less that there is some advantage in using it. So, will there ever be a manual to MK IV? In how many years? ___ 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 ___
