by CSchenk2. October 2008 22:30
MiKTeX 2.5 specific packages will be removed from the primary package repository on December 30, 2008. This has some consequences for MiKTeX 2.5 users: More...
by CSchenk22. January 2007 10:32
MiKTeX 2.5 is not designed to be run on Windows Vista. But Microsoft "added some shims to Windows Vista specifically for the MiKTeX 2.5 installer. They do not resolve all the compatibility problems, but they do resolve the UAP-related issues". There remain a few issues, but all in all you will find that MiKTeX 2.5 runs reasonable well on Windows Vista. More...
by CSchenk21. January 2007 09:58
I have rebuilt all the MiKTeX binaries because new runtime libraries have been released by Microsoft. I thought it would be best to update all binaries at one go.
by CSchenk22. June 2006 03:31
This is a new feature in Beta 11:
TeX's input/output primitives can now be used for unidirectional interprocess communication by prepending a pipe symbol to the file name. More...
by CSchenk16. May 2006 05:25
pdfeTeX becomes the default TeX engine, i.e., running latex.exe will give you this banner:
This is pdfeTeX, Version 3.141592-1.30.6-2.2 (MiKTeX 2.5)
Please note that latex.exe still produces DVI output.
by CSchenk10. April 2006 23:32
A new version of the MiKTeX 2.5 Preview Document is avalailable (PDF).
by CSchenk6. March 2006 10:01
Yap is on the workbench and I can promise that support for PostScript will be improved significantly. The motto is: Every DVI document that can be viewed with a PostScript viewer (after DVI-to-PostScript) can be viewed with Yap. More...
by CSchenk12. December 2005 09:58The MiKTeX package manager currently supports only Microsoft cabinet files. This makes it a little hard (impossible) to do packaging on a non-Windows system. Therefore, I have decided to implement in MiKTeX 2.5 support for bzip2 compressed tar files.
by CSchenk9. April 2005 00:48
MiKTeX 2.5 developmet has started in December. According to the roadmap, the first step is to redesign the internal interfaces (aka refactoring). The outcome will be a portable set of components. Portable in the sense that it will be easy to build the components for other systems.
I am currently working on the core component (MiKTeX-core*.dll). The core component handles
- file searching
- running secondary processes
- reading configuration files
System-dependent features in this area are:
- reading directories
- reading/writing memory-mapped files
- threads
There are well known design patterns which help to separate system-dependent code. Implementing these design patterns is an interesting job which will keep me busy the next few months.