Re: Mark IV and pre-processing input file processing.

[Wolfgang Schuster <schuster.wolfgang@googlemail.com>]

On Tue, 06 Nov 2007 20:48:26 +0100
Hans Hagen <pragma@wxs.nl> wrote:

> Johannes Graumann wrote:
> > Hans Hagen wrote:
> > 
> >>> Thanks for that! I found the zipping reference and got it to work.
> >>> Returning now to the example above ("texmfstart
> >>> texexec --lua --environments=myfile.tex someotherfile.zip"), what I would
> >>> like to do is using lua in "myfile.tex" to extract the filename to be
> >>> texed (someotherfile.zip) and rewrite it on the fly to a zip-archive
> >>> content along the lines of
> >>> \input zip::someotherfile.zip::somezipcontent.tex
> >>>
> >>> Is that possible? "texmfstart texexec --verbose" produces something like
> >>> TeXExec | option 'filename' is set to 'someotherfile.tex', so how to
> >>> access this during processing using lua?
> >> texmfstart texexec --lua myfile.tex --arg="name=someotherfile.zip"
> >>
> >> mak emyfile.tex your main tex file (use --global if needed) and then use
> >> \env{name}
> > 
> > Thanks Hans! Not as elegant as I had hoped, but it does what I want when I
> > use "\input zip::\env{name}::somezipcontent.tex" in myfile.tex ... 
> > Now is there any way to define the output-filename from within myfile.tex?
> > This would be analogous to texexec's '--result' option, but from within the
> > texfile to change the output-name with the help of the newly
> > defined '\env{name}' - in the example to '\env{name}.pdf'.
> 
> no ... maybe some day

this give us so many options.

I think about something like,

We can create a zip archive of a current project with a file ending
like cdx (ConTeXt Document Excange) and can now process this file by
calling texexec only on this file.

Nothing special at this moment for now but it is easier send only one
files to someone else instead of a many files or many files in a zip
file he has to unzip first and call texexec later on the main file.

What I want is to create a document in one directory with the normal
structure with projects, components, a figure directory etc. and zip
this directory to only one file. I can now process file simply by
calling texexec on the directory and it is unzipped on the fly
(unnoticed by the user) and I have no longer many different files in my
directory and it is easier to send a docuemnt to someone else because
he get from me only the zipped project file.

I know this is nearly the same as a openoffice document (also a zip
archive with many files) but why not.

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
___________________________________________________________________________________