Re: [NTG-context] can I upgrade yet?
Hans Hagen wrote: Gary wrote: Hans Hagen wrote: Gary wrote: [...] 3.) Is there some other way besides my traditional method of unzipping cont-tmf.zip file into /localtexmf ? Do I need to rebuild the file system? no, you can unzip, run textools --fixtexmf --force, regenerate the database, and cross your fingers ok, here's what I did: 1. Upgraded MikTeX 2. Unzipped the latest cont-tmf.zip (from pragma-ade.com) into c:\tex\localtexmf 3. ran textools --fixtexmf --force (what does that do?) if needed it moves you rlocal enc/map files to their new locations, not needed if you have no commercial fonts 4. checked c:\tex\localtex\context\config. texexec.ini is newer than texexec.rme, so I left it alone. 5. ran texexec --make en nl (do I need nl? I'm exclusively English. I guess it can't hurt.) 6. noticed that cont-en.efmt was automatically relocated to c:\tex\localtex\miktex\fmt but cont-nl was not. 7. moved cont-nl.efmt to c:\tex\localtex\miktex\fmt 8. renamed them both to *.fmt (per a note in the contextgarden wiki. Is this necessary?) 9. ran texexec --make metafun 10. moved metefun.mem to c:\tex\localtex\miktex\mem 11. ran mktexlsr texexec --make (--all if you want all patterns) is normally enough, apart from moving the fmt and mem files (aren't those put at the right spot by miktex?) Hans Hmm. I normally open a command line window, and execute texexec --make en nl in some random directory. The result appears to be cont-en.efmt in the correct place, and cont-nl.efmt in the current directory. It's possible that I did not look closely enough, and something entirely different happened. I can't see why MikTeX would have any say in the matter of what texexec does. Anyway, thanks for commenting. I wasn't sure I was doing the right thing. -g ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] can I upgrade yet?
Some months ago I stopped upgrading ConTeXt. Here and there I saw references to new file hierarchies, and something about installation scripts ... if I remember correctly. I didn't want to break my system, so I just stopped upgrading, and stopped reading those messages (which I didn't understand, anyway). I'm currently using MikTeX. 1.) Concerning file hierarchy: did something monumental indeed ocurr that I ignored? 2.) If so, is it safe to upgrade? 3.) Is there some other way besides my traditional method of unzipping cont-tmf.zip file into /localtexmf ? Do I need to rebuild the file system? 4.) Have I misinterpreted, and nothing much has changed? Sorry about this. I really want to avoid getting my system into some strange state, and spending hours unraveling the mystery. Done that too many times in my life. -gary ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] can I upgrade yet?
Gary wrote: Some months ago I stopped upgrading ConTeXt. Here and there I saw references to new file hierarchies, and something about installation scripts ... if I remember correctly. I didn't want to break my system, so I just stopped upgrading, and stopped reading those messages (which I didn't understand, anyway). I'm currently using MikTeX. 1.) Concerning file hierarchy: did something monumental indeed ocurr that I ignored? enc and map files as well as scripts are now in new locations, i assume that miktex has been adapted to that 2.) If so, is it safe to upgrade? miktex has a good reputation or upgrading 3.) Is there some other way besides my traditional method of unzipping cont-tmf.zip file into /localtexmf ? Do I need to rebuild the file system? no, you can unzip, run textools --fixtexmf --force, regenerate the database, and cross your fingers 4.) Have I misinterpreted, and nothing much has changed? thing shave changed, e,g, the pdftex cfg file is gone now; no real problem for context since it never depended on that; the danger is in partially upgrading: a new pdftex will not work in an old tree Sorry about this. I really want to avoid getting my system into some strange state, and spending hours unraveling the mystery. Done that too many times in my life. i do my best to avoid problem sfo rusers, but some things are out of my control Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] can I upgrade yet?
Is there some other way besides my traditional method of unzipping cont-tmf.zip file into /localtexmf ? I'm on MikTeX as well. I've kept my system up to date via the MikTeX Update Wizard. But just to see if unzipping cont-tmf.zip over my \texmf would break anything, I just tried it. No problem. That said, I updated my installation via the wizard only a few weeks ago ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] can I upgrade yet?
Hans Hagen wrote: Gary wrote: [...] Sorry about this. I really want to avoid getting my system into some strange state, and spending hours unraveling the mystery. Done that too many times in my life. i do my best to avoid problem sfo rusers, but some things are out of my control Hans Understood and appreciated. I am *not* annoyed, and I apologize if I sounded annoyed. Thanks for the upgrade tips. -gary ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] can I upgrade yet?
Hans Hagen wrote: Gary wrote: [...] 3.) Is there some other way besides my traditional method of unzipping cont-tmf.zip file into /localtexmf ? Do I need to rebuild the file system? no, you can unzip, run textools --fixtexmf --force, regenerate the database, and cross your fingers ok, here's what I did: 1. Upgraded MikTeX 2. Unzipped the latest cont-tmf.zip (from pragma-ade.com) into c:\tex\localtexmf 3. ran textools --fixtexmf --force (what does that do?) 4. checked c:\tex\localtex\context\config. texexec.ini is newer than texexec.rme, so I left it alone. 5. ran texexec --make en nl (do I need nl? I'm exclusively English. I guess it can't hurt.) 6. noticed that cont-en.efmt was automatically relocated to c:\tex\localtex\miktex\fmt but cont-nl was not. 7. moved cont-nl.efmt to c:\tex\localtex\miktex\fmt 8. renamed them both to *.fmt (per a note in the contextgarden wiki. Is this necessary?) 9. ran texexec --make metafun 10. moved metefun.mem to c:\tex\localtex\miktex\mem 11. ran mktexlsr So far, everything seems to be fine. Are all of these steps necessary? or advisable? Did I forget anything? Is there an shorter method that I've missed? (not that this is long or difficult) Thanks again, -gary ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] can I upgrade yet?
Gary wrote: Understood and appreciated. I am *not* annoyed, and I apologize if I sounded annoyed. i was not annoyed at all -) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] can I upgrade yet?
Gary wrote: Hans Hagen wrote: Gary wrote: [...] 3.) Is there some other way besides my traditional method of unzipping cont-tmf.zip file into /localtexmf ? Do I need to rebuild the file system? no, you can unzip, run textools --fixtexmf --force, regenerate the database, and cross your fingers ok, here's what I did: 1. Upgraded MikTeX 2. Unzipped the latest cont-tmf.zip (from pragma-ade.com) into c:\tex\localtexmf 3. ran textools --fixtexmf --force (what does that do?) if needed it moves you rlocal enc/map files to their new locations, not needed if you have no commercial fonts 4. checked c:\tex\localtex\context\config. texexec.ini is newer than texexec.rme, so I left it alone. 5. ran texexec --make en nl (do I need nl? I'm exclusively English. I guess it can't hurt.) 6. noticed that cont-en.efmt was automatically relocated to c:\tex\localtex\miktex\fmt but cont-nl was not. 7. moved cont-nl.efmt to c:\tex\localtex\miktex\fmt 8. renamed them both to *.fmt (per a note in the contextgarden wiki. Is this necessary?) 9. ran texexec --make metafun 10. moved metefun.mem to c:\tex\localtex\miktex\mem 11. ran mktexlsr texexec --make (--all if you want all patterns) is normally enough, apart from moving the fmt and mem files (aren't those put at the right spot by miktex?) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
