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 fil
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 build.
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
/context-osx-6
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 the
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,
\c!st
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 for
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
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
Ridderstraa
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 r
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
chara
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
\
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 printed as
is. I
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 s
> 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.
Thomas
___
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 when
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 an
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
-
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/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 th
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 this
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
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 replie
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 Wolf
Pablo Rodriguez schrieb:
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.
1. Does the
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 yo
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
--
http:/
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[newo
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 Class
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)
Ma
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:
[...]
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
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)
Many thank
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 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:
\usemodule[newotf]
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
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
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 it
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
-
Note that the || in tufte does not get handled transparently.
Alan
On Mon, 15 Jun 2015 00:21:56 +0200
Mojca Miklavec 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 handles outlines. Her
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.
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
On 05/15/2015 11:53 AM, Hans Hagen wrote:
> Hi,
>
> I uploaded a new beta. This is the last before a current that goes on tl
> 2015.
Hans,
I get this error with the latest beta from 2015.05.15 11:42:
luajittex: ../../../source/texk/web2c/luatexdir/tex/texnodes.w:2255:
delete_attribute_ref: Ass
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
--
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]
\starttext
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 \index
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
--
h
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 m
On 31 juil. 2013, at 23:43, 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:
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
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?
Am 17.07.2013 um 12:23 schrieb Hans Hagen :
> 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 17.07.2013 um 12:23 schrieb Hans Hagen :
> 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
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 tha
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?
T
On 7/14/2013 10:37 AM, Philipp Gesang 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.
There a copy’n’paste mistake in luatex-ba
·
> ·
>
> > 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 that it is
> als
·
> On 14/07/13 10:53, Philipp Gesang wrote:
> > ·
> >
> >> it might be that some changes are
> >> reflected in the betas, and hopefully not breaking anything.
> > [...]
> > Failing example with ligatures:
> >
> > \font\foo="file:Iwona-Regular
On 14/07/13 10:53, Philipp Gesang wrote:
> ·
>
>> it might be that some changes are
>> reflected in the betas, and hopefully not breaking anything.
> [...]
> Failing example with ligatures:
>
> \font\foo="file:Iwona-Regular.otf:mode=node;+liga"
> \
·
> 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 that it is
also required to contain certa
·
> 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 luatex-basics-nod.lua. See
attached diff.
Best,
On 13/07/13 03:57, Otared Kavian wrote:
> On 12 juil. 2013, at 20:06, Aditya Mahajan 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 b
On 12 juil. 2013, at 20:06, Aditya Mahajan 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 refle
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/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 w
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
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 Thu, Apr 11, 2013 at 6:25 PM, Otared Kavian 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 which canno
On 10 avr. 2013, at 20:09, Hans Hagen 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 new
fe
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 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
context("\\type{
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
-
On 27-7-2012 04:22, Li Yanrui (李延瑞) wrote:
2012/7/27 Hans Hagen :
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:
\definefontsy
2012/7/27 Hans Hagen :
> 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]
\definefon
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 th
On 16-7-2012 22:30, Wolfgang Schuster wrote:
be changed to
\unexpanded\def\strc_itemgroups_start_columns
{\startmixedcolumns[itemgroupcolumns]}
\unexpanded\def\strc_itemgroups_stop_columns
{\stopmixedcolumns}
because “start” and “stop” are interface/language dependant strings.
Ok. I n
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
>
> \definemi
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
[column
On 9-7-2012 23:40, Meer, H. van der wrote:
This is beta: ConTeXt ver: 2012.07.09 22:35 MKIV fmt: 2012.7.9 int:
english/english
It fails me with (see below). I am fairly sure now this must be an error seeing
the minimal example provided. Here is the most minimal example I could concoct:
it
On 17-1-2012 09:08, Mari Voipio wrote:
On Mon, Jan 16, 2012 at 19:47, Hans Hagen wrote:
I uploaded a new beta. This time a couple of fixes + some reorganization of
font related code. More to follow.
There's something fishy somewhere in the fonts or the simplefonts
module, because a file that
On Mon, Jan 16, 2012 at 19:47, Hans Hagen wrote:
> I uploaded a new beta. This time a couple of fixes + some reorganization of
> font related code. More to follow.
There's something fishy somewhere in the fonts or the simplefonts
module, because a file that worked last week now gets
Am 01.01.2012 um 03:39 schrieb Li Yanrui (李延瑞):
> 2011/12/31 Hans Hagen :
>> Hi,
>>
>> I uploaded a new beta. As I'm still in cleaning-up mode, the usual problems
>> could show up as quite some code was adapted (moved around). For those
>> interested there is a file 'status-mkiv' that can be run
2011/12/31 Hans Hagen :
> Hi,
>
> I uploaded a new beta. As I'm still in cleaning-up mode, the usual problems
> could show up as quite some code was adapted (moved around). For those
> interested there is a file 'status-mkiv' that can be run to get an overview
> of where we stand.
>
> One big chang
Am 31.12.2011 um 13:58 schrieb Meer, H. van der:
> Has the following been found and corrected?
>
>>> \definetypeface [\typescriptone] [tt] [mono] [cursor] [default]
>>> \@tlstyle
> \@tlstyle
>
> \dousestyleparameter ...\currentstyleparameter {#1
>
Has the following been found and corrected?
>> \definetypeface [\typescriptone] [tt] [mono] [cursor]
>> [default] \@tlstyle
\@tlstyle
\dousestyleparameter ...\currentstyleparameter {#1
}\ifx \curre
On 22-12-2011 16:37, Henning Hraban Ramm wrote:
Am 2011-12-22 um 14:55 schrieb Hans Hagen:
This version might also solve some of the reported problems with page
imposition (as the page-* modules are being cleaned up buglets cna be
introduced .. nothing really changes there apart from speedup a
Am 2011-12-22 um 14:55 schrieb Hans Hagen:
This version might also solve some of the reported problems with
page imposition (as the page-* modules are being cleaned up buglets
cna be introduced .. nothing really changes there apart from speedup
and namespacing).
"typing" (\starttyping) s
On 3-10-2011 12:42, Thomas A. Schmitz wrote:
Another problem: interactive links appear to be broken with the latest
beta. This works with 2011.09.20, but not with the latest:
\setupinteraction
[state=start,
color=darkblue]
\useURL[luatex][http://www.luatex.org][][luatex website]
\starttext
Do
Another problem: interactive links appear to be broken with the latest
beta. This works with 2011.09.20, but not with the latest:
\setupinteraction
[state=start,
color=darkblue]
\useURL[luatex][http://www.luatex.org][][luatex website]
\starttext
Does this work? \from[luatex]
\stoptext
TeXt users
Reply-To: mailing list for ConTeXt users
Subject: Re: [NTG-context] new beta
On 10/01/2011 11:16 AM, Hans Hagen wrote:
> Hi,
>
> I uploaded a new beta. Apart from some fixes the following has been
> added/changed. Some are side effects of discussions at the context meeting.
&g
On 10/02/2011 10:59 PM, Hans Hagen wrote:
On 2-10-2011 18:16, Thomas A. Schmitz wrote:
the cross-referencing is excellent new, I will have to play with it very
soon! In the meantime, here's something which broke with the October
beta (worked a week ago):
fixed (just a forgotten low level rena
On 2-10-2011 18:16, Thomas A. Schmitz wrote:
the cross-referencing is excellent new, I will have to play with it very
soon! In the meantime, here's something which broke with the October
beta (worked a week ago):
fixed (just a forgotten low level rename)
Hans
On 10/01/2011 11:16 AM, Hans Hagen wrote:
Hi,
I uploaded a new beta. Apart from some fixes the following has been
added/changed. Some are side effects of discussions at the context meeting.
However, the biggest new thing is adapted cross document referencing.
This was already possible but we co
On 28-1-2011 6:55, Alan BRASLAU wrote:
Hans,
Typing the full path name (in response to the prompt)
satisfies the program, and the installation process proceeds.
Mistyping the file name causes the prompt to be repeated,
so I assume that the file is indeed there.
ok, but is it mentioned in the f
Hans,
Typing the full path name (in response to the prompt)
satisfies the program, and the installation process proceeds.
Mistyping the file name causes the prompt to be repeated,
so I assume that the file is indeed there.
Alan
On Thursday 27 January 2011 22:43:09 Hans Hagen wrote:
> On 26-1-201
On 26-1-2011 3:31, Alan BRASLAU wrote:
Here is a log.
Notice the instances of "Please type another input file name:"
In your log we find:
resolvers:
scanning path '/usr/local/context/beta/tex/texmf-context'
resolvers:
category 'files',
cachename '/usr/local/context/beta/tex/texmf-
On 01/26/11 22:01, Alan BRASLAU wrote:
> On Wednesday 26 January 2011 19:56:04 Mojca Miklavec wrote:
>>
>> I will rewrite some of the scripts from scratch anyway, but I hope
>> that this should work now. I would have to test whether there is a
>> more elegant way for enforcing some specific type
On Wednesday 26 January 2011 19:56:04 Mojca Miklavec wrote:
>
> I will rewrite some of the scripts from scratch anyway, but I hope
> that this should work now. I would have to test whether there is a
> more elegant way for enforcing some specific type of platform when
> uname lies.
>
Maybe "bash
I think I understand at least part of the problem now.
When I run ./first-setup.sh it runs
/usr/local/texlive/2010/bin/x86_64-darwin/mktexlsr
/usr/local/texlive/2010/bin/x86_64-darwin/mtxrun
instead of mktexlsr and mtxrun from the newly installed distribution.
Is anyone willing to try to
1 - 100 of 488 matches
Mail list logo