Hallo all, When I tried to update the new version of ConTeXt into texlive 2009 (uploading new files to BIN directory and run commands ctxtools --update, texexec --make --all and luatools --generate), then ConTeXt MKIV stopped working and I failed to return original state. What happened and how to fix?? I get this message, when I run context: MTXrun | forcing cache reload MTXrun | resolvers: warning: no lua configuration files found MTXrun | resolvers MTXrun | resolvers MTXrun | the resolver databases are not present or outdated MTXrun | resolvers: using suffix based filetype 'lua' MTXrun | resolvers: using suffix based filetype 'lua' MTXrun | resolvers: remembering file 'mtx-context.lua' MTXrun | resolvers: using suffix based filetype 'lua' MTXrun | unknown script 'context.lua' or 'mtx-context.lua' Thanx, Jaroslav
On 21-7-2010 12:28, Jaroslav Hajtmar wrote:
Hallo all,
When I tried to update the new version of ConTeXt into texlive 2009 (uploading new files to BIN directory and run commands ctxtools --update, texexec --make --all and luatools --generate), then ConTeXt MKIV stopped working and I failed to return original state. What happened and how to fix?? I get this message, when I run context:
MTXrun | forcing cache reload MTXrun | resolvers: warning: no lua configuration files found MTXrun | resolvers MTXrun | resolvers MTXrun | the resolver databases are not present or outdated MTXrun | resolvers: using suffix based filetype 'lua' MTXrun | resolvers: using suffix based filetype 'lua' MTXrun | resolvers: remembering file 'mtx-context.lua' MTXrun | resolvers: using suffix based filetype 'lua' MTXrun | unknown script 'context.lua' or 'mtx-context.lua'
it should be enough to do mtxrun --generate did you move texmfcnf.lua to the right web2c dir? 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 -----------------------------------------------------------------
Dne 21.7.2010 12:44, Hans Hagen napsal(a):
On 21-7-2010 12:28, Jaroslav Hajtmar wrote:
Hallo all,
When I tried to update the new version of ConTeXt into texlive 2009 (uploading new files to BIN directory and run commands ctxtools --update, texexec --make --all and luatools --generate), then ConTeXt MKIV stopped working and I failed to return original state. What happened and how to fix?? I get this message, when I run context:
MTXrun | forcing cache reload MTXrun | resolvers: warning: no lua configuration files found MTXrun | resolvers MTXrun | resolvers MTXrun | the resolver databases are not present or outdated MTXrun | resolvers: using suffix based filetype 'lua' MTXrun | resolvers: using suffix based filetype 'lua' MTXrun | resolvers: remembering file 'mtx-context.lua' MTXrun | resolvers: using suffix based filetype 'lua' MTXrun | unknown script 'context.lua' or 'mtx-context.lua'
it should be enough to do
mtxrun --generate Unfortunately it did not work...
did you move texmfcnf.lua to the right web2c dir?
No, I only copy new files to BIN directory and run uptate commands (I use Win 7 and TL2009) Thanx Jaroslav
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 -----------------------------------------------------------------
It is interesting that even though I back up the entire WIN32 directory, so after I had returned to its original state, so it just does not work... Jaroslav Dne 21.7.2010 12:44, Hans Hagen napsal(a):
On 21-7-2010 12:28, Jaroslav Hajtmar wrote:
Hallo all,
When I tried to update the new version of ConTeXt into texlive 2009 (uploading new files to BIN directory and run commands ctxtools --update, texexec --make --all and luatools --generate), then ConTeXt MKIV stopped working and I failed to return original state. What happened and how to fix?? I get this message, when I run context:
MTXrun | forcing cache reload MTXrun | resolvers: warning: no lua configuration files found MTXrun | resolvers MTXrun | resolvers MTXrun | the resolver databases are not present or outdated MTXrun | resolvers: using suffix based filetype 'lua' MTXrun | resolvers: using suffix based filetype 'lua' MTXrun | resolvers: remembering file 'mtx-context.lua' MTXrun | resolvers: using suffix based filetype 'lua' MTXrun | unknown script 'context.lua' or 'mtx-context.lua'
it should be enough to do
mtxrun --generate
did you move texmfcnf.lua to the right web2c dir?
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 -----------------------------------------------------------------
On 21-7-2010 1:05, Jaroslav Hajtmar wrote:
It is interesting that even though I back up the entire WIN32 directory, so after I had returned to its original state, so it just does not work...
Jaroslav
Dne 21.7.2010 12:44, Hans Hagen napsal(a):
On 21-7-2010 12:28, Jaroslav Hajtmar wrote:
Hallo all,
When I tried to update the new version of ConTeXt into texlive 2009 (uploading new files to BIN directory and run commands ctxtools --update, texexec --make --all and luatools --generate), then ConTeXt MKIV stopped working and I failed to return original state. What happened and how to fix?? I get this message, when I run context:
MTXrun | forcing cache reload MTXrun | resolvers: warning: no lua configuration files found MTXrun | resolvers MTXrun | resolvers MTXrun | the resolver databases are not present or outdated MTXrun | resolvers: using suffix based filetype 'lua' MTXrun | resolvers: using suffix based filetype 'lua' MTXrun | resolvers: remembering file 'mtx-context.lua' MTXrun | resolvers: using suffix based filetype 'lua' MTXrun | unknown script 'context.lua' or 'mtx-context.lua'
it should be enough to do
mtxrun --generate
did you move texmfcnf.lua to the right web2c dir?
the current mkiv can best be taken from the minimals ... just a separate tree independent of texlive 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 -----------------------------------------------------------------
Needing to create PDF/X-1a:2001 files to satisfy a particularly persnickety printer, I downloaded the 30-day free trial of Adobe Acrobat 9 Pro today. It seems to work OK when "printed" to from Scribus but I'm having trouble with my Context output. Using TexLive MKII, I can create a PDF that looks great directly from it, unfortunately it isn't PDF/X-1a:2001. texexec mytexfile --dvi readily produces a dvi file but I don't know if it's any good. dvips mytexfile VERY quickly produces as postscript file. Acrobat quickly converts the .ps file to a PDF without displaying error message. However, all the images are missing from the PDF that Acrobat creates. Is there a special setting required for it to pick up the images? Tom Benjey 717-258-9733 voice 717-243-0074 fax Twitter: @TomBenjey
Here's an update to my question. I found DVIOUT and viewed the dvi file. It is missing the images. Why would Context put the images in the PDF it creates and not the DVI? I made NO source code changes between running
texexec mytexfile
and
texexec mytexfile --dvi
Tom Benjey 717-258-9733 voice 717-243-0074 fax Twitter: @TomBenjey -----Original Message----- From: ntg-context-bounces@ntg.nl [mailto:ntg-context-bounces@ntg.nl] On Behalf Of Tom Sent: Wednesday, July 21, 2010 7:26 PM To: 'mailing list for ConTeXt users' Subject: [NTG-context] Images missing from PDF when created by Adobe Needing to create PDF/X-1a:2001 files to satisfy a particularly persnickety printer, I downloaded the 30-day free trial of Adobe Acrobat 9 Pro today. It seems to work OK when "printed" to from Scribus but I'm having trouble with my Context output. Using TexLive MKII, I can create a PDF that looks great directly from it, unfortunately it isn't PDF/X-1a:2001. texexec mytexfile --dvi readily produces a dvi file but I don't know if it's any good. dvips mytexfile VERY quickly produces as postscript file. Acrobat quickly converts the .ps file to a PDF without displaying error message. However, all the images are missing from the PDF that Acrobat creates. Is there a special setting required for it to pick up the images? Tom Benjey 717-258-9733 voice 717-243-0074 fax Twitter: @TomBenjey ____________________________________________________________________________ _______ 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 ____________________________________________________________________________ _______
Am 22.07.10 03:58, schrieb Tom:
Here's an update to my question.
I found DVIOUT and viewed the dvi file. It is missing the images. Why would Context put the images in the PDF it creates and not the DVI?
In PDF mode TeX can use images in pdf, png, jpg and jbig format but in dvi mode it can only use images in eps format. Wolfgang
-----Original Message----- Am 22.07.10 03:58, schrieb Tom:
Here's an update to my question.
I found DVIOUT and viewed the dvi file. It is missing the images. Why would Context put the images in the PDF it creates and not the DVI?
In PDF mode TeX can use images in pdf, png, jpg and jbig format but in dvi mode it can only use images in eps format. Wolfgang Thanks, Wolfgang. I never would have considered this to be the problem. Converting the first image to eps made it work. Should PostScript Level 2 and Encapsulated PostScript be selected when converting the images in Gimp? Does MKIV require the same image formats as MKII? Is this all an artifact of some early incarnation of Context? Tom Benjey 717-258-9733 voice 717-243-0074 fax Twitter: @TomBenjey
Am 22.07.10 06:07, schrieb Tom:
Thanks, Wolfgang. I never would have considered this to be the problem. Converting the first image to eps made it work. Should PostScript Level 2 and Encapsulated PostScript be selected when converting the images in Gimp?
Does MKIV require the same image formats as MKII? Is this all an artifact of some early incarnation of Context?
mkiv has only pdf as output format so you can use the same image formats as mkii in pdf mode, the restriction has nothing to do with context, it comes from the driver (pdftex) which allows only certain formats for pdf and dvi Wolfgang
On 22-7-2010 8:44, Wolfgang Schuster wrote:
Am 22.07.10 06:07, schrieb Tom:
Thanks, Wolfgang. I never would have considered this to be the problem. Converting the first image to eps made it work. Should PostScript Level 2 and Encapsulated PostScript be selected when converting the images in Gimp?
Does MKIV require the same image formats as MKII? Is this all an artifact of some early incarnation of Context?
mkiv has only pdf as output format so you can use the same image formats as mkii in pdf mode, the restriction has nothing to do with context, it comes from the driver (pdftex) which allows only certain formats for pdf and dvi
also, in mkiv, some graphic formats will be converted automatically before inclusion 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 -----------------------------------------------------------------
-----Original Message----- Am 22.07.10 06:07, schrieb Tom:
Thanks, Wolfgang. I never would have considered this to be the problem. Converting the first image to eps made it work. Should PostScript Level 2 and Encapsulated PostScript be selected when converting the images in Gimp?
Does MKIV require the same image formats as MKII? Is this all an artifact of some early incarnation of Context?
mkiv has only pdf as output format so you can use the same image formats as mkii in pdf mode, the restriction has nothing to do with context, it comes from the driver (pdftex) which allows only certain formats for pdf and dvi Wolfgang Do I understand correctly that MKIV will not output a dvi or ps file and that no stable version of it outputs a PDF/X-1a:2001 format file? Is a version with this feature expected to be stable in a year? Tom Benjey 717-258-9733 voice 717-243-0074 fax Twitter: @TomBenjey
On Fri, Jul 23, 2010 at 2:44 AM, Tom
true at 99%
that no stable version of it outputs a PDF/X-1a:2001 format file?
Did you search for pdf/x in this mailling list ?
Is a version with this feature expected to be stable in a year?
yes
-- luigi
On Jul 21, 2010, at 7:26 PM, Tom wrote:
Using TexLive MKII, I can create a PDF that looks great directly from it, unfortunately it isn't PDF/X-1a:2001.
There's a LaTeX package which will create .pdfs conformant to that specification --- perhaps the code could be ported over? If not, use pdf2ps to get a PostScript file from the .pdf, then distill the .ps file w/ the correct settings. William -- William Adams senior graphic designer Fry Communications Sphinx of black quartz, judge my vow.
-----Original Message----- On Jul 21, 2010, at 7:26 PM, Tom wrote:
Using TexLive MKII, I can create a PDF that looks great directly from it, unfortunately it isn't PDF/X-1a:2001.
There's a LaTeX package which will create .pdfs conformant to that specification --- perhaps the code could be ported over? If not, use pdf2ps to get a PostScript file from the .pdf, then distill the .ps file w/ the correct settings. William -- William Adams senior graphic designer Fry Communications Sphinx of black quartz, judge my vow. Thanks for the tip, William. I am running TexLive MKII on a Windows system and it doesn't seem to have pdf2ps. Bummer. BTW, are you located in Mechanicsburg? If so, it's a small world. Tom Benjey 717-258-9733 voice 717-243-0074 fax Twitter: @TomBenjey
On Jul 22, 2010, at 9:17 AM, Tom wrote:
Thanks for the tip, William. I am running TexLive MKII on a Windows system and it doesn't seem to have pdf2ps. Bummer.
If you install Ghostscript you'll get it. If not, install a nice, generic PostScript driver, then print to a PostScript file using Adobe Reader, then distill the .ps file.
BTW, are you located in Mechanicsburg? If so, it's a small world.
Not from here (moved up from Virginia a couple of years ago), but living here now. Drop me a line off-list --- we'll have to get together. William -- William Adams senior graphic designer Fry Communications Sphinx of black quartz, judge my vow.
participants (6)
-
Hans Hagen -
Jaroslav Hajtmar -
luigi scarso -
Tom -
William Adams -
Wolfgang Schuster