Re: Module documentation

Re: Module documentation

[richard.stephens]

[-- Attachment #1.1: Type: text/plain, Size: 192 bytes --]

Wolfgang and Mojca,

Thank-you for your replies.  They have enabled me to set up a little batch 
file to make life easier when I want to generate a module document.

Thanks,

Richard Stephens

[-- Attachment #1.2: Type: text/html, Size: 381 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

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

Module documentation

[richard.stephens]

[-- Attachment #1.1: Type: text/plain, Size: 969 bytes --]

Hello all,

I have been using Context for a while now and have learnt a lot from the 
manuals and wiki.  I now want to start to use features that are not 
documented.  On the wiki 
(http://wiki.contextgarden.net/Official_ConTeXt_Documentation#ConTeXt_Sources) 
I found the following command for producing a pdf output for a module:

texmfstart texexec --module kpse:core-tab.tex

which seems ideal for learning more.  When I run the above command line it 
creates a .ted file but then complains:

"I can't find the format file 'cont-en.fmt'!"

On Luigi Scarso's page 
(http://wiki.contextgarden.net/User:Luigi.scarso/modules.pdf) he suggests 
the following:

texexec --module --pdf core-tab.tex

but this returns no output at all, and no pdf.

I am working on Windows.  I installed (this week) from the 
context/install/mswincontext.zip on the Pragma site and normally build 
from the Scite editor.

Can anyone suggest what I'm doing wrong?

Thanks.

Richard Stephens


[-- Attachment #1.2: Type: text/html, Size: 1588 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
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: Module documentation

[Wolfgang Schuster]

On Fri, Apr 11, 2008 at 4:25 PM,  <richard.stephens@converteam.com> wrote:
>
> Hello all,
>
> I have been using Context for a while now and have learnt a lot from the
> manuals and wiki.  I now want to start to use features that are not
> documented.  On the wiki
> (http://wiki.contextgarden.net/Official_ConTeXt_Documentation#ConTeXt_Sources)
> I found the following command for producing a pdf output for a module:
>
> texmfstart texexec --module kpse:core-tab.tex
>
> which seems ideal for learning more.  When I run the above command line it
> creates a .ted file but then complains:
>
> "I can't find the format file 'cont-en.fmt'!"
>
> On Luigi Scarso's page
> (http://wiki.contextgarden.net/User:Luigi.scarso/modules.pdf) he suggests
> the following:
>
> texexec --module --pdf core-tab.tex
>
> but this returns no output at all, and no pdf.
>
> I am working on Windows.  I installed (this week) from the
> context/install/mswincontext.zip on the Pragma site and normally build from
> the Scite editor.
>
> Can anyone suggest what I'm doing wrong?

The mswincontext package use local settings for the paths and you can
use them only with scite or the setup script. You could try to add the path
for the setuptext script to the global path variables to use LuaTeX etc.
systemwide or you use the command line from scite.

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: Module documentation

[Mojca Miklavec]

On Mon, Apr 14, 2008 at 10:27 AM, Wolfgang Schuster wrote:
>
> On Fri, Apr 11, 2008 at 4:25 PM,  <richard.stephens@converteam.com> wrote:
>  >
>  > Hello all,
>  >
>  > I have been using Context for a while now and have learnt a lot from the
>  > manuals and wiki.  I now want to start to use features that are not
>  > documented.  On the wiki
>  > (http://wiki.contextgarden.net/Official_ConTeXt_Documentation#ConTeXt_Sources)
>  > I found the following command for producing a pdf output for a module:
>  >
>  > texmfstart texexec --module kpse:core-tab.tex
>  >
>  > which seems ideal for learning more.  When I run the above command line it
>  > creates a .ted file but then complains:
>  >
>  > "I can't find the format file 'cont-en.fmt'!"
>  >
>  > On Luigi Scarso's page
>  > (http://wiki.contextgarden.net/User:Luigi.scarso/modules.pdf) he suggests
>  > the following:
>  >
>  > texexec --module --pdf core-tab.tex
>  >
>  > but this returns no output at all, and no pdf.
>  >
>  > I am working on Windows.  I installed (this week) from the
>  > context/install/mswincontext.zip on the Pragma site and normally build from
>  > the Scite editor.
>  >
>  > Can anyone suggest what I'm doing wrong?
>
>  The mswincontext package use local settings for the paths and you can
>  use them only with scite or the setup script. You could try to add the path
>  for the setuptext script to the global path variables to use LuaTeX etc.
>  systemwide or you use the command line from scite.

You need to run something like (single line!!!):

C:\Programs\context\usr\local\context\tex\setuptex.bat
C:\Programs\context\usr\local\context\tex

in command prompt. For "texexec --module --pdf core-tab.tex" to work
you need to be in context base folder (tex/context/base; kpse makes
sure that you find & take the proper file automatically), and you
probably need to report a few problems in the source to be able to
compile that particular source file :)

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: Module documentation

[luigi scarso]

> On Luigi Scarso's page
> (http://wiki.contextgarden.net/User:Luigi.scarso/modules.pdf) he suggests
> the following:
>
> texexec --module --pdf core-tab.tex
sooner I will move this stuffs to supelec


-- 
luigi
it's new .
it's powerful .
it's luatex .
http://www.luatex.org
___________________________________________________________________________________
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: Module documentation

[Hans Hagen]

At 06:29 PM 12/30/00 +0100, Giuseppe Bilotta wrote:
>I recently began "playing" with the TeXexec --module capabilities, and lo! I
>have a a couple of hints :-)
>
>It would be nice if \input'ed files could be (at the user's choice) be
>processed at together with the main files, if they are modules (e.g., there
>would be not much to do on plain.mp included by metafun.mp, but it would be
>nice if all the others were typeset too; in such a case (or even _not_ in
>such a case), \input's could be turned to links.

That would lead to quite bug files over here -) 

I can put the link on the todo list. It will never be watertight, since
there is no way to find out alternative inputs. 

>Also, I would like to signal a couple of bugs
>
>a) double %D %D bug in metafun.mp;

bug. 

>1) syntax highlighting is too aggressive: filenames should not be syntax
>highlighted (I mean mp-char.mp has "char" highlighted);

This is a bug but hard to catch since a-b is syntactically right, and i
cannot [like wirh strings] use " as signals.  

>2) it seems that some modules use cont-nl, while other use cont-en
>(specifically for the latter: mp-tool has a \quote command, which is not
>recognized; core-fnt has a \getbuffer whici is not recognized);

For the moment cont-nl indeed, so i need to change that. 

>enough by now ...
>
>(Hans, shall I post other bugs I find publicly, or do you want them sent
>separately?)

separate mail is probably less boring for other list members; real context
core-bugs can go to the list

Hans
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Module documentation

[Giuseppe Bilotta]

I recently began "playing" with the TeXexec --module capabilities, and lo! I
have a a couple of hints :-)

It would be nice if \input'ed files could be (at the user's choice) be
processed at together with the main files, if they are modules (e.g., there
would be not much to do on plain.mp included by metafun.mp, but it would be
nice if all the others were typeset too; in such a case (or even _not_ in
such a case), \input's could be turned to links.

Also, I would like to signal a couple of bugs

a) double %D %D bug in metafun.mp;

1) syntax highlighting is too aggressive: filenames should not be syntax
highlighted (I mean mp-char.mp has "char" highlighted);

2) it seems that some modules use cont-nl, while other use cont-en
(specifically for the latter: mp-tool has a \quote command, which is not
recognized; core-fnt has a \getbuffer whici is not recognized);

enough by now ...

(Hans, shall I post other bugs I find publicly, or do you want them sent
separately?)

Giuseppe Bilotta