Am Thu, 25 Nov 2010 12:31:05 +0200 schrieb Khaled Hosny:
limited utf-8 is now available -- so interesting that Aleks made MkIV
default --, don't know when/if-ever bidi support will be there ...
>>>
>>> I don't know if bidi will ever be there either, but the sole fact that
>>> it suppor
On Thu, Nov 25, 2010 at 11:01:17AM +0100, Ulrike Fischer wrote:
> Am Tue, 23 Nov 2010 19:43:13 +0100 schrieb Mojca Miklavec:
>
> >> limited utf-8 is now available -- so interesting that Aleks made MkIV
> >> default --, don't know when/if-ever bidi support will be there ...
> >
> > I don't know if
Am Tue, 23 Nov 2010 19:43:13 +0100 schrieb Mojca Miklavec:
>> limited utf-8 is now available -- so interesting that Aleks made MkIV
>> default --, don't know when/if-ever bidi support will be there ...
>
> I don't know if bidi will ever be there either, but the sole fact that
> it supports UTF-8
Update on using MikTeX 2.9, ConTeXt MKIV, Winedt 6.?!!!
First let me thank Mojca, Aditya, Ulrike and Hans for looking into this.
I received a suggestion to remove Miktex Full and install Miktex basic. That
did NOT work as I like lucida and lucida math which will not function
correctly using Mikte
2010/11/23 "\"Idris Samawi Hamid ادريس سماوي حامد\"" wrote:
>
> I used winedt for years, and turning it into a full-fledged dedicated
> ConTeXt editor would not be hard ... I had to leave it because there was no
> utf-8 or bidi support.
>
> limited utf-8 is now available -- so interesting that Alek
On Sun, 21 Nov 2010 02:03:33 -0700, barney schwartz
wrote:
>>> New build of WinEdt 6.0 (Build: 20101121) has been uploaded to
>
>>> www.winedt.com
>
>>> This build contains macros that work with the latest ConTeXt Mark
>>> IV (previous versions were designed for older version of ConTeXt).
>>> If
On Sun, Nov 21, 2010 at 10:03, barney schwartz wrote:
>>> New build of WinEdt 6.0 (Build: 20101121) has been uploaded to
>
>>> www.winedt.com
>
>>> This build contains macros that work with the latest ConTeXt Mark
>>> IV (previous versions were designed for older version of ConTeXt).
>>> If you are
On 21-11-2010 10:03, barney schwartz wrote:
Just thought I would post this here for other Winedt users.
ah, good. thanks,
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8
>> New build of WinEdt 6.0 (Build: 20101121) has been uploaded to
>> www.winedt.com
>> This build contains macros that work with the latest ConTeXt Mark
>> IV (previous versions were designed for older version of ConTeXt).
>> If you are upgrading from older version of WinEdt make sure that
>> the
Hi Thomas,
Thomas A. Schmitz wrote:
> On Dec 6, 2007, at 8:26 AM, Arthur Reutenauer wrote:
>
>> That particular line:
>>
>> # Error in lua file loading: ?:0: attempt to call field '?' (a nil
>> value)
>>
>> is often the sign of mismatching luatools and ConTeXt version :-)
>>
>> Arthur
>
On Dec 6, 2007, at 8:26 AM, Arthur Reutenauer wrote:
> That particular line:
>
> # Error in lua file loading: ?:0: attempt to call field '?' (a nil
> value)
>
> is often the sign of mismatching luatools and ConTeXt version :-)
>
> Arthur
Yes, thanks for your help, now it works wonderf
Arthur Reutenauer wrote:
> That particular line:
>
> # Error in lua file loading: ?:0: attempt to call field '?' (a nil value)
>
> is often the sign of mismatching luatools and ConTeXt version :-)
indeed, make sure that luatools --generate is run; many new files ...
---
That particular line:
# Error in lua file loading: ?:0: attempt to call field '?' (a nil value)
is often the sign of mismatching luatools and ConTeXt version :-)
Arthur
___
If your question is of interest
Wolfgang Schuster wrote:
> the new release did work for me with LuaTeX but the mkii part give
> a error message in conbination with XeTeX., only a short error message
> but it should be also fixed.
>
> Line 53 in regi-ini.mkii use in a message for XeTeX "\m!regime" as
> messageconstant and not "\
2007/12/5, Thomas A. Schmitz <[EMAIL PROTECTED]>:
> Oops, I was too fast upgrading... luatex fails to produce format files
> on my system:
>
> luatex --version
> This is LuaTeX, Version snapshot-0.20.0-2007120515
>
> luatools --ini --compile cont-en
>
> LuaTools | creating initialization file cont-
On Dec 6, 2007, at 12:08 AM, Idris Samawi Hamid wrote:
> On Wed, 05 Dec 2007 15:40:50 -0700, Thomas A. Schmitz
> <[EMAIL PROTECTED]> wrote:
>
>> Oops, I was too fast upgrading... luatex fails to produce format
>> files
>> on my system:
>>
>> luatex --version
>> This is LuaTeX, Version snapshot-
On Wed, 05 Dec 2007 15:40:50 -0700, Thomas A. Schmitz
<[EMAIL PROTECTED]> wrote:
> Oops, I was too fast upgrading... luatex fails to produce format files
> on my system:
>
> luatex --version
> This is LuaTeX, Version snapshot-0.20.0-2007120515
>
> luatools --ini --compile cont-en
>
> LuaTools |
Oops, I was too fast upgrading... luatex fails to produce format files
on my system:
luatex --version
This is LuaTeX, Version snapshot-0.20.0-2007120515
luatools --ini --compile cont-en
LuaTools | creating initialization file cont-en
LuaTools | using library path : /usr/local/texlive/texmf-loc
Christopher Creutzig wrote:
> Hans Hagen wrote:
>
>
>> texmfstart --verbose --unix --stubpath= --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 wrote:
> texmfstart --verbose --unix --stubpath= --make all
That is a cool feature. But it does not set executable bits on the
stubs yet, could you fix that?
Regards,
Christopher
___
ntg-context mailing list
ntg-context@ntg.nl
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 nee
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?
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)
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.
> >
> >
Christopher Creutzig wrote:
> Hans Hagen wrote:
>
>
>>> Same for me. The problem is that in line 113, we have
>>> .ge5r�
>>> in Latin-1 encoding, but XeTeX tries reading the file in UTF-8.
>>>
>
>
>> how old is your context
>>
>
> Indeed, that was stone age: 2006.05.08 12:59 -
Hans Hagen wrote:
>> Same for me. The problem is that in line 113, we have
>> .ge5rö
>> in Latin-1 encoding, but XeTeX tries reading the file in UTF-8.
> how old is your context
Indeed, that was stone age: 2006.05.08 12:59 - more than five days
old. :-)
> the latest version uses utf patte
Christopher Creutzig wrote:
>> (/usr/local/teTeX/share/texmf.local/tex/context/patterns/lang-de.pat
>> ! Bad \patterns.
>> \unknownchar ->{
>> \hbox {\vrule \!!width .5em\!!height 1ex\!!depth
>> \zeropoint }}
>> l.114 .ge
>> s6
>> ?
>
> Same for me. The problem is that i
On 5/13/06, Christopher Creutzig <[EMAIL PROTECTED]> wrote:
Still, XeConTeXt does not work as expected in the current version:Hi Christopher,I tried the file you suggest with the latest version of ConTeXt and generated a new XeConTeXt (ConTeXt ver:
2006.05.11 10:30 fmt: 2006.5.13, on MacOS X 1
Otared KAVIAN wrote:
sudo texexec --make --xtx en
(/usr/local/teTeX/share/texmf.local/tex/context/patterns/lang-de.pat
! Bad \patterns.
\unknownchar ->{
\hbox {\vrule \!!width .5em\!!height 1ex\!!depth \zeropoint }}
l.114 .ge
s6
?
Same for me. The problem is that
Johannes Graumann wrote:
> Hans Hagen wrote:
>
>
>> \defineXMLenvironment
>>[document]
>>{\starttext}
>>{\stoptext}
>>
>> \starttext
>>
>> \startXMLdata
>>
>> \stopXMLdata
>>
>> \stoptext
>>
>
> You catch my folly as usually. Thanks. While I get the solution above to
> work,
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}
>>
>> \s
Hans Hagen wrote:
> \defineXMLenvironment
>[document]
>{\starttext}
>{\stoptext}
>
> \starttext
>
> \startXMLdata
>
> \stopXMLdata
>
> \stoptext
You catch my folly as usually. Thanks. While I get the solution above to
work, the alternative 'ruby
~/texmf/scripts/context/ruby/texe
On May 11, 2006, at 17:16, Hans Hagen wrote:
> Gerben Wierda wrote:
>>> btw, doesn't gwtex set the TEXMFCNF env variable?
>>>
>>
>> It does not get a useful value.
>>
>> TEXMFCNF is defined at compile-time and its setting in a texmf.cnf
>> file is
>> ignored for obvious reasons. The compiled-in v
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
>>
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
>>
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
> {\sho
Gerben Wierda wrote:
>> btw, doesn't gwtex set the TEXMFCNF env variable?
>>
>
> It does not get a useful value.
>
> TEXMFCNF is defined at compile-time and its setting in a texmf.cnf file is
> ignored for obvious reasons. The compiled-in version shows my compile
> environment which differs fr
> btw, doesn't gwtex set the TEXMFCNF env variable?
It does not get a useful value.
TEXMFCNF is defined at compile-time and its setting in a texmf.cnf file is
ignored for obvious reasons. The compiled-in version shows my compile
environment which differs from the install environment on people's s
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
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
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
Gerben Wierda wrote:
> On May 10, 2006, at 19:13, Hans Hagen wrote:
>
>
>> 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 mons
nico wrote:
> On Thu, 11 May 2006 00:11:47 +0200, Thomas A. Schmitz
> <[EMAIL PROTECTED]> 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 beh
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
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/
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, Co
On May 10, 2006, at 19:13, Hans Hagen wrote:
> 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
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
On Thu, 11 May 2006 00:11:47 +0200, Thomas A. Schmitz
<[EMAIL PROTECTED]> 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
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
TeX
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 o
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
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/
>
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/
>
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 ou
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/script
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//:
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 compl
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 complet
Dear all,
After upgrading to the latest release (that is TeXExec 5.4.3, and
ConTeXt ver: 2006.05.08 12:59 fmt: 2006.5.9 int: english mes:
english), when I tried to generate the format with XeTeX (that is to
generate XeConTeXt), with the command
sudo texexec --make --xtx en
I get the folllowi
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.
\par
l.13
Can't
nico wrote:
> On Tue, 09 May 2006 17:16:38 +0200, Hans Hagen <[EMAIL PROTECTED]> wrote:
>
>
>>> #ENV['TEXFONTMAPS'] =
>>> ".;\$TEXMF/fonts/map/{#{backend},pdftex,dvips,}//"
>>>
>> i wonder why this does not work
>>
>
> Unix likes column separator (and often cannot stand
On Tue, 09 May 2006 17:16:38 +0200, Hans Hagen <[EMAIL PROTECTED]> 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 ':' i
nico wrote:
> On Tue, 09 May 2006 15:11:23 +0200, Hans Hagen <[EMAIL PROTECTED]> 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
>>
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
---
On Tue, 09 May 2006 15:11:23 +0200, Hans Hagen <[EMAIL PROTECTED]> 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
On Tue, 09 May 2006 15:11:23 +0200, Hans Hagen <[EMAIL PROTECTED]> wrote:
> 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 probl
On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen <[EMAIL PROTECTED]> 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)?
Rega
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.
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
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
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
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 hy
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 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/r
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 sys
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 sys
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 mea
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
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
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 el
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 exec
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 (mo
Thomas A. Schmitz wrote:
> On Feb 1, 2006, at 6:37 PM, VnPenguin wrote:
>
>>Which commands have you used for updating ?
>>I follow the page http://wiki.contextgarden.net/TeTeX_3.0_installation
>>, it works perfectly for me.
>
>
>
> No, that's not the point, updating works. I just see that in
On Feb 1, 2006, at 9:07 PM, Thomas A. Schmitz wrote:
> No, that's not the point, updating works. I just see that in my
> $HOMETEXMF, I now have a directory web2c/pdfetex where format files
> are stored. This directory has been created on Jan 25, at one of the
> latest updates. I haven't changed m
On Feb 1, 2006, at 6:37 PM, VnPenguin wrote:
> Which commands have you used for updating ?
> I follow the page http://wiki.contextgarden.net/TeTeX_3.0_installation
> , it works perfectly for me.
No, that's not the point, updating works. I just see that in my
$HOMETEXMF, I now have a directory
On 2/1/06, Thomas A. Schmitz <[EMAIL PROTECTED]> wrote:
>
> Just a quick question about the new release(s): I've seen that
> formats are now installed in $HOMETEXMF instead of $TEXMFLOCAL. Is
> there a reason for this change, and is it possible to have them
> installed in the old place? I preferred
Thomas A. Schmitz wrote:
>
> Just a quick question about the new release(s): I've seen that
> formats are now installed in $HOMETEXMF instead of $TEXMFLOCAL. Is
> there a reason for this change, and is it possible to have them
> installed in the old place? I preferred that way because it k
On Jan 31, 2006, at 7:46 PM, Taco Hoekwater wrote:
>
> On the subject of fixes:
>
> Hans' new ConTeXt release is now available for download, and it
> includes fixes for \eqalign and \startalign. The release notes
> are here:
>
>http://wiki.contextgarden.net/Context_2006.01.31
>
> I'll do a fo
On the subject of fixes:
Hans' new ConTeXt release is now available for download, and it
includes fixes for \eqalign and \startalign. The release notes
are here:
http://wiki.contextgarden.net/Context_2006.01.31
I'll do a formal announcement and CTAN upload tomorrow.
Cheers, taco
Matthias
Adam Lindsay wrote:
I can do a release of these fonts, once we figure out a few things:
1) what to call this family (optima? optima-nova? classico?),
2) how to package this up for people, and
3) where to put it.
just use 'classico'
optima and optima-nova are real different (hermann zapf exp
Thanks from me, too, to Taco for the change summary...
I notice this:
>new typescript: optima (uses optima-nova & palatino & lmtt)
Which is cool, but there's a free URW Optima clone available ("URW-
Classico"), that potentially makes Optima available to everyone. It's
slightly "buggy" as a font,
Hi all,
Hans has issued a new release of ConTeXt yesterday (2005.01.13).
Highlights:
* The distribution now contains Taco's bib module and related files
* The TeXShow program now uses the XML versions of the interface
definition files, the .tws variants have been removed
* Math font definitions (
Hi Hans.
I just noticed this morning in your enco-uc (also appears in the new
release) that the following is outside the start/stopencoding, and
therefore causes some Bad Things (looking for UnicodeRegular20) if people
use language settings:
\stopencoding
\definecharacter endash {\uchar
93 matches
Mail list logo
