Hi, I uploaded a beta (for luatex 0.80) that has some changes in low level interfaces. Hopefully there are no side effects but there are they can be sorted out fast. I tested the code on projects and manuals so it should not be too bad. Depending on how complex your setup up is, there can be a speed gain of some 5% compared to previous versions. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Hi Hans,
with the new beta following mwe produces a bug. Perhaps I'm doing something
wrong.
MWE:
\definefontfamily[mainface][sans][DejaVu Sans]
%or \definefontfamily[mainface][sans][gosmicksans] with the same result
\setupbodyfont[mainface]
\starttext
\input tufte
\stoptext
Error log:
Typesetting /home/ubuntu/workspace/mwe.tex
mtx-context | run 1: luatex
--fmt="/home/ubuntu/workspace/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en"
--jobname="mwe"
--lua="/home/ubuntu/workspace/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.lui"
--no-parse-first-line --c:currentrun=1 --c:fulljobname="./mwe.tex"
--c:input="./mwe.tex" --c:kindofrun=1 --c:maxnofruns=8 "cont-yes.mkiv"
This is LuaTeX, Version beta-0.80.0 (TeX Live 2015/dev) (rev 5195)
\write18 enabled.
interfaces > implementor > warning: 'commands.writestatus' is redefined
interfaces > implementor > error: no actions for
'btxresolvelistreference'
open source > 1 > 1 >
/home/ubuntu/workspace/context/tex/texmf-context/tex/context/base/cont-yes.mkiv
ConTeXt ver: 2015.03.26 19:19 MKIV beta fmt: 2015.3.26 int:
english/english
system > 'cont-new.mkiv' loaded
open source > 2 > 2 >
/home/ubuntu/workspace/context/tex/texmf-context/tex/context/base/cont-new.mkiv
close source > 2 > 2 >
/home/ubuntu/workspace/context/tex/texmf-context/tex/context/base/cont-new.mkiv
system > files > jobname 'mwe', input './mwe', result 'mwe'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > 2 > 3 >
/home/ubuntu/workspace/documents/snippets/bug/mwe.tex
tex error > error on line 179 in file
/home/ubuntu/workspace/documents/snippets/bug/mwe.tex: ! Argument of
\splitoffbase has an extra }
<inserted text>
\par
<to be read again>
}
\rawdoifinsetelse ...def \m_syst_sub_string {,#1,}
\ifx \m_syst_sub_string
\m...
\addtocommalist #1#2->\rawdoifinsetelse {#1}
#2\resetglobal {\dodoglobal
\ede...
\font_typefaces_define_a ...usetypescriptfile [#4]
\font_typescripts_use_one
...
l.179 ]
...
l.2 \setupbodyfont
[mainface]
Thanks for your help.
Christian
2015-03-26 19:24 GMT+01:00 Hans Hagen
Hi,
I uploaded a beta (for luatex 0.80) that has some changes in low level interfaces. Hopefully there are no side effects but there are they can be sorted out fast. I tested the code on projects and manuals so it should not be too bad. Depending on how complex your setup up is, there can be a speed gain of some 5% compared to previous versions.
Hans
----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl ----------------------------------------------------------------- ____________________________________________________________ _______________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/ listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ____________________________________________________________ _______________________
On 03/26/2015 07:24 PM, Hans Hagen wrote:
Hi,
I uploaded a beta (for luatex 0.80) that has some changes in low level interfaces. Hopefully there are no side effects but there are they can be sorted out fast. I tested the code on projects and manuals so it should not be too bad. Depending on how complex your setup up is, there can be a speed gain of some 5% compared to previous versions.
Hans, many thanks for the new beta. I’m afraid that the three documents I tested (rather complex ones) cannot be compiled and the error message is the same. \definefontfamily seems to be the offending command The minimal sample: \definefontfamily[mainface][rm][TeX Gyre Pagella] \setupbodyfont[mainface] \starttext \input zapf \stoptext Many thanks for your help, Pablo -- http://www.ousia.tk
Am 26.03.2015 um 20:14 schrieb Pablo Rodriguez
: On 03/26/2015 07:24 PM, Hans Hagen wrote:
Hi,
I uploaded a beta (for luatex 0.80) that has some changes in low level interfaces. Hopefully there are no side effects but there are they can be sorted out fast. I tested the code on projects and manuals so it should not be too bad. Depending on how complex your setup up is, there can be a speed gain of some 5% compared to previous versions.
Hans,
many thanks for the new beta.
I’m afraid that the three documents I tested (rather complex ones) cannot be compiled and the error message is the same. \definefontfamily seems to be the offending command
The minimal sample:
\definefontfamily[mainface][rm][TeX Gyre Pagella] \setupbodyfont[mainface] \starttext \input zapf \stoptext
Many thanks for your help,
The bug happens further down in the \usetypescriptfile command and is triggered when a empty argument is given. The cause can be reproduced with the following example when you pass an empty string to \splitfilename. \starttext \letempty\CommaList \splitfilename{}% fails %\splitfilename{text}% works \addtocommalist\splitoffbase\CommaList \stoptext Wolfgang
On 3/26/2015 8:35 PM, Wolfgang Schuster wrote:
Am 26.03.2015 um 20:14 schrieb Pablo Rodriguez
: On 03/26/2015 07:24 PM, Hans Hagen wrote:
Hi,
I uploaded a beta (for luatex 0.80) that has some changes in low level interfaces. Hopefully there are no side effects but there are they can be sorted out fast. I tested the code on projects and manuals so it should not be too bad. Depending on how complex your setup up is, there can be a speed gain of some 5% compared to previous versions.
Hans,
many thanks for the new beta.
I’m afraid that the three documents I tested (rather complex ones) cannot be compiled and the error message is the same. \definefontfamily seems to be the offending command
The minimal sample:
\definefontfamily[mainface][rm][TeX Gyre Pagella] \setupbodyfont[mainface] \starttext \input zapf \stoptext
Many thanks for your help,
The bug happens further down in the \usetypescriptfile command and is triggered when a empty argument is given. The cause can be reproduced with the following example when you pass an empty string to \splitfilename.
\starttext
\letempty\CommaList
\splitfilename{}% fails %\splitfilename{text}% works \addtocommalist\splitoffbase\CommaList
\stoptext
ok, fix in engine needed ... i uploaded a temp fix Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (4)
-
Christian Prim
-
Hans Hagen
-
Pablo Rodriguez
-
Wolfgang Schuster