Re: [NTG-context] Internal clickable links

2014-09-03 Thread Keith McKay

Thanks for the advice Wolfgang.
I went back to the wiki and found \setupfootnotes, \placefootnotes and 
\setupfootnotedefinition.  Playing around with these I almost get what I 
want.  What I don't get is two way interaction i.e. clicking on the 
superscript in the text doesn't take me to the footnote (or endnote in 
this case), but clicking on the superscript of the footnote takes me 
back to the word in the text.  I would really prefer to be able to click 
on a word to take me to the definition and click on the definition to 
take me back to the word.


Here is a test file to show the effect I found above:

\setupinteraction[state=start,
color=black]

\setupfootnotes[location=text,
interaction=yes,
bodyfont=11pt]

\setupfootnotedefinition

[headstyle=italic,

location=top,

color=red,

headcolor=blue]

\starttext

barley \footnote{barley used to make beer} hops

filter chocolate\footnote{chocolate used to make chocolate bars} malt

secondary fermentation\footnote{fermentation the process of beer making} 
adjunct


\page

Lorem\footnote{ipsum}

\page

\placefootnotes

\stoptext



Thanks and best wishes
Keith Mckay

On 02/09/2014 22:54, Wolfgang Schuster wrote:

Am 02.09.2014 um 23:49 schrieb Keith McKay mckaymeis...@gmail.com:


Colleagues

I'm setting up a document which at the end of each chapter will have a Glossary 
of word definitions.  To get to these definitions one would click on the word 
in the chapter which would take them to the page where the definition of the 
word is in the Glossary.  Once the user has done this, they could then click on 
the definition to go back to the original word in the chapter.  \footnote works 
after a fashion, however I would like the word to be clickable and the 
definition not to appear at the bottom of the page.  It's not really what I 
want.

Is there another way to get the functionality I'm looking for?

The placement of footnotes at the bottom of the page can be disabled to flush 
them at another position, e.g. at the end of a chapter. Instead of footnotes 
you can use endnotes which are configures in this way or create your own note 
command.

Wolfgang
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


___
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] Internal clickable links

2014-09-03 Thread Wolfgang Schuster

Am 03.09.2014 um 11:13 schrieb Keith McKay mckaymeis...@gmail.com:

 Thanks for the advice Wolfgang.
 I went back to the wiki and found \setupfootnotes, \placefootnotes and 
 \setupfootnotedefinition.  Playing around with these I almost get what I 
 want.  What I don't get is two way interaction i.e. clicking on the 
 superscript in the text doesn't take me to the footnote (or endnote in this 
 case), but clicking on the superscript of the footnote takes me back to the 
 word in the text.  I would really prefer to be able to click on a word to 
 take me to the definition and click on the definition to take me back to the 
 word.

I can’t reproduce this behavior, both links from the footnote marker in the 
text and back from the footnote to the reference work for me.

\setupinteraction[state=start]

\setupnote[footnote][location=text]

\starttext

barley\footnote{barley} chocolate\footnote{chocolate}

\page

\placenotes[footnote]

\stoptext

Wolfgang___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Internal clickable links

2014-09-03 Thread Keith McKay
I'm running ConText through TeXworks on my mac mini.  The console shows 
that I running Context Mkiv


This is LuaTeX, Version beta-0.76.0-2013061817 (rev 4627)

\write18 enabled.

(/usr/local/texlive/2013/texmf-dist/tex/context/base/cont-yes.mkiv


ConTeXt ver: 2013.05.28 00:36 MKIV current fmt: 2014.9.3 int: 
english/english



However, when I change the typesetting engine to Context(pdftex) or 
Context(XeTex) it works as you said it should.


I think I should maybe upgrade to the latest version of Context. :-[

Thanks for help

Best Wishes
Keith McKay

On 03/09/2014 10:24, Wolfgang Schuster wrote:


Am 03.09.2014 um 11:13 schrieb Keith McKay mckaymeis...@gmail.com 
mailto:mckaymeis...@gmail.com:



Thanks for the advice Wolfgang.
I went back to the wiki and found \setupfootnotes, \placefootnotes 
and \setupfootnotedefinition.  Playing around with these I almost get 
what I want.  What I don't get is two way interaction i.e. clicking 
on the superscript in the text doesn't take me to the footnote (or 
endnote in this case), but clicking on the superscript of the 
footnote takes me back to the word in the text.  I would really 
prefer to be able to click on a word to take me to the definition and 
click on the definition to take me back to the word.


I can't reproduce this behavior, both links from the footnote marker 
in the text and back from the footnote to the reference work for me.


\setupinteraction[state=start]

\setupnote[footnote][location=text]

\starttext

barley\footnote{barley} chocolate\footnote{chocolate}

\page

\placenotes[footnote]

\stoptext

Wolfgang


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


___
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] Remove left and right offset from nested frames?

2014-09-03 Thread Wolfgang Schuster

Am 03.09.2014 um 01:12 schrieb Mica Semrick m...@silentumbrella.com:

 Thanks Wolfgang, that worked well.
 
 Are there more reasons to use start  stop over start{}?

It’s more a matter of taste. \framed is better when you use to to frame short 
parts os text and \startframed when you want to put complete sentences into a 
frame.


A big difference is how leading and trailing spaces are handled, as can be seen 
in the following example the spaces before and after “text” are removed with 
\startframed.

\starttext

\framed[foregroundcolor=red]{ text }

\startframed[foregroundcolor=red] text \stopframed

\stoptext

Wolfgang
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] the new simplefonts stuff

2014-09-03 Thread Joshua Krämer
On 2014-09-01, 21:20, Sandra Snan wrote:

 This is probably a pretty basic question, but how do I find out the
 name of the font that \definefontfamily expects in the third argument?

Hi Sandra,

the only reliable method I have found is to inspect the font with
FontForge.

Here is an example: the Swiss 721 font from Bitstream (Helvetica
digitization).

FontForge reports:

Font name:Swiss721BT-Roman
Family name:  Swis721 BT
Display name: Swiss 721 BT
Weight:   Book

mtxrun --script fonts --list --all --pattern=swiss result:

swiss721bt  swiss721btroman Swiss721.ttf
swiss721btroman swiss721btroman Swiss721.ttf

The only name which works in ConTeXt is the family name (which can be
seen in FontForge): Swis721 BT, note the single s.  However, this
name is *not* shown in the mtxrun output.

Interestingly, I have also seen mtxrun show the family name (different
from the font name) for other fonts, so I really do not know how it
makes up its output.  It is certainly not useful to find out the
name that is to be used in ConTeXt.

Kind regards,
Joshua


___
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 new simplefonts stuff

2014-09-03 Thread Wolfgang Schuster

Am 01.09.2014 um 21:20 schrieb Sandra Snan sandra.s...@idiomdrottning.org:

 This is probably a pretty basic question, but how do I find out the name
 of the font that \definefontfamily expects in the third argument?
 
 For example,
 \definefontfamily [dejavu] [serif] [DejaVu Serif]
 works fine and sets the text in DejaVu Serif, but that’s not a name I
 can find with mtxrun –scripts font:
 
 ellen% mtxrun --script fonts  --list --all --pattern='*DejaVu*'|wc -l
 28
 ellen% mtxrun --script fonts  --info --list --all --pattern='*DejaVu*'|grep 
 -i DejaVu Serif|wc -l
 0
 
 
 
 mtxrun --script fonts --info for Deja Vu doesn't
 show that identifier anywhere. I want to find out what, for example,
 Bookman is called.
 
 \definetypeface [five] [rm] [serif] [bookman]
 works fine and sets the text in some font that sure looks a lot like
 Bookman to my eyes, but
 \definefontfamily [five] [serif] [bookman]
 doesn’t work at all and the text doesn’t show up.
 
 ellen% mtxrun --script fonts  --list --all --pattern='*bookman*'|wc -l
 5
 
 I’ve looked all over for this... even tried understanding font-sel.mkvii
 (with mediocre success).

You can take a look into the font manager of your os, attached is a screenshot 
from my system
where you can see in the second column the name of the font which does also go 
into the third
argument of the \definefontfamily command. This is also the same name which is 
shown
in the font selection menu form MS Office or OpenOffice.

 Extra thanks if there’s a way to get ligatures and protrusion to work for it.

\definefontfamily [examplefont] [rm] [TeX Gyre Pagella] 
[features={default,quality}]
\definefontfamily [examplefont] [ss] [TeX Gyre Heros]   
[features={default,quality}]
\definefontfamily [examplefont] [mm] [TeX Gyre Pagella Math]

\setupbodyfont[examplefont]

\setupalign[hanging]

\showframe[text][text]

\starttext

\input tufte

\ss\input tufte

\stoptext

Wolfgang
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] the new simplefonts stuff

2014-09-03 Thread Wolfgang Schuster

Am 03.09.2014 um 21:40 schrieb Joshua Krämer joshua.krae...@gmail.com:

 On 2014-09-01, 21:20, Sandra Snan wrote:
 
 This is probably a pretty basic question, but how do I find out the
 name of the font that \definefontfamily expects in the third argument?
 
 Hi Sandra,
 
 the only reliable method I have found is to inspect the font with
 FontForge.
 
 Here is an example: the Swiss 721 font from Bitstream (Helvetica
 digitization).
 
 FontForge reports:
 
 Font name:Swiss721BT-Roman
 Family name:  Swis721 BT
 Display name: Swiss 721 BT
 Weight:   Book
 
 mtxrun --script fonts --list --all --pattern=swiss result:
 
 swiss721bt  swiss721btroman Swiss721.ttf
 swiss721btroman swiss721btroman Swiss721.ttf
 
 The only name which works in ConTeXt is the family name (which can be
 seen in FontForge): Swis721 BT, note the single s.  However, this
 name is *not* shown in the mtxrun output.

Don’t expect logic in the internal names of a font, there is none.

 Interestingly, I have also seen mtxrun show the family name (different
 from the font name) for other fonts, so I really do not know how it
 makes up its output.  It is certainly not useful to find out the
 name that is to be used in ConTeXt.

The family name is shown when you use the info option, e.g.

mtxrun --script font --list --info --all texgyrepagella*

Wolfgang___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___