>>> This reminds me. Two columns of text over three columns of footnotes.
>>> Is it possible?
Hans Hagen :
>indeed, just multicolumns with page notes in 3 columns
My footnotes all end up at the bottom of the last column.
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://w
\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
> 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 app
> 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
> 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,
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:BNBI
\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
> 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
> 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
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 ro
> 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://ww
> 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 sr
> 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
> 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:
\defin
mpile --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 wrote:
> On 30-5-2010 1:24, Michael Saunders wrote:
>
>> " ! Undefined control sequence.
>> \@@bklocation
>> \processaction
>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
\definef
> > 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
> defaul
> 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
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{chap
\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
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?
\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 interes
Finding simple \at[] statements inadequate for glossaries (where there
might be zero, one, or several page references per entry), I'm
experimenting with registers, but I'm not getting the expected
results:
\defineregister[glind][glinds]
\setupregister[glind][style=\it]
\setupinteraction[state=star
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 t
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. Phi
> (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 stand
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
> 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
wh
>> 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".
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 .
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
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 surro
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 i
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
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]
...
\placepublicatio
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
"criteriu
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,
I want to be able to write, in my text, \cite[myKey] (where myKey is
the key of a record in my .bib file), and have this appear in print
as: []
linked to the bibliograpy page where it () occurs.
I've been puzzling over bibmod-doc.pdf. I think the solution has to
do with the commands \setuppublic
> 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[sty
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
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]%numer
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
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
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{footn
>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"?
_
\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
\usetypescrip
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 s
> > 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 i
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 err
> > 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 brok
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 w
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 m
"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 rea
>> 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 thi
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?
__
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
functionali
> 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 Man
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
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
overpr
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 lef
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
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 behavio
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
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
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]
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
(
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 was
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:
>> switch
>> serif \rm
>> sans \ss
>> mono
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
[] []
I see! So, I'm guessing that it is this w
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
> 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 s
> 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
__
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 d
> 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 readabl
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
> 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 differe
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
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, un
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
>
> 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-
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.
_
82 matches
Mail list logo
