Hi, Currently most mails on the list about mkiv and luatex concern installation and fonts. This is ok since quite some code is related to that. The next couple of months other (sub)systems will be activated (or discovered by users since quite some stuff is already there). - reading from other media: reading from zip files is possible, reading from e.g. http also if you have curl installed - color support: mkiv will use attributes; this works already on my machine; other features (outline) and such will follow this route - spacing, vertical as well as horizontal (inter character spacing, french punctuation), it's there but needs integration - indexing: is already using lua, needs to be tested and we need tables for languages - numbering lines etc: work in progress - verbatim: new pretty printers will show up (i expect users to step in once we have the api ready) - synchronization of text streams, multiple text streams etc ... work in progress - sectioning and list handling, needs some rework for mkii too - debugging and error handling: there (try \showdebuginfo \page or maybe \overloaderror \crap); we need a way to refresh browser windows automatically - runtime feature toggling and font extensions: work in progress - etc etc maybe we should set up a wiki page where users can make a wishlist for fundamental features cq. exploring features under construction 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 -----------------------------------------------------------------
Hans Hagen wrote:
Hi,
Currently most mails on the list about mkiv and luatex concern installation and fonts. This is ok since quite some code is related to that. The next couple of months other (sub)systems will be activated (or discovered by users since quite some stuff is already there).
- reading from other media: reading from zip files is possible, reading from e.g. http also if you have curl installed
- color support: mkiv will use attributes; this works already on my machine; other features (outline) and such will follow this route
- spacing, vertical as well as horizontal (inter character spacing, french punctuation), it's there but needs integration
- indexing: is already using lua, needs to be tested and we need tables for languages
- numbering lines etc: work in progress
- verbatim: new pretty printers will show up (i expect users to step in once we have the api ready)
- synchronization of text streams, multiple text streams etc ... work in progress
- sectioning and list handling, needs some rework for mkii too
- debugging and error handling: there (try \showdebuginfo \page or maybe \overloaderror \crap); we need a way to refresh browser windows automatically
- runtime feature toggling and font extensions: work in progress
- etc etc
maybe we should set up a wiki page where users can make a wishlist for fundamental features cq. exploring features under construction
Hans
How about the support for Chinese ? Will it be enhanced or just remains the same with ConTeXt ? And can mkiv produce pdf files in which the Chinese characters can be selected and copied to other place ? Thanks.
fdu.xiaojf@gmail.com wrote:
How about the support for Chinese ? Will it be enhanced or just remains the same with ConTeXt ?
sure, a matter of time ... i need to implement the right methods best prepare some samples (opentype.truetype font, utf-8 based input, etc)
And can mkiv produce pdf files in which the Chinese characters can be selected and copied to other place ?
indeed 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 -----------------------------------------------------------------
maybe we should set up a wiki page where users can make a wishlist for fundamental features cq. exploring features under construction
Hans
Yes, at least for me. -- luigi ---------------------------------------------------------------- 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
On Mon, 13 Aug 2007, Hans Hagen wrote:
Hi,
Currently most mails on the list about mkiv and luatex concern installation and fonts. This is ok since quite some code is related to that. The next couple of months other (sub)systems will be activated (or discovered by users since quite some stuff is already there).
This is great.
- sectioning and list handling, needs some rework for mkii too
There needs to be better support for section separators. Right now, section separators work for section heads, but modifying separtors for referencing sections is very ugly. Here is what IEEE publications want, which is hard to do right now: While placing section heads, do not use parent number. So sections are I, II, III, etc., subsections are A, B, C, etc., subsubsections are \alpha), \beta), etc. But when you are referencing sections, you need to have sepators. So a subsection needs to be referred to as I-B.\gamma. Right now, there is no easy way to do this.
- debugging and error handling: there (try \showdebuginfo \page or maybe \overloaderror \crap); we need a way to refresh browser windows automatically
This is wonderful. Is the error format configurable? Do you plan to support something other than XML output? HTML display of errors is great, but for my workflow, I want something tightly integrated with the editor. Vim allows that, provided I can write rules which tell vim how tex errors look. Currently, it is really hard to write something that captures all the tex errors. Hopefully, writing something for an xml error will be easy. But if it is possible, the easiest will be "C" compiler type errors: "Error on line xx of file yy:" With the errortype-c (or something like that) flag to pdftex, for some errors yo get this, but for others you do not (File ended while scanning \startbuffer, etc).
maybe we should set up a wiki page where users can make a wishlist for fundamental features cq. exploring features under construction
My other set of requests is about two column design. The \startcolumns ... \stopcolumns works, but does not support footnotes on each column. With columnsets (with a bit of tweaking) you can get two column footnotes, but columsets do not seem to like the rest of my setup (equation run over the top and bottom marins). I have never managed to nail it down precisely. And then there are floats. topfloats should be always below a chapter or a title, and checking indentation after top and bottom floats. Let me know when you get to columns and floats, and I can provide some details, and so some testing. Aditya
participants (4)
-
Aditya Mahajan -
fdu.xiaojf＠gmail.com -
Hans Hagen -
luigi scarso