Khaled Hosny wrote:
Maybe, we can have an infobox for the wiki pages, so we can say
something like
{{ Infobox command
| name = setupframed
| ...
}}
It also makes editing the wiki much easier (using also wiki tables
instead of HTML tables etc.)
This is definitely true, but for the export
On Tue, May 11 2010, Taco Hoekwater wrote:
It also makes editing the wiki much easier (using also wiki tables
instead of HTML tables etc.)
This is definitely true, but for the export there is a simple solution:
export as xml, feed the output through Tidy, then process with mkiv's
native xml
On Sun, May 09 2010, Hans Hagen wrote:
So, how about more extensive info. As each command has a unique reference,
the best approach is to have a separate file for each such entry. I suppose
that this can be generated from the wiki.
Hello Hans,
Yes, I also like one file per command, it's
On 10-5-2010 11:23, Peter Münster wrote:
On Sun, May 09 2010, Hans Hagen wrote:
So, how about more extensive info. As each command has a unique reference,
the best approach is to have a separate file for each such entry. I suppose
that this can be generated from the wiki.
Hello Hans,
Yes, I
\usemodule[set-11]
\loadsetups
\starttext
\showsetup{framed}
\stoptext
works -)
here too with last current
--
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context
On 10-5-2010 1:13, Taco Hoekwater wrote:
Hans Hagen wrote:
So what about:
- a new directory
http://foundry.supelec.fr/svn/contextman/context-commands;
- one tex-file per command
If you agree, I just start.
let me think about it for a while (naming and such)
I would much prefer working on
On 10-5-2010 1:51, Peter Münster wrote:
On Mon, May 10 2010, Taco Hoekwater wrote:
I would much prefer working on the wiki, then export to .tex with
a script. Having two sources for what is essentially the same
information is asking for trouble, imo.
Hello Taco,
There is not enough
Hans Hagen wrote:
On 10-5-2010 1:51, Peter Münster wrote:
On Mon, May 10 2010, Taco Hoekwater wrote:
I would much prefer working on the wiki, then export to .tex with
a script. Having two sources for what is essentially the same
information is asking for trouble, imo.
Hello Taco,
There is
Peter Münster wrote:
BTW, how can I get automatic emails for every change in
http://wiki.contextgarden.net/Reference/en/ ?
You can only get emails for pages on your watchlist.
To do that, log on to the wiki and go to 'my preferences',
there is a heading with 'Email' settings on that page.
On Mon, 10 May 2010, Peter Münster wrote:
On Mon, May 10 2010, Taco Hoekwater wrote:
I would much prefer working on the wiki, then export to .tex with
a script. Having two sources for what is essentially the same
information is asking for trouble, imo.
Hello Taco,
There is not enough
On Mon, May 10, 2010 at 03:50:40PM -0400, Aditya Mahajan wrote:
On Mon, 10 May 2010, Peter Münster wrote:
On Mon, May 10 2010, Taco Hoekwater wrote:
I would much prefer working on the wiki, then export to .tex with
a script. Having two sources for what is essentially the same
information
On Thu, May 06 2010, Idris Samawi Hamid ادريس سماوي حامد wrote:
I'm interested in an audit of all current mid-to-high-level mkiv commands,
including experimental or undocumented ones. I'm trying to come up with, as
much as possible, a set of context commands which is
mutually exclusive
On 8-5-2010 10:43, Peter Münster wrote:
Here my questions:
- How could all these efforts be shared in the most efficient way?
- Are others already working for the above project?
- Is the structure of cont-en.xml already the good choice and it only
needs some extensions for additional
2010/5/6 Idris Samawi Hamid ادريس سماوي حامد isha...@colostate.edu:
Dear gangsters,
I'm interested in an audit of all current mid-to-high-level mkiv commands,
including experimental or undocumented ones. I'm trying to come up with, as
much as possible, a set of context commands which is
On 7-5-2010 9:41, luigi scarso wrote:
Starting from it, and modifying the pdftew.web, I've produced the
lists of all macros and their meaning simple put something like
\tracingmacros3
etc at the beginning of context.tex and then rebuild the format.
I can revisit it now for luatex:
this should
On 7-5-2010 10:07, luigi scarso wrote:
2010/5/7 Hans Hagenpra...@wxs.nl:
On 7-5-2010 9:41, luigi scarso wrote:
Starting from it, and modifying the pdftew.web, I've produced the
lists of all macros and their meaning simple put something like
\tracingmacros3
etc at the beginning of context.tex
Hans Hagen wrote:
On 7-5-2010 10:07, luigi scarso wrote:
2010/5/7 Hans Hagenpra...@wxs.nl:
On 7-5-2010 9:41, luigi scarso wrote:
Starting from it, and modifying the pdftew.web, I've produced the
lists of all macros and their meaning simple put something like
\tracingmacros3
etc at the
if you have problems
http://www.logosrl.it/luatex/cont-en.log.bz2
--
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context
Idris, maybe this is what you are looking for:
http://www.pragma-ade.com/general/qrcs/setup-en.pdf
And at the same time I have a question. Does this list of commands is
the most recent? Is it generated automaticaly?
2010/5/7 Idris Samawi Hamid ادريس سماوي حامد isha...@colostate.edu:
Hi Luigi,
Hi,
On Fri, 07 May 2010 08:04:06 -0600, Marius mariau...@gmail.com wrote:
Idris, maybe this is what you are looking for:
http://www.pragma-ade.com/general/qrcs/setup-en.pdf
That list is not complete. For example, in open type we have a lot of
fontfeature commands in mkiv only. The sourse is
On Fri, May 7, 2010 at 4:05 PM, Marius mariau...@gmail.com wrote:
Idris, maybe this is what you are looking for:
http://www.pragma-ade.com/general/qrcs/setup-en.pdf
And at the same time I have a question. Does this list of commands is
the most recent? Is it generated automaticaly?
If I
On 7-5-2010 4:05, Marius wrote:
the most recent? Is it generated automaticaly?
yes
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel:
Dear gangsters,
I'm interested in an audit of all current mid-to-high-level mkiv commands,
including experimental or undocumented ones. I'm trying to come up with,
as much as possible, a set of context commands which is
mutually exclusive
jointly exhaustive.
By 'mutually exlcusive' in
23 matches
Mail list logo
