[NTG-context] \usepseudocaps

2010-11-08 Thread Herbert Voss
Also from the documentation:

systems : begin file latex5 at line 2
error: ...text/tex/texmf-context/tex/context/base/typo-cap.lua:100:
attempt to call global 'copy_node' (a nil value)
.

system   error on line 6 in file latex5.tex: ? ...

1
2 \starttext
3
4 \userealcaps   \Caps{Herbert Voß}
5 \usepseudocaps \Caps{Herbert Voß}
6 
7 \stoptext

l.6


context minimal

Herbert
___
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] [OT] xkcd Knuth

2010-11-08 Thread Mojca Miklavec
http://www.xkcd.com/816/
___
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] [OT] xkcd Knuth

2010-11-08 Thread Martin Schröder
2010/11/8 Mojca Miklavec mojca.miklavec.li...@gmail.com:
 http://www.xkcd.com/816/

Nice. :-)

But Don doesn't write checks in US$ anymore. :-)

Best
   Martin
___
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] Lucida

2010-11-08 Thread Herbert Voss
Has someone a working typescript file for the Lucida
from TUG?

Herbert
___
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] [OT] xkcd Knuth

2010-11-08 Thread Tobias Burnus

On 11/08/2010 01:07 PM, Martin Schröder wrote:

2010/11/8 Mojca Miklavecmojca.miklavec.li...@gmail.com:

http://www.xkcd.com/816/


Don't miss the tool tip to the comic! (Put the mouse pointer over the 
image and wait a second or so - then the browser should should show a 
tool tip.)



Nice. :-)
But Don doesn't write checks in US$ anymore. :-)


I think if one really insists, one can also get real cash (I shall do 
my best to find a suitable way to send money to anyone who really 
prefers legal tender). Cf. 
http://sunburn.stanford.edu/~knuth/news08.html and 
http://en.wikipedia.org/wiki/Knuth_reward_check


Tobias
___
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] Lucida

2010-11-08 Thread Mojca Miklavec
2010/11/8 Herbert Voss wrote:
 Has someone a working typescript file for the Lucida
 from TUG?

Lucida should work out of the box (since beginning of 2010) if you
have the files from TUG installed:

% \usetypescript[lucida][ec] % for MKII
\setupbodyfont[lucida]

If you have any problems setting up the font, please ask. (See also
the beginning of http://wiki.contextgarden.net/Lucida, ignoring the
old instructions.)

If you find any problems with the math part, please report.

Mojca
___
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] Purpose of backend (export=yes)

2010-11-08 Thread Vladimir Lomov
Hi.

(I'm reading this ML but rarely ask questions.)

I try to understand the purpose of 'setupbackend'.

Consider the following three examples:

--

example name=ex1.tex
\setupbackend[export=yes]

\starttext

This is simple example. No font switching, no math.

\stoptext
/example

--

example name=ex2.tex
\setupbackend[export=yes]

\starttext

This is second example.
This time we try to use font switching mechanism:
This is normal, but this \bold{one is bold}. Normal again.

\stoptext
/example

--

example name=ex3.tex
\setupbackend[export=yes]

\starttext

This is third example with 'backend' 'export=yes'. Now we try simple math:

This is inline formula $E=mc^{2}$.

This is display formula
\startformula
  E=mc^{2}
\stopformula

\stoptext
/example

--

I compiled them with context (mkIV, context minimal) and got
ex{1,2,3}.export. I thought that I get not only the document content but
also its logical structure (for example some markup for font switching).

Is it true that 'backend' only output document content not its logic
strcuture? Does it work with math? The third example gives for math only
not letters.

I attached the resulted export files.

P.S. Then I saw the announce about 'backend'  'export=yes' I thought
that context would be good tool for notes. I imagine that I could wrote
a text file and make from it either pdf (for printing/screening) or html
(for screening) or may be convert xml (using existing tools and
methods) to other formats (rtf/odt/xhtml) that would contain math,
images, tables. But seems that I was wrong or this will be in future
of the backend?

---
WBR, Vladimir Lomov


-- 
If you make people think they're thinking, they'll love you; but if you
really make them think they'll hate you.
?xml version='1.0' standalone='yes' ?

!-- input filename   : ex1   --
!-- processing date  : Mon Nov  8 22:44:56 2010 --
!-- context version  : 2010.11.03 19:42  --
!-- exporter version : 0.10  --

document language='en' file='ex1' date='Mon Nov  8 22:44:56 2010' 
context='2010.11.03 19:42' version='0.10'
This is simple example. No font switching, no math.
/document
?xml version='1.0' standalone='yes' ?

!-- input filename   : ex2   --
!-- processing date  : Mon Nov  8 22:45:03 2010 --
!-- context version  : 2010.11.03 19:42  --
!-- exporter version : 0.10  --

document language='en' file='ex2' date='Mon Nov  8 22:45:03 2010' 
context='2010.11.03 19:42' version='0.10'
This is second example. This time we try to use font switching mechanism: This 
is normal, but this one is bold. Normal again.
/document
?xml version='1.0' standalone='yes' ?

!-- input filename   : ex3   --
!-- processing date  : Mon Nov  8 22:45:09 2010 --
!-- context version  : 2010.11.03 19:42  --
!-- exporter version : 0.10  --

document language='en' file='ex3' date='Mon Nov  8 22:45:09 2010' 
context='2010.11.03 19:42' version='0.10'
This is third example with 'backend' 'export=yes'. Now we try simple math:
  break/
 This is inline formula 
  math
mrow
  mi퐸/mi
  mo=/mo
  mi푚/mi
  msup
mi푐/mi
mn2/mn
  /msup
/mrow
  /math___
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] Ligatures on Linux Libertine Bold Italic

2010-11-08 Thread Marco

Hello there. 

I'm pretty new to ConTeXt and I'm really impressed by your work. So a
huge thanks is due. 

Anyway. Today I found that Linux Libertine Bold Italic doesn't create
the ligatures. These work on XeTeX. I took a look at
/tex/texmf-context/tex/context/base/type-otf.mkiv where the libertine
typescript is defined, but I couldn't find anything wrong. The fonts are
the one shipped with the latest updated TeXlive 2010 (they are correctly
loaded). 

With other fonts the ligatures for Bold Italic are created, so I'm a bit
lost. Is my setup broken somehow? Or the fonts are broken? Or is it a
bug? 

Thanks in advance. 

 start minimal example % 
\usetypescript[termes,libertine]
\setupbodyfont[termes,12pt]

\def\testtext{
The fi ffl ffi fluf \par 
{\it The fi ffl ffi fluf fi} \par
{\bf The fi ffl ffi fluf} \par
{\bi The fi ffl ffi fluf}\par}



\starttext
Termes:
\testtext
\switchtobodyfont[libertine,12pt]
Libertine: 
\testtext
\stoptext

% end minimal example %%

ConTeXt  ver: 2010.11.03 19:42 MKIV  fmt: 2010.11.8  
LuaTeX, Version beta-0.63.0-2010091123 (From the latest minimal distribution)


pdffonts output

name type  emb sub uni object ID
 - --- --- --- -
PHAMRR+TeXGyreTermes-Regular CID Type 0C   yes yes yes 18  0
OOTVTU+TeXGyreTermes-Italic  CID Type 0C   yes yes yes 19  0
QEYIRB+TeXGyreTermes-BoldCID Type 0C   yes yes yes 20  0
ONUACL+TeXGyreTermes-BoldItalic  CID Type 0C   yes yes yes 21  0
YFUCDN+LinLibertineO CID Type 0C   yes yes yes 22  0
PYLANJ+LinLibertineOICID Type 0C   yes yes yes 23  0
LBBYDA+LinLibertineOBCID Type 0C   yes yes yes 24  0
FBIQKN+LinLibertineOBI   CID Type 0C   yes yes yes 25  0





-- 
Marco


___
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] Ligatures on Linux Libertine Bold Italic

2010-11-08 Thread Wolfgang Schuster

Am 08.11.2010 um 15:53 schrieb Marco:

 
 Hello there. 
 
 I'm pretty new to ConTeXt and I'm really impressed by your work. So a
 huge thanks is due. 
 
 Anyway. Today I found that Linux Libertine Bold Italic doesn't create
 the ligatures. These work on XeTeX. I took a look at
 /tex/texmf-context/tex/context/base/type-otf.mkiv where the libertine
 typescript is defined, but I couldn't find anything wrong. The fonts are
 the one shipped with the latest updated TeXlive 2010 (they are correctly
 loaded). 
 
 With other fonts the ligatures for Bold Italic are created, so I'm a bit
 lost. Is my setup broken somehow? Or the fonts are broken? Or is it a
 bug? 

Add \definefontfeature[default][default][script=latn] before \setupbodyfont for 
Libertine.

ConTeXt expects for fonts to have ligatures in the default script of the font
which is for the case for the libertine fonts except for the bolditalic style
where you need the latin script to have ligatures, for me this is a bug in
the font and you should make a bug report.

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] Ligatures on Linux Libertine Bold Italic

2010-11-08 Thread Taco Hoekwater

On 11/08/2010 03:53 PM, Marco wrote:


Hello there.

I'm pretty new to ConTeXt and I'm really impressed by your work. So a
huge thanks is due.

Anyway. Today I found that Linux Libertine Bold Italic doesn't create
the ligatures. These work on XeTeX. I took a look at
/tex/texmf-context/tex/context/base/type-otf.mkiv where the libertine
typescript is defined, but I couldn't find anything wrong. The fonts are
the one shipped with the latest updated TeXlive 2010 (they are correctly
loaded).

With other fonts the ligatures for Bold Italic are created, so I'm a bit
lost. Is my setup broken somehow? Or the fonts are broken? Or is it a
bug?


Whether this is broken and/or a bug is not clear cut, but the Bold
Italic font does not have a default script, so it needs an explicit
script=latn in the feature setup (the other fonts actually do have a
default script, it is just the bold italic that does not have one).

I don't really know how to set that up in such a way that it will not 
affect other fonts as well, but as a workaround/large hammer method,

adding this

  \definefontfeature[default][default][script=latn]

before loading the typescript will probably work.

Best wishes,
Taco
___
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] Ligatures on Linux Libertine Bold Italic

2010-11-08 Thread Marco
Taco Hoekwater t...@elvenkind.com writes:

 On 11/08/2010 03:53 PM, Marco wrote:

 Hello there.

 I'm pretty new to ConTeXt and I'm really impressed by your work. So a
 huge thanks is due.

 Anyway. Today I found that Linux Libertine Bold Italic doesn't create
 the ligatures. These work on XeTeX. I took a look at
 /tex/texmf-context/tex/context/base/type-otf.mkiv where the libertine
 typescript is defined, but I couldn't find anything wrong. The fonts are
 the one shipped with the latest updated TeXlive 2010 (they are correctly
 loaded).

 With other fonts the ligatures for Bold Italic are created, so I'm a bit
 lost. Is my setup broken somehow? Or the fonts are broken? Or is it a
 bug?

 Whether this is broken and/or a bug is not clear cut, but the Bold
 Italic font does not have a default script, so it needs an explicit
 script=latn in the feature setup (the other fonts actually do have a
 default script, it is just the bold italic that does not have one).

 I don't really know how to set that up in such a way that it will not
 affect other fonts as well, but as a workaround/large hammer method,
 adding this

   \definefontfeature[default][default][script=latn]

 before loading the typescript will probably work.

 Best wishes,
 Taco

It worked. Now it's all clear to me. Thanks Wolfgang and Taco. 

I'll report the bug to the linux libertine project.

-- 
Marco

___
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] Lucida

2010-11-08 Thread Herbert Voss
Am 08.11.2010 14:42, schrieb Mojca Miklavec:
 2010/11/8 Herbert Voss wrote:
 Has someone a working typescript file for the Lucida
 from TUG?
 
 Lucida should work out of the box (since beginning of 2010) if you
 have the files from TUG installed:
 
 % \usetypescript[lucida][ec] % for MKII
 \setupbodyfont[lucida]
 
 If you have any problems setting up the font, please ask. (See also
 the beginning of http://wiki.contextgarden.net/Lucida, ignoring the
 old instructions.)
 
 If you find any problems with the math part, please report.

load otf preprocessing and caching took 0.057 seconds
define fonts source file 'lbr' is not found
define fonts unable to determine font format for ''
define fonts source file 'lbd' is not found
...


it looks for the yy filenames, but I have only the TUG ones.
In which file is this defined?

\setupbodyfont[lucida]

\starttext
foo \ss bar
\stoptext

context-minimal

Herbert
___
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] MkIV doesn't find font

2010-11-08 Thread Oliver Heins
I try to use Minion Pro as main font:

\usetypescriptfile[type-adobe]
\usetypescript[minion]
\setupbodyfont[minion]

To my irritation, ConTeXt/LuaTeX complains about not finding the font.

[…]
(/usr/local/texlive/2010/texmf-dist/tex/context/third/typescripts/type-adobe.mkiv)
define fonts font with name minionpro-regular is not found
define fonts unknown font minionpro-regular, loading aborted
define fonts unable to define minionpro-regular as \*minion12ptrmtf*
[…]

However, Minion Pro is installed on the system, running

$ mtxrun --script fonts --list --all --pattern=minionpro*

shows lots of entries.  However, there is no such font as
minionpro-regular, but minionproregular (without the hyphen):

Running $ mtxrun --script fonts --list --all --pattern=minionproregular
yields 
minionproregular   minionprocapt   /usr/local/share/fonts/MinionPro_Capt.otf,
while $ mtxrun --script fonts --list --all --pattern=minionpro-regular
returns an empty result.

What am I doing wrong?

TIA,
 olli

-- 
Oliver Heins he...@sopos.org  http://www.sopos.org/olli
GPG: F27A BA8C 1CFB B905 65A8  2544 0F07 B675 9A00 D827
1024D/9A00D827 2004-09-24 -- gpg --recv-keys 0x9A00D827
Please avoid sending me Word or PowerPoint attachments:
http://www.gnu.org/philosophy/no-word-attachments.html
___
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] FiXme-module

2010-11-08 Thread Wolfgang Schuster

Am 05.11.2010 um 13:12 schrieb Andreas Harder:

 Hi Wolfgang,
 
 I've played a bit with your FiXme-module. First of all, thanks for the work! 
 But I ran into following issues.
 
 1. Something is going wrong if I allow interaction. So the text is marked as 
 a link, but one can't jump to the right location.

Works for me, maybe a bug in context which is now solved.

 2. Instead of margin notes I would like to use PDF annotations, so I tried:
 \setupfixme
  [before={\startcomment[FiXme]},
   after=\stopcomment]
 This gives an error.

comments are defined as buffers and buffers can’t be used in before/after keys 
but i can add a „location=comment“ to the module.

 3. Is it possible to save the FiXme-list in a external text file? Something 
 like \savebuffer[expanded list of fixmes][list.txt]

Do you want a separate file for each entry or one file with all entries?

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] letter module, vertical offset of reference line

2010-11-08 Thread Wolfgang Schuster

Am 31.10.2010 um 11:16 schrieb Florian Wobbe:

 Can you make a example where this calculation goes wrong!
 
 Thanks! Of cause, a commented minimal example is attached.
 
 I have two problems and a wish:
 
 1) The reference line and the following subject line are placed too high.

I uploaded a new version where you disable the automatic placement of the 
reference line and the start of the letter text with

  \setupletterstyle[position=no] % default: position=yes

To remove the overlap of the information block and the reference you need the 
following settings in your style:

\setupletterstyle   [position=no]
\setupletterstyle[reference][voffset=11cm]
\setupletterstyle[firstpage][topspace=12cm,bottomspace=4cm]

 2) The footer has not enough space before and after.

The module has no default values for the footer because the din layouts ignore 
the foot but this should work:

\setupletterstyle
  [foot]
  [style=small]

\setupletterstyle
  [foot][layer]
  [voffset=1cm]

\setupletterstyle
  [foot][frame]
  [width=\textwidth,
   height=2.5cm,
   topframe=on]

\startsetups letter:foot
  A custom footer\\that is\\longer than\\three lines\\and misses space before 
and after and has strange linespacing.\par
\stopsetups

 3) It would be nice to have a bottomframe for the backaddress field that is 
 not longer than then the text itself.

\setupletterstyle
  [reference][frame]
  [width=fit]

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] MkIV doesn't find font

2010-11-08 Thread Hans Hagen
On 8-11-2010 7:37, Oliver Heins wrote:
 I try to use Minion Pro as main font:
 
 \usetypescriptfile[type-adobe]
 \usetypescript[minion]
 \setupbodyfont[minion]
 
 To my irritation, ConTeXt/LuaTeX complains about not finding the font.

I don't know type-adobe but it probably sets up a type 1 minion.

Take a look at type-otf.mkiv (at the end) and make yourself a minion
typescript (one of those 4 liners typescripts)

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] Lucida

2010-11-08 Thread Hans Hagen

On 8-11-2010 4:58, Herbert Voss wrote:

Am 08.11.2010 14:42, schrieb Mojca Miklavec:

2010/11/8 Herbert Voss wrote:

Has someone a working typescript file for the Lucida
from TUG?


Lucida should work out of the box (since beginning of 2010) if you
have the files from TUG installed:

% \usetypescript[lucida][ec] % for MKII
\setupbodyfont[lucida]

If you have any problems setting up the font, please ask. (See also
the beginning of http://wiki.contextgarden.net/Lucida, ignoring the
old instructions.)

If you find any problems with the math part, please report.


load otf  preprocessing and caching took 0.057 seconds
define fonts  source file 'lbr' is not found
define fonts  unable to determine font format for ''
define fonts  source file 'lbd' is not found



it looks for the yy filenames, but I have only the TUG ones.
In which file is this defined?

\setupbodyfont[lucida]

\starttext
foo \ss bar
\stoptext

context-minimal


Lucida is somewhat special. Context has always supported lucida but used 
the original lucida names (lbr.* etc). However, when tig took over from 
yandy it decided not to ship those files and as a result lucida became 
unuseable. Recently we adapted the typescripts to mkiv (and mkii). Math 
was also done again (lucida had its own math vector but the files that 
tug shipped were tuned for latex.).


So, for mkiv you need the latest typescript files for lucida 
(type-otf.mkiv etc), there should also be a lucida-math.flg file that 
defines the virtual open type math variant).


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] \usepseudocaps

2010-11-08 Thread Hans Hagen

On 8-11-2010 9:00, Herbert Voss wrote:

Also from the documentation:

systems : begin file latex5 at line 2
error: ...text/tex/texmf-context/tex/context/base/typo-cap.lua:100:
attempt to call global 'copy_node' (a nil value)
.

system  error on line 6 in file latex5.tex: ? ...

1
2 \starttext
3
4 \userealcaps   \Caps{Herbert Voß}
5 \usepseudocaps \Caps{Herbert Voß}
6
7 \stoptext

l.6


in typo-cap.lua, add

local copy_node   = node.copy

somewhere at the top and then remake the format.

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] MkIV doesn't find font

2010-11-08 Thread Oliver Heins
Hans Hagen pra...@wxs.nl writes:

 On 8-11-2010 7:37, Oliver Heins wrote:
 I try to use Minion Pro as main font:
 
 \usetypescriptfile[type-adobe]
 \usetypescript[minion]
 \setupbodyfont[minion]
 
 To my irritation, ConTeXt/LuaTeX complains about not finding the font.

 I don't know type-adobe but it probably sets up a type 1 minion.

 Take a look at type-otf.mkiv (at the end) and make yourself a minion
 typescript (one of those 4 liners typescripts)

Thank you Hans, it works now.

Best regards,
 olli

PS: For the record: type-minion.mkiv

\starttypescriptcollection[minionpro]

\starttypescript [serif] [minionpro]
\definefontsynonym [MinionPro-Regular][\s!file:MinionPro_Regular]
\definefontsynonym [MinionPro-Italic] [\s!file:MinionPro_It]
\definefontsynonym [MinionPro-Bold]   [\s!file:MinionPro_Bold]
\definefontsynonym [MinionPro-BoldItalic] [\s!file:MinionPro_BoldIt]
\stoptypescript

\starttypescript [serif] [minionpro] [name]
\setups[\s!font:\s!fallback:\s!serif]
\definefontsynonym [\s!Serif]   [MinionPro-Regular]
[\s!features=\s!default]
\definefontsynonym [\s!SerifItalic] [MinionPro-Italic] 
[\s!features=\s!default]
\definefontsynonym [\s!SerifBold]   [MinionPro-Bold]   
[\s!features=\s!default]
\definefontsynonym [\s!SerifBoldItalic] [MinionPro-BoldItalic] 
[\s!features=\s!default]
\definefontsynonym [\s!SerifCaps]   [MinionPro-Regular]
[\s!features=\s!smallcaps]
\stoptypescript

\starttypescript [minionpro]
\definetypeface [minionpro] [rm] [serif] [minionpro] [default]
\definetypeface [minionpro] [tt] [mono]  [default]   [default]
\quittypescriptscanning
\stoptypescript

\stoptypescriptcollection


-- 
Oliver Heins he...@sopos.org  http://www.sopos.org/olli
GPG: F27A BA8C 1CFB B905 65A8  2544 0F07 B675 9A00 D827
1024D/9A00D827 2004-09-24 -- gpg --recv-keys 0x9A00D827
Please avoid sending me Word or PowerPoint attachments:
http://www.gnu.org/philosophy/no-word-attachments.html
___
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] Lucida

2010-11-08 Thread Herbert Voss
Am 08.11.2010 14:42, schrieb Mojca Miklavec:
 2010/11/8 Herbert Voss wrote:
 Has someone a working typescript file for the Lucida
 from TUG?
 
 Lucida should work out of the box (since beginning of 2010) if you
 have the files from TUG installed:
 
 % \usetypescript[lucida][ec] % for MKII
 \setupbodyfont[lucida]
 
 If you have any problems setting up the font, please ask. (See also
 the beginning of http://wiki.contextgarden.net/Lucida, ignoring the
 old instructions.)

that didn't work for me. The documentation is no help
in this area. I put all Lucida fonts under
/opt/context/texmf-context/fonts/
Is this the correct dir, because there is also a texmf-fonts?
However, I tried to convert the commands for Libertine to Lucida
and now I can use the fonts except math. But I have
absoluteley no idea, if this is the right way ...

 Font Setup
\starttypescriptcollection [lucida]
\starttypescript[serif][lucida]
\definefontsynonym[LucidaBright]   [name:lucidabrightce]
  [features=default]
\definefontsynonym[LucidaBright-Italic]
[name:lucidabrightceitalic][features=default]
\definefontsynonym[LucidaBright-Bold]
[name:lucidabrightcedemibold]  [features=default]

\definefontsynonym[LucidaBrightBold-Italic][name:lucidabrightcedemibolditalic][features=default]
\definefontsynonym[LucidaBright-Caps]  [name:lucidabrightwest]
  [features=default]
\stoptypescript

\starttypescript[sans][lucida]
%\setups[font:fallback:serif]
\definefontsynonym[LucidaSans]   [name:lucidasansce]
  [features=default]
\definefontsynonym[LucidaSans-Italic][name:lucidasansdemiitalic]
 [features=default]
\definefontsynonym[LucidaSans-Bold]  [name:lucidasanscedemibold]
 [features=default]

\definefontsynonym[LucidaSans-BoldItalic][name:lucidasanscedemibolditalic][features=default]
\definefontsynonym[LucidaSans-Caps]  [Lucidabright-Caps]
  [features=default]
\stoptypescript

\starttypescript[mono][lucida]
%\setups[font:fallback:serif]
\definefontsynonym[LucidaMono] [name:lucidatypece]
[features=default]

\definefontsynonym[LucidaMono-Bold][name:lucidatypecebold][features=default]
\stoptypescript

\starttypescript[cal][lucida]
%\setups[font:fallback:serif]
\definefontsynonym[LucidaCal]   [name:lucidacalligraphy]
[features=default]

\definefontsynonym[LucidaCal-Italic][name:lucidacalligraphyitalic][features=default]
\stoptypescript

\starttypescript[handwritten][lucida]
%\setups[font:fallback:serif]
\definefontsynonym[LucidaHandwriting]
[name:lucidahandwriting][features=default]
\definefontsynonym[LucidaHandwriting-Italic]
[name:lucidahandwritingitalic][features=default]
\stoptypescript

\starttypescript[lucida]
\definetypeface[\typescriptone][rm][serif]  [lucida][default]
\definetypeface[\typescriptone][ss][sans]   [lucida][default]
\definetypeface[\typescriptone][tt][mono]   [lucida][default]
\definetypeface[\typescriptone][cal][cal]   [lucida][default]
\definetypeface[\typescriptone][hw][handwriting][lucida][default]
\definetypeface[\typescriptone][mm][math]   [modern][default]
\stoptypescript
\stoptypescriptcollection

\setupbodyfont[lucida,11pt,rm]

\starttext

Lucida Bright \ss Lucida Sans
\tt Lucida Mono \hw Lucida Handwriting
\\cal Lucida Clalligraphic

\stoptext

Herbert
___
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] writebetweenlist regression (mkiv)

2010-11-08 Thread Marco

Hello there. 

Currently \writebetweenlist doesn't work as advised. It inserts the
argument before the last entry of the list. The minimal example is
provided by the reference itself. 

http://wiki.contextgarden.net/Reference/en/writebetweenlist

The rule is correctly inserted at http://live.contextgarden.net/ and in
the ConTeXt shipped with TeXlive 2010 (2010.05.24), but not with the
current beta and the 2010.07.30 version. mkii works fine.

It prints 

--rule--
List entry A
List entry B

Best regards

-- 
Marco


___
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] FiXme-module

2010-11-08 Thread Andreas Harder

Am 08.11.2010 um 20:16 schrieb Wolfgang Schuster:

 
 Am 05.11.2010 um 13:12 schrieb Andreas Harder:
 
 Hi Wolfgang,
 
 I've played a bit with your FiXme-module. First of all, thanks for the work! 
 But I ran into following issues.
 
 1. Something is going wrong if I allow interaction. So the text is marked as 
 a link, but one can't jump to the right location.
 
 Works for me, maybe a bug in context which is now solved.

Hmm, I'm using the latest beta. I checked some documents and it works there but 
fails in something simple like
\setupinteraction[state=start]
\starttext
\placelist[chapter][interaction=all]
\dorecurse{5}{\chapter{Chapter} }
\stoptext
But anyway it has nothing to do with your module.

 2. Instead of margin notes I would like to use PDF annotations, so I tried:
 \setupfixme
 [before={\startcomment[FiXme]},
  after=\stopcomment]
 This gives an error.
 
 comments are defined as buffers and buffers can’t be used in before/after 
 keys but i can add a „location=comment“ to the module.

That would be nice, but would't alternative=comment“ more appropriate?

 3. Is it possible to save the FiXme-list in a external text file? Something 
 like \savebuffer[expanded list of fixmes][list.txt]
 
 Do you want a separate file for each entry or one file with all entries?

I thought of one file with all entries. 

My first idea was to write something like:
\startTODO
* \currentcomponent
** TODO fix that, fix this
** DONE fix that, fix this
\stopTODO
Write all TODO environments in a single file and use Emacs Org-mode to navigate 
through the list.

Best regards
Andreas
___
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] linebreak in part title

2010-11-08 Thread Michael Goerz
Hi everyone,

I want part titles to appear on the own (empty) page, centered
horizontally and vertically, and in small caps. To this end, I've set
up the \part command as

\def\Partcommand#1#2{\centerline{\smcp #2}}
\setuphead[part][
placehead=yes,
number=no,
page=mychapterpagebreak,
header=high,
footer=high,
before={\hbox{}\vfill},
command=\Partcommand,
after={\vfill},
prefix=no,
]

However, this does not seem to allow line breaks in a part title,
which is a problem with very long titles, e.g.
\part{Perspectives on Decision Ethics from the USA, Russian
Federation, Egypt, and the Czech Republic}

Is there any way to get a line break on the part page?

I should note that in the TOC, the part title is broken properly, and
also observes \crlf.

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
___


Re: [NTG-context] linebreak in part title

2010-11-08 Thread Michael Murphy

On 09/11/2010 00:30, Michael Goerz wrote:

Hi everyone,

I want part titles to appear on the own (empty) page, centered
horizontally and vertically, and in small caps. To this end, I've set
up the \part command as

 \def\Partcommand#1#2{\centerline{\smcp #2}}
 \setuphead[part][
 placehead=yes,
 number=no,
 page=mychapterpagebreak,
 header=high,
 footer=high,
 before={\hbox{}\vfill},
 command=\Partcommand,
 after={\vfill},
 prefix=no,
 ]



The problem is that \centerline puts things in a hbox, which won't break 
across lines. The solution below might not be the most ConTeXt-y way, 
but is perhaps the TeX way:


\def\raggedcenter{%
\hyphenpenalty=1 % no hyphenation
  \parindent=0pt \rightskip0pt plus1em % add stretchy glue to left
 \leftskip0pt plus1em  % and right
  \spaceskip.em \xspaceskip.5em \parfillskip=0pt % reg. word spacing
  \hbadness=1 % Last line will usually be underfull, so turn off
  % badness reporting.
}

\def\Partcommand#1#2{{\raggedcenter\smcp #2}}
  \setuphead[part][
  placehead=yes,
  number=no,
  page=mychapterpagebreak,
  header=high,
  footer=high,
  before={\hbox{}\vfill},
  command=\Partcommand,
  after={\vfill},
  prefix=no,
  ]

--
Michael Murphy
___
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] linebreak in part title

2010-11-08 Thread Michael Goerz
Hi Michael!

Thanks for your answer!

On Tue, Nov 9, 2010 at 1:01 AM, Michael Murphy
michael.mur...@uni-ulm.de wrote:
 On 09/11/2010 00:30, Michael Goerz wrote:

 Hi everyone,

 I want part titles to appear on the own (empty) page, centered
 horizontally and vertically, and in small caps. To this end, I've set
 up the \part command as

     \def\Partcommand#1#2{\centerline{\smcp #2}}
     \setuphead[part][
         placehead=yes,
         number=no,
         page=mychapterpagebreak,
         header=high,
         footer=high,
         before={\hbox{}\vfill},
         command=\Partcommand,
         after={\vfill},
         prefix=no,
     ]


 The problem is that \centerline puts things in a hbox, which won't break
 across lines.
That's probably right... just removing centerline doesn't lead to
linebreaks, however
 The solution below might not be the most ConTeXt-y way, but is
 perhaps the TeX way:

 \def\raggedcenter{%
        \hyphenpenalty=1 % no hyphenation
  \parindent=0pt \rightskip0pt plus1em % add stretchy glue to left
  \leftskip0pt plus1em                  % and right
  \spaceskip.em \xspaceskip.5em \parfillskip=0pt % reg. word spacing
  \hbadness=1 % Last line will usually be underfull, so turn off
                  % badness reporting.
 }

 \def\Partcommand#1#2{{\raggedcenter\smcp #2}}
  \setuphead[part][
      placehead=yes,
      number=no,
      page=mychapterpagebreak,
      header=high,
      footer=high,
      before={\hbox{}\vfill},
      command=\Partcommand,
      after={\vfill},
      prefix=no,
  ]
Hmm... that doesn't seem to do linebreaks. It shifts the part title a
bit horizontally. It also does weird things to some my *chapter* titles
(add a large space after the first word), which is configured as
\setuphead[chapter][
page=mychapterpagebreak,
number=no,
alternative=c,
align={center, nothyphenated, verytolerant},
style={\switchtobodyfont[16pt]},
header=high,
footer=chapterpage,
]

WTF? Very very strange!

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

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


Re: [NTG-context] linebreak in part title

2010-11-08 Thread Wolfgang Schuster

Am 09.11.2010 um 00:30 schrieb Michael Goerz:

 Hi everyone,
 
 I want part titles to appear on the own (empty) page, centered
 horizontally and vertically, and in small caps. To this end, I've set
 up the \part command as
 
\def\Partcommand#1#2{\centerline{\smcp #2}}
\setuphead[part][
placehead=yes,
number=no,
page=mychapterpagebreak,
header=high,
footer=high,
before={\hbox{}\vfill},
command=\Partcommand,
after={\vfill},
prefix=no,
]


\definefont[PartStyle][Caps sa 1]

\setuphead
   [part]
   [placehead=yes,
number=no,
before={\startstandardmakeup[align={middle,lohi}]},
after=\stopstandardmakeup,
style=PartStyle,
   %align=middle,
   %page={yes,header,footer,right},
   %header=high,
   %footer=high,
prefix=no]

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] Lucida

2010-11-08 Thread Mojca Miklavec
2010/11/8 Herbert Voss wrote:
 Am 08.11.2010 14:42, schrieb Mojca Miklavec:
 2010/11/8 Herbert Voss wrote:
 Has someone a working typescript file for the Lucida
 from TUG?

 Lucida should work out of the box (since beginning of 2010) if you
 have the files from TUG installed:

 % \usetypescript[lucida][ec] % for MKII
 \setupbodyfont[lucida]

 If you have any problems setting up the font, please ask. (See also
 the beginning of http://wiki.contextgarden.net/Lucida, ignoring the
 old instructions.)

 that didn't work for me. The documentation is no help
 in this area. I put all Lucida fonts under
 /opt/context/texmf-context/fonts/
 Is this the correct dir, because there is also a texmf-fonts?

You don't need any additional fonts subfolder since it is already in
the zip; and if you exctract the fonts into texmf-context, the font
might be deleted when you update the distribution, so you should
better use texmf-context, texmf-local, or ~/.texmf for example (not
100% about the last one, but I can check).

 However, I tried to convert the commands for Libertine to Lucida
 and now I can use the fonts except math. But I have
 absoluteley no idea, if this is the right way ...

You don't need any typescripts at all. They are already in
type-one.mkiv (type-one.mkii).

Just do the following:

1.) extract http://www.ctan.org/tex-archive/install/fonts/psfonts/bh/lucida.zip
into /opt/context/texmf-fonts/

2.) copy all *.pfb files into /opt/context/texmf-fonts/fonts/type1/bh/lucida

3.) run mktexlsr and mtxrun --generate

And don't use any self-made typescript. Math is done using
\starttypescript [math] [lucida]
\loadfontgoodies[lucida-math]
\definefontsynonym[mathroman][lucidam...@lucida-math]
\stoptypescript

For details you may check the file
/opt/context/texmf-context/tex/context/fonts/lucida-math.lfg

The last file is typically not something that user is expected to
write on his own (if he/she does, it could just as well be included in
ConTeXt itself; as the number of available math fonts is very very
limited).

Mojca
___
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
___