new release

new release

[Hans Hagen]

Hi,

Today i'll upload a new release. Highlights:

- some fixes/extensions discussed the last few weeks
- xetex support adapted to using xdvipdfmx
- ctxtools --update which will update your local context
- an update feature in scite (can be used a example for other editors)
- an integrated mpto (more robust that the binary approach)

(btw, use textext instead of btex .. etex when possible)

Taco will undoubtely give mnore details later. 

Keep in mind that you need to change the stubs: 

- preferable use texmfstart to launch scripts
- texmfstart itself can be stubbed if needed 
- there is a ../scripts/context/stubs path in the zip 

Hans 

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

Re: new release

[David Arnold]

Hans et al,

I don't understand the word "stub."

What are ctxtools?

What is meant by an update feature in Scite? Where are context  
features in scite discussed? For example, Hans let me knoow about Ctrl 
+F12 for compiling my figure library, but that's not on any of the  
menus of scite. What else is cool but hidden?

On May 8, 2006, at 4:04 AM, Hans Hagen wrote:

> Hi,
>
> Today i'll upload a new release. Highlights:
>
> - some fixes/extensions discussed the last few weeks
> - xetex support adapted to using xdvipdfmx
> - ctxtools --update which will update your local context
> - an update feature in scite (can be used a example for other editors)
> - an integrated mpto (more robust that the binary approach)
>
> (btw, use textext instead of btex .. etex when possible)
>
> Taco will undoubtely give mnore details later.
>
> Keep in mind that you need to change the stubs:
>
> - preferable use texmfstart to launch scripts
> - texmfstart itself can be stubbed if needed
> - there is a ../scripts/context/stubs path in the zip
>
> Hans
>
> -----------------------------------------------------------------
>                                           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
> -----------------------------------------------------------------
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context

Re: new release

[Taco Hoekwater]

Hi David,

I have no time right now to write the release notes, I will do
that in the morning (mine, that is). I'll keep your questions in
mind.

Cheers, Taco

David Arnold wrote:
> Hans et al,
> 
> I don't understand the word "stub."
> 
> What are ctxtools?
> 
> What is meant by an update feature in Scite? Where are context  
> features in scite discussed? For example, Hans let me knoow about Ctrl 
> +F12 for compiling my figure library, but that's not on any of the  
> menus of scite. What else is cool but hidden?

Re: new release

[Hans Hagen]

David Arnold wrote:
> Hans et al,
>
> I don't understand the word "stub."
>   
look in scripts/context/stubs

they are small bat files put in the bin path and launch rograms
> What are ctxtools?
>   
ctxtools pdftools xmltools textoosl tmftools .... are goodies that ship 
with context
> What is meant by an update feature in Scite? Where are context  
> features in scite discussed? For example, Hans let me knoow about Ctrl 
> +F12 for compiling my figure library, but that's not on any of the  
> menus of scite. What else is cool but hidden?
>   
in the new big windows zip there is a scite that has a menu entry (under 
tools) for updating your context

hans


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

Re: new release

[Aditya Mahajan]

On Mon, 8 May 2006, Hans Hagen wrote:

> (btw, use textext instead of btex .. etex when possible)

Some naive thoughts....

Do people still use

draw "string" infont fontname

Is it possible to provide a metapost package so that "...." defaults to 
textext?

For most graphics, I want TeX to do the typesetting. Using btex 
... etex or textext(...) for everything makes the source look ugly.


Something less drastic. Is it possible to define macros, say LABEL such 
that

LABEL("a string", origin)

is same as

label(textext(a string), origin)

I do not understand metapost well enough to  know if a macro can 
handle all the cases like

LABEL("a string" scaled 1.5, origin)

and so on.

Aditya

Re: new release

[Thomas A. Schmitz]

Hi Hans,

just downloaded the new release and regenerated the formats. Will play
with it later. For the time being just one question: the stubs in
scripts/context/stubs/unix and .../mswin seem to be identical; is that
what you meant? I doubt that many unixoid systems will be at ease with 
.bat executables and c: paths...

Best

Thomas

On Mon, 2006-05-08 at 13:04 +0200, Hans Hagen wrote:
> Hi,
> 
> Today i'll upload a new release. Highlights:
> 
> - some fixes/extensions discussed the last few weeks
> - xetex support adapted to using xdvipdfmx
> - ctxtools --update which will update your local context
> - an update feature in scite (can be used a example for other editors)
> - an integrated mpto (more robust that the binary approach)
> 
> (btw, use textext instead of btex .. etex when possible)
> 
> Taco will undoubtely give mnore details later. 
> 
> Keep in mind that you need to change the stubs: 
> 
> - preferable use texmfstart to launch scripts
> - texmfstart itself can be stubbed if needed 
> - there is a ../scripts/context/stubs path in the zip 
> 
> Hans 
> 
> -----------------------------------------------------------------
>                                           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
> -----------------------------------------------------------------
> 
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context

Re: new release

[Hans Hagen]

Thomas A. Schmitz wrote:
> Hi Hans,
>
> just downloaded the new release and regenerated the formats. Will play
> with it later. For the time being just one question: the stubs in
> scripts/context/stubs/unix and .../mswin seem to be identical; is that
> what you meant? I doubt that many unixoid systems will be at ease with 
> .bat executables and c: paths...
>   
hm, i will check that 

Hans 

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

Re: new release

[Hans Hagen]

Thomas A. Schmitz wrote:
> Hi Hans,
>
> just downloaded the new release and regenerated the formats. Will play
> with it later. For the time being just one question: the stubs in
> scripts/context/stubs/unix and .../mswin seem to be identical; is that
> what you meant? I doubt that many unixoid systems will be at ease with 
> .bat executables and c: paths...
>   
a typo indeed, you can correct it with: 

texmfstart --verbose --unix --stubpath=<yourbinpath>  --make all

Hans 

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

Re: new release

[Christopher Creutzig]

Hans Hagen wrote:

> texmfstart --verbose --unix --stubpath=<yourbinpath>  --make all

  That is a cool feature.  But it does not set executable bits on the 
stubs yet, could you fix that?


Regards,
	Christopher

Re: new release

[Hans Hagen]

Christopher Creutzig wrote:
> Hans Hagen wrote:
>
>   
>> texmfstart --verbose --unix --stubpath=<yourbinpath>  --make all
>>     
>
>   That is a cool feature.  But it does not set executable bits on the 
> stubs yet, could you fix that?
>   
if you tell me what magic code is needed ... 

Hans 

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

Re: new release

[nico]

On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen <pragma@wxs.nl> wrote:

> Hi,
>
> Today i'll upload a new release.

Got big problems with the fonts that are no more found when using the ruby  
stuff. Since the unix stubs are crappy, I do this:

ruby /usr/local/share/texmf-local/scripts/context/ruby/texmfstart.rb  
texexec.rb --pdf typefile.tex

What's wrong?

Here is the log:

This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=cont-en
2006.5.8)  8 MAY 2006 19:55
entering extended mode
    (/usr/local/share/texmf-local/web2c/natural.tcx)
**typefile.tex emergencyend
(./typefile.tex

ConTeXt  ver: 2006.05.08 12:59  fmt: 2006.5.8  int: english  mes: english

language        : language en is active
<protectionstate 0>
system          : cont-new loaded
(/usr/local/share/texmf-local/tex/context/base/cont-new.tex
systems         : beware: some patches loaded from cont-new.tex
color           : palette rollover is available
)
system          : cont-old loaded
(/usr/local/share/texmf-local/tex/context/base/cont-old.tex
loading         : Context Old Macros
)
system          : cont-fil loaded
(/usr/local/share/texmf-local/tex/context/base/cont-fil.tex
loading         : Context File Synonyms
)
system          : cont-sys loaded
(/usr/local/share/texmf-dist/tex/context/user/cont-sys.tex
(/usr/local/share/texmf-local/tex/context/base/type-exa.tex)
(/usr/local/share/texmf-local/tex/context/base/type-syn.tex)
(/usr/local/share/texmf-local/tex/context/base/type-enc.tex)
(/usr/local/share/texmf-local/tex/context/base/type-siz.tex)
(/usr/local/share/texmf-local/tex/context/base/type-map.tex)
(/usr/local/share/texmf-local/tex/context/base/type-spe.tex)
(/usr/local/share/texmf-local/tex/context/base/type-akb.tex))
bodyfont        : 12pt rm is loaded
language        : patterns nl->texnansi:texnansi->1->2:3 nl->ec:ec->2->2:3
fr->
texnansi:texnansi->3->2:3 fr->ec:ec->4->2:3 de->texnansi:texnansi->5->2:3
de->e
c:ec->6->2:3 it->texnansi:texnansi->7->2:3 it->ec:ec->8->2:3
pt->texnansi:texna
nsi->9->2:3 pt->ec:ec->10->2:3 hr->ec:ec->11->2:3 pl->pl0:pl0->12->2:3
pl->ec:e
c->13->2:3 pl->qx:qx->14->2:3 cz->il2:il2->15->2:3 cz->ec:ec->16->2:3
sk->il2:i
l2->17->2:3 sk->ec:ec->18->2:3 sl->ec:ec->19->2:3 en->ec:ec->21->2:3
uk->ec:ec-
> 22->2:3 us->ec:ec->23->2:3 agr->agr:agr->24->2:3 da->ec:ec->25->2:3  
> sv->ec:ec-
> 26->2:3 af->ec:ec->27->2:3 no->ec:ec->28->2:3 deo->ec:ec->29->2:3  
> es->ec:ec->3
0->2:3 ca->ec:ec->31->2:3 la->ec:ec->32->2:3 ro->ec:ec->33->2:3
tr->ec:ec->34->
2:3 fi->ec:ec->36->2:3 hu->ec:ec->37->2:3 loaded
specials        : tex,postscript,rokicki loaded
\openout2 = `typefile.tui'.

system          : typefile.top loaded
(./typefile.top
specials        : loading definition file tpd
(/usr/local/share/texmf-local/tex/context/base/spec-tpd.tex
specials        : loading definition file fdf
(/usr/local/share/texmf-local/tex/context/base/spec-fdf.tex)
specials        : fdf loaded
)
specials        : fdf,tpd loaded
)
\openout0 = `typefile-mpgraph.mp'.

\openout0 = `mpgraph.mp'.

    (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo)
(./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo)
(./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo)
systems         : begin file typefile at line 146
(/usr/local/share/texmf-local/tex/context/base/pdfr-ec.tex)
verbatim        : file ./test-001.tex does not exist
verbatim        : file joke does not exist
fonts           : resetting map file list
fonts           : using map file: original-base
fonts           : using map file: ec-public-lm
fonts           : using map file: ec-base
fonts           : using map file: 8r-base
fonts           : using map file: t5-base
fonts           : using map file: original-ams-base
fonts           : using map file: original-ams-euler
fonts           : using map file: original-public-lm
[1.1
Warning: pdfetex (file original-empty.map): cannot open font map file

Warning: pdfetex (file original-base.map): cannot open font map file

Warning: pdfetex (file ec-public-lm.map): cannot open font map file

Warning: pdfetex (file ec-base.map): cannot open font map file

Warning: pdfetex (file 8r-base.map): cannot open font map file

Warning: pdfetex (file t5-base.map): cannot open font map file

Warning: pdfetex (file original-ams-base.map): cannot open font map file

Warning: pdfetex (file original-ams-euler.map): cannot open font map file

Warning: pdfetex (file original-public-lm.map): cannot open font map file
] [2.2]
systems         : end file typefile at line 167
    )
Here is how much of TeX's memory you used:
    1168 strings out of 58787
    21094 string characters out of 563686
    4585586 words of memory out of 5529308
    39652 multiletter control sequences out of 10000+100000
    75349 words of font info for 38 fonts, out of 500000 for 2000
    232 hyphenation exceptions out of 1000
    47i,18n,54p,252b,773s stack positions out of
1500i,500n,5000p,200000b,5000s
PDF statistics:
    10 PDF objects out of 300000
    0 named destinations out of 131072
    5 words of extra memory for PDF output out of 65536

Warning: pdfetex (file ec-lmtt12): Font ec-lmtt12 at 600 not found

Warning: pdfetex (file ec-lmr12): Font ec-lmr12 at 600 not found
Output written on typefile.pdf (2 pages, 3101 bytes).


Regards,
BG

Re: new release

[Hans Hagen]

nico wrote:
> On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen <pragma@wxs.nl> wrote:
>
>   
> Got big problems with the fonts that are no more found when using the ruby  
> stuff. Since the unix stubs are crappy, I do this:
>
> ruby /usr/local/share/texmf-local/scripts/context/ruby/texmfstart.rb  
> texexec.rb --pdf typefile.tex
>   
this should be ok in this mornings version
> What's wrong?
>   
maybe you need  to run mktexlsr

Hans

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

Re: new release

[nico]

On Tue, 09 May 2006 11:09:43 +0200, Hans Hagen <pragma@wxs.nl> wrote:

> nico wrote:
>> On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen <pragma@wxs.nl> wrote:
>>
>>
>> Got big problems with the fonts that are no more found when using the  
>> ruby
>> stuff. Since the unix stubs are crappy, I do this:
>>
>> ruby /usr/local/share/texmf-local/scripts/context/ruby/texmfstart.rb
>> texexec.rb --pdf typefile.tex
>>
> this should be ok in this mornings version

Seems that the unix texmfstart stub is missing.

>> What's wrong?
>>
> maybe you need  to run mktexlsr

Doesn't help, and the required map files are here for a while (eg:  
kpsewhich ec-base.map gives
/usr/local/share/texmf-local/fonts/map/pdftex/context/ec-base.map).

I tried to use the perl version, and now it tries to find stuff in dvipdfm  
fonts, which plants:

Warning: pdfetex (file  
/usr/local/share/texmf-local/fonts/map/dvipdfm/context/original-base.map):  
invalid entry for `fmvr8x': font file missing

It works if i remove (or rename) the dvipdfm directory.

What can i do to have ruby thing working, and pdftex fonts used instead of  
dvipdfm ones?

Regards,
BG

Re: new release

[Hans Hagen]

nico wrote:
> On Tue, 09 May 2006 11:09:43 +0200, Hans Hagen <pragma@wxs.nl> wrote:
>
>   
>> nico wrote:
>>     
>>> On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen <pragma@wxs.nl> wrote:
>>>
>>>
>>> Got big problems with the fonts that are no more found when using the  
>>> ruby
>>> stuff. Since the unix stubs are crappy, I do this:
>>>
>>> ruby /usr/local/share/texmf-local/scripts/context/ruby/texmfstart.rb
>>> texexec.rb --pdf typefile.tex
>>>
>>>       
>> this should be ok in this mornings version
>>     
>
> Seems that the unix texmfstart stub is missing.
>   
indeed; the fastest method is:

cp texmfstart.rb  .../bin/texmfstart

or make a  stub that directly points to your copy of texmfstart
>   
>>> What's wrong?
>>>
>>>       
>> maybe you need  to run mktexlsr
>>     
>
> Doesn't help, and the required map files are here for a while (eg:  
> kpsewhich ec-base.map gives
> /usr/local/share/texmf-local/fonts/map/pdftex/context/ec-base.map).
>
> I tried to use the perl version, and now it tries to find stuff in dvipdfm  
> fonts, which plants:
>
> Warning: pdfetex (file  
> /usr/local/share/texmf-local/fonts/map/dvipdfm/context/original-base.map):  
> invalid entry for `fmvr8x': font file missing
>
> It works if i remove (or rename) the dvipdfm directory.
>
> What can i do to have ruby thing working, and pdftex fonts used instead of  
> dvipdfm ones?
>   
your texmf.cnf file should contain:

TEXFONTMAPS   = 
.;$TEXMF/fonts/map/{$progname,pdftex,dvips,}//;$TEXMF/{$progname,pdftex,dvips}/{config,}//

as long as we have no uniform map file syntax, progs needs to be able to 
find their own map files

Hans 

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

Re: new release

[nico]

On Tue, 09 May 2006 15:11:23 +0200, Hans Hagen <pragma@wxs.nl> wrote:

> nico wrote:
>> On Tue, 09 May 2006 11:09:43 +0200, Hans Hagen <pragma@wxs.nl> wrote:
>>
>>
>>> nico wrote:
>>>
>>>> On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen <pragma@wxs.nl> wrote:
>>>>
>>>>
>>>> Got big problems with the fonts that are no more found when using the
>>>> ruby
>>>> stuff. Since the unix stubs are crappy, I do this:
>>>>
>>>> ruby /usr/local/share/texmf-local/scripts/context/ruby/texmfstart.rb
>>>> texexec.rb --pdf typefile.tex
>>
>>>> What's wrong?
>>>>
>>> maybe you need  to run mktexlsr
>>>
>> Doesn't help, and the required map files are here for a while (eg:
>> kpsewhich ec-base.map gives
>> /usr/local/share/texmf-local/fonts/map/pdftex/context/ec-base.map).
>>
>> I tried to use the perl version, and now it tries to find stuff in  
>> dvipdfm
>> fonts, which plants:
>>
>> Warning: pdfetex (file
>> /usr/local/share/texmf-local/fonts/map/dvipdfm/context/original-base.map):
>> invalid entry for `fmvr8x': font file missing
>>
>> It works if i remove (or rename) the dvipdfm directory.
>>
>> What can i do to have ruby thing working, and pdftex fonts used instead  
>> of
>> dvipdfm ones?
>>
> your texmf.cnf file should contain:
>
> TEXFONTMAPS   =
> .;$TEXMF/fonts/map/{$progname,pdftex,dvips,}//;$TEXMF/{$progname,pdftex,dvips}/{config,}//
>
> as long as we have no uniform map file syntax, progs needs to be able to
> find their own map files

Ok, thanks, modifying texmf.cnf as you say fixes the path precedence. Now,  
is there a ruby debug mode to see why the paths are lost with texexec.rb?  
Or tests I could do to find out what happens?

Regards,
BG

Re: new release

[Hans Hagen]

nico wrote:
>
> Ok, thanks, modifying texmf.cnf as you say fixes the path precedence. Now,  
> is there a ruby debug mode to see why the paths are lost with texexec.rb?  
> Or tests I could do to find out what happens?
>   
--verbose gives some info 

Hans  

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

Re: new release

[nico]

On Tue, 09 May 2006 15:11:23 +0200, Hans Hagen <pragma@wxs.nl> wrote:

>>>> What's wrong?
>>>>
>>> maybe you need  to run mktexlsr
>>>
>> Doesn't help, and the required map files are here for a while (eg:
>> kpsewhich ec-base.map gives
>> /usr/local/share/texmf-local/fonts/map/pdftex/context/ec-base.map).
>>
>> I tried to use the perl version, and now it tries to find stuff in  
>> dvipdfm
>> fonts, which plants:
>>
>> Warning: pdfetex (file
>> /usr/local/share/texmf-local/fonts/map/dvipdfm/context/original-base.map):
>> invalid entry for `fmvr8x': font file missing
>>
>> It works if i remove (or rename) the dvipdfm directory.
>>
>> What can i do to have ruby thing working, and pdftex fonts used instead  
>> of
>> dvipdfm ones?
>>
> your texmf.cnf file should contain:
>
> TEXFONTMAPS   =
> .;$TEXMF/fonts/map/{$progname,pdftex,dvips,}//;$TEXMF/{$progname,pdftex,dvips}/{config,}//

For the ruby issue:

if I remove the TEXFONTMAPS environment setting from tex.rb, it works on  
my machine. I don't know if it can be a fix working on any platform:

     def fixbackendvars(backend)
         if backend then
             report("fixing backend map path for #{backend}") if  
getvariable('verbose')
             ENV['backend']     = backend ;
             ENV['progname']    = backend unless validtexengine(backend)
             #ENV['TEXFONTMAPS'] =  
".;\$TEXMF/fonts/map/{#{backend},pdftex,dvips,}//"
         else
             report("unable to fix backend map path") if  
getvariable('verbose')
         end
     end

Regards,
BG

Re: new release

[Hans Hagen]

nico wrote:
> On Tue, 09 May 2006 15:11:23 +0200, Hans Hagen <pragma@wxs.nl> wrote:
>
>   
>>>>> What's wrong?
>>>>>
>>>>>           
>>>> maybe you need  to run mktexlsr
>>>>
>>>>         
>>> Doesn't help, and the required map files are here for a while (eg:
>>> kpsewhich ec-base.map gives
>>> /usr/local/share/texmf-local/fonts/map/pdftex/context/ec-base.map).
>>>
>>> I tried to use the perl version, and now it tries to find stuff in  
>>> dvipdfm
>>> fonts, which plants:
>>>
>>> Warning: pdfetex (file
>>> /usr/local/share/texmf-local/fonts/map/dvipdfm/context/original-base.map):
>>> invalid entry for `fmvr8x': font file missing
>>>
>>> It works if i remove (or rename) the dvipdfm directory.
>>>
>>> What can i do to have ruby thing working, and pdftex fonts used instead  
>>> of
>>> dvipdfm ones?
>>>
>>>       
>> your texmf.cnf file should contain:
>>
>> TEXFONTMAPS   =
>> .;$TEXMF/fonts/map/{$progname,pdftex,dvips,}//;$TEXMF/{$progname,pdftex,dvips}/{config,}//
>>     
>
> For the ruby issue:
>
> if I remove the TEXFONTMAPS environment setting from tex.rb, it works on  
> my machine. I don't know if it can be a fix working on any platform:
>
>      def fixbackendvars(backend)
>          if backend then
>              report("fixing backend map path for #{backend}") if  
> getvariable('verbose')
>              ENV['backend']     = backend ;
>              ENV['progname']    = backend unless validtexengine(backend)
>              #ENV['TEXFONTMAPS'] =  
> ".;\$TEXMF/fonts/map/{#{backend},pdftex,dvips,}//"
>          else
>              report("unable to fix backend map path") if  
> getvariable('verbose')
>          end
>      end
>   
i wonder why this does not work 

Hans 

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

Re: new release

[nico]

On Tue, 09 May 2006 17:16:38 +0200, Hans Hagen <pragma@wxs.nl> wrote:

>>              #ENV['TEXFONTMAPS'] =
>> ".;\$TEXMF/fonts/map/{#{backend},pdftex,dvips,}//"
> i wonder why this does not work

Unix likes column separator (and often cannot stand windows one ;-). If i  
change ';' into ':' it works. BTW, why is this set? Isn't it up to  
texmf.cnf to configure this (like for texexec.pl)?

Regards,
BG

Re: new release

[Hans Hagen]

nico wrote:
> On Tue, 09 May 2006 17:16:38 +0200, Hans Hagen <pragma@wxs.nl> wrote:
>
>   
>>>              #ENV['TEXFONTMAPS'] =
>>> ".;\$TEXMF/fonts/map/{#{backend},pdftex,dvips,}//"
>>>       
>> i wonder why this does not work
>>     
>
> Unix likes column separator (and often cannot stand windows one ;-). If i  
> change ';' into ':' it works. BTW, why is this set? Isn't it up to  
> texmf.cnf to configure this (like for texexec.pl)?
>   
as usual, it takes a while before such changes end up in the mainstream distributions 

Hans 

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

Re: new release

[frantisek holop]

hmm, on Tue, May 09, 2006 at 03:11:23PM +0200, Hans Hagen said that
> > Warning: pdfetex (file  
> > /usr/local/share/texmf-local/fonts/map/dvipdfm/context/original-base.map):  
> > invalid entry for `fmvr8x': font file missing
> >
> > It works if i remove (or rename) the dvipdfm directory.
> >
> > What can i do to have ruby thing working, and pdftex fonts used instead of  
> > dvipdfm ones?
> >   
> your texmf.cnf file should contain:
> 
> TEXFONTMAPS   = 
> .;$TEXMF/fonts/map/{$progname,pdftex,dvips,}//;$TEXMF/{$progname,pdftex,dvips}/{config,}//
> 
> as long as we have no uniform map file syntax, progs needs to be able to 
> find their own map files

i just did:

# rm -r /usr/local/share/texmf-local/fonts/map/dvipdfm/context
# rm -r /usr/local/share/texmf-local/fonts/map/dvips/context
# texhash

aren't these files awfully old anyway?  are they needed?
as cont-lm is not needed anymore i thought these are obsolete files...

-f
-- 
light doesn't emit energy; it emits little dark eaters

Re: new release

[Hans Hagen]

frantisek holop wrote:
> hmm, on Tue, May 09, 2006 at 03:11:23PM +0200, Hans Hagen said that
>   
>>> Warning: pdfetex (file  
>>> /usr/local/share/texmf-local/fonts/map/dvipdfm/context/original-base.map):  
>>> invalid entry for `fmvr8x': font file missing
>>>
>>> It works if i remove (or rename) the dvipdfm directory.
>>>
>>> What can i do to have ruby thing working, and pdftex fonts used instead of  
>>> dvipdfm ones?
>>>   
>>>       
>> your texmf.cnf file should contain:
>>
>> TEXFONTMAPS   = 
>> .;$TEXMF/fonts/map/{$progname,pdftex,dvips,}//;$TEXMF/{$progname,pdftex,dvips}/{config,}//
>>
>> as long as we have no uniform map file syntax, progs needs to be able to 
>> find their own map files
>>     
>
> i just did:
>
> # rm -r /usr/local/share/texmf-local/fonts/map/dvipdfm/context
> # rm -r /usr/local/share/texmf-local/fonts/map/dvips/context
> # texhash
>
> aren't these files awfully old anyway?  are they needed?
> as cont-lm is not needed anymore i thought these are obsolete files...
>   
the lm map files are needed (unless you have files on your syetem that do the same); context loads map files on demand and does not use updmap things 

Hans 

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

Re: new release

[frantisek holop]

hmm, on Tue, May 16, 2006 at 01:15:55AM +0200, Hans Hagen said that
> > i just did:
> >
> > # rm -r /usr/local/share/texmf-local/fonts/map/dvipdfm/context
> > # rm -r /usr/local/share/texmf-local/fonts/map/dvips/context
> > # texhash
> >
> > aren't these files awfully old anyway?  are they needed?
> > as cont-lm is not needed anymore i thought these are obsolete files...
> >   
> the lm map files are needed (unless you have files on your syetem that
> do the same); context loads map files on demand and does not use
> updmap things 

i meant, the cont-lm zip file is not needed anymore (if i get it right)
because it is now distributed with context, not that the files are not
needed.  do the files distributed with context make the dvip{s,dfm}
files obsolete (say from teTeX-3.0)?

-f
-- 
never trust a person who says, "trust me"

Re: new release

[frantisek holop]

hmm, on Tue, May 16, 2006 at 01:06:26AM +0200, frantisek holop said that
> > your texmf.cnf file should contain:
> > 
> > TEXFONTMAPS   = 
> > .;$TEXMF/fonts/map/{$progname,pdftex,dvips,}//;$TEXMF/{$progname,pdftex,dvips}/{config,}//
> > 
> > as long as we have no uniform map file syntax, progs needs to be able to 
> > find their own map files
> 
> i just did:
> 
> # rm -r /usr/local/share/texmf-local/fonts/map/dvipdfm/context
> # rm -r /usr/local/share/texmf-local/fonts/map/dvips/context
> # texhash
> 
> aren't these files awfully old anyway?  are they needed?
> as cont-lm is not needed anymore i thought these are obsolete files...

btw. http://live.contextgarden.net/ is suffering from this also:

from the texexec output:

[1.1{/opt/context/current/texmf/fonts/map/dvipdfm/context/original-empty.map}{/
opt/context/current/texmf/fonts/map/dvipdfm/context/original-base.map
Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `fmvr8x': font file missing

Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `xycmat11': font file missing

Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `xycmbt11': font file missing

Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `xyeuat11': font file missing

Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `xyeubt11': font file missing

Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `xycmat12': font file missing

Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `xycmbt12': font file missing

Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `xyeuat12': font file missing


and pdftex could be updated there also :-)

-f
-- 
can't have everything. where would you put it?

Re: new release

[Thomas A.Schmitz]

On May 8, 2006, at 1:04 PM, Hans Hagen wrote:

> Hi,
>
> Today i'll upload a new release. Highlights:
>

Hans,

another (big) problem with the new release. Unfortunately, I can't  
really say what breaks, but when I compile a file under the new  
release, I get hundreds of overfull boxes. I get hyphenation, but TeX  
doesn't seem to find the same break points as before. The same file  
compiles wonderfully with version 2006.04.27. Can I send a logfile or  
something?

Hope this message makes it to the list...

Thomas

Re: new release

[Hans Hagen]

Thomas A.Schmitz wrote:
> On May 8, 2006, at 1:04 PM, Hans Hagen wrote:
>
>   
>> Hi,
>>
>> Today i'll upload a new release. Highlights:
>>
>>     
>
> Hans,
>
> another (big) problem with the new release. Unfortunately, I can't  
> really say what breaks, but when I compile a file under the new  
> release, I get hundreds of overfull boxes. I get hyphenation, but TeX  
> doesn't seem to find the same break points as before. The same file  
> compiles wonderfully with version 2006.04.27. Can I send a logfile or  
> something?
>
> Hope this message makes it to the list...
>   
can you send some example hyphenatable words?  

Hans 

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

Re: new release

[Hans Hagen]

Thomas A.Schmitz wrote:
> On May 8, 2006, at 1:04 PM, Hans Hagen wrote:
>
>   
>> Hi,
>>
>> Today i'll upload a new release. Highlights:
>>
>>     
>
> Hans,
>
> another (big) problem with the new release. Unfortunately, I can't  
> really say what breaks, but when I compile a file under the new  
> release, I get hundreds of overfull boxes. I get hyphenation, but TeX  
> doesn't seem to find the same break points as before. The same file  
> compiles wonderfully with version 2006.04.27. Can I send a logfile or  
> something?
>
> Hope this message makes it to the list...
>   
btw, there was a problem with the german patterns for a while; let me check it  

Hans 

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

Re: new release

[nico]

On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen <pragma@wxs.nl> wrote:

> Hi,
>
> Today i'll upload a new release. Highlights:
>
> - some fixes/extensions discussed the last few weeks

What about fixing this one  
(http://archive.contextgarden.net/message/20060430.190029.2f68d437.en.html)?

Regards,
BG

Re: new release

[Johannes Graumann]

Trouble with tex/context/base/cont-err.tex:


system          : cont-err loaded
(/home/balin/texmf/tex/context/base/cont-err.tex
Runaway argument?
on Otten}] %C %C This module is part of the \CONTEXT\ macro||package \ETC.
! Paragraph ended before & was complete.
<to be read again>
                   \par
l.13

Can't find anything wrong though ...

Joh

Hans Hagen wrote:

> Hi,
> 
> Today i'll upload a new release. Highlights:
> 
> - some fixes/extensions discussed the last few weeks
> - xetex support adapted to using xdvipdfmx
> - ctxtools --update which will update your local context
> - an update feature in scite (can be used a example for other editors)
> - an integrated mpto (more robust that the binary approach)
> 
> (btw, use textext instead of btex .. etex when possible)
> 
> Taco will undoubtely give mnore details later.
> 
> Keep in mind that you need to change the stubs:
> 
> - preferable use texmfstart to launch scripts
> - texmfstart itself can be stubbed if needed
> - there is a ../scripts/context/stubs path in the zip
> 
> Hans
> 
> -----------------------------------------------------------------
>                                           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
> -----------------------------------------------------------------

Re: new release

[Hans Hagen]

Johannes Graumann wrote:
> Trouble with tex/context/base/cont-err.tex:
>
>
> system          : cont-err loaded
> (/home/balin/texmf/tex/context/base/cont-err.tex
> Runaway argument?
> on Otten}] %C %C This module is part of the \CONTEXT\ macro||package \ETC.
> ! Paragraph ended before & was complete.
> <to be read again>
>                    \par
> l.13
>
> Can't find anything wrong though ...
>   
just to be sure, i use version  2006.05.09 23:03

i looks like you're ignoring comments 

how does the tex file look that you process? 

Hans 


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

Re: new release

[Johannes Graumann]

Hans,

This ruby stuff has me confused to no end.
I'm compiling this document (which compiled just fine with the last
release - no changes since) with the following command:

ruby ~/texmf/scripts/context/ruby/texexec.rb PhD-Thesis.tex

For trying to figure out the version I do:

ruby ~/texmf/scripts/context/ruby/texexec.rb --check

And get 

TeXExec | current distribution: web2c
TeXExec | context source date: unknown
TeXExec | format path:
TeXExec | start of analysis
/home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not
found: texmfstart texexec --help
/home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not
found: texmfstart texutil --help
/home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not
found: texmfstart ctxtools --help
TeXExec | end of analysis
TeXExec |
TeXExec |
TeXExec |
TeXExec |

Which is mostly related to the UNIX stubs not working no?

How do I now actually figure out what I'm running and whether it all got
rebuild correctly?

Thanks, Joh

Hans Hagen wrote:

> Johannes Graumann wrote:
>> Trouble with tex/context/base/cont-err.tex:
>>
>>
>> system          : cont-err loaded
>> (/home/balin/texmf/tex/context/base/cont-err.tex
>> Runaway argument?
>> on Otten}] %C %C This module is part of the \CONTEXT\ macro||package
>> \ETC. ! Paragraph ended before & was complete.
>> <to be read again>
>>                    \par
>> l.13
>>
>> Can't find anything wrong though ...
>>   
> just to be sure, i use version  2006.05.09 23:03
> 
> i looks like you're ignoring comments
> 
> how does the tex file look that you process?
> 
> Hans
> 
> 
> -----------------------------------------------------------------
>                                           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
> -----------------------------------------------------------------

Re: new release

[Hans Hagen]

Johannes Graumann wrote:
> Hans,
>
> This ruby stuff has me confused to no end.
> I'm compiling this document (which compiled just fine with the last
> release - no changes since) with the following command:
>
> ruby ~/texmf/scripts/context/ruby/texexec.rb PhD-Thesis.tex
>
> For trying to figure out the version I do:
>
> ruby ~/texmf/scripts/context/ruby/texexec.rb --check
>
> And get 
>
> TeXExec | current distribution: web2c
> TeXExec | context source date: unknown
> TeXExec | format path:
> TeXExec | start of analysis
> /home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not
> found: texmfstart texexec --help
> /home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not
> found: texmfstart texutil --help
> /home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not
> found: texmfstart ctxtools --help
> TeXExec | end of analysis
> TeXExec |
> TeXExec |
> TeXExec |
> TeXExec |
>
> Which is mostly related to the UNIX stubs not working no?
>   
cp texmfstart.rb <samepathaspdftex>/texmfstart
chmod 755 <samepathaspdftex>/texmfstart
> How do I now actually figure out what I'm running and whether it all got
> rebuild correctly?
>   
so, no stub for texmfstart, just a copy (althoughj you may want to call it indirectly 

Hans  

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

Re: new release

[Johannes Graumann]

Hans,

I linked texmfstart.rb to texmfstart in my local bin directory (which is in
the path) and issued 'chmod -R +x ~/texmf/scripts'. If I call 'ruby
~/texmf/scripts/context/ruby/texexec.rb --check' now, I get this error free
(but not informative) output:

TeXExec | current distribution: web2c
TeXExec | context source date: unknown
TeXExec | format path:
TeXExec | start of analysis
TeXExec | end of analysis
TeXExec |
TeXExec |
TeXExec |
TeXExec |

Any ideas what I might be doing wrong?

Joh


Hans Hagen wrote:

> Johannes Graumann wrote:
>> Hans,
>>
>> This ruby stuff has me confused to no end.
>> I'm compiling this document (which compiled just fine with the last
>> release - no changes since) with the following command:
>>
>> ruby ~/texmf/scripts/context/ruby/texexec.rb PhD-Thesis.tex
>>
>> For trying to figure out the version I do:
>>
>> ruby ~/texmf/scripts/context/ruby/texexec.rb --check
>>
>> And get
>>
>> TeXExec | current distribution: web2c
>> TeXExec | context source date: unknown
>> TeXExec | format path:
>> TeXExec | start of analysis
>> /home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not
>> found: texmfstart texexec --help
>> /home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not
>> found: texmfstart texutil --help
>> /home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not
>> found: texmfstart ctxtools --help
>> TeXExec | end of analysis
>> TeXExec |
>> TeXExec |
>> TeXExec |
>> TeXExec |
>>
>> Which is mostly related to the UNIX stubs not working no?
>>   
> cp texmfstart.rb <samepathaspdftex>/texmfstart
> chmod 755 <samepathaspdftex>/texmfstart
>> How do I now actually figure out what I'm running and whether it all got
>> rebuild correctly?
>>   
> so, no stub for texmfstart, just a copy (althoughj you may want to call it
> indirectly
> 
> Hans
> 
> -----------------------------------------------------------------
>                                           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
> -----------------------------------------------------------------

Re: new release

[Taco Hoekwater]

Johannes Graumann wrote:
> Trouble with tex/context/base/cont-err.tex:
> 
> 
> system          : cont-err loaded
> (/home/balin/texmf/tex/context/base/cont-err.tex
> Runaway argument?
> on Otten}] %C %C This module is part of the \CONTEXT\ macro||package \ETC.
> ! Paragraph ended before & was complete.
> <to be read again>
>                    \par
> l.13
> 
> Can't find anything wrong though ...

This is the very top of cont-err.tex, the 'module header'.
If that does not look broken, then probably the file that
loads it does so while some really strange catcode settings
are in effect. The most likely cause is that you have an
invalid zip file or an error has occured during extraction.

If you cannot figure it out, try posting a few extra
lines from the log, just before 'cont-err loaded'.


Cheers, taco

Re: new release

[Thomas A. Schmitz]

Hans,

do I need to re-report that format generation with texmfstart  
newtexexec --make is still broken on OS X (I'll check on my linux box  
later)? I still get these monstrous paths like

TeXExec | tex engine path: .:/Users/tas/texmf/web2c//:!!/usr/local/ 
teTeX/share//share/texmf-local/web2c//:!!/usr/local/teTeX/share// 
share/texmf/web2c//:!!/usr/local/teTeX/share//share/texmf-dist/web2c// 
pdfetex

Best

Thomas

Re: new release

[Hans Hagen]

Thomas A. Schmitz wrote:
> Hans,
>
> do I need to re-report that format generation with texmfstart  
> newtexexec --make is still broken on OS X (I'll check on my linux box  
> later)? I still get these monstrous paths like
>
> TeXExec | tex engine path: .:/Users/tas/texmf/web2c//:!!/usr/local/ 
> teTeX/share//share/texmf-local/web2c//:!!/usr/local/teTeX/share// 
> share/texmf/web2c//:!!/usr/local/teTeX/share//share/texmf-dist/web2c// 
> pdfetex
>   
strange, since i suppose that linux and osx behave the same (don't call it newtexexec any more) 

Hans 

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

Re: new release

[Thomas A. Schmitz]

Yes, that's strange. I just checked, and everything is golden on a linux
system (gentoo, but I gues the same is true for other linux distros). So
I really don't see why OS X should behave differently. Is there any
debugging info that I could provide? How 'bout the other OS X users (I
seem to recall there were quite a few of them): do you get the same
error?

Best

Thomas

On Wed, 2006-05-10 at 19:10 +0200, Hans Hagen wrote:
> strange, since i suppose that linux and osx behave the same (don't
> call it newtexexec any more) 
> 
> Hans 
> 

Re: new release

[Hans Hagen]

Thomas A. Schmitz wrote:
> Yes, that's strange. I just checked, and everything is golden on a linux
> system (gentoo, but I gues the same is true for other linux distros). So
> I really don't see why OS X should behave differently. Is there any
> debugging info that I could provide? How 'bout the other OS X users (I
> seem to recall there were quite a few of them): do you get the same
> error?
>   
i'm uploading a coupls of zips with fixes for xetex but i'm not sure if they solve your problem 

(concerning the path ... what is the path separator on osx?) 

Hans 

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

Re: new release

[Uwe Koloska]

Am Donnerstag, 11. Mai 2006 00:21 schrieb Hans Hagen:
>
> (concerning the path ... what is the path separator on osx?)

The normal unix path separator '/'.  On OS9 it was ':'.

Uwe

Re: new release

[Thomas A. Schmitz]

On May 11, 2006, at 12:21 AM, Hans Hagen wrote:

> i'm uploading a coupls of zips with fixes for xetex but i'm not  
> sure if they solve your problem
>
> (concerning the path ... what is the path separator on osx?)
>
> Hans
>

Nope, still get the same bizarre result. Path separator is a ":"

echo $PATH
/sw/bin:/sw/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/tas/bin:/usr/ 
local/bin:/usr/lib/portage/bin:/usr/local/teTeX/bin/powerpc-apple- 
darwin-current:/Developer/Tools:/usr/X11R6/bin

So maybe Gerben's guess is right, and it's some hard-coded path thing  
in kpsefast?

texmfstart texexec --make --all

TeXExec | using search method 'kpsefast'
TeXExec | updating file database
mktexlsr: Updating /usr/local/teTeX/share/texmf/ls-R...
mktexlsr: Updating /usr/local/teTeX/share/texmf.gwtex/ls-R...
mktexlsr: Updating /usr/local/teTeX/share/texmf.local/ls-R...
mktexlsr: Updating /usr/local/teTeX/share/texmf.tetex/ls-R...
mktexlsr: Updating /var/tmp/texfonts/ls-R...
mktexlsr: Done.
TeXExec | using tex engine pdfetex
TeXExec | using tex format path .:/Users/tas/texmf/web2c//:!!/usr/ 
local/teTeX/share//share/texmf-local/web2c//:!!/usr/local/teTeX/ 
share//share/texmf/web2c//:!!/usr/local/teTeX/share//share/texmf-dist/ 
web2c//pdfetex

As you can see: while mltexlsr find the corret paths for updating,  
the format path given by TeXExec uses default values.

Thomas

Re: new release

[Hans Hagen]

Thomas A. Schmitz wrote:
> On May 11, 2006, at 12:21 AM, Hans Hagen wrote:
>
>   
>> i'm uploading a coupls of zips with fixes for xetex but i'm not  
>> sure if they solve your problem
>>
>> (concerning the path ... what is the path separator on osx?)
>>
>> Hans
>>
>>     
>
> Nope, still get the same bizarre result. Path separator is a ":"
>   
btw, concerning the texmfstart script itself: 

- on unix it's indeed best to make a symlink from texmfstart -> texmfstart.rb in the whatever-tree it resides in 

- on windows, one can associate the .rb suffix with ruby and add the context ruby path to the bin path, or use the 'exe' variant which can be located anywhere 

(texmfstart uses a few libe but when they are not found, it will enter stupid-mode and lack some features that probably go unnoticed) 

Hans 

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

Re: new release

[nico]

On Thu, 11 May 2006 00:11:47 +0200, Thomas A. Schmitz  
<thomas.schmitz@uni-bonn.de> wrote:

> Yes, that's strange. I just checked, and everything is golden on a linux
> system (gentoo, but I gues the same is true for other linux distros). So
> I really don't see why OS X should behave differently. Is there any
> debugging info that I could provide? How 'bout the other OS X users (I
> seem to recall there were quite a few of them): do you get the same
> error?

Strictly speaking it's not OSX, but i've a FreeBSD distro, which is close,  
and it works fine.

Are you sure you have the permission to write in any of these paths?

BTW, i find dangerous to do (kpse.formatpath method):

                 # locate writable path
                 if ! formatpath.empty? then
                     formatpath.split_path.each do |fp|
                         fp.gsub!(/\\/,'/')
                         # remove funny patterns
                         fp.sub!(/^!!/,'')
                         fp.sub!(/\/+$/,'')
                         fp.sub!(/unsetengine/,if enginepath then engine  
else '' end)
                         if ! fp.empty? && (fp != '.') then
                             # strip (possible engine) and test for  
writeability
                             fpp = fp.sub(/#{engine}\/*$/,'')
                             if FileTest.directory?(fpp) &&  
FileTest.writable?(fpp) then
                                 # use this path
                                 formatpath = fp.dup
                                 break
                             end
                         end
                     end
                 end
                 # needed !
                 begin File.makedirs(formatpath) ; rescue ; end ;

If none of the paths from formatpath is valid, we keep the whole concat  
path in this variable... that then is used to create a directory tree.  
Thomas, maybe that you have ugly directories created starting with an  
hidden directory named ".:". You should check that.

Regards,
BG

Re: new release

[Hans Hagen]

nico wrote:
> On Thu, 11 May 2006 00:11:47 +0200, Thomas A. Schmitz  
> <thomas.schmitz@uni-bonn.de> wrote:
>
>   
>> Yes, that's strange. I just checked, and everything is golden on a linux
>> system (gentoo, but I gues the same is true for other linux distros). So
>> I really don't see why OS X should behave differently. Is there any
>> debugging info that I could provide? How 'bout the other OS X users (I
>> seem to recall there were quite a few of them): do you get the same
>> error?
>>     
>
> Strictly speaking it's not OSX, but i've a FreeBSD distro, which is close,  
> and it works fine.
>
> Are you sure you have the permission to write in any of these paths?
>
> BTW, i find dangerous to do (kpse.formatpath method):
>
>                  # locate writable path
>                  if ! formatpath.empty? then
>                      formatpath.split_path.each do |fp|
>                          fp.gsub!(/\\/,'/')
>                          # remove funny patterns
>                          fp.sub!(/^!!/,'')
>                          fp.sub!(/\/+$/,'')
>                          fp.sub!(/unsetengine/,if enginepath then engine  
> else '' end)
>                          if ! fp.empty? && (fp != '.') then
>                              # strip (possible engine) and test for  
> writeability
>                              fpp = fp.sub(/#{engine}\/*$/,'')
>                              if FileTest.directory?(fpp) &&  
> FileTest.writable?(fpp) then
>                                  # use this path
>                                  formatpath = fp.dup
>                                  break
>                              end
>                          end
>                      end
>                  end
>                  # needed !
>                  begin File.makedirs(formatpath) ; rescue ; end ;
>
> If none of the paths from formatpath is valid, we keep the whole concat  
> path in this variable... that then is used to create a directory tree.  
> Thomas, maybe that you have ugly directories created starting with an  
> hidden directory named ".:". You should check that.
>   
i can make the fallback '.' in that case, not that it helps much

                if ! formatpath.empty? then
                    done = false
                    formatpath.split_path.each do |fp|
                        fp.gsub!(/\\/,'/')
                        # remove funny patterns
                        fp.sub!(/^!!/,'')
                        fp.sub!(/\/+$/,'')
                        fp.sub!(/unsetengine/,if enginepath then engine 
else '' end)
                        if ! fp.empty? && (fp != '.') then
                            # strip (possible engine) and test for 
writeability
                            fpp = fp.sub(/#{engine}\/*$/,'')
                            if FileTest.directory?(fpp) && 
FileTest.writable?(fpp) then
                                # use this path
                                formatpath, done = fp.dup, true
                                break
                            end
                        end
                    end
                    formatpath = '.' unless done
                end


Hans

-- 

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

Re: new release

[Hans Hagen]

Thomas A. Schmitz wrote:
> Hans,
>
> do I need to re-report that format generation with texmfstart  
> newtexexec --make is still broken on OS X (I'll check on my linux box  
> later)? I still get these monstrous paths like
>
> TeXExec | tex engine path: .:/Users/tas/texmf/web2c//:!!/usr/local/ 
> teTeX/share//share/texmf-local/web2c//:!!/usr/local/teTeX/share// 
> share/texmf/web2c//:!!/usr/local/teTeX/share//share/texmf-dist/web2c// 
> pdfetex
>
>   
btw, i cannot test the mac here since the machine is broken (does not start up and i already wasted half a day on it) 

Hans 

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

Re: new release

[Johannes Graumann]

Taco Hoekwater wrote:

> This is the very top of cont-err.tex, the 'module header'.
> If that does not look broken, 
> then probably the file that 
> loads it does so while some really strange catcode settings
> are in effect. The most likely cause is that you have an
> invalid zip file or an error has occured during extraction.
I went back and looked at the file - nothing obvious. I repeated my install
from the pragma server ... no changes.

The document in question compiled just fine before the update.

> If you cannot figure it out, try posting a few extra
> lines from the log, just before 'cont-err loaded'.
I append the log region around the 'cont-err loaded' part.

Thanks for any help, Joh

chapter         : - About this Document
publications    : warning: cite argument knuth:86 is unknown on 80
publications    : warning: cite argument hagen:01 is unknown on 80
publications    : warning: cite argument lamport:94 is unknown on 80
publications    : warning: cite argument thanh:98 is unknown on 80
publications    : warning: cite argument knuth:84 is unknown on 80
publications    : warning: cite argument adobe:04 is unknown on 80

Overfull \hbox (4.7209pt too wide) in paragraph at lines 4--4
[]\*modern12ptrmtf*: This doc-u-ment was type-set in Com-puter Mod-ern
(Xxxxxxx
xxx, 0000), us-ing ConT[]Xt

\hbox(8.82599+3.0)x438.77812, glue set - 1.0
\kern-0.432 (left margin)
\hbox(0.0+0.0)x0.0
\*modern12ptrmtf*: T
\*modern12ptrmtf*: h
\*modern12ptrmtf*: i
etc.

publications    : warning: cite argument graumann:04 is unknown on 80
publications    : warning: cite argument yergeau:04 is unknown on 80
section         : - References
)
structure       : end of sectionblock backmatter
[175.162]
systems         : end file PhD-Thesis at line 77
system          : cont-err loaded
(/home/balin/texmf/tex/context/base/cont-err.tex
Runaway argument?
on Otten}] %C %C This module is part of the \CONTEXT\ macro||package \ETC.
! Paragraph ended before & was complete.
<to be read again> 
                   \par 
l.13 
     
? s
OK, entering \scrollmode...

Overfull \hbox (42.98929pt too wide) in paragraph at lines 1--13
\*modern12ptrmtf*: Sys-tem Files, %D sub-ti-tle=Just A warn-ing, %D
au-thor=Han
s Ha-gen, %D date=\currentdate,

\hbox(8.82599+3.0)x438.77812, glue set - 1.0
\*modern12ptrmtf*: S
\*modern12ptrmtf*: y
\*modern12ptrmtf*: s
\discretionary
.\*modern12ptrmtf*: -
\*modern12ptrmtf*: t
etc.

)
Runaway argument?
} \writeline \par \endinput 
! File ended while scanning use of \xparseXMLelement.
<inserted text> 
                \par 
<to be read again> 
                   \relax 
\dodoreadfile ...\preprocesssuffix \or \fi \relax 
                                                  \the \everyafterreadfile 
\loadallsystemfiles ...ssage \m!systems 2{#1}}{#2}
                                                  \else \def
\doloadsystemfi...

\finalend ...se \the \everybye \the \everygoodbye 
                                                  \global \everybye
\emptyto...
l.77 </document>

Re: new release

[Taco Hoekwater]

Johannes Graumann wrote:
> 
>>If you cannot figure it out, try posting a few extra
>>lines from the log, just before 'cont-err loaded'.
> 
> I append the log region around the 'cont-err loaded' part.

It looks to me like context found a cont-err.tex when it
should not have.

At the end of a job, ConTeXt looks for a file named cont-err.tex,
in the directory path that is set by the \setupsystem command in 
<jobname>.tmp. This file itself is generated by texexec, and the
directory value is based on "setuppath").

In your case, it looks like this directory entry is either
incorrect, or there is a bug in context, because it finds and
then loads the file while XML mode is still active.

I do not know how to proceed from here. Hans?

Cheers, taco

Re: new release

[Hans Hagen]

Taco Hoekwater wrote:
> Johannes Graumann wrote:
>   
>>> If you cannot figure it out, try posting a few extra
>>> lines from the log, just before 'cont-err loaded'.
>>>       
>> I append the log region around the 'cont-err loaded' part.
>>     
>
> It looks to me like context found a cont-err.tex when it
> should not have.
>
> At the end of a job, ConTeXt looks for a file named cont-err.tex,
> in the directory path that is set by the \setupsystem command in 
> <jobname>.tmp. This file itself is generated by texexec, and the
> directory value is based on "setuppath").
>
> In your case, it looks like this directory entry is either
> incorrect, or there is a bug in context, because it finds and
> then loads the file while XML mode is still active.
>
> I do not know how to proceed from here. Hans?
>   
in core-sys.tex, replace: 

\ifx\disableXML\undefined \let\disableXML\relax \fi

\def\loadsystemfiles
  {\reportprotectionstate
   \readsysfile\f!newfilename
     {\showmessage\m!systems2\f!newfilename}%
     \donothing
   \readsysfile\f!oldfilename
     {\showmessage\m!systems2\f!oldfilename}%
     \donothing
   \loadallsystemfiles\f!filfilename
     \donothing
   \loadallsystemfiles\f!sysfilename
     {\loadallsystemfiles{\f!sysfilename.rme}\donothing % new, fall back
      \doglobal\appendtoks
        \bgroup
        \disableXML
        \loadallsystemfiles\f!errfilename\donothing
        \egroup
      \to\everygoodbye}}

and let me know if that works ok 

Hans 
-----------------------------------------------------------------
                                          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
-----------------------------------------------------------------

Re: new release

[Johannes Graumann]

Hans Hagen wrote:
> in core-sys.tex, replace:
> 
> \ifx\disableXML\undefined \let\disableXML\relax \fi
> 
> \def\loadsystemfiles
>   {\reportprotectionstate
>    \readsysfile\f!newfilename
>      {\showmessage\m!systems2\f!newfilename}%
>      \donothing
>    \readsysfile\f!oldfilename
>      {\showmessage\m!systems2\f!oldfilename}%
>      \donothing
>    \loadallsystemfiles\f!filfilename
>      \donothing
>    \loadallsystemfiles\f!sysfilename
>      {\loadallsystemfiles{\f!sysfilename.rme}\donothing % new, fall back
>       \doglobal\appendtoks
>         \bgroup
>         \disableXML
>         \loadallsystemfiles\f!errfilename\donothing
>         \egroup
>       \to\everygoodbye}}

I have appended this to core-sys.tex (just before the final '\protect
\endinput'; latest version of 11.5.) and used 'texexec.rb --make'.
I get the same error - even for a document containing nothing but this:

\defineXMLenvironment
   [document]
   {\starttext}
   {\stoptext}
\startXMLdata
  <document></document>
\stopXMLdata

How do we proceed from here?

Joh

Re: new release

[Hans Hagen]

Johannes Graumann wrote:
> Hans Hagen wrote:
>   
>> in core-sys.tex, replace:
>>
>> \ifx\disableXML\undefined \let\disableXML\relax \fi
>>
>> \def\loadsystemfiles
>>   {\reportprotectionstate
>>    \readsysfile\f!newfilename
>>      {\showmessage\m!systems2\f!newfilename}%
>>      \donothing
>>    \readsysfile\f!oldfilename
>>      {\showmessage\m!systems2\f!oldfilename}%
>>      \donothing
>>    \loadallsystemfiles\f!filfilename
>>      \donothing
>>    \loadallsystemfiles\f!sysfilename
>>      {\loadallsystemfiles{\f!sysfilename.rme}\donothing % new, fall back
>>       \doglobal\appendtoks
>>         \bgroup
>>         \disableXML
>>         \loadallsystemfiles\f!errfilename\donothing
>>         \egroup
>>       \to\everygoodbye}}
>>     
>
> I have appended this to core-sys.tex (just before the final '\protect
> \endinput'; latest version of 11.5.) and used 'texexec.rb --make'.
> I get the same error - even for a document containing nothing but this:
>
> \defineXMLenvironment
>    [document]
>    {\starttext}
>    {\stoptext}
> \startXMLdata
>   <document></document>
> \stopXMLdata
>
> How do we proceed from here?
>   
a minimal test file showing the problem; as taco said, maybe some 
interference with xml processing

Hans

-- 

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

Re: new release

[Hans Hagen]

Johannes Graumann wrote:
> Hans Hagen wrote:
>   
>> in core-sys.tex, replace:
>>
>> \ifx\disableXML\undefined \let\disableXML\relax \fi
>>
>> \def\loadsystemfiles
>>   {\reportprotectionstate
>>    \readsysfile\f!newfilename
>>      {\showmessage\m!systems2\f!newfilename}%
>>      \donothing
>>    \readsysfile\f!oldfilename
>>      {\showmessage\m!systems2\f!oldfilename}%
>>      \donothing
>>    \loadallsystemfiles\f!filfilename
>>      \donothing
>>    \loadallsystemfiles\f!sysfilename
>>      {\loadallsystemfiles{\f!sysfilename.rme}\donothing % new, fall back
>>       \doglobal\appendtoks
>>         \bgroup
>>         \disableXML
>>         \loadallsystemfiles\f!errfilename\donothing
>>         \egroup
>>       \to\everygoodbye}}
>>     
>
> I have appended this to core-sys.tex (just before the final '\protect
> \endinput'; latest version of 11.5.) and used 'texexec.rb --make'.
> I get the same error - even for a document containing nothing but this:
>
> \defineXMLenvironment
>    [document]
>    {\starttext}
>    {\stoptext}
> \startXMLdata
>   <document></document>
> \stopXMLdata
>
> How do we proceed from here?
>   
\defineXMLenvironment
   [document]
   {\starttext}
   {\stoptext}

\starttext

\startXMLdata
  <document></document>
\stopXMLdata

\stoptext

does that work ok? in your example, you stay inside a group and then end  the doc

\starttext 

\processXMLfilegrouped{somedoc}

\stoptext 

is ok, as is

  texexec somedoc.xml 

which wraps the xml processing in a run file 

Hans 


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

Re: new release

[Johannes Graumann]

Hans Hagen wrote:

> \defineXMLenvironment
>    [document]
>    {\starttext}
>    {\stoptext}
> 
> \starttext
> 
> \startXMLdata
>   <document></document>
> \stopXMLdata
> 
> \stoptext

You catch my folly as usually. Thanks. While I get the solution above to
work, the alternative 'ruby
~/texmf/scripts/context/ruby/texexec.rb --pdf --environments=PhD-Thesis ../XML/main.xml'
doesn't. Error is:

> User file 'cont-sys.tex' not found, 'cont-sys.rme' has been used instead. 

Hints?

Joh

Re: new release

[David Arnold]

Not sure what settings you need, but I think I know that you take the  
cont-sys.rme and rename it to cont-sys.tex and go from there.

On May 11, 2006, at 5:46 PM, Johannes Graumann wrote:

> Hans Hagen wrote:
>
>> \defineXMLenvironment
>>    [document]
>>    {\starttext}
>>    {\stoptext}
>>
>> \starttext
>>
>> \startXMLdata
>>   <document></document>
>> \stopXMLdata
>>
>> \stoptext
>
> You catch my folly as usually. Thanks. While I get the solution  
> above to
> work, the alternative 'ruby
> ~/texmf/scripts/context/ruby/texexec.rb --pdf --environments=PhD- 
> Thesis ../XML/main.xml'
> doesn't. Error is:
>
>> User file 'cont-sys.tex' not found, 'cont-sys.rme' has been used  
>> instead.
>
> Hints?
>
> Joh
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context

Re: new release

[Hans Hagen]

Johannes Graumann wrote:
> Hans Hagen wrote:
>
>   
>> \defineXMLenvironment
>>    [document]
>>    {\starttext}
>>    {\stoptext}
>>
>> \starttext
>>
>> \startXMLdata
>>   <document></document>
>> \stopXMLdata
>>
>> \stoptext
>>     
>
> You catch my folly as usually. Thanks. While I get the solution above to
> work, the alternative 'ruby
> ~/texmf/scripts/context/ruby/texexec.rb --pdf --environments=PhD-Thesis ../XML/main.xml'
> doesn't. Error is:
>
>   
>> User file 'cont-sys.tex' not found, 'cont-sys.rme' has been used instead. 
>>     

has nothing to do with ruby, just copy cont-sys.rme to cont-sys.tex in 
tex/context/user; i ship the rme as example and fallback so that it does 
not overwrite you rlocal copy

Hans

ConTeXt template ?

[nm]

Hi *,

I'm new w/ ConTeXt..
Where can i found publication, articles, whitepaper template for
ConTeXt ?

thanks,

nm.

Re: ConTeXt template ?

[Renaud AUBIN]

http://wiki.contextgarden.net/Main_Page
http://www.pragma-ade.nl/show-man-1.htm

nm a écrit :

>Hi *,
>
>I'm new w/ ConTeXt..
>Where can i found publication, articles, whitepaper template for
>ConTeXt ?
>
>thanks,
>
>nm.
>_______________________________________________
>ntg-context mailing list
>ntg-context@ntg.nl
>http://www.ntg.nl/mailman/listinfo/ntg-context
>
>
>  
>