Hi,
I uploaded an mkiv and lmtx beta (remake/cache needed).
---
1 spacekerns for own features (experimental)
---
% decouple feature from 'kern' only
\definefontfeature [TestA] [default]
Hi Hans,
Thanks a lot for the new beta and for having fixed the issue with luametatex
binaries.
Everything works great with version 2019.12.06 21:40.
Best regards: OK
> On 6 Dec 2019, at 15:05, Hans Hagen wrote:
>
> On 12/6/2019 1:34 PM, Otared Kavian wrote:
>
>> Is this too old? Is this
On 12/6/2019 1:34 PM, Otared Kavian wrote:
Is this too old? Is this file created during installation or is it contained in
the zip files downloaded from Pragma's site?
Ok, I think that there is some issue with the builder. Mojca, it looks
like there is no binary upload happening after a
Hi again,
I just installed anew lmtx from Pragma website
http://lmtx.pragma-ade.nl/install-lmtx/context-osx-64.zip
and I have the same problem: the format cannot be made.
Looking at luametatex in a Terminal window, I get
-rwxr--r-- 1 kavian staff 2.7M Dec 6 13:15
On 12/5/2019 8:28 PM, Otared Kavian wrote:
Hi Hans,
Thanks for the new features and the new release.
I could download the new installer for MacOS which installs the latest version
but it cannot make the formats ending with the error message which I copy below.
Best regards: OK
PS: this is
Otared Kavian schrieb am 06.12.2019 um 04:23:
Dear Hans,
The problem I described in my previous message comes indeed from
\defineexpansion which is not defined.
Upon commenting out the lines 95--98 in the file « hand-ini.mkxl » that is the
four lines:
\defineexpansion
[\c!step=1,
Hello,
** Otared Kavian [2019-12-06 04:23:28 +0100]:
> Dear Hans,
> The problem I described in my previous message comes indeed from
> \defineexpansion which is not defined. Upon commenting out the lines
> 95--98 in the file « hand-ini.mkxl » that is the four lines:
> \defineexpansion
>
Dear Hans,
The problem I described in my previous message comes indeed from
\defineexpansion which is not defined.
Upon commenting out the lines 95--98 in the file « hand-ini.mkxl » that is the
four lines:
\defineexpansion
[\c!step=1,
\c!stretch=40,
\c!shrink=20]
I could remake the
Hi Hans,
Thanks for the new features and the new release.
I could download the new installer for MacOS which installs the latest version
but it cannot make the formats ending with the error message which I copy below.
Best regards: OK
PS: this is the error message when installing:
tex error
Hi,
I uploaded a new lmtx beta. Hopefully the installer works ok as I redid
some of the "zip" related code (simpler, smaller binary too). FWIW, the
luametatex codebase is now pretty close to okay, but of course there can
be bugs, but nothing thay can't be solved fast.
Given some earlier
On 11/13/19 9:34 AM, Hans Hagen wrote:
> On 11/12/2019 10:20 PM, Pablo Rodriguez wrote:
>
>> LMTX has no problems with this. Could you fix this in MkIV?
>
> Can you check again?
Many thanks for your fast fix, Hans.
Everything works fine now.
Pablo
--
http://www.ousia.tk
On 11/12/2019 10:20 PM, Pablo Rodriguez wrote:
LMTX has no problems with this. Could you fix this in MkIV?
Can you check again?
Hans
-
Hans Hagen | PRAGMA ADE
On 11/12/19 7:50 PM, Hans Hagen wrote:
> Hi,
>
> I uploaded a new beta. Apart from some fixes, the main change in lmtx is
> that on windows most (a few exceptions) of the mechanisms that interface
> to the operating system support the internal wide character model which
> should make the lot more
Hi,
I uploaded a new beta. Apart from some fixes, the main change in lmtx is
that on windows most (a few exceptions) of the mechanisms that interface
to the operating system support the internal wide character model which
should make the lot more robust for file names, environment variables,
Hi,
I uploaded a new beta. Some might have noticed that stepwise some font
support has been redone. We're talking of lmtx only here. For instance
low level handling of color fonts as used for emoji but there are also
other (often incomplete) fonts out there (overlay, png, svg) has become
(on
Hi,
I uploaded a new beta. There is a new command \setextrafontkerns which
is described in the fonts-mkiv manual section 8.12. probably not that
useful but kind of fun.
Hans
-
Hans
On 12/18/2015 9:38 AM, Jan U. Hasecke wrote:
Hi all,
after updating to the new beta this doesn't work anymore.
\definepagebreak
[pagebreak:chapter]
[yes, header, footer]
\setuphead
[chapter,title]
[page=pagebreak:chapter]
\starttext
\chapter{Lorem ipsum}
\input tufte
Hi all,
after updating to the new beta this doesn't work anymore.
\definepagebreak
[pagebreak:chapter]
[yes, header, footer]
\setuphead
[chapter,title]
[page=pagebreak:chapter]
\starttext
\chapter{Lorem ipsum}
\input tufte
\chapter{Dolor sit}
\input tufte
\stoptext
TIA
On 12/18/2015 12:53 PM, Otared Kavian wrote:
Hi Hans,
I just installed the new beta for testing purposes. In math mode the
exponennts, indices, and punctuations do not work properly as you may see in
the attached files.
ok, an engine bug (something goes out of range) (math mode active
On 19 November 2015 at 22:29, Mojca Miklavec wrote:
> On 17 November 2015 at 11:53, Hans Hagen wrote:
>> Hi,
>>
>> There is a new beta coming but it goes in sync with a new release of luatex
>> (0.85). As there have been some fundamental changes the macros and engine
>> need to be updated in sync
On 11/20/2015 8:03 AM, Schmitz Thomas A. wrote:
On 19 Nov 2015, at 22:45, Pablo Rodriguez wrote:
I have just updated and compilation from XML sources works fine again
(at least with the file I tested ;-)).
The problem with xml entities persists. They are not processed, but
On 17 November 2015 at 11:53, Hans Hagen wrote:
> Hi,
>
> There is a new beta coming but it goes in sync with a new release of luatex
> (0.85). As there have been some fundamental changes the macros and engine
> need to be updated in sync so when something goes wrong with an update, be
> patient
On 11/19/2015 10:29 PM, Mojca Miklavec wrote:
> On 17 November 2015 at 11:53, Hans Hagen wrote:
>> Hi,
>>
>> There is a new beta coming but it goes in sync with a new release of luatex
>> (0.85). As there have been some fundamental changes the macros and engine
>> need to be updated in sync so
> On 19 Nov 2015, at 22:45, Pablo Rodriguez wrote:
>
> I have just updated and compilation from XML sources works fine again
> (at least with the file I tested ;-)).
The problem with xml entities persists. They are not processed, but printed as
is. I sent an example on Oct. 13.
Hi,
There is a new beta coming but it goes in sync with a new release of
luatex (0.85). As there have been some fundamental changes the macros
and engine need to be updated in sync so when something goes wrong with
an update, be patient and wait till binaries are in sync with macros for
your
Hi,
If you compile the following file with new beta, the placement of the table
and the figure is incorrect.
Thank you,
Fabrice
\definefloat
[recipe]
[figure]
\setupfloat
[recipe]
[default={right,none}]
\startsetups[table:initialize]
Hi,
If you compile the following file with new beta, the placement of the table
and the figure is incorrect.
Thank you,
Fabrice
\definefloat
[recipe]
[figure]
\setupfloat
[recipe]
[default={right,none}]
\startsetups[table:initialize]
Hi,
I uploaded a new beta. The reported bidi issue with footnotes had to do
with some unhboxing that doesn't play well with the bidi analyzers, i.e.
in case of
new text unhboxed done text new text
the done text is already treated. I now use a slightly different
implementation.
I also
On 7/12/2015 12:22 AM, Lukáš Procházka wrote:
Hello,
\pushbackground seems to be broken in the last beta - this doesn't
compile (but it did till now):
works ok here ... also, that code hasn't changed
-
On 07/11/2015 10:53 AM, Hans Hagen wrote:
On 7/11/2015 7:17 AM, Pablo Rodriguez wrote:
[...]
I’m afraid that newotf crashes with this sample:
[...]
define crashes ... i donwloaded the font, ran mtxrun --generate and
remade the font database and this works:
[GFS Didot Classic]
I
Pablo Rodriguez schrieb:
On 07/11/2015 12:57 PM, Wolfgang Schuster wrote:
[...]
The font [1,2] works for me without problems.
[1] http://www.greekfontsociety.gr/pages/en_typefaces20th.html
[2] http://www.greekfontsociety.gr/pages/en_typefaces19th.html
They all work fine for me until I load:
On 07/11/2015 12:57 PM, Wolfgang Schuster wrote:
[...]
The font [1,2] works for me without problems.
[1] http://www.greekfontsociety.gr/pages/en_typefaces20th.html
[2] http://www.greekfontsociety.gr/pages/en_typefaces19th.html
They all work fine for me until I load:
\usemodule[newotf]
On 7/11/2015 7:17 AM, Pablo Rodriguez wrote:
On 07/11/2015 01:33 AM, Hans Hagen wrote:
On 7/10/2015 5:05 PM, Thomas A. Schmitz wrote:
[...]
resolversmodules 'newotf' is not found
i had a typo in the zip maker ... that file is missing (the rest is there)
(i've send the file send in
Pablo Rodriguez schrieb:
On 07/11/2015 01:33 AM, Hans Hagen wrote:
On 7/10/2015 5:05 PM, Thomas A. Schmitz wrote:
[...]
resolvers modules 'newotf' is not found
i had a typo in the zip maker ... that file is missing (the rest is there)
(i've send the file send in another mail to list)
On 07/11/2015 01:26 PM, Wolfgang Schuster wrote:
[...]
Do you get the same problem when you use the font as main font?
\usemodule[newotf]
\definefontfamily[mainface][rm][GFS Didot]
\setupbodyfont[mainface]
\starttext
αβγ {\bf αβγ}
\stoptext
Yes, I do.
Pablo
--
On 07/11/2015 02:02 PM, Pablo Rodriguez wrote:
Do you get the same problem when you use the font as main font?
\usemodule[newotf]
\definefontfamily[mainface][rm][GFS Didot]
\setupbodyfont[mainface]
\starttext
αβγ {\bf αβγ}
\stoptext
Yes, I do.
Pablo
Both Wolfgang's file and your
Pablo Rodriguez schrieb:
On 07/11/2015 02:32 PM, Wolfgang Schuster wrote:
[...]
1. Does the same happen with other fonts in this folder.
2. What happens when you put the fonts in your local TeX directory (or
texmf-fonts/fonts/opentype of your context installation).
Many thanks for your
On 07/11/2015 05:23 PM, Wolfgang Schuster wrote:
[...]
It works for me when I use the Postscript files from the txfonts
package, you need the following files:
Many thanks for your reply, Wolfgang.
I wanted to avoid using PostScript files, but it seems that I have to
use them.
Many thanks
On 07/11/2015 02:32 PM, Wolfgang Schuster wrote:
[...]
1. Does the same happen with other fonts in this folder.
2. What happens when you put the fonts in your local TeX directory (or
texmf-fonts/fonts/opentype of your context installation).
Many thanks for your replies, Thomas and
On 7/11/2015 1:15 PM, Pablo Rodriguez wrote:
On 07/11/2015 10:53 AM, Hans Hagen wrote:
On 7/11/2015 7:17 AM, Pablo Rodriguez wrote:
[...]
I’m afraid that newotf crashes with this sample:
[...]
define crashes ... i donwloaded the font, ran mtxrun --generate and
remade the font database and
On 7/11/2015 4:27 PM, Pablo Rodriguez wrote:
On 07/11/2015 02:32 PM, Wolfgang Schuster wrote:
[...]
1. Does the same happen with other fonts in this folder.
2. What happens when you put the fonts in your local TeX directory (or
texmf-fonts/fonts/opentype of your context installation).
Many
Hello,
\pushbackground seems to be broken in the last beta - this doesn't compile (but
it did till now):
\defineheadalternative
[PartAlt]
[renderingsetup=set:PartPage]
\startsetups[set:PartPage]
\startmakeup[mu:PartPage]
\white
\headnumbercontent
\blank[2*big]
On 7/10/2015 7:13 PM, Pablo Rodriguez wrote:
On 07/10/2015 05:05 PM, Thomas A. Schmitz wrote:
On 07/09/2015 03:39 PM, Hans Hagen wrote:
Of course there will be bugs although the test suite runs without
crashing. I will use the new code on my machine but you can test it with:
On 7/10/2015 5:05 PM, Thomas A. Schmitz wrote:
On 07/09/2015 03:39 PM, Hans Hagen wrote:
Of course there will be bugs although the test suite runs without
crashing. I will use the new code on my machine but you can test it with:
\usemodule[newotf]
before \starttext (or in cont-loc.mkiv).
Hi
On 07/11/2015 01:33 AM, Hans Hagen wrote:
On 7/10/2015 5:05 PM, Thomas A. Schmitz wrote:
[...]
resolversmodules 'newotf' is not found
i had a typo in the zip maker ... that file is missing (the rest is there)
(i've send the file send in another mail to list)
Many thanks for the
On 07/09/2015 03:39 PM, Hans Hagen wrote:
Of course there will be bugs although the test suite runs without
crashing. I will use the new code on my machine but you can test it with:
\usemodule[newotf]
before \starttext (or in cont-loc.mkiv).
Hi Hans,
did the new font mechanism really make
On 07/10/2015 05:05 PM, Thomas A. Schmitz wrote:
On 07/09/2015 03:39 PM, Hans Hagen wrote:
Of course there will be bugs although the test suite runs without
crashing. I will use the new code on my machine but you can test it with:
\usemodule[newotf]
before \starttext (or in cont-loc.mkiv).
Hi Hans,
the new beta, 2015.07.10 00:05, messes up punctuation (.:,;) for some fonts
like Calluna. This happens with and without \usemodule[newotf]:
\definefontfamily [default] [rm] [Calluna]\setupbodyfont [default]
\starttext
This is not, as it should be; Email: em...@example.net\stoptext
Hi,
I uploaded a new beta. As a prelude to some updates / improvements in
the font handling an experimental new otf fontloader/handler is present.
This one is not used by default but will likely replace the current one
(only when it has been tested enough). At that time also some other
Note that the || in tufte does not get handled transparently.
Alan
On Mon, 15 Jun 2015 00:21:56 +0200
Mojca Miklavec mojca.miklavec.li...@gmail.com wrote:
On Sat, Jun 13, 2015 at 10:00 AM, Hans Hagen wrote:
Hi,
I uploaded a beta. The most significant (visible) change is in the
way mp
On 6/15/2015 9:22 AM, Alan BRASLAU wrote:
Note that the || in tufte does not get handled transparently.
indeed ... not that i worry too much about those special catcodes now
(something i'll look at when i need it)
Hans
-
On Sat, Jun 13, 2015 at 10:00 AM, Hans Hagen wrote:
Hi,
I uploaded a beta. The most significant (visible) change is in the way mp
handles outlines. Here are some examples:
% outlinetext (text) transformations ;
% outlinetext.d (text) (draw options) transformations ;
% outlinetext.f
Hi,
I uploaded a beta. The most significant (visible) change is in the way
mp handles outlines. Here are some examples:
% outlinetext (text) transformations ;
% outlinetext.d (text) (draw options) transformations ;
% outlinetext.f (text) (fill options) transformations ;
% outlinetext.b
Hi,
I uploaded a new beta. This is the last before a current that goes on tl
2015.
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
On 5/15/2015 3:58 PM, Pablo Rodriguez wrote:
Is a sample file required?
The files that trigger the bug are rather big and I don’t have the time
right now.
I hope I can elaborate a minimal file this afternoon.
ok, probably only the text around the issue is needed
Hi,
I uploaded a beta ... there is a new feature (for Alan):
\starttext
\chapter{The never ending story}
\section{An ending story}
\in{chapter}[match(complex bibliographies)]
\in{chapter}[match(never ending)]
\in{chapter}[match(ending)]
\in{chapter}[match(chapter:never ending)]
Hi,
I uploaded a new beta. This one has some new font code
- the generic code now uses the context code as of 2014-12-01
- that code uses a slightly faster access method
- it works in plain but for latex the wrapper might need to be adjusted
(as the base pass is now integrated)
The context
Hi,
the first beta after the meeting:
There are some changes to export and epub generation (will be explained
in a manual). The most important is that there has been some
improvements of the math export (esp fences and stackers). More will
follow. The export now happens in a subpath. The
Hi,
I uploaded a new beta. Apart from the usual 'improvements' and a few
'fulfilled wishes' the main difference is in some optimized register
generation code: in the crited project we're dealing with tens of
thousands of different index entries and that gave problems with
luajittex (first of
On 03/07/2014 12:14 PM, Hans Hagen wrote:
Hi,
I uploaded a new beta.
Many thanks for it, Hans.
The following sample worked (partially) with previous beta:
\starttext
\startTEXpage[offset=1em]
``---'' `--'
\stopTEXpage
\stoptext
Many thanks for your help,
Pablo
--
On 03/07/2014 12:14 PM, Hans Hagen wrote:
Hi,
I uploaded a new beta.
Hans,
I’m afraid I have just found another two issues in the new beta.
\setupdirections[bidi=on]
\definefontfamily[mainface][serif][FreeSerif]
\setupbodyfont[mainface]
\starttext
\dorecurse{5}{\index{one}A text in
On 3/7/2014 6:17 PM, Pablo Rodriguez wrote:
On 03/07/2014 12:14 PM, Hans Hagen wrote:
Hi,
I uploaded a new beta.
Hans,
I’m afraid I have just found another two issues in the new beta.
\setupdirections[bidi=on]
\definefontfamily[mainface][serif][FreeSerif]
\setupbodyfont[mainface]
On 3/7/2014 6:17 PM, Pablo Rodriguez wrote:
\setupdirections[bidi=on] seems not to work. Removing the command gives
the same results.
indeed, already for a while i think ... buglet introduced during
optimization a while ago (resulting in not enabling)
Hans
\starttext
foo
\stoptext
! LuaTeX error [string \directlua ]:1: attempt to call field 'resetprevdepth'
(a nil value)
stack traceback:
[string \directlua ]:1: in main chunk.
Marco
signature.asc
Description: Digital signature
On 7/31/2013 10:56 PM, Marco Patzer wrote:
\starttext
foo
\stoptext
! LuaTeX error [string \directlua ]:1: attempt to call field 'resetprevdepth'
(a nil value)
stack traceback:
[string \directlua ]:1: in main chunk.
not here ... maybe spac-ver.lua has not been updated at your end?
On 2013–07–31 Hans Hagen wrote:
On 7/31/2013 10:56 PM, Marco Patzer wrote:
\starttext
foo
\stoptext
! LuaTeX error [string \directlua ]:1: attempt to call field
'resetprevdepth' (a nil value)
stack traceback:
[string \directlua ]:1: in main chunk.
not here ... maybe
On 31 juil. 2013, at 23:43, Marco Patzer home...@lavabit.com wrote:
On 2013–07–31 Hans Hagen wrote:
On 7/31/2013 10:56 PM, Marco Patzer wrote:
\starttext
foo
\stoptext
! LuaTeX error [string \directlua ]:1: attempt to call field
'resetprevdepth' (a nil value)
stack traceback:
On 7/31/2013 11:43 PM, Marco Patzer wrote:
On 2013–07–31 Hans Hagen wrote:
On 7/31/2013 10:56 PM, Marco Patzer wrote:
\starttext
foo
\stoptext
! LuaTeX error [string \directlua ]:1: attempt to call field 'resetprevdepth'
(a nil value)
stack traceback:
[string \directlua ]:1: in main
On 7/16/2013 11:12 AM, Steffen Kram wrote:
Hi all,
ligature seems to fail also with beta from 2013.06.10.
But with the latest beta, pages start numbering from 2:
\starttext
\input knuth
\stoptext
Am I the only one hit by this?
I can confirm this, too. Anyone already tracked
Am 17.07.2013 um 12:23 schrieb Hans Hagen pra...@wxs.nl:
On 7/16/2013 11:12 AM, Steffen Kram wrote:
Hi all,
ligature seems to fail also with beta from 2013.06.10.
But with the latest beta, pages start numbering from 2:
\starttext
\input knuth
\stoptext
Am I the only one hit
Am 17.07.2013 um 12:23 schrieb Hans Hagen pra...@wxs.nl:
On 7/16/2013 11:12 AM, Steffen Kram wrote:
Hi all,
ligature seems to fail also with beta from 2013.06.10.
But with the latest beta, pages start numbering from 2:
\starttext
\input knuth
\stoptext
Am I the only one
Hi all,
ligature seems to fail also with beta from 2013.06.10.
But with the latest beta, pages start numbering from 2:
\starttext
\input knuth
\stoptext
Am I the only one hit by this?
I can confirm this, too. Anyone already tracked that down and has a working fix?
Thanks,
···date: 2013-07-12, Friday···from: Hans Hagen···
Hi,
I uploaded a beta. There are not that many changes. Currently I
develop in a separate branch but it might be that some changes are
reflected in the betas, and hopefully not breaking anything.
There a copy’n’paste mistake in
···date: 2013-07-12, Friday···from: Hans Hagen···
it might be that some changes are
reflected in the betas, and hopefully not breaking anything.
Unhappily, it does. In the generic font loader the new “nuts”
table is a synonym for “nodes”, but it would appear
On 14/07/13 10:53, Philipp Gesang wrote:
···date: 2013-07-12, Friday···from: Hans Hagen···
it might be that some changes are
reflected in the betas, and hopefully not breaking anything.
[...]
Failing example with ligatures:
···date: 2013-07-14, Sunday···from: Pablo Rodríguez···
On 14/07/13 10:53, Philipp Gesang wrote:
···date: 2013-07-12, Friday···from: Hans Hagen···
it might be that some changes are
reflected in the betas, and hopefully not breaking anything.
[...]
···date: 2013-07-14, Sunday···from: Philipp Gesang···
···date: 2013-07-12, Friday···from: Hans Hagen···
it might be that some changes are
reflected in the betas, and hopefully not breaking anything.
Unhappily, it does. In the generic font loader the new
On 7/14/2013 10:37 AM, Philipp Gesang wrote:
···date: 2013-07-12, Friday···from: Hans Hagen···
Hi,
I uploaded a beta. There are not that many changes. Currently I
develop in a separate branch but it might be that some changes are
reflected in the betas, and hopefully not breaking anything.
On 13/07/13 03:57, Otared Kavian wrote:
On 12 juil. 2013, at 20:06, Aditya Mahajan adit...@umich.edu wrote:
On Fri, 12 Jul 2013, Pablo Rodríguez wrote:
On 12/07/13 19:21, Hans Hagen wrote:
Hi,
I uploaded a beta. There are not that many changes. Currently I develop
in a separate branch but
Hi,
I uploaded a beta. There are not that many changes. Currently I develop
in a separate branch but it might be that some changes are reflected in
the betas, and hopefully not breaking anything.
Hans
-
On 12/07/13 19:21, Hans Hagen wrote:
Hi,
I uploaded a beta. There are not that many changes. Currently I develop
in a separate branch but it might be that some changes are reflected in
the betas, and hopefully not breaking anything.
Thanks for the new beta, Hans.
Could the two bugs with
On Fri, 12 Jul 2013, Pablo Rodríguez wrote:
On 12/07/13 19:21, Hans Hagen wrote:
Hi,
I uploaded a beta. There are not that many changes. Currently I develop
in a separate branch but it might be that some changes are reflected in
the betas, and hopefully not breaking anything.
Thanks for the
On 12 juil. 2013, at 20:06, Aditya Mahajan adit...@umich.edu wrote:
On Fri, 12 Jul 2013, Pablo Rodríguez wrote:
On 12/07/13 19:21, Hans Hagen wrote:
Hi,
I uploaded a beta. There are not that many changes. Currently I develop
in a separate branch but it might be that some changes are
On 10 avr. 2013, at 20:09, Hans Hagen pra...@wxs.nl wrote:
Hi,
An extra chapter in:
http://www.pragma-ade.nl/general/manuals/about.pdf
explaining abit the updated math fractions (and math styles mechanism).
Hi Hans,
Thanks for the explanations given in the above new manual about the
On Thu, Apr 11, 2013 at 6:25 PM, Otared Kavian ota...@gmail.com wrote:
However, on page 27, there is a sentence which I disagree with…
You say there:
« ConTEXt is always considered somewhat less math savvy than for instance
LaTEX »,
but actually I cannot see any example of maths typesetting
On Thu, Apr 11 2013, luigi scarso wrote:
It's true that ConTEXt is always considered less math savy than LaTeX
not that ConTEXt is less math savy than LaTeX.
Perhaps better: always - often ?
--
Peter
On 4/11/2013 10:15 PM, Peter Münster wrote:
On Thu, Apr 11 2013, luigi scarso wrote:
It's true that ConTEXt is always considered less math savy than LaTeX
not that ConTEXt is less math savy than LaTeX.
Perhaps better: always - often ?
Ok.
Concerning math ... in many aspects the
Hi,
An extra chapter in:
http://www.pragma-ade.nl/general/manuals/about.pdf
explaining abit the updated math fractions (and math styles mechanism).
Hans
-
Hans Hagen | PRAGMA ADE
Hi,
The uploaded beta has marco's ugs fixed (minus one) plus some (less
important) pending issues in test files. The main change is that the
root setup commands of enumerations, notes, formulas, floats, etc can
now be used to set up the counters (was only possible by explicit setups
e.g. per
Hi,
I chucked it in here, for lack of a better place.
http://wiki.contextgarden.net/String_Manipulation#String_formatter
I don't understand what they whitespace does: I tried to test it with
this code, and changing the number did nothing.
\starttext
\startluacode
x = 999
On 3/11/2013 6:13 PM, Sietse Brouwer wrote:
I don't understand what they whitespace does: I tried to test it with
this code, and changing the number did nothing.
for i=0,10 do
print(string.formatters(%wsietse,i))
end
for i=9,0,-1 do
print(string.formatters(%wsietse,i))
end
Hi,
I uploaded a beta. The most important change is that the 'context'
function now uses the formatters mechanism instead of Lua's format.
This has several benefits. First of all it's in most cases faster (I
measured upto 3 times) but it also permits us to support some more:
integer
On 27-7-2012 04:22, Li Yanrui (李延瑞) wrote:
2012/7/27 Hans Hagen pra...@wxs.nl:
The memory footprint should be somewhat smaller for non cjk usage. (format
generation as well as runtime) and the format file is some 10-15% smaller
now.
The fonts fallback can not work.
This is a minmal example:
On 26-7-2012 20:36, Pablo Rodríguez wrote:
I'm not sure whether this is important, but
http://www.pragma-ade.com/general/qrcs/setup-en.pdf#page=3 contains the
date July z, 2012
fixed in next
-
Hi,
I uploaded a beta. There is also an updated status-mkiv document:
files done644
files todo314
files pending 21 (some day)
obsolete2
total 981
So, I have some files to go (mostly lua files) before I pick up the
column thread.
The memory footprint should be
On 26/07/12 20:12, Hans Hagen wrote:
Hi,
I uploaded a beta. There is also an updated status-mkiv document:
files done644
files todo314
files pending 21 (some day)
obsolete2
total 981
So, I have some files to go (mostly lua files) before I pick up the
column
2012/7/27 Hans Hagen pra...@wxs.nl:
The memory footprint should be somewhat smaller for non cjk usage. (format
generation as well as runtime) and the format file is some 10-15% smaller
now.
The fonts fallback can not work.
This is a minmal example:
\definefontsynonym[song][name:adobesongstd]
Hi,
I uploaded a new beta. The usual fixes. New is a first version of a new
multi column handler. Pretty experimental but eventually it will replace
the current multi column routine, which is fact is then an instance,
think of
\definemixedcolumns
[columns]
\unexpanded\def\setupcolumns
On 16-7-2012 22:02, Hans Hagen wrote:
Hi,
I uploaded a new beta. The usual fixes. New is a first version of a new
multi column handler. Pretty experimental but eventually it will replace
the current multi column routine, which is fact is then an instance,
think of
\definemixedcolumns
Am 16.07.2012 um 22:02 schrieb Hans Hagen:
Hi,
I uploaded a new beta. The usual fixes. New is a first version of a new multi
column handler. Pretty experimental but eventually it will replace the
current multi column routine, which is fact is then an instance, think of
1 - 100 of 542 matches
Mail list logo