/ruby/texmstart.rb
cp .../scripts/ruby/texmstart.rb /usr/local/bin
(/usr/local/bin on my path, as it is in most unix-like systems).
After that I had to tweak my TeXShop to use texmfstart accordingly.
For those MacOSX-TeXShop users among you who want this too and
without much trouble, here
Aditya Mahajan wrote:
Should the test-suite contain tests for ruby scripts also?
for some of the functionality that makes sense indeed
Hans
-
Hans Hagen | PRAGMA ADE
generated formats
typesetting ok
2. generated metafun.mem afresh with texmfstart texexec --make alone
metafun
typesetting ok
3. changed the ruby scripts over to the 2006-06-07 ones.
typesetting ok
4. changed the context base files in tex/context/base to their
2006
:
inlocaldocument = indocument
inlocaldocument = false # else first
line skipped when not empty
please test all kind of variants (there most have been a reason for
this, so it may as well be a bug related to translating from perl to ruby)
Hans
In order to purge the temporary context files I did (throught an alias) texutil --purgeThis worked fine.Since the introduction of the ruby scripts this call now tells me: remark: 'texutil' is now part of 'texexec' warning: use 'texmfstart texutil' insteadSo I obediently call: texmfstart.rb texutil
Hans van der Meer wrote:
In order to purge the temporary context files I did (throught an alias)
texutil --purge
This worked fine.
Since the introduction of the ruby scripts this call now tells me:
remark: 'texutil' is now part of 'texexec'
warning: use 'texmfstart texutil' instead
So I
, pdftools.rb, rlxtools.rb
etc
it's now:
ctxtools --purge
For those on UNIX(-like) systems that have only texmfstart.rb enabled
as executable (chmod a+x texmfstart.rb) this will not work as none
the ruby scripts in the distribution seem to have their execution
bits set.
The next seems
Hans van der Meer wrote:
For those on UNIX(-like) systems that have only texmfstart.rb enabled
as executable (chmod a+x texmfstart.rb) this will not work as none
the ruby scripts in the distribution seem to have their execution
bits set.
The next seems mandatory if only texmfstart
has been moved to texexec.rb, ctxtools.rb, pdftools.rb, rlxtools.rb
etc
it's now:
ctxtools --purge
For those on UNIX(-like) systems that have only texmfstart.rb enabled
as executable (chmod a+x texmfstart.rb) this will not work as none
the ruby scripts in the distribution
inlocaldocument = false # else first
line skipped when not empty
please test all kind of variants (there most have been a reason for
this, so it may as well be a bug related to translating from perl to ruby)
From the code, I can not understand why
. be a wrapper only); the functionality
has been moved to texexec.rb, ctxtools.rb, pdftools.rb, rlxtools.rb
etc
it's now:
ctxtools --purge
For those on UNIX(-like) systems that have only texmfstart.rb enabled
as executable (chmod a+x texmfstart.rb) this will not work as none
the ruby scripts
On Tue, 6 Jun 2006, Taco Hoekwater wrote:
Aditya Mahajan wrote:
Hi,
How does one generate module documentation? I copied mult-ini.tex to
a temp directory and did
texmfstart texexec --modules mult-ini.tex
It seems that 'texutil -- documents' is not implemented yet
in the ruby scripts, so
of
| the first wiki page.
| (*) read: you have to
Well, sorry I forgot to say about my installation; actually I have an uptodate
one, less than 10 days, last metapost, and using texmfstart texexec all
right (I found a script for that on the list with this line:
ruby path to ruby dir/texmfstart.rb
the formats using
sudo ruby /usr/local/teTeX/share/texmf.local/scripts/context/ruby/
texmfstart.rb texexec --make --all
I get the error message
language: patterns agr for agr loaded (n=24,e=agr,m=agr)
(/usr/local/teTeX/share/texmf.local/tex/context/patterns/lang-
agr.pat
! Nonletter
/context/patterns/.
When I try to regenerate the formats using
sudo ruby /usr/local/teTeX/share/texmf.local/scripts/context/ruby/
texmfstart.rb texexec --make --all
I get the error message
language: patterns agr for agr loaded (n=24,e=agr,m=agr)
(/usr/local/teTeX/share/texmf.local/tex
/teTeX/share/texmf.local/tex/context/patterns/.
When I try to regenerate the formats using
sudo ruby /usr/local/teTeX/share/texmf.local/scripts/context/ruby/
texmfstart.rb texexec --make --all
I get the error message
language: patterns agr for agr loaded (n=24,e=agr,m=agr)
(/usr
be since the
files
lang-agr.hyp and
lang-agr.pat are in the right place,
/usr/local/teTeX/share/texmf.local/tex/context/patterns/.
When I try to regenerate the formats using
sudo ruby /usr/local/teTeX/share/texmf.local/scripts/context/
ruby/
texmfstart.rb texexec --make --all
I get the error
should be since the files
lang-agr.hyp and
lang-agr.pat are in the right place,
/usr/local/teTeX/share/texmf.local/tex/context/patterns/.
When I try to regenerate the formats using
sudo ruby /usr/local/teTeX/share/texmf.local/scripts/context/ruby/
texmfstart.rb texexec --make --all
I get the error
they presumably should be since the files
lang-agr.hyp and
lang-agr.pat are in the right place,
/usr/local/teTeX/share/texmf.local/tex/context/patterns/.
When I try to regenerate the formats using
sudo ruby /usr/local/teTeX/share/texmf.local/scripts/context/ruby/
texmfstart.rb texexec
hyphenation patterns
are not available, though they presumably should be since the files
lang-agr.hyp and
lang-agr.pat are in the right place,
/usr/local/teTeX/share/texmf.local/tex/context/patterns/.
When I try to regenerate the formats using
sudo ruby /usr/local/teTeX/share/texmf.local/scripts
that the ancient Greek hyphenation patterns
are not available, though they presumably should be since the files
lang-agr.hyp and
lang-agr.pat are in the right place,
/usr/local/teTeX/share/texmf.local/tex/context/patterns/.
When I try to regenerate the formats using
sudo ruby /usr/local/teTeX
know how it is on Mac. Under windows I have a binary (cont-win
on pragma download site), under Linux I create a file texmfstart
with
ruby /path-to-tex/texmfstart.rb $*
(or something similar)
see also the new scripts/context/stubs/mac folder (I didn't check, I
only suppose that it's
= {!!$TEXMFCONFIG,!!$TEXMFVAR,$TEXMFHOME,!!$TEXMFSYSCONFIG,!!
$TEXMFSYSVAR,!!$TEXMFMAIN,!!$TEXMFLOCAL,!!$TEXMFDIST}
% font name map files.
TEXFONTMAPS = .;$TEXMF/fonts/map//
Mirabile dictu! The font missing messages disappear after changing
texexec to the ruby script texmfstart texexec
. ensuring that the scripts are executable with:
cd .../texmf-local-/context/ruby
(sudo) chmod -R a+x *.rb
execute this in terminal as a user with administrator priveliges.
Hope this will help you on the way.
Well sort of.
I tried your way and got
texmfstart.rb not found
into the directory /usr/local/teTeX/share/texmf-local/scripts/context/ruby
and see that many scripts are not executable for others (regular users);
so I say chmod +x * in that directory and then texmfstart texexec toto
still doesn't work but it actually works with the full path; however my
path is correctly set
permission denied; so I go
into the directory /usr/local/teTeX/share/texmf-local/scripts/context/ruby
and see that many scripts are not executable for others (regular users);
so I say chmod +x * in that directory and then texmfstart texexec toto
still doesn't work but it actually works with the full
of texmfstart.rb and get permission denied; so I go
into the directory /usr/local/teTeX/share/texmf-local/scripts/context/ruby
and see that many scripts are not executable for others (regular users);
so I say chmod +x * in that directory and then texmfstart texexec toto
still doesn't work
uses kpsewhich
| to find the .rb or .pl script corresponding to the name used to invoke
| the script, and then runs perl or ruby with the full path to the
| script. This saves having to copy the scripts everytime you update
| context.
Thank you and Hans, I'll look for your script asa I go back
been testing to the list. The
| script uses kpsewhich
| to find the .rb or .pl script corresponding to the name used to invoke
| the script, and then runs perl or ruby with the full path to the
| script. This saves having to copy the scripts everytime you update
| context.
Thank you and Hans
., the first one being the important one.
2. ensuring that the scripts are executable with:
cd .../texmf-local-/context/ruby
(sudo) chmod -R a+x *.rb
execute this in terminal as a user with administrator priveliges.
Hope this will help you on the way.
Hans van der Meer
installation, as others seem to have other requirements?
As for texmfstart texexec it is unknown on my machine, I don't have ruby
installed anyway (is it necessary?).
Thanks to all!
--
jean
___
ntg-context mailing list
ntg-context@ntg.nl
http
source texsetup manually (in the tex directory?
What do you get for ruby `kpsewhich -format=texmfscripts texexec.rb`
..., which bypasses
texmfstart.rb, where you can try ...=--check, etc.?
--
George N. White III [EMAIL PROTECTED]
Head of St. Margarets Bay, Nova Scotia
recently that looks for the ruby scripts.
I like to keep context in a separate tree, texmf-cont, so it is easy
to see what files comes from cont-tmf in logs, etc.
Thomas Esser has (apparently just) announced that he will no longer
be maintaining teTeX. Which version of TeX do you recommend I
TEXPOOL=$TEXFORMATS
export MPPOOL=$TEXPOOL
export RUBYLIB=$TEXMFLOCAL/scripts/context/ruby:$RUBYLIB
export CTXMINIMAL=yes
create the directory specified by $VARTEXMF
cd $TEXMFOS/bin
chmod +x *
chmod -x xpdfsuite.zip
download http://www.pragma-ade.nl/context/current/cont-tmf.zip
mv cont-tmp.zip
Hello,
Tobias Burnus schrieb:
I freshly switched to the ruby script and have now a problem:
texmfstart texexec --pdf --pages=1:2
produces: No pages of output.
texmfstart texexec --pdf
however, works: Output written on tmp_.pdf (3 pages, 103204 bytes)
I do not know what that option
Tobias Burnus wrote:
Hello,
Tobias Burnus schrieb:
I freshly switched to the ruby script and have now a problem:
texmfstart texexec --pdf --pages=1:2
produces: No pages of output.
texmfstart texexec --pdf
however, works: Output written on tmp_.pdf (3 pages, 103204 bytes
Matt Gushee wrote:
Probably you just need either to put the Ruby script directory
($TEXMF/scripts/context/ruby) on your PATH, or create links from the
scripts you want to use to a directory in your current PATH. Maybe just
link texmfstart--it seems to be a front end for all the Ruby
I've been away from ConTeXt for a while, so I don't have full knowledge
of the recent changes. But it seems that many of the original Perl
scripts are being replaced by Ruby scripts (of which texmfstart is one),
which are in a different directory.
Is my system suddenly incomplete?
I am using
of passon
in all sources just returns mptopdf.pl texexec.pl and texutil.pl
With texmfstart --verbose texexec --passon='--interaction=nonstopmode'
-- verbose test, I get
using 'system' call: ruby
e:/isoimage/usr/local/context/tex/texmf-local/scripts/context/ruby/texexec.rb
--verbose --passon
[EMAIL PROTECTED] wrote:
The line in scripts/context/ruby/graphics/gs.rb with -dSAFER needs a
space before the closing quote. The corrected line is:
arguments -q -sDEVICE=pdfwrite -dNOPAUSE -dNOCACHE -dBATCH -dSAFER
ok, corrected (actually there were two places without trailing space
[EMAIL PROTECTED] wrote:
This version runs the ruby scripts directly, rather than the suggested
form, e.g., texfmstart pstopdf.rb file.ps. I have no idea if that
is intended to work -- it did in my very simple tests . I'm not sure
the RUBYLIB line is needed.
when you use texmfstart
Hello,
I freshly switched to the ruby script and have now a problem:
texmfstart texexec --pdf --pages=1:2
produces: No pages of output.
texmfstart texexec --pdf
however, works: Output written on tmp_.pdf (3 pages, 103204 bytes)
Tobias
___
ntg
even tried a chmod 755 -R isoimage, but that
did not help.
How can I debug why pdfetex is not able to *open* the map files?
Well, there was something in the path that was interfering with
context.
set PATH=E:\Ruby\bin
E:\isoimage\usr\local\context\tex\setuptex.bat E:\isoimage\usr\local\context
* the map files?
so, since you're running the mswin thing, how come that you have this chmod
stuff
Well, I use cygwin to get all the typical unixy tools. But, it seems
that context (and ruby) do not like cygwin. I need to do some more
testing to see exactly what was interfering, but removing cygwin
The line in scripts/context/ruby/graphics/gs.rb with -dSAFER needs a
space before the closing quote. The corrected line is:
arguments -q -sDEVICE=pdfwrite -dNOPAUSE -dNOCACHE -dBATCH -dSAFER
--
George N. White III [EMAIL PROTECTED]
Head of St. Margarets Bay, Nova Scotia
texexec.rb ...
when running context, the following script may be helpful.
TeX Live on linux runs texexec, etc. via a shell script that is linked
to the names of various
perl utilities. Here is my first cut at a version that tries to use
the ruby scripts
. If
I remove cygwin from the path (and use native windows' ruby) context
works fine. I still have the old problem with metapost and windows'
ruby. texexec --mptex does not work correctly. However, when I wrap
the metapost examples in a \startstop MPpage in a tex file, they work
fine.
So, I have
Hi Christian
I would like to include texmfstart.exe in the MiKTeX distribution, but I
don't know how to build texmfstart.exe. Is there a simple recipe
(Makefile) I can start with?
I'm switching from perl to ruby, so texmfstart is a ruby script. Say that the
next code is put
Le 15 mai 06 à 09:23, Hans Hagen a écrit :
Hi,
I played a bit with texmfstart on the (so so slow Q3) mac and i
think that i managed to get texmfstart working with less problems.
I now
also ship a texmfstart with all the used (context/ruby/base) libraries
merged in (new undocumented
Maurice Diamantini wrote:
Le 15 mai 06 � 09:23, Hans Hagen a �crit :
Hi,
I played a bit with texmfstart on the (so so slow Q3) mac and i
think that i managed to get texmfstart working with less problems.
I now
also ship a texmfstart with all the used (context/ruby/base) libraries
On 15 May 2006, at 09:23, Hans Hagen wrote:
(btw, is there a clever way to avoid this sudo stuff and become
real root?)
This depends on what you want to do and on which system. On most
unixes, you can say. You can in perl (and probably also ruby which I
do not know) set all kinds
hmm, on Fri, May 05, 2006 at 12:03:15AM +0200, Hans Hagen said that
I'd like to make the ruby version of texexec the default. Are there any
strong objections to this?
Also, i'd like the stubs to run texmfstart as launcher. For that
purpose i'll add a /scripts/context/stubs/[mswin|unix] path
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
frantisek holop wrote:
hmm, on Fri, May 05, 2006 at 12:03:15AM +0200, Hans Hagen said that
I'd like to make the ruby version of texexec the default. Are there any
strong objections to this?
Also, i'd like the stubs to run texmfstart as launcher. For that
purpose i'll add a /scripts
with the ruby
version of texexec. The cite command prints only .
Cheers, Peter
--
http://pmrb.free.fr/contact/
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Peter Münster wrote:
I've just seen, that there are a lot of symbolic links in the teTeX
installation to /opt/teTeX/bin/texexec, so please forget my advice above.
Yes, you have to delele all those symlinks that teTeX provides.
If you go to the unix stubs directory in the ConTeXt
Peter Münster wrote:
\placepublications[criterium=all]
Yes.
Hans and Taco, it seems that the bib module does not work with the ruby
version of texexec. The cite command prints only .
You still have to run bibtex by hand in the new version. And perhaps
you need to regerate the bbl
Dalyoung wrote:
Dear Aditya,
I did what you told me,
set RUBYLIB=/texmf.local/scripts/context/ruby
export $RUBYLIB
i'll post a version that has all the modules/classes embedded (i.e. i
made a ruby module that will package a script with libraries so that
they become standalone
On Sun, 14 May 2006, Taco Hoekwater wrote:
Peter Münster wrote:
Hans and Taco, it seems that the bib module does not work with the ruby
version of texexec. The cite command prints only .
It works fine for me, so giving advice is hard.
Hello Taco,
I've retried with the ruby-version
Dear Aditya,
I did what you told me,
set RUBYLIB=/texmf.local/scripts/context/ruby
export $RUBYLIB
But there is no change in the output of texmfstart --verbose texexec.
I copied texexec.rb in the home directory, then I got
~ mac$ texmfstart --verbose texexec
texmfstart version 1.8.6
On Thu, 11 May 2006, Hans Hagen wrote:
? wrote:
One remark for the texexec developer: it seems, when searching for
executables, the order in $PATH is not respected. For example: I had
/opt/teTeX/bin/dvips and /usr/bin/dvips and PATH=/opt/teTeX/bin:...
but it was /usr/bin/dvips that was
On Thu, 11 May 2006, Peter Münster wrote:
Using teTeX-3.0, here is what I've done to switch from perl texexec to the
ruby one:
chmod +x /opt/teTeX/texmf-context/scripts/context/ruby/texmfstart.rb
cd /usr/local/bin
ln -s /opt/teTeX/texmf-context/scripts/context/ruby/texmfstart.rb texmfstart
On Sat, 13 May 2006, Dalyoung wrote:
Dear Aditya,
I did what you told me,
set RUBYLIB=/texmf.local/scripts/context/ruby
export $RUBYLIB
I assume that by ... you mean the exact path of texmf.local
But there is no change in the output of texmfstart --verbose texexec.
I copied
, 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
Dear listers,
Forgive me for my beginner's question again.
As in the list(ntg-context Digest, Vol 23, Issue 28), I did the
following:
cp /usr/local/teTeX/share/texmf.local/scripts/context/ruby/
texmfstart.rb /usr/local/teTeX/bin/powerpc-apple-darwin-current/
texmfstart
chmod 755 /usr/local
On Sat, 13 May 2006, Dalyoung wrote:
Dear listers,
Forgive me for my beginner's question again.
As in the list(ntg-context Digest, Vol 23, Issue 28), I did the
following:
cp /usr/local/teTeX/share/texmf.local/scripts/context/ruby/
texmfstart.rb /usr/local/teTeX/bin/powerpc-apple-darwin
Peter Münster wrote:
Hello,
texexec --check takes about 2 minutes on my system and there are a lot of
warnings like:
What version of ruby?
Cheers, Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Taco Hoekwater wrote:
Peter M�nster wrote:
Hello,
texexec --check takes about 2 minutes on my system and there are a lot of
warnings like:
What version of ruby?
what does
texmfstart --verbose texexec
report? if it takes long, texmfstart will do a rather extensive search
. 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
features (since April 24):
* Integrated support for XeTeX on Linux
* The Ruby scripts are now preferred over the perl ones
* The included pattern files now use UTF-8 encoding
* Automatic handling of UTF-8 Byte Order Marks
Happy TeXing,
Taco Hoekwater
___
Ann
On Thu, 11 May 2006, Taco Hoekwater wrote:
Peter Münster wrote:
texexec --check takes about 2 minutes on my system and there are a lot of
warnings like:
What version of ruby?
1.8.0
I've made an update to 1.8.2 and the warnings are gone, thanks!
Cheers, Peter
--
http://pmrb.free.fr
On Thu, 11 May 2006, Hans Hagen wrote:
Taco Hoekwater wrote:
Peter M?nster wrote:
Hello,
texexec --check takes about 2 minutes on my system and there are a lot of
warnings like:
What version of ruby?
what does
texmfstart --verbose texexec
report
Hello,
I'm on Debian unstable and have the latest context sitting in my home
directory's 'texmf'. The new ruby scripts confuse me to no end - I just
don't understand how to make it works. Here is what works and what doesn't:
1) 'ruby ~/texmf/scripts/context/ruby/texexec.rb document.tex' works.
2
On Thu, 11 May 2006 10:12:58 -0700, Johannes Graumann
[EMAIL PROTECTED] wrote:
I'm at the end of my knowledge and intuition. Can anybody help
circumventing
the need for the monster 'ruby ~/texmf/scripts/context/ruby/texexec.rb
document.tex'?
Since I'm lazy, I didn't add any new path nor
Until a few minutes ago my Linux Slackware system dd not have a
Ruby interpreter. Yet Context runs fine. I seem to remember
something about some components of Context existing as Ruby
scripts. Am I dreaming or are there such beasties?
--
John Culleton
Books with answers to marketing
RUBYLIB=~/texmf/scripts/context/ruby
Using teTeX-3.0, here is what I've done to switch from perl texexec to the
ruby one:
chmod +x /opt/teTeX/texmf-context/scripts/context/ruby/texmfstart.rb
cd /usr/local/bin
ln -s /opt/teTeX/texmf-context/scripts/context/ruby/texmfstart.rb texmfstart
copy these 3
� wrote:
One remark for the texexec developer: it seems, when searching for
executables, the order in $PATH is not respected. For example: I had
/opt/teTeX/bin/dvips and /usr/bin/dvips and PATH=/opt/teTeX/bin:...
but it was /usr/bin/dvips that was called to create the PS-file.
hm, i just
Johannes Graumann wrote:
Hello,
I'm on Debian unstable and have the latest context sitting in my home
directory's 'texmf'. The new ruby scripts confuse me to no end - I just
don't understand how to make it works. Here is what works and what doesn't:
Have you run mktexlsr? I had to do
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
\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
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
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
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
On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen [EMAIL PROTECTED] 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
nico wrote:
On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen [EMAIL PROTECTED] 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
On Tue, 09 May 2006 11:09:43 +0200, Hans Hagen [EMAIL PROTECTED] wrote:
nico wrote:
On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen [EMAIL PROTECTED] 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
nico wrote:
On Tue, 09 May 2006 11:09:43 +0200, Hans Hagen [EMAIL PROTECTED] wrote:
nico wrote:
On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen [EMAIL PROTECTED] wrote:
Got big problems with the fonts that are no more found when using the
ruby
stuff. Since the unix stubs
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
.
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
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
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
Aditya Mahajan wrote:
On Fri, 5 May 2006, Hans Hagen wrote:
Hi,
I'd like to make the ruby version of texexec the default. Are there any
strong objections to this?
Is ruby stable with respect to system calls? Is the behaviour
consistent on Linux and Windows? Are there active
On Sun, 7 May 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
On Fri, 5 May 2006, Hans Hagen wrote:
Hi,
I'd like to make the ruby version of texexec the default. Are there any
strong objections to this?
Is ruby stable with respect to system calls? Is the behaviour
consistent on Linux
Aditya Mahajan wrote:
I get.
F:\tmp\cont-test\testruby --version
ruby 1.8.4 (2005-12-24) [i386-mswin32]
F:\tmp\cont-test\testruby test.rb
mpto mp-test-01.mp
\gdef\mpxshipout{\shipout\hbox\bgroup
\setbox0=\hbox\bgroup}
\gdef\stopmpxshipout{\egroup \dimen0=\ht0 \advance\dimen0\dp0
Aditya Mahajan wrote:
F:\tmp\cont-test\testruby test.rb
mpto mp-test-01.mp
actually, i can best write an mpto function in ruby -)
Hans
-
Hans Hagen | PRAGMA ADE
On Sun, 7 May 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
F:\tmp\cont-test\testruby test.rb
mpto mp-test-01.mp
actually, i can best write an mpto function in ruby -)
That will be great. The lesser external dependencies, the better :)
Aditya
--
Aditya Mahajan, EECS Systems, University
On Sun, 7 May 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
I get.
F:\tmp\cont-test\testruby --version
ruby 1.8.4 (2005-12-24) [i386-mswin32]
F:\tmp\cont-test\testruby test.rb
mpto mp-test-01.mp
\gdef\mpxshipout{\shipout\hbox\bgroup
\setbox0=\hbox\bgroup}
\gdef\stopmpxshipout
Aditya Mahajan wrote:
On Sun, 7 May 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
On Fri, 5 May 2006, Hans Hagen wrote:
Hi,
I'd like to make the ruby version of texexec the default. Are there any
strong objections to this?
Is ruby stable with respect
The Aditya's example works OK here (no cygwin installed; not one-click
installer, but extracted files + bin path set, ruby 1.9.0 (2005-07-22)
[i386-mswin32]). But I remember having problems on computers where
cygwin was installed.
Even if you run ruby from cmd.exe: if cygwin resides in your path
On Sun, 7 May 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
On Sun, 7 May 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
On Fri, 5 May 2006, Hans Hagen wrote:
Hi,
I'd like to make the ruby version of texexec the default. Are there any
strong objections to this?
Is ruby stable
901 - 1000 of 1321 matches
Mail list logo
