Re: [NTG-context] LuaTex error attempt to index global 'lang' (a nil value)

2008-04-07 Thread Taco Hoekwater


Roland wrote:
 Hi Taco, thanks for the quick reply. Something seems to work better
 now (no more errors about missing texmf directories) but I still get
 an error message after installing the new binary you pointed me to:
 
   (/usr/local/texlive/texmf-local/tex/context/base/sort-lan.tex
   loading : Context Sorting Macros (languages)
   (/usr/local/texlive/texmf-local/tex/context/base/sort-lan.mkiv))error:
 ...al/texlive/texmf-local/tex/context/base/node-ini.lua:345: attempt
 to index field 'otf' (a nil value)
   .
   l.3174
 
 Any idea?

No, this is about as confusing to me as it is to you. Can you post
a full log  please? I would like to know where the line 3174
comes from.

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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


[NTG-context] Mapping to SmallCaps for Latin Modern

2008-04-07 Thread Wolfgang Schuster
Hi Hans,

the mapping for the SmallCaps fonts from Latin Modern use the slanted version
for upright and the upright version for slanted style.

font-otf.tex:

\definefontsynonym [LMRoman10-CapsRegular]
[file:lmromancaps10-oblique] [features=default] % features=smallcaps?
\definefontsynonym [LMRoman10-CapsOblique]
[file:lmromancaps10-regular] [features=default]

should be

\definefontsynonym [LMRoman10-CapsRegular]
[file:lmromancaps10-regular] [features=default]
\definefontsynonym [LMRoman10-CapsOblique]
[file:lmromancaps10-oblique] [features=default]



The mapping for the Dunhill style seems to be wrong too.

\definefontsynonym [LMRoman10-Dunhill]
[file:lmromandunh10-oblique] [features=default]
\definefontsynonym [LMRoman10-DunhillOblique]
[file:lmromandunh10-regular] [features=default]


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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] scite properties enable utf8 and customizing

2008-04-07 Thread Jan-Erik Hägglöf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hans Hagen skrev:
 Jan-Erik Hägglöf wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 HI!

 I am trying to make Scite work in a context way by copying
 context.properties and friends, and it does work .

 The problem seems to be that make scite automatic be in utf8 mode. I
 have copying following parameters in the file .SciTEUser.properies by
 inserting following:

 LC_CTYPE=sv_SE.UTF-8
 output.code.page=65001

 but it seems not working when the program is restarted.

 All adjustments seems to be forgotten every time I restart.
 
 code.page=65001
 output.code.page=65001

This I've tried with no effect. Still the default alternative
8-bit instead of utf-8 is marked in file - encoding menu Therefore
I must remember to change that before i start writing, otherwise ååö
gets nasty.

Thanks for answer anyway

Best regards

Jan-Erik hägglöf


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH+fNY/zRis+sQPvARAuqOAKDp5EcdjHWDXjiwfi0SXPa3giKMqgCg6LyV
h6EUBnBrVFBrX4Sd22FRHjs=
=U6oQ
-END PGP SIGNATURE-
___
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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] analyzing type-otf.tex

2008-04-07 Thread Mojca Miklavec
Hello Hraban,

thanks for pointing this out.

To Hans: the \typescriptthree indeed needs to go out of those
definitions (line 300 in type-otf).

To Hraban: encoding=uc has *zero* effect. To be honest - I doubt that
you will be able to extract any more than (theoretical limit of) 256
glyphs from the Type1 font with XeTeX - character slots and font
glyphs are in one-to-one correlation, so I doubt that you can access
the glyphs outside of those 256 slots (unless you make tfm  map
files, but that's probably the reason why one wants to use XeTeX - to
get rid of that encoding mess). So: I guess that Latin-1 works, but
encoding=uc is ignored anyway.

type-xtx contains quite some uc leftovers, but I'm not sure if
fixing them is a wise idea or not (backward compatibility).

Mojca


On Sun, Apr 6, 2008 at 2:37 PM, Henning Hraban Ramm wrote:
 Am 2008-04-06 um 13:35 schrieb Henning Hraban Ramm:

  (2)
   This seems wrong to me (i.e. I don't understand it):
  
   \starttypescript [serif]
   [adventor,bonum,cursor,heros,pagella,schola,termes]
 \definefontsynonym
   [\typescriptprefix{n:\typescripttwo}-Regular]
   [file:texgyre\typescriptthree\typescriptprefix{f:\typescripttwo}-
   regular]
   [features=default]

  Works for me if I just leave out \typescriptthree !

  Here's my working setup, including a PostScript font:

  \usetypescriptfile  [type-otf2] % with change mentioned above
  \usetypescript  [schoolbook][uc]

  \starttypescript[sans]  [urw-grotesk]
 % PostScript name /  file name (in texmf tree) / instead of an 
 encoding
 \definefontsynonym  [URWGroteskT-LighNarr]  [file:u004242t]
  [features=default]
 \definefontsynonym  [URWGroteskT-MediNarr]  [file:u004244t]
  [features=default]
 \definefontsynonym  [URWGroteskT-LighNarrObli]  
 [file:u004262t]
  [features=default]
 \definefontsynonym  [URWGroteskT-MediNarrObli]  
 [file:u004264t]
  [features=default]
  \stoptypescript

  \starttypescript[sans]  [urw-grotesk]   %[name]
 \definefontsynonym  [Sans]  [URWGroteskT-LighNarr]
 \definefontsynonym  [SansItalic][URWGroteskT-LighNarrObli]
 \definefontsynonym  [SansBold]  [URWGroteskT-MediNarr]
 \definefontsynonym  [SansBoldItalic][URWGroteskT-MediNarrObli]
 \definefontsynonym  [SansSlanted]   [SansItalic]
 \definefontsynonym  [SansBoldSlanted]   [SansBoldItalic]
  \stoptypescript

  \starttypescript[fiee]  [mix]
 \definetypeface [mix]   [rm][serif] [schola][default] 
   %[encoding=
  \defaultencoding]
 \definetypeface [mix]   [ss][sans]  [urw-grotesk]   [default] 
   [encoding=uc]
  \stoptypescript
  \usetypescript  [fiee][mix]
  \setupbodyfont  [mix,rm,8pt]
___
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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


[NTG-context] luatex and interaction

2008-04-07 Thread Jean Magnan de Bornier
Hi all,
There had been a thread about it in august, but it seems part of the problem is
still there: words or sentences appearing in interaction are split: here
is a minimal example:

..
\setupinteraction [state=start]

\starttext
 L'un de ces documents
\useURL[bb][http://junon.univ-cezanne.fr/bornier/BBMon/bbmm.html][][The Nature 
of Boehm-Bawerk's Capital 
Market]\from[bb]\footnote{http://junon.univ-cezanne.fr/bornier/BBMon/bbmm.html} 
a été présenté en 2004

æ€ûœ
\stoptext

..

Same problem with bibliographical references when interaction is activated.

(Minimal version from minimals.contextgarden.net, up to date from yesterday.)

-- 
Jean
___
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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] several details (maybe bugs)

2008-04-07 Thread Wolfgang Schuster
On Sat, Apr 5, 2008 at 4:03 PM, Henning Hraban Ramm [EMAIL PROTECTED] wrote:
 While typesetting some proceedings, I stumpled upon the following
 issues:

 (1)
 \setupheads seems to do nothing - I must set every option for every
 head separately.
 AFAIR this is broken forever, at least it was the same in 2000.

It should as long as none of the values is overload with \setuphead

 (2)
 \setuphead[chapter][header=none]
 should switch off the header only on that page where the chapter
 starts, shouldn't it? (It disables headers completely.)
 Or how else would I achieve that?

 (3)
 \startitemize[n]
 Numbered itemizations suddenly(?) start with 0 - as this may be
 suitable for programmers, but it's, ehm, a bit unusual in every other
 context.
 Hm, it works in the garden.

 (4)
 Is it possible to include footnotes in tables in the normal footnote
 numbering and placement?
 (At the moment I use localfootnotes to enable footnotes in tables at
 all, but that's unsatisfying.)

No.

 (5)
 Is it possible to disable hyphenation in titles?

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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] several details (maybe bugs)

2008-04-07 Thread Wolfgang Schuster
On Sat, Apr 5, 2008 at 6:04 PM, Henning Hraban Ramm [EMAIL PROTECTED] wrote:
 Am 2008-04-05 um 17:28 schrieb Aditya Mahajan:
 
  (2)
  \setuphead[chapter][header=none]
  should switch off the header only on that page where the chapter
  starts, shouldn't it? (It disables headers completely.)
  Or how else would I achieve that?
 
  I remeber using \setuphead[chapter][header=high] in one of my
  projects.

 I found that, but it doesn't work. Nor does empty.

Make a *complete* example.

  (5)
  Is it possible to disable hyphenation in titles?
  Untested, but did you try passing
  align={flushleft,nothyphenated,verytolerant} to \setuphead?

 Thank you, I didn't remember that one can use several options for align.
 Wikified that.

Should be documented for \setupalign.

 Another one:
 (6)
 texshow documentation of indenting is wrong:
 This works:
 \setupindenting[yes, medium, next]
 But this doesn't:
 \setupindenting[normal, next]
 yes isn't documented.

\setupindenting was broken a little bit in the past (two to three years ago),
the manuals mention only what should have worked in the past (before my
time) and someone should add a note to the wiki.

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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] luatex and interaction

2008-04-07 Thread Taco Hoekwater


Jean Magnan de Bornier wrote:
 Hi all,
 There had been a thread about it in august, but it seems part of the problem 
 is
 still there: words or sentences appearing in interaction are split: here
 is a minimal example:

This is caused by the macro \processisolatedwords that is not updated
for MkIV yet. An extra \language=-1 is needed to fix this:


\def\processisolatedwords#1#2%
   {\bgroup
\fakecompoundhyphen
\dontcomplain
\forgetall
\nopenalties
\ifcase\isolatedwordsmode
  \def\processisolatedwords##1##2{##2{##1}}% we split only once
\fi
\global\let\localbetweenisolatedwords\betweenisolatedwords
\setbox0\normalhbox
  {\language=-1 % needed for MkIV
   \ignorespaces#1%
   \global\isolatedlastskip\lastskip}%
  .


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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] Scite startup script error

2008-04-07 Thread Abhishek Seth
I have updated lua to the latest version 5.1.3. And yes I have updated
to scite-ctx from the latest context distribution in the scite
directory.

On Sun, 2008-04-06 at 20:21 +0200, Hans Hagen wrote:
 Abhishek Seth wrote:
  Hi,
  
  After reinstalling the Scite 1.76 and putting the support files in
  place, I am getting the following error:
  
  attempt to call a string value
  Lua: error occured while loading startup script
  
  I don't know what it is. Can someone please help?
 
 probably related to scite using lua 5 now; did you update to the 
 scite-ctx from the context distribution?
 
 
 -
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


[NTG-context] first steps

2008-04-07 Thread Wolfgang Werners-Lucchini
hallo,

I tried to make my first luatex-steps with the following wiki-example
-
\usetypescript[palatino]
\setupbodyfont[palatino,12pt]
effe fietsen 2: \input tufte $\sqrt{2}$ \eogonek

\sc effe fietsen 2: \input tufte $\sqrt{2}$ \eogonek
-
after adding a \start/stoptext pair I get in 4 runs the following 
error:
-
){d:/context/tex/texmf/fonts/enc/dvips/tex-gyre/q-ec-sc.enc}fclose: 
No such file or directory
fclose: No such file or directory

! Emergency stop.
* tst3.tex

!  == Fatal error occurred, no output PDF file produced!
-

and in the 3. run I get 

-
fonts  : using map file: original-youngryu-px
[1.1
! This can't happen (ext4).
\actualshipout ... \box \postponedcontent \box 0}}
  \else \message 
{[\ifarrang...
\myshipout ... \fi {\thisisrealpage \realfolio #1}
  \gotonextrealpage 
\aftersh...
\dofinaloutput ...gebody #1#2\setpagecounters 
  \else \the 
\pageboundsetti...
\finaloutput ...EAEAEA \dofinaloutput \fi \fi #1#2
  
\resetselectiepagina \incr...
\sidefloatoutput ...e \else \finalsidefloatoutput 
  \global 
\sidefloatvsize \n...
argument ...\fi \else \the \defaultstreamoutput 
  \fi 
...
l.8 \stoptext
-

I can not interpret this error.
Can someone please explain!

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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] first steps

2008-04-07 Thread Taco Hoekwater


Wolfgang Werners-Lucchini wrote:
 hallo,
 
 I tried to make my first luatex-steps with the following wiki-example
 -
 \usetypescript[palatino]
 \setupbodyfont[palatino,12pt]
 effe fietsen 2: \input tufte $\sqrt{2}$ \eogonek
 
 \sc effe fietsen 2: \input tufte $\sqrt{2}$ \eogonek
 -
 after adding a \start/stoptext pair I get in 4 runs the following 
 error:

Exactly how did you run luatex? The canonical way is

   texexec --luatex tst3

but I expect you are using some editor interface?

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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] analyzing type-otf.tex

2008-04-07 Thread Henning Hraban Ramm
Am 2008-04-07 um 12:58 schrieb Mojca Miklavec:
 To Hraban: encoding=uc has *zero* effect. To be honest - I doubt that
 you will be able to extract any more than (theoretical limit of) 256
 glyphs from the Type1 font with XeTeX - character slots and font
 glyphs are in one-to-one correlation, so I doubt that you can access
 the glyphs outside of those 256 slots (unless you make tfm  map
 files, but that's probably the reason why one wants to use XeTeX - to
 get rid of that encoding mess). So: I guess that Latin-1 works, but
 encoding=uc is ignored anyway.

Oh? I thought uc encoding would magically enhance my type1 fonts with  
full unicode range...
;-)

Thanks for the clarification - I wasn't sure if I'd need uc, but  
since it worked this way, I left it there.


Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)

___
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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] first steps with XeTeX

2008-04-07 Thread Henning Hraban Ramm
Am 2008-04-07 um 00:53 schrieb Mojca Miklavec:
 Else you need to ask on the XeTeX mailing list. (But indeed: why not
 trying out LuaTeX?)
  I'm too lazy to recompile my binaries all the time; my old Mac is
  rather slow...
 That's why the minimal distribution (minimals.contextgarden.net) has
 been created. A single command should update everything.

ok, ok, I'll try luaTeX. But not just now.

  But I installed all necessary fonts for pdfTeX anyway.
  Lots of them, back in 2004/2005, see my typescripts collection:
  http://www.fiee.net/texnique/?menu=0-1-4lang=en
 Those should work, I guess. Not when called by name, but calling them
 by filename should be no problem.

Yes, seems to work. (see other thread)
I guess I'll re-publish my typescripts as soon as I'm actively using  
luaTeX - and as soon as I relaunch my website on Django (planning  
that for some months now...)

  BTW: I'd love to come to the gathering in Slovenija, but I must
  typeset my main project (a monthly city magazine) at that time.
 But that's a remote job, right? ;-)
 (We will have internet connection there :)

Unfortunately I can't do it on my own, need help from two colleagues  
to do it in time. Besides working full-time on that myself. And  
sending tons of images back and forth through any internet connection  
is no fun.

 Besides that - BachoTeX might be interesting to visit as well.

Of course. And PostNuke meeting, Django sprint, PyCon, DANTE, EUU  
Retreats, some courses  festivals and a lot more that I can't join  
this year... Only visiting DRUPA (printing fair).

Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)

___
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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] first steps

2008-04-07 Thread Wolfgang Werners-Lucchini
On 7 Apr 2008 at 20:22, [EMAIL PROTECTED] wrote:

  I tried to make my first luatex-steps with the following
 wiki-example
  -
  \usetypescript[palatino]
  \setupbodyfont[palatino,12pt]
  effe fietsen 2: \input tufte $\sqrt{2}$ \eogonek
  
  \sc effe fietsen 2: \input tufte $\sqrt{2}$ \eogonek
  -
  after adding a \start/stoptext pair I get in 4 runs the following
  error:
 
 Exactly how did you run luatex? The canonical way is
 
texexec --luatex tst3
 
 but I expect you are using some editor interface?

I am using scite with the following command:
texmfstart texexec --autopdf --luatex tst3.tex

If I try: 'texexec --luatex tst3' I get two runs with

{d:/context/tex/texmf/fonts/map/dvips/tex-gyre/qpl-ec.map}
fonts  : using map file: original-youngryu-px
{d:/context/tex/texmf-context/fonts/map/pdftex/context/original-
youngryu-px.map} [1.1]
systems: end file tst3 at line 8
 ){d:/context/tex/texmf/fonts/enc/dvips/tex-gyre/q-ec-sc.enc}fclose: 
No such file or directory
fclose: No such file or directory

! Emergency stop.
* tst3.tex

!  == Fatal error occurred, no output PDF file produced!

LuaTools | running command: luatex --fmt=d:/context/tex/texmf-
cache/luatex-
cache/context/c80dc1fd5292ec817c6e82c295beaf1e/formats/cont-en --
lua=d:/context/tex/texmf-cache/luatex-
cache/context/c80dc1fd5292ec817c6e82c295beaf1e/formats/cont-en.luc 
tst3.tex 
LuaTools | 
LuaTools | runtime: 23.213 secondsTeXUtil | parsing file tst3.tui


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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] analyzing type-otf.tex

2008-04-07 Thread Mojca Miklavec
On Mon, Apr 7, 2008 at 8:22 PM, Henning Hraban Ramm [EMAIL PROTECTED] wrote:
 Am 2008-04-07 um 12:58 schrieb Mojca Miklavec:

  To Hraban: encoding=uc has *zero* effect. To be honest - I doubt that
   you will be able to extract any more than (theoretical limit of) 256
   glyphs from the Type1 font with XeTeX - character slots and font
   glyphs are in one-to-one correlation, so I doubt that you can access
   the glyphs outside of those 256 slots (unless you make tfm  map
   files, but that's probably the reason why one wants to use XeTeX - to
   get rid of that encoding mess). So: I guess that Latin-1 works, but
   encoding=uc is ignored anyway.

  Oh? I thought uc encoding would magically enhance my type1 fonts with
  full unicode range...
  ;-)

It just used to map \eacute (and similar) to the proper Unicode glyph.
With pdfTeX that mapping depends on font encoding, so it has to be
specified. With XeTeX and LuaTeX unicode encoding is now applied
automatically. That's much better since now even
\font\a=low-level-font-loading \a \eacute works OK, which wasn't the
case one year ago.

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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] analyzing type-otf.tex

2008-04-07 Thread Mojca Miklavec
On Mon, Apr 7, 2008 at 8:22 PM, Henning Hraban Ramm wrote:

  Oh? I thought uc encoding would magically enhance my type1 fonts with
  full unicode range...
  ;-)

I almost forgot ... to be honest, I wanted to say: LuaTeX does
exactly that, but then I have remembered that you have explicitely
asked not to mention any LuaTeX benefits to you any more (at least
until next TeX Live comes out) ... :)

Mojca

PS: I didn't mean it seriously with internet connection in Bohinj -
that's why there were smilies next to the remark :)
___
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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


[NTG-context] patch for m-chemic.tex

2008-04-07 Thread Peter Münster
Hello,

What about the integration of this patch from Wolfgang Schuster into the
distribution:

- Forwarded message from Wolfgang Schuster [EMAIL PROTECTED] -

Date: Fri, 22 Feb 2008 11:57:37 +0100
From: Wolfgang Schuster [EMAIL PROTECTED]
Reply-To: mailing list for ConTeXt users ntg-context@ntg.nl
To: mailing list for ConTeXt users ntg-context@ntg.nl
Subject: Re: [NTG-context] \chemical and MKIV

On Thu, Feb 21, 2008 at 11:23 PM, Peter Münster [EMAIL PROTECTED] wrote:
 Hello,

  The following test-file produces an error:

  % engine=luatex
  \usemodule[chemic]
  \starttext
  \chemical{CO_2}
  \stoptext

This is tooo long.

\usemodule[chemic] is enough to produce the error with mkiv.

Replace the following lines in m-chemic

\ifx\beginpicture\undefined
  \let\normalgrid\grid
  \let\normalaxis\axis
  \input pictex.tex \relax
  \let\pictexgrid\grid
  \let\pictexaxis\axis
  \let\grid\normalgrid
  \let\axis\normalaxis
\fi

with

\ifx\beginpicture\undefined
  \let\beginpicture\relax
\fi

and the module works.

Wolfgang

- End forwarded message -

-- 
http://pmrb.free.fr/contact/

___
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  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___