I just installed ConTeXtMinimal using first-setup.bat. But it seems it has some serious bug that context even couldn't deal with such a easy document: \starttext Hello world! \stoptext What's the problem? Anybody can help me? Thanks. Fengnan Gao fnsteed@hotmail.com
log message, please.
On Sun, Dec 21, 2008 at 3:19 PM, Fengnan Gao
I just installed ConTeXtMinimal using first-setup.bat. But it seems it has some serious bug that context even couldn't deal with such a easy document:
\starttext Hello world! \stoptext
What's the problem? Anybody can help me?
Thanks.
Fengnan Gao fnsteed@hotmail.com ___________________________________________________________________________________ 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
I did a clean minimals install on my Windows XP Home SP3 system and
get the same strange output.
ConTeXt ver: 2008.11.10 21:40 MKIV fmt: 2008.12.22 int: english/english
This is LuaTeX, Version snapshot-0.31.2-2008121200, build 1659
texmfstart texexec --lua hello
context.cmd --lua hello
C:\context\tex\texmf-cache\luatex-cache\context\2fea56f92e5267d7cc9662e4d5f52e1e\fonts\otf\lmroman12-regular.tma
C:\context\tex\texmf\fonts\opentype\public\lm\lmroman12-regular.otf
mailed to Taco.
Best,
Alan
On Sun, Dec 21, 2008 at 8:19 AM, Fengnan Gao
I just installed ConTeXtMinimal using first-setup.bat. But it seems it has some serious bug that context even couldn't deal with such a easy document:
\starttext Hello world! \stoptext
What's the problem? Anybody can help me?
Thanks.
Fengnan Gao fnsteed@hotmail.com ___________________________________________________________________________________ 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
Alan STONE wrote:
I did a clean minimals install on my Windows XP Home SP3 system and get the same strange output.
ConTeXt ver: 2008.11.10 21:40 MKIV fmt: 2008.12.22 int: english/english This is LuaTeX, Version snapshot-0.31.2-2008121200, build 1659
texmfstart texexec --lua hello context.cmd --lua hello
C:\context\tex\texmf-cache\luatex-cache\context\2fea56f92e5267d7cc9662e4d5f52e1e\fonts\otf\lmroman12-regular.tma C:\context\tex\texmf\fonts\opentype\public\lm\lmroman12-regular.otf
mailed to Taco.
Thanks, got them. More later, but at first glance the tma does not look all that weird. Best wishes, Taco
Taco Hoekwater wrote:
Alan STONE wrote:
I did a clean minimals install on my Windows XP Home SP3 system and get the same strange output.
ConTeXt ver: 2008.11.10 21:40 MKIV fmt: 2008.12.22 int: english/english This is LuaTeX, Version snapshot-0.31.2-2008121200, build 1659
texmfstart texexec --lua hello context.cmd --lua hello
C:\context\tex\texmf-cache\luatex-cache\context\2fea56f92e5267d7cc9662e4d5f52e1e\fonts\otf\lmroman12-regular.tma
C:\context\tex\texmf\fonts\opentype\public\lm\lmroman12-regular.otf
mailed to Taco.
Thanks, got them. More later, but at first glance the tma does not look all that weird.
Short update on the files people sent me: * the otf file is identical, * the tma and tmc seem fine It seems that somehow, when the tmc is read in, context (i.e. luatex) misinterprets the numeric values in the bytecode completely, resulting in ridiculous values for character widths, heights, depths etc. I am afraid I still have no idea why this happens. Best wishes, Taco
Hi, all Can I roll back and use the old version when context isn't broken? I have several documents which need to be processed ASAP. Thanks. Fengnan Gao
On Wed, Dec 24, 2008 at 3:45 AM, Fengnan Gao
Hi, all
Can I roll back and use the old version when context isn't broken? I have several documents which need to be processed ASAP. Thanks.
Hello Fengan, you need both an older version of luatex and an older version of ConTeXt. Suggestion 1: You can download mswincontext.zip from PRAGMA, though that one dates months back. If that is not an issue, you can use that one. Suggestion 2: Change first-setup.bat, so that --context=beta switch will read --context=2008.10.31 and run first-setup.bat again. This will give you the version of ConTeXt that's still OK, but the same broken LuaTeX, so you need to download some older version of luatex binary from http://foundry.supelec.fr/projects/luatex (0.30.3 should be fine). You need to delete the contents of texmf-cache and regenerate formats. I would like to fix this, but I don't know how. One option is to revert both ConTeXt and LuaTeX to an older version. A much better thing would be to fix font-otf.lua. Hans? Taco? Mojca
On Wed, Dec 24, 2008 at 3:45 AM, Fengnan Gao
Hi, all
Can I roll back and use the old version when context isn't broken? I have several documents which need to be processed ASAP. Thanks.
Fengnan Gao
As an alternative to Mojca's today suggestions to go back to "both an older version of luatex and an older version of ConTeXt" I still have an older (Windows) working version ConTeXt ver: 2008.11.10 21:40 LuaTeX, Version snapshot-0.30.2-2008102120, build 1568 and can zip it & upload it (to somewhere) if you like. Best, Alan
On Sun, Dec 21, 2008 at 8:19 AM, Fengnan Gao wrote:
I just installed ConTeXtMinimal using first-setup.bat. But it seems it has some serious bug that context even couldn't deal with such a easy document:
\starttext Hello world! \stoptext
What's the problem? Anybody can help me?
Hmmm ... I just figured out that the problem is easily reproducible on my platform if I create a fresh install. But in my case luatex crashes. With the old installation (same version of luatex, same version of ConTeXt) the old files from cache are being used, so everything works OK. (/tmp/context/tex/texmf-context/tex/context/base/cont-err.tex systems : no file 'cont-sys.tex', using 'cont-sys.rme' instead ) ) Fatal error occurred, no output PDF file produced! So at least there's something to start with ... Mojca
Hi Mojca, Mojca Miklavec wrote:
!luaTeX error (file /tmp/context/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf): Parsing CFF DICT failed. (error=-1)
I can almost certainly reproduce this, I see an uninitialized variable in valgrind. More about this later, but this is *not* the same as Fengnan's problem. This problem happens in the backend when the pdf resources are output, while his problem occurs much earlier in the process, during the actual typesetting. Best wishes, Taco
Taco Hoekwater wrote:
Hi Mojca,
Mojca Miklavec wrote:
!luaTeX error (file /tmp/context/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf): Parsing CFF DICT failed. (error=-1)
I can almost certainly reproduce this, I see an uninitialized variable in valgrind.
Nope, couldn't do it. I am _almost_ sorry to say that luatex on linux-64 is behaving fine. Mojca (or someone else that has this 'Parsing CFF' problem), can you try to pinpoint the problem in a debugger? Best wishes, Taco
On Wed, Dec 24, 2008 at 11:03 AM, Taco Hoekwater
Taco Hoekwater wrote:
Hi Mojca,
Mojca Miklavec wrote:
!luaTeX error (file /tmp/context/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf): Parsing CFF DICT failed. (error=-1)
I can almost certainly reproduce this, I see an uninitialized variable in valgrind.
Nope, couldn't do it. I am _almost_ sorry to say that luatex on linux-64 is behaving fine. Mojca (or someone else that has this 'Parsing CFF' problem), can you try to pinpoint the problem in a debugger?
Which debugger Taco ?
Best wishes, Taco
Alan STONE wrote:
Nope, couldn't do it. I am _almost_ sorry to say that luatex on linux-64 is behaving fine. Mojca (or someone else that has this 'Parsing CFF' problem), can you try to pinpoint the problem in a debugger?
Which debugger Taco ?
A source debugger (like gdb). You'll also need to comment out the "$STRIP "$B"/texk/web2c/luatex" line in build.sh, otherwise the debugger cannot use symbols. The message is produced by font/writecff.c, line 820: pdftex_fail("Parsing CFF DICT failed. (error=%d)", status); you can set a breakpoint there, but the error happens earlier. The (error=-1) actually signifies a CFF parsing (decoding) error, but that does not help much in finding the problem. What is needed is at least a stack backtrace, and probably also the current location inside the CFF file. Best wishes, Taco
On Wed, Dec 24, 2008 at 2:21 PM, Taco Hoekwater
Alan STONE wrote:
Nope, couldn't do it. I am _almost_ sorry to say that luatex on linux-64 is behaving fine. Mojca (or someone else that has this 'Parsing CFF' problem), can you try to pinpoint the problem in a debugger?
Which debugger Taco ?
A source debugger (like gdb). You'll also need to comment out the "$STRIP "$B"/texk/web2c/luatex" line in build.sh, otherwise the debugger cannot use symbols.
The message is produced by font/writecff.c, line 820:
pdftex_fail("Parsing CFF DICT failed. (error=%d)", status);
you can set a breakpoint there, but the error happens earlier.
The (error=-1) actually signifies a CFF parsing (decoding) error, but that does not help much in finding the problem. What is needed is at least a stack backtrace, and probably also the current location inside the CFF file.
Best wishes, Taco
There's a windows version at http://www.equation.com/servlet/equation.cmd?call=gdb and I'm trying to figure out how to use this thing. That's for the day after tomorrow. To be continued... Best, Alan
Taco Hoekwater wrote:
Taco Hoekwater wrote:
Hi Mojca,
Mojca Miklavec wrote:
!luaTeX error (file /tmp/context/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf): Parsing CFF DICT failed. (error=-1) I can almost certainly reproduce this, I see an uninitialized variable in valgrind.
Nope, couldn't do it. I am _almost_ sorry to say that luatex on linux-64 is behaving fine. Mojca (or someone else that has this 'Parsing CFF' problem), can you try to pinpoint the problem in a debugger?
After lots and lots of debugging work by Mojca, the problem itself turned out to be simple (as is usually the case). This bug surfaces always and only when your locale is set to using a comma for the decimal separator in numbers. It turns out that the bug was already 'mechanically' fixed in the development trunk, and that explains why Hans was not affected (my own locale is "C"). Luatex 0.31.3 will be released on monday. Best wishes, Taco
On Sun, Dec 21, 2008 at 12:49 PM, Fengnan Gao
I just installed ConTeXtMinimal using first-setup.bat. But it seems it has some serious bug that context even couldn't deal with such a easy document:
\starttext Hello world! \stoptext
What's the problem? Anybody can help me?
I got the same error so I tried texexec instead of context and it seems to work fine. How different is context from texexec? Regards, Derek -- _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Blog: http://www.derekcordeiro.com Follow Me: http://twitter.com/derekcordeiro
On Tue, Dec 23, 2008 at 8:51 PM, Derek CORDEIRO
On Sun, Dec 21, 2008 at 12:49 PM, Fengnan Gao
wrote: I just installed ConTeXtMinimal using first-setup.bat. But it seems it has some serious bug that context even couldn't deal with such a easy document:
\starttext Hello world! \stoptext
What's the problem? Anybody can help me?
I got the same error so I tried texexec instead of context and it seems to work fine. How different is context from texexec?
Oops dumb question on my part... did not realise that texexec used pdfTeX by default and context uses luaTeX. ... Derek
participants (6)
-
Alan STONE
-
Derek CORDEIRO
-
Fengnan Gao
-
Mojca Miklavec
-
Taco Hoekwater
-
Yue Wang