Wolfgang Schuster wrote:
Hi Hans,
from syst-ini.tex:
\chardef\plusseven = 6
\chardef\pluseight = 6
\chardef\plusnine = 6
yeah, we introduce a new numbering system -)
-
Taco Hoekwater writes:
> Corin Royal Drummond wrote:
>> Many have voiced the same complaint. I understand that Hans and every
>> one are occupied with building MKIV (aka LuaTeX), and that documentation
>> is not their highest priority. There's the wiki, the wonderfully active
>> mailing list, a
Hi,
can the number rounding commands (interger/onedigit/...rounding) commands
be done with Lua in MkIV, the TeX version fails on big numbers.
Wolfgang
___
If your question is of interest to others as well, please add
On Fri, Mar 20, 2009 at 11:11 AM, Wolfgang Schuster
wrote:
> Hi,
>
> can the number rounding commands (interger/onedigit/...rounding) commands
> be done with Lua in MkIV, the TeX version fails on big numbers.
a bit off topic,just to store this link
What Every Scientist Should Know About Floating
Hi Hans,
can you add command which will print the name (e.g. LuaTeX, pdfTeX ...)
and version (e.g. 0.36.0) of the current used TeX engine.
Wolfgang
___
If your question is of interest to others as well, please add an
Wolfgang Schuster schrieb:
Hi Hans,
can you add command which will print the name (e.g. LuaTeX, pdfTeX ...)
and version (e.g. 0.36.0) of the current used TeX engine.
Hi Wolfgang,
I think this should better be done by a command in pdftex/luatex. The
'Procucer' key is already set by pdftex/
Peter Rolf wrote:
Hi Wolfgang,
I think this should better be done by a command in pdftex/luatex.
No. All engines have multiple version commands already, I see
absolutely no need for yet another version-related primitive.
Best wishes,
Taco
This is the reply to my letter sent to Boguslav Yatskovsky. He allowed
me to share it with ConTeXt users and developers. I believe it will be
of some interest.
I'm your namesake, from Ukraine :)
:-))
I
Wolfgang Schuster wrote:
On Fri, Mar 20, 2009 at 1:13 PM, Taco Hoekwater wrote:
Peter Rolf wrote:
Hi Wolfgang,
I think this should better be done by a command in pdftex/luatex.
No. All engines have multiple version commands already, I see
absolutely no need for yet another version-related pr
Hi,
when I use enco-fde or -ffr (others not tried) I get an error with the beta
from 19.3.:
%coding: utf-8
\enableregime[utf]
\mainlanguage[de]
\useencoding[fde]
% \useencoding[ffr]
\starttext
blabla
\stoptext
ConTeXt ver: 2009.03.19 10:04 MKII fmt: 2009.3.the\normalday int:
english/e
ngl
On Fri, Mar 20, 2009 at 1:13 PM, Taco Hoekwater wrote:
> Peter Rolf wrote:
>>
>> Hi Wolfgang,
>>
>> I think this should better be done by a command in pdftex/luatex.
>
> No. All engines have multiple version commands already, I see
> absolutely no need for yet another version-related primitive.
I
On Fri, Mar 20, 2009 at 1:30 PM, Hans Hagen wrote:
> ok, i added
>
> \def\currenttexenginename
> {\ifcase\texengine\or pdf\or Xe\or Lua\else no\fi\TeX}
Can you also add \currenttexengineversion?
Wolfgang
___
If your
Wolfgang Schuster wrote:
On Fri, Mar 20, 2009 at 1:30 PM, Hans Hagen wrote:
ok, i added
\def\currenttexenginename
{\ifcase\texengine\or pdf\or Xe\or Lua\else no\fi\TeX}
Can you also add \currenttexengineversion?
hm, that would be a pretty inconsistent thing, so it needs some testing
Hans
Hi
today , while writing some code I have made a mistake like this
\input combine[file=depliant-block.pdf]
instead of
\input combine
(I have combine.tex in my path of course)
After a while I have thought :
"Is it possibile to implement this (as a macro) in mkiv ?"
I think yes, but I'm not sure
luigi scarso wrote:
Hi
today , while writing some code I have made a mistake like this
\input combine[file=depliant-block.pdf]
instead of
\input combine
(I have combine.tex in my path of course)
After a while I have thought :
"Is it possibile to implement this (as a macro) in mkiv ?"
parsing
Am 20.03.2009 um 14:11 schrieb luigi scarso:
Hi
today , while writing some code I have made a mistake like this
\input combine[file=depliant-block.pdf]
instead of
\input combine
(I have combine.tex in my path of course)
After a while I have thought :
"Is it possibile to implement this (as a m
On Fri, Mar 20, 2009 at 2:17 PM, Wolfgang Schuster
wrote:
>
> Am 20.03.2009 um 14:11 schrieb luigi scarso:
>
>> Hi
>> today , while writing some code I have made a mistake like this
>> \input combine[file=depliant-block.pdf]
>> instead of
>> \input combine
>>
>> (I have combine.tex in my path of c
Am 20.03.2009 um 14:19 schrieb luigi scarso:
And what is this supposed to do?
save the world ?
:-X
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist :
On Fri, Mar 20, 2009 at 2:15 PM, Hans Hagen wrote:
> luigi scarso wrote:
>>
>> Hi
>> today , while writing some code I have made a mistake like this
>> \input combine[file=depliant-block.pdf]
>> instead of
>> \input combine
>>
>> (I have combine.tex in my path of course)
>>
>> After a while I have
luigi scarso wrote:
indeed, or \loadfile[...] depending on your needs
there is no \loadfile but there are many other variants -)
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 |
2009/3/20 Hans Hagen :
> luigi scarso wrote:
>
>>> indeed, or \loadfile[...] depending on your needs
>
>
> there is no \loadfile but there are many other variants -)
good , so I wll think to def
\def\Loadfile[#1][...]{..}
--
luigi
__
Thomas Floeren wrote:
Hi,
when I use enco-fde or -ffr (others not tried) I get an error with the beta
from 19.3.:
%coding: utf-8
\enableregime[utf]
\mainlanguage[de]
\useencoding[fde]
% \useencoding[ffr]
\starttext
blabla
\stoptext
ok, fixed (keep in mind that in mkiv we no longer have this
Yanrui Li wrote:
2009/3/17 Hans Hagen :
Hi,
In the process of a major cleanup and code split I uploaded a beta. Some
important changes are:
- initialization code is ready for upcoming luatex
- language files have been cleaned up
- core- is renamed to tabl-
- several changes in file names and s
On Fri, Mar 20, 2009 at 2:10 PM, Hans Hagen wrote:
>> Can you also add \currenttexengineversion?
>
> hm, that would be a pretty inconsistent thing, so it needs some testing
How about:
\def\currenttexengineversion
{\ifcase\texengine
\or\number\numexpr\pdftexversion/100.\modulonumber{100}\pd
On Fri, 20 Mar 2009, Hans Hagen wrote:
Yanrui Li wrote:
2009/3/17 Hans Hagen :
Hi,
In the process of a major cleanup and code split I uploaded a beta. Some
important changes are:
- initialization code is ready for upcoming luatex
- language files have been cleaned up
- core- is renamed to ta
Wolfgang Schuster wrote:
On Fri, Mar 20, 2009 at 2:10 PM, Hans Hagen wrote:
Can you also add \currenttexengineversion?
hm, that would be a pretty inconsistent thing, so it needs some testing
How about:
\def\currenttexengineversion
{\ifcase\texengine
\or\number\numexpr\pdftexversion/10
Aditya Mahajan wrote:
Same problem with \hat. Both \hat and \tilde work fine with cambria and
asana (asana gives funny wide accents). Non otf math fonts---lm, times,
and palatino---give wrong behaviour. Antykwa and iwona do not give an
accent at all, but that may be due to missing virual font.
On Fri, Mar 20, 2009 at 6:57 PM, Hans Hagen wrote:
> did you notice that your pdftex is a future version?
Why?
terminal: This is pdfTeX, Version 3.1415926-1.40.9 (Web2C 7.5.7)
document: 1.40.9
Wolfgang
___
If your
Hi,
this weeks beta ...
-- a couple of bug fixes, some are still pending
-- the context script can recognize files for mkii (first line
directive) and listens to --pdftex and --xetex; it still calls texexec
but this method can replace the texmfstart call (mtxrun is faster); it
also permits i
Wolfgang Schuster wrote:
On Fri, Mar 20, 2009 at 6:57 PM, Hans Hagen wrote:
did you notice that your pdftex is a future version?
Why?
terminal: This is pdfTeX, Version 3.1415926-1.40.9 (Web2C 7.5.7)
document: 1.40.9
well, the version macro reported version 2 (i run version 1.50) because
Hans Hagen schrieb:
Peter Rolf wrote:
Hi,
my testing yesterday was only limited to a very small test file
(overprinting test). i had no problems with that, but any approach
with one of my graphics directly ends with
! Undefined control sequence.
l.1 \abortinputifdefined
oops, is syst-gen.t
Aditya Mahajan wrote:
Hi Hans,
Something has changed recently with the mkii color model, due to which
page backgrounds do not change. (I am guessing that this is a grouping
issue, but then colors are like a black box to me). Consider the
following example
\setuppapersize[S6][S6]
\setupcolor
On Fri, Mar 20, 2009 at 7:30 PM, Peter Rolf wrote:
> Hans Hagen schrieb:
>>
>> Peter Rolf wrote:
>>>
>>> Hi,
>>>
>>> my testing yesterday was only limited to a very small test file
>>> (overprinting test). i had no problems with that, but any approach with one
>>> of my graphics directly ends with
Peter Rolf wrote:
The interesting thing is, that it works after the third run. After you
delete all temporary files (tuo,tui) you need again three runs to get a
working pdf. All I can see is, that there are multiple {docushade} (one
per page) entries (donno the details).
Tested with beta from
Hans Hagen schrieb:
Peter Rolf wrote:
The interesting thing is, that it works after the third run. After
you delete all temporary files (tuo,tui) you need again three runs to
get a working pdf. All I can see is, that there are multiple
{docushade} (one per page) entries (donno the details).
On Fri, 20 Mar 2009, Hans Hagen wrote:
Aditya Mahajan wrote:
Hi Hans,
Something has changed recently with the mkii color model, due to which page
backgrounds do not change. (I am guessing that this is a grouping issue,
but then colors are like a black box to me). Consider the following examp
36 matches
Mail list logo
