but not been able to isolate it. It would be
really great if this could be fixed in the ruby script.
Duncan
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
the ruby variant installed yet)
although I know that that's not quite the same. (I know some people in
LaTeX world who use make files to copy/remove files.)
Mojca
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
on the ruby version). I
also added support for nesting ranges, which I then discovered weren't
supported anyway. (I also had to change the sort order on
@RegisterEntries so that [f] and [t] entries would be consecutive,
instead of all the [f] entries preceding the [t] entries, but it looks
like
Just to let you know: if you want to convert your ConTeXt documents
into HTML, you can try to install tex4ht and replace the old files
with new ones: http://www.cse.ohio-state.edu/~gurari/TeX4ht/bugfixes.html
(newt4ht.zip)
It works OK with the old perl texexec.pl, the ruby version causes some
Willi Egger wrote:
Hi Hans,
When arranging pfd pages from a pdf file with the ruby version of the
texexec script the following error occurs:
cid:part1.07050109.01020703@boede.nltexmfstart texexec.rb --pdfarrange
--paper=a5a4 --print=2up --result=a5a4-artiplydoc artiply-doc.pdf
(if not, then it may be a ruby issue).
Cheers, taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
of output, and you will probably
see an expansion loop occuring (if not, then it may be a ruby issue).
i just ran into the loop as well,
it has to do with a change in load order of modules, i'll fix it (i'm trying to
get rid of funny dependencies and this alpha/beta release was actually
, and you will probably
see an expansion loop occuring (if not, then it may be a ruby issue).
i just ran into the loop as well,
it has to do with a change in load order of modules, i'll fix it
It works fine with the new version.
(i'm trying to get rid of funny dependencies and this alpha
Hi,
today i have try to run the *new* one, i get the following error, please
can anybody help ;-)
---
ruby /home/al/texmf/scripts/context/ruby/texmfstart.rb --verbose texexec
layout.text
texmfstart version 2.0.0
expanding 'texexec' to 'texexec.rb'
locating 'texexec.rb' in current path
On Saturday 12 August 2006 13:52, Taco Hoekwater wrote:
I am using texexec 5.4.3. I get warning messages telling me to
use texmfstart instead but since that script is not functional on my
What do you mean with 'not functional'? No ruby installed?
Cheers,
Taco
files and probably logs.
Mojca
PS: try to update ConTeXt to the latest version if you intend to send
log files and try to use the ruby version of texexec (texmfstart
texexec) if possible. None should be necessary (it should work with
the ancient version as well), but it often helps, esp. because
. That is much faster (at the expense
of always having the whole contents of those files in memory)
I am using texexec 5.4.3. I get warning messages telling me to
use texmfstart instead but since that script is not functional on my
What do you mean with 'not functional'? No ruby installed?
Cheers
In Unix ruby (like in Perl) the $TEXMFLOCAL is expanded by the shell
because of the $, and the result is run by the backticks. Usually
TEXMFLOCAL has no setting in the shell or environment so ruby runs the
command with $TEXMFLOCAL replaced by an empty string, giving:
kpsewhich --expand
:
$ TEXMFLOCAL=/home/sanjoy/texmf texmfstart ctxtools --updatecontext
This fixes the problem that ctxtools uses (I think) Windows quoting in
this source line:
tree = `kpsewhich --expand-path $TEXMFLOCAL`.chomp rescue nil
In Unix ruby (like in Perl) the $TEXMFLOCAL is expanded by the shell
and everything after it is what I type:
$ TEXMFLOCAL=/home/sanjoy/texmf texmfstart ctxtools --updatecontext
This fixes the problem that ctxtools uses (I think) Windows quoting in
this source line:
tree = `kpsewhich --expand-path $TEXMFLOCAL`.chomp rescue nil
In Unix ruby (like
pdftotext + ruby regexp
b)
\usemodule[wordcount]
whatever
\startstatistics[name][words|letters|lines]
some more-or-less plain text
\stopstatistics
whatever
and according to Aditya's idea, run a (ruby) regular expression
(insead of detex) on it which would write
Mojca Miklavec wrote:
t complementary) methods that might be sensible:
a) ctxtools --wordcount filename[tex|pdf]
to do the wordcount for the whole document using pdftotext + ruby regexp
counting words in tex docs is not that hard:
it needs in addition:
delete all the words starting
On Sun, 6 Aug 2006, Mojca Miklavec wrote:
Base on those three answers I got a more clear idea of two (different,
but complementary) methods that might be sensible:
a) ctxtools --wordcount filename[tex|pdf]
to do the wordcount for the whole document using pdftotext + ruby regexp
b
be implemented
in perl/ruby which context uses anyway.
Some time ago Hans mentioned that he counts the number of appearance
of single charactres, but I don't know how difficult it would be to
extend it to count the number of words.
The problem is not that well defined (how to handle equations
like a parser for hardcoded (La)TeX
(someone should correct me if I'm wrong).
However, the fact that abstracts for which one might need wordcount
usually don't have too much trickery involved (they're usually olmost
pure plain text), doing the same, only with a simple ruby script
instead of compiling
at all. Do you indeed have
any ideas how to set environmental variables inside of a ruby script,
so that they would be seen from outside? Because that would solve a
whole lot of problems in MikTeX.
The traditional trick is to start a new shell/command window inside
your script (last line
Same batch file, so yes.
It would be possible to convert the batch file into a perl or
ruby
scripts plus a one-line batch that starts the interpreter +
script,
Hmm,
aren't you shutting with 'Kanonen auf Spatzen'?
I have running the standalone-context here on WindowsME.
I have modifyed
[EMAIL PROTECTED] wrote:
Same batch file, so yes.
It would be possible to convert the batch file into a perl or
ruby
scripts plus a one-line batch that starts the interpreter +
script,
Hmm,
aren't you shutting with 'Kanonen auf Spatzen'?
Perhaps, but the advantage is that you don't
David Arnold wrote:
Taco,
Is this also true about:
http://www.pragma-ade.com/context/install/mswincontext.zip
Same batch file, so yes.
It would be possible to convert the batch file into a perl or ruby
scripts plus a one-line batch that starts the interpreter + script,
but not being
Taco Hoekwater wrote:
David Arnold wrote:
Taco,
Is this also true about:
http://www.pragma-ade.com/context/install/mswincontext.zip
Same batch file, so yes.
It would be possible to convert the batch file into a perl or ruby
scripts plus a one-line batch that starts
On 8/2/06, Taco Hoekwater wrote:
David Arnold wrote:
Taco,
Is this also true about:
http://www.pragma-ade.com/context/install/mswincontext.zip
Same batch file, so yes.
It would be possible to convert the batch file into a perl or ruby
scripts plus a one-line batch that starts
etc
- you can now distinguish matching pairs and take some action
- afterwards you convert the .. things back to { }
(at least that is how i did such thing until now in e.g. ruby)
Hans
All,
I have cdwincontext installed and I am trying to run texmfstart from
a perl script on windows. I tried associating file extension .rb with
the ruby that comes with the context distro.
Am I missing something here?
#!/usr/bin/perl
use warnings;
use strict;
my $os;
if ($^O =~ /darwin/i
David Arnold wrote:
All,
I have cdwincontext installed and I am trying to run texmfstart from
a perl script on windows. I tried associating file extension .rb with
the ruby that comes with the context distro.
just run texmfstart.exe
Hans
Sanjoy Mahajan wrote:
How does Windows quoting work? Well, the whole story isn't needed,
but only how would this ruby line
`kpsewhich --expand-var '$TEXMFLOCAL'`
differ on Windows relative to Unix?
the problem is that one never knows when the shell does things and when
the program
Hans Hagen wrote:
Sanjoy Mahajan wrote:
How does Windows quoting work? Well, the whole story isn't needed,
but only how would this ruby line
`kpsewhich --expand-var '$TEXMFLOCAL'`
differ on Windows relative to Unix?
the problem is that one never knows when the shell does things
, or taking public transit...but I dream.
can you try: ...
I ran this ruby script (on Linux):
def locatedlocaltree
tree = `kpsewhich --expand-path $TEXMFLOCAL`.chomp rescue nil
unless tree FileTest.directory?(tree) then
tree = `kpsewhich --expand-path $TEXMF`.chomp rescue
Hi,
Ralf Schmitt wrote:
Beforehand I had been using the 2006.04.17 beta and had put off
upgrading because I was scared of the change from perl texexec to ruby
texexec.
1. (optional cleanup) Delete the old Context-installed files in
~/texmf/. This step is optional, but I do it so that I
is almost like
'sh' but has the ~ idiom for $HOME.
Updating context was one of the things on my todo list. great.
Beforehand I had been using the 2006.04.17 beta and had put off
upgrading because I was scared of the change from perl texexec to ruby
texexec.
1. (optional cleanup) Delete
Taco Hoekwater wrote:
Hi,
Ralf Schmitt wrote:
Beforehand I had been using the 2006.04.17 beta and had put off
upgrading because I was scared of the change from perl texexec to ruby
texexec.
1. (optional cleanup) Delete the old Context-installed files in
~/texmf/. This step is optional
to (mailing list, contextgarden)? texexec or texmfstart?
Should
./scripts/context/perl/texexec.pl
still be distributed?
And should
./scripts/context/ruby/newtexexec.rb
(and others new*.rb sripts) still be distributed if it significantly
differs from newer
./scripts/context/ruby/texexec.rb
Jano
sure you are not using an out-of-date version of
these files.
Good point, thanks. I'll incorporate it into the eventual wiki page.
A somehwat more flexible version is
#!/bin/sh
ruby `kpsewhich --format='texmfscripts' texmfstart.rb` $@
(also notice the lack of quotes around
the stub scripts.
Would it not work to simply point the variable TEXMFLOCAL to
~/texmf?
I was a little leery but tried it. Meanwhile here's a patch that
fixes the need for that:
--- a/scripts/context/ruby/ctxtools.rb Wed Jul 26 14:50:16 2006 -0400
+++ b/scripts/context/ruby/ctxtools.rb Wed
is
overwritten by the unzip in the middle of running the script? Will
ruby execute half from the old script and half from the new script?
That is safe. Modern scripting languages normally byte-compile the
entire file before running it (the main advantage is that this
captures syntrax errors before any
for windows as well (differ ent quoting)
How does Windows quoting work? Well, the whole story isn't needed,
but only how would this ruby line
`kpsewhich --expand-var '$TEXMFLOCAL'`
differ on Windows relative to Unix?
And the $@ - $@ change can be done in the Unix stubs only, so the
change
did you make texmfstart.rb executable? as well as all the ruby scripts?
On Jul 26, 2006, at 3:59 PM, John R. Culleton wrote:
I successfully updated to the latest cont-tem zip but it wasn't
easy.
Karl Berry suggested the following:
cd $TMPDIR
dir=`pwd`
wget http://www.pragma-ade.com
the ~ idiom for $HOME.
Beforehand I had been using the 2006.04.17 beta and had put off
upgrading because I was scared of the change from perl texexec to ruby
texexec.
1. (optional cleanup) Delete the old Context-installed files in
~/texmf/. This step is optional, but I do it so that I can
wouldn't help much,
but the full log in attachment might.
This might have nothing to do with your problem, but it might be
sensible to try to use texmfstart texexec.rb instead of the old perl
script.
You need to create an executable texmfstart (in the bin folder of
course) with content
ruby path
Hello Hans and others,I'd have two comments to the texmf/scripts/context/ruby/base/tex.rb script.1. I find quite impractical that the formats (cont-en, cont-nl etc.) are hardcoded in the scripts. When one wants to add a new format, then he must add it on 4 or 5 places in the script, and do
Hans Hagen wrote:
Richard Gabriel wrote:
Hello Hans and others,
I'd have two comments to the texmf/scripts/context/ruby/base/tex.rb
script.
1. I find quite impractical that the formats (cont-en, cont-nl etc.)
are hardcoded in the scripts. When one wants to add a new format, then
he
well, we can use:
def validsomething(str,something) if str then list = [str].flatten.collect do |s| something[s] || s # || s addedExcellent! Could you please add it to the distribution?Many thanks!-RichardP.S. I'll probably have to learn at basics of Ruby... I'm familiar with Perl, PHP
The Wizard wrote:
All -
I downloaded and installed ruby 1.8.4 from sunfreeware.com, and now
I can at least use the texmfstart command. I ran texmfstart texexec
--check and get this back:
TeXExec | current distribution: web2c
TeXExec | context source date: 2006.07.14 12:08
TeXExec
Aditya Mahajan wrote:
On Tue, 11 Jul 2006, Hans Hagen wrote:
(There is this Best Of Ruby Quiz book, maybe we should make a Best Of
Context Quiz one ... )
Maybe we should first start a Context Quiz?
sounds ok to me; we can use the wiki for that and or something similar (maybe
Hello,
For some time I was doing
ruby /tex/texmf-local/scripts/context/ruby/texsync.rb --update --force
--destination=/tex --make
to upgrade minimal distribution but it doesn't work for me
anymore. Has anything changed in the meantime?
Piotr
Piotr Kopszak wrote:
Hello,
For some time I was doing
ruby /tex/texmf-local/scripts/context/ruby/texsync.rb --update --force
--destination=/tex --make
normally that tree lage behind the current version of context (i generate those
minimal trees only when i need them since it takes
: command not found.
Does it matter that I have the line
alias texmfstart='ruby /usr/local/teTeX/share/texmf.local/scripts/
context/ruby/texmfstart.rb'
in my .profile rather than an executable version of the texmfstart
script in my $PATH?
Hello Alan,
I doubt, that an alias is inherited
texmfstart='ruby
/usr/local/teTeX/share/texmf.local/scripts/context/ruby/
texmfstart.rb'
in my .profile rather than an executable version of the texmfstart
script in my $PATH?
Yes -- sudo doesn't know about shell aliases, it's trying to find an
executable file named texmfstart in your PATH
texmfstart texexec --make --allfailed with the error message sudo: texmfstart: command not found.Fortunately, sudo texexec --make --allstill works, so life goes on.Still, why is this happening?Does it matter that I have the line alias texmfstart='ruby /usr/local/teTeX/share/texmf.local/scripts
the line
alias texmfstart='ruby /usr/local/teTeX/share/texmf.local/scripts/
context/ruby/texmfstart.rb'
in my .profile rather than an executable version of the texmfstart
script in my $PATH?
Hello Alan,
I doubt, that an alias is inherited by the shell of sudo.
Here is one way, how to set up
--make --all
(which worked with the last ConTeXt installation)
and
sudo -H texmfstart texexec --make --all
failed with the error message
sudo: texmfstart: command not found.
[...]
Does it matter that I have the line
alias texmfstart='ruby
/usr/local/teTeX/share/texmf.local
On Tue, 11 Jul 2006, Hans Hagen wrote:
(There is this Best Of Ruby Quiz book, maybe we should make a Best Of Context
Quiz one ... )
Maybe we should first start a Context Quiz?
Aditya
___
ntg-context mailing list
ntg-context@ntg.nl
http
Hans van der Meer wrote:
I send the offending mpgraph.mp file. It has ;'s all over. There are so
many ;;'s and even some ;;;'s that I am tempted to think that one of
the translation scripts is the culprit, adding a ; per newline maybe? I
am sorry not having taken a look into the ruby
maybe? I
am sorry not having taken a look into the ruby scripts, but my ruby
knowledge is nihil.
The tex input file would be more useful. The mpgraph file is
autogenerated from that, after all.
I am afraid that isn't possible just now. The problem seems very
specific in the placing
{MyTrick}]
\startframedtext
\placeformula
\startformula
a+b=c
\stopformula
\stopframedtext
\stoptext
I'm sure that yuou can explain this on the wiki
(There is this Best Of Ruby Quiz book, maybe we should make a Best Of Context
Quiz one ... )
Hans
[EMAIL PROTECTED] wrote:
On 6/23/06, Taco Hoekwater [EMAIL PROTECTED] wrote:
After following those instructions, everything should be ok except
for the new ruby script links and texmfstart's warning. For
that, do the following:
* make sure you have ruby installed. If not, do that first
Thanks,
on what does it depend?
On gwConetxt? (Or that I haven't installed ruby?)
-a-
On 11 Jul 2006, at 09:56, Hans Hagen wrote:
Matthias Wächter wrote:
Hans Hagen schrieb:
andrea valle wrote:
I reinstalled all (tex, texshop) and solved the problem. Now I
installed ConTeXt Beta
I send the offending mpgraph.mp file. It has ;'s all over. There are
so many ;;'s and even some ;;;'s that I am tempted to think that one
of the translation scripts is the culprit, adding a ; per newline
maybe? I am sorry not having taken a look into the ruby scripts, but
my ruby knowledge
with:
ruby /usr/local/teTeX/share/texmf.local/scripts/context/ruby/texmfstart.rb
, which is my path to texmfstart.rb, in \runR solved the problem.
I had followed the Other method from the ConTeXt wiki for enabling
texmfstart on my system. This works fine for calling commands from
the command line
ruby script links and texmfstart's warning. For
that, do the following:
* make sure you have ruby installed. If not, do that first
* go to the scripts/context/stubs/unix/ directory in your
freshly unpacked ConTeXt distribution, make sure you
have write permissions to the TeX
Dear consortium,
I am using an ConTeXt from Jan-28-06 (ancient) and wish to upgrade. Now
things have changed (perl=ruby, no more texexec.ini etc.), I still use
both the pdftex and aleph engines, and I want to do this as cleanly as
possible. I am using mswincontext.zip with the xemtex latex
Hans Hagen [EMAIL PROTECTED] writes:
i prefer the rules, so if you can sort that out with peter
In that case, you can examine the internals of my Perl script
elhyph-utf8 and translate its logic to Ruby in ctxtools. But that is a
non-trivial effort, and I cannot do it. A better alternative may
Idris Samawi Hamid wrote:
Dear consortium,
I am using an ConTeXt from Jan-28-06 (ancient) and wish to upgrade. Now
things have changed (perl=ruby, no more texexec.ini etc.), I still use
both the pdftex and aleph engines, and I want to do this as cleanly as
possible. I am using
Peter Heslin wrote:
Hans Hagen [EMAIL PROTECTED] writes:
i prefer the rules, so if you can sort that out with peter
In that case, you can examine the internals of my Perl script
elhyph-utf8 and translate its logic to Ruby in ctxtools. But that is a
non-trivial effort, and I
On Fri, 30 Jun 2006 11:07:15 -0600, Hans Hagen [EMAIL PROTECTED] wrote:
I am using an ConTeXt from Jan-28-06 (ancient) and wish to upgrade. Now
things have changed (perl=ruby, no more texexec.ini etc.), I still use
both the pdftex and aleph engines, and I want to do this as cleanly
A few weeks ago, I looked at Context, because I wanted utf-8 hyphenation
patterns for ancient Greek, but then I saw that the patterns shipped
with Context have serious bugs. I had hoped to patch ctxtools, but the
required changes went beyond my knowledge of Ruby.
I recently posted a Perl script
texexec' instead
Now for questions:
1. How do I configure my system to use texmstart?
Under windows it comes as an executable, under linux I sometimes
created an executable file named texexec (in the bin folder of course)
with the content
ruby path-to-context-ruby-scripts/texmfstart.rb
Mojca Miklavec wrote:
with the content
ruby path-to-context-ruby-scripts/texmfstart.rb
What I have is this simple script (and it should work on MacOSX
just as well). Name it 'texfmstart', make it executable, fill in
the correct path and put it in a binaries directory.
#!/bin/sh
On 28 juin 2006, at 15:11, Taco Hoekwater wrote:
Mojca Miklavec wrote:
with the content
ruby path-to-context-ruby-scripts/texmfstart.rb
What I have is this simple script (and it should work on MacOSX
just as well). Name it 'texfmstart', make it executable, fill in
the correct path and put
Taco, Mojca,
Thanks, on my Mac OSX 10.4.6 with Gerben's TeX, I:
cd /usr/local/teTeX/share/texmf.local/scripts/context/ruby/
sudo chmod -R a+x *.rb
Then I wrote in .bash_profile:
alias texmfstart='/usr/local/teTeX/share/texmf.local/scripts/context/
ruby/texmfstart.rb'
Now I have:
chapter1
On 6/28/06, David Arnold wrote:
Taco, Mojca,
Thanks, on my Mac OSX 10.4.6 with Gerben's TeX, I:
cd /usr/local/teTeX/share/texmf.local/scripts/context/ruby/
sudo chmod -R a+x *.rb
Then I wrote in .bash_profile:
alias texmfstart='/usr/local/teTeX/share/texmf.local/scripts/context/
ruby
Am 2006-06-28 um 18:07 schrieb Otared Kavian:
On 28 juin 2006, at 15:11, Taco Hoekwater wrote:
Mojca Miklavec wrote:
with the content
ruby path-to-context-ruby-scripts/texmfstart.rb
What I have is this simple script (and it should work on MacOSX
just as well). Name it 'texfmstart
-n ${ZSH_VERSION+set} alias -g '${1+$@}'='$@'
what=`echo $0 | sed '[EMAIL PROTECTED]/@@'`
p=`kpsewhich -format=texmfscripts $what.pl`
{ test -n $p test -f $p; } \
|| { echo \`$what.pl' not found.; exit 1; }
perl $p ${1+$@}
Ruby is installed:
tmp $ which ruby
/usr/bin/ruby
tmp $ ruby
texexec' instead
tmp $ which texexec
/usr/local/teTeX/bin/powerpc-apple-darwin-current/texexec
Which appears to be some sort of shell script.
Yes, it is a wrapper that uses kpsewhch to search for what.pl and
then fires up perl with the full path to the script. The same trick
works for ruby
-linux\web2c\pdfetex, depending on your texexec.ini setup.
IIRC, the new (ruby) texexec does not read texexec.ini. One
possibility is that $TEXMFLOCAL is not set (as you did not run
setuptex) so texexec did not know where to place the format files.
This also happens with Miktex and texexec creates
be ok except
for the new ruby script links and texmfstart's warning. For
that, do the following:
* make sure you have ruby installed. If not, do that first
* go to the scripts/context/stubs/unix/ directory in your
freshly unpacked ConTeXt distribution, make sure you
have write
is supposed to do. It is a
Ruby script. Does it replace texexec or does it manage texexec?
Anyhow back to the starting line. I have reinstalled the version
of tetex that comes with Slackware 10.2 so at least I am
operational. I have in addition downloaded the iso's for
slackware-current. I tried upgrading
the texmfstart command instead. This is as I recall a Windows thingie.
you need texmfstart on linux also. Does everything work fine if you
use texmfstart?
Not yet. I am unsure what texmfstart is supposed to do. It is a
Ruby script. Does it replace texexec or does it manage texexec?
texmfstart is a ruby
There is now a teTeX binary package available on
http://pmrb.free.fr/work/OS/ConTeXt/tetex/
Features:
* support for easy ConTeXt update (command updateConTeXt.sh)
* support for URW Garamond
* support for Adobe eurofont
* support for ruby versions of ConTeXt scripts
* latest pdfTeX
* latest
On 6/20/06, Peter Münster [EMAIL PROTECTED] wrote:
There is now a teTeX binary package available on
http://pmrb.free.fr/work/OS/ConTeXt/tetex/
Features:
* support for easy ConTeXt update (command updateConTeXt.sh)
* support for URW Garamond
* support for Adobe eurofont
* support for ruby
to *see* code -)
Correct. Subversion repo for the entire project (including schema
for CSL, and the start of a Ruby port of citeproc) is here:
http://sourceforge.net/svn/?group_id=117435
Bruce
___
ntg-context mailing list
ntg-context@ntg.nl
http
On Thursday 04 May 2006 18:03, Hans Hagen wrote:
Hi,
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
John R. Culleton wrote:
On Thursday 04 May 2006 18:03, Hans Hagen wrote:
Hi,
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
Am Mittwoch, 14. Juni 2006 09:35 schrieb Hans Hagen:
if data =~ /output files* written\:\s*(.*)$/mois then
I am no ruby programmer, but although the above works, it should be
if data =~ /output files? written ...
Uwe
Uwe Koloska wrote:
Am Mittwoch, 14. Juni 2006 09:35 schrieb Hans Hagen:
if data =~ /output files* written\:\s*(.*)$/mois then
I am no ruby programmer, but although the above works, it should be
if data =~ /output files? written ...
well, s
don't know
any Ruby, so it will be an interesting challenge -- the changes required
go beyond tweaking the existing code.
The characters in the file lang-agr.pat are precomposed, Unicode
normalization form D. But I'd like to support both normalization forms
C and D, if possible, in the same
are you using? Because it might be far easier to get
Chineese working with XeTeX than with pdfTeX. In that case you don't
need dozens of those (soon-to-become-obsolete) .map, .tfm and .enc
files. (and you don't need that ruby script)
XeTeX is runnung on Mac OS X for quite some time now, on Linux since
] in your bin path
and see what happens then?
No pdftex is in the path.
I call context by using
set PATH=E:\Ruby\bin
call E:\isoimage\usr\local\context\tex\setuptex.bat
E:\isoimage\usr\local\context\tex
so there should not be any mismatched executables.
ah ... typo in base/tex.rb
; can
you remove all traces or pdftex[.exe] in your bin path and see what
happens then?
No pdftex is in the path.
I call context by using
set PATH=E:\Ruby\bin
call E:\isoimage\usr\local\context\tex\setuptex.bat
E:\isoimage\usr\local\context\tex
so there should not be any mismatched
is that the latest pdfetex is not called pdftex;
can you remove all traces or pdftex[.exe] in your bin path and see what
happens then?
No pdftex is in the path.
I call context by using
set PATH=E:\Ruby\bin
call E:\isoimage\usr\local\context\tex\setuptex.bat
E:\isoimage\usr\local\context
, the problem is that the latest pdfetex is not called
pdftex; can you remove all traces or pdftex[.exe] in your bin path
and see what happens then?
No pdftex is in the path.
I call context by using
set PATH=E:\Ruby\bin
call E:\isoimage\usr\local\context\tex\setuptex.bat
E:\isoimage\usr
and see what happens
then?
No pdftex is in the path.
I call context by using
set PATH=E:\Ruby\bin
call E:\isoimage\usr\local\context\tex\setuptex.bat
E:\isoimage\usr\local\context\tex
so there should not be any mismatched executables.
Aditya
___
ntg
XECcommand{texmfstart texexec} \fiIf I understand correctly, this effectuates a change from the perl to the ruby scripts.Removing the texmfstart solves the problem.I compared two runs for the transparency problem in order to see if there is some clue:1. Both mp-files turn out being the same (except for
--verbose texexec --verbose --make --all
actually, the problem is that the latest pdfetex is not called pdftex;
can you remove all traces or pdftex[.exe] in your bin path and see what
happens then?
No pdftex is in the path.
I call context by using
set PATH=E:\Ruby\bin
call E:\isoimage
\TEXEXECcommand{texexec} \fi
This gives me the impression it might not be in context itself,
especially since to my (inexperienced) eye there are no or few
changes between the working and nonworking versions that might
explain the problem.
It might be the change from the perl to the ruby scripts
, .tfm and .enc
files. (and you don't need that ruby script)
XeTeX is runnung on Mac OS X for quite some time now, on Linux since
end of April and on Windows for some days or weeks (not officially
released yet).
If you have Mac you can use i-Installer for installing XeTeX, on Linux
it might
801 - 900 of 1321 matches
Mail list logo
