Aditya Mahajan wrote:
> On Tue, 9 May 2006, Aditya Mahajan wrote:
>
>
>>--batch --interaction=batch does not always process file in batch
>>mode, while internally running mp.
>>
>>\starttext
>>\startMPpage
>> draw path ;
>>\stopMPpage
>>\stoptext
>>
>>texmfstart texexec.rb --batch --interaction=
--
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
[EMAIL PROTECTED] wrote:
> The line in scripts/context/ruby/graphics/gs.rb with -dSAFER needs a
> 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 spa
[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-cont
Aditya Mahajan wrote:
> Hi Hans,
>
> 1. Allow \definematrix and \definemathcases to have a parameter
> displaystyle or textstyle. Right now, everything is in textstyle.
> ...
> I don't know which syntax is better displaystyle=on|off (yes|no) or
> [mathstyle=display|text].
I vote for [mathstyl
hmm, on Thu, May 18, 2006 at 08:48:23AM +0200, Taco Hoekwater said that
> The mathematical center of the line is not necesarily the
> optical center, so a somewhat more correct approach would
> put all the stuff in an \hbox and then compute manually
> how far it has to drop down.
i haven't used la
frantisek holop wrote:
> hmm, on Thu, May 18, 2006 at 08:48:23AM +0200, Taco Hoekwater said that
>
>> The mathematical center of the line is not necesarily the
>> optical center, so a somewhat more correct approach would
>> put all the stuff in an \hbox and then compute manually
>> how far it ha
frantisek holop wrote:
> i've tried the old style numeral but i didn't like it.
> by "keeping the same vertical alignment ratio" do you
> mean something like \raise?
Take the 'normal' 7 in the 'normal' tf size, but place it
as if it was an old-style numeral (using something like
\lower2pt\hbox{
hmm, on Thu, May 18, 2006 at 11:57:47AM +0200, Hans Hagen said that
> > i haven't used latex for quite some time now, so i can't
> > recall how problematic it was to accomplish something like this,
> > but i find it interesting that there is no easy approach to this.
> >
> there probably is, so
Hello,
on the [tex-fonts] mailing list there was a recent discussion of
people putting effort into enabling proper encoding to support
typesetting of Lithuanian (in LaTeX). Before they start creating and
using yet another encoding (incompatible with others and not shipped
with any standard TeX dis
frantisek holop wrote:
> hmm, on Thu, May 18, 2006 at 11:57:47AM +0200, Hans Hagen said that
>
>>> i haven't used latex for quite some time now, so i can't
>>> recall how problematic it was to accomplish something like this,
>>> but i find it interesting that there is no easy approach to this.
>
Mojca Miklavec wrote:
> Hello,
>
> on the [tex-fonts] mailing list there was a recent discussion of
> people putting effort into enabling proper encoding to support
> typesetting of Lithuanian (in LaTeX). Before they start creating and
> using yet another encoding (incompatible with others and not
Hello,
I have some troubles with a PNG image, that is not correctly rendered by
context (too small). The difference I've found with another correctly
displayed image is that the file does not contain any resolution unit (but
a pixels/inch default seems reasonable).
Is there a workaround or
nico wrote:
> Hello,
>
> I have some troubles with a PNG image, that is not correctly rendered by
> context (too small). The difference I've found with another correctly
> displayed image is that the file does not contain any resolution unit (but
> a pixels/inch default seems reasonable).
On Thu, 18 May 2006 17:28:42 +0200, Taco Hoekwater <[EMAIL PROTECTED]>
wrote:
> nico wrote:
>> Hello,
>>
>> I have some troubles with a PNG image, that is not correctly rendered by
>> context (too small). The difference I've found with another correctly
>> displayed image is that the file does n
>> {\pdfimageresolution=72 \externalfigure[ch01dia1.png]}
> when you set pdfimageresolution there isn't any unit either, the
> unit is implicit
What about a new pdftex primitive: \pdfimagepixel, which would force
using a unit. Then the above would be done by \pdfimagepixel=1bp
This subject is d
Sanjoy Mahajan wrote:
>>>{\pdfimageresolution=72 \externalfigure[ch01dia1.png]}
>
>>when you set pdfimageresolution there isn't any unit either, the
>>unit is implicit
It is defined to be an integer number of pixels per inch, in the
pdftex manual.
> What about a new pdftex primitive: \pdfimagepi
What's the safe way to make \def's local to a component? I could wrap
each component in a \begingroup..\endgroup but that might do bad
things to the output routine.
-Sanjoy
`Never underestimate the evil of which men of power are capable.'
--Bertrand Russell, _War Crimes in Vietnam_, cha
Sanjoy Mahajan wrote:
> What's the safe way to make \def's local to a component? I could wrap
> each component in a \begingroup..\endgroup but that might do bad
> things to the output routine.
>
\pushmacro\whateveryouwant
ungrouped stuff
\popmacro\whateveryouwant
--
Hi,
For those interested in mathml/openmath ... i've added some support for
openmath -> mathml conversion to the distribution (there is some stuff
in the manual svn repos as well). I dunno how many of you actually have
used openmath. Anyhow, it makes a nice demo of applying ctx job
description
On 5/18/06, Taco Hoekwater <[EMAIL PROTECTED]> wrote:
> > What about a new pdftex primitive: \pdfimagepixel, which would force
> > using a unit. Then the above would be done by \pdfimagepixel=1bp
>
> You can (as always) propose it on the pdftex list, but i personally
> do not see the point. Bear i
When I regenerate the formats on my linux box with the latest release, I
get this error:
language : patterns pl for pl loaded (n=13,e=pl0,m=pl0)
(/usr/share/texmf/tex/generic/hyphen/plhyph.tex
!Improper alphabetic constant.
\else
\utffouruniglph [EMAIL PROTECTED] *([EMAIL P
Thomas A. Schmitz wrote:
> When I regenerate the formats on my linux box with the latest release, I
> get this error:
>
> language : patterns pl for pl loaded (n=13,e=pl0,m=pl0)
> (/usr/share/texmf/tex/generic/hyphen/plhyph.tex
> !Improper alphabetic constant.
>
> \else
> \u
Hans Hagen wrote:
> Thomas A. Schmitz wrote:
>
>>When I regenerate the formats on my linux box with the latest release, I
>>get this error:
>>
>>language : patterns pl for pl loaded (n=13,e=pl0,m=pl0)
>>(/usr/share/texmf/tex/generic/hyphen/plhyph.tex
>>!Improper alphabetic constant.
>>
>>
On May 18, 2006, at 11:53 PM, Hans Hagen wrote:
> seems so, is natural.ctx loaded? (i assume that you use texexec --
> make since i have no clue what fmtutil does)
>
> [patterns are now in utf and i can generate formats in my linux vm
> without problems]
>
> Hans
>
Yes, I use texmfstart texex
I encountered a very strange problem. The very presence of
\definetextbackground changed the meaning of \midaligned (and
\rightaligned). Attached are the minimal example that illustrate the
problem. The first file, nobackground.tex has no background and works
as expected. The second file backgr
> \pushmacro\whateveryouwant
> ungrouped stuff
> \popmacro\whateveryouwant
Thanks, that works. A small example, in case others find it useful:
\starttext
\def\y{outside\par}
\y
\pushmacro\y
\def\y{inside\par}
\y
\popmacro\y
\y
\stoptext
which produces
outside
inside
outside
-Sanjoy
`Never
28 matches
Mail list logo
