Re: [NTG-context] suggestion for LMTX
On 4/27/19 1:15 PM, Hans Hagen wrote: > On 4/27/2019 12:22 PM, Pablo Rodriguez wrote: >> Hi Hans, >> >> compiling the following sample with LMTX >> [...] >> \contextmark >> [...] >> outputs MKIV. >> >> Wouldn’t LMTX be a better option than LMTX? > > Why? Although there are some fundamental differences deep down, the LMTX > version has the MKIV functionality. There might be a point where we bind > a frozen version of MKIV to LuaTeX, but only when the code base becomes > too hybrid to my taste. Of course there will be functionality only > available when you use LMTX, but that is something Wolfgang and I need > to figure out wrr the interface specification. Also, Alan and I need to > deal with in the MetaFun code and documentation. At some point Taco and > Mojca might want granularity in the Wiki. We'll see. I have no clue when > users will have switched to lmtx for production anyway, as it's not > something we want to enforce. (fwfw: I run lmtx by default.) Well, it was only an idea... which seems to be wrong. Many thanks for your help, Pablo -- http://www.ousia.tk ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] suggestion for LMTX
On 4/27/2019 12:22 PM, Pablo Rodriguez wrote: Hi Hans, compiling the following sample with LMTX \starttext \contextmark \contextbanner \stoptext outputs MKIV. Wouldn’t LMTX be a better option than LMTX? Why? Although there are some fundamental differences deep down, the LMTX version has the MKIV functionality. There might be a point where we bind a frozen version of MKIV to LuaTeX, but only when the code base becomes too hybrid to my taste. Of course there will be functionality only available when you use LMTX, but that is something Wolfgang and I need to figure out wrr the interface specification. Also, Alan and I need to deal with in the MetaFun code and documentation. At some point Taco and Mojca might want granularity in the Wiki. We'll see. I have no clue when users will have switched to lmtx for production anyway, as it's not something we want to enforce. (fwfw: I run lmtx by default.) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] suggestion for LMTX
Hi Hans, compiling the following sample with LMTX \starttext \contextmark \contextbanner \stoptext outputs MKIV. Wouldn’t LMTX be a better option than LMTX? Many thanks for your help, Pablo -- http://www.ousia.tk ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] suggestion on [option=TEX]
On 02/07/2014 12:36 AM, Wolfgang Schuster wrote:
Am 06.02.2014 um 19:29 schrieb Pablo Rodriguez:
[...]
After reading the document, I think it could be achieved with:
[...]
But this doesn’t work. I must be missing something obvious.
You have to add a comma after \letterpercent. You should also be
careful with the text in the comments because commands are expanded,
e.g. take a look at the \TeX in the comment.
\setupbodyfont[dejavu]
\defineprocessor[myescape][style=\ttbf,color=gray,left={\letterpercent}]
\setuptyping[TEX][escape=myescape-{\letterpercent,}]
\starttext
\startTEX
This is \TeX\ code % and this is a \TeX\ comment.
\stopTEX
\stoptext
Sorry for not having replied before and many thanks for your help, Wolfgang.
The code works as you told me. I really appreciate your help.
I have a further question about the option=TEX to color code. This was
my original issue, but I haven’t expressed myself clearly. The question
is directed primarily to Hans.
With option=TEX, comment seems to be the only element that isn’t colored
and formatted as a whole. Other elements are formatted as a whole and
the format even extends in multiple lines.
My question here isn’t technical (unless the described behavior is a
bug). The issue is on visual coherence. At least for newbies, it would
be better to differentiate visually between regular text and commented text.
Is there any reason not to format whole comments option=TEX? (Sorry, but
I don’t understand why this is different.)
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
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
___
Re: [NTG-context] suggestion on [option=TEX]
On 02/06/2014 12:57 AM, Wolfgang Schuster wrote:
Am 05.02.2014 um 19:50 schrieb Pablo Rodriguez oi...@gmx.es:
Hi Hans,
I have the following sample:
\setuptyping[option=TEX]
\starttext
\starttyping
\input zapf % knuth
\stoptyping
\stoptext
The percent character is in bold font and gray color, but the rest of
the commented text isn’t.
[...]
http://pragma-ade.com/general/magazines/mag-1102.pdf
Many thanks for your reply, Wolfgang.
After reading the document, I think it could be achieved with:
\definefontfamily[mainface][mono][DejaVu Sans Mono]
\setupbodyfont[mainface]
\defineprocessor[myescape][style=bold,color=gray, left=\%]
\setuptyping[TEX][escape=myescape-{\%}]
\starttext
\startTEX
This is a c%omment.
% And this is another one.
\command
[with colored]
{brackets}
\stopTEX
\stoptext
But this doesn’t work. I must be missing something obvious.
What am I doing wrong here?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
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
___
Re: [NTG-context] suggestion on [option=TEX]
Am 06.02.2014 um 19:29 schrieb Pablo Rodriguez oi...@gmx.es:
On 02/06/2014 12:57 AM, Wolfgang Schuster wrote:
Am 05.02.2014 um 19:50 schrieb Pablo Rodriguez oi...@gmx.es:
Hi Hans,
I have the following sample:
\setuptyping[option=TEX]
\starttext
\starttyping
\input zapf % knuth
\stoptyping
\stoptext
The percent character is in bold font and gray color, but the rest of
the commented text isn’t.
[...]
http://pragma-ade.com/general/magazines/mag-1102.pdf
Many thanks for your reply, Wolfgang.
After reading the document, I think it could be achieved with:
\definefontfamily[mainface][mono][DejaVu Sans Mono]
\setupbodyfont[mainface]
\defineprocessor[myescape][style=bold,color=gray, left=\%]
\setuptyping[TEX][escape=myescape-{\%}]
\starttext
\startTEX
This is a c%omment.
% And this is another one.
\command
[with colored]
{brackets}
\stopTEX
\stoptext
But this doesn’t work. I must be missing something obvious.
What am I doing wrong here?
Many thanks for your help,
You have to add a comma after \letterpercent. You should also be careful with
the text in the comments because commands are expanded, e.g. take a look
at the \TeX in the comment.
\setupbodyfont[dejavu]
\defineprocessor[myescape][style=\ttbf,color=gray,left={\letterpercent}]
\setuptyping[TEX][escape=myescape-{\letterpercent,}]
\starttext
\startTEX
This is \TeX\ code % and this is a \TeX\ comment.
\stopTEX
\stoptext
Wolfgang___
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
___
[NTG-context] suggestion on [option=TEX]
Hi Hans, I have the following sample: \setuptyping[option=TEX] \starttext \starttyping \input zapf % knuth \stoptyping \stoptext The percent character is in bold font and gray color, but the rest of the commented text isn’t. My suggestion would be to apply the same color and font of the percent character to the rest of the comment. So it is easier to see that the text is a comment. And I think coloring the whole commented text (not only the percent character) is the normal practice in all text editors (if comments are colored at all). Many thanks for your help, Pablo -- http://www.ousia.tk ___ 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 ___
Re: [NTG-context] suggestion on [option=TEX]
Am 05.02.2014 um 19:50 schrieb Pablo Rodriguez oi...@gmx.es: Hi Hans, I have the following sample: \setuptyping[option=TEX] \starttext \starttyping \input zapf % knuth \stoptyping \stoptext The percent character is in bold font and gray color, but the rest of the commented text isn’t. My suggestion would be to apply the same color and font of the percent character to the rest of the comment. So it is easier to see that the text is a comment. And I think coloring the whole commented text (not only the percent character) is the normal practice in all text editors (if comments are colored at all). http://pragma-ade.com/general/magazines/mag-1102.pdf Wolfgang ___ 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 ___
Re: [NTG-context] suggestion: setups for \startitem
Am 04.07.2013 um 09:32 schrieb Thomas A. Schmitz thomas.schm...@uni-bonn.de:
Hi,
this is just a small suggestion for the interface: since a while, we've had
\startitem \stopitem. Would it be possible / feasible / interesting to add a
bit of configuration to it? I tried looking at the source. but couldn't find
anything. This minimal example explains what I mean:
\starttext
\startitemize
\item One
\item Two
\sym{$\Rightarrow$} Three
\stopitemize
\startitemize
\startitem
One
\stopitem
\startitem
Two
\stopitem
\startitem[sym=$\Rightarrow$]
Three
\stopitem
\stopitemize
\stoptext
How to achieve the result of #1 with the syntax in #2?
You have the change the definition for \startitem but I would go for a bigger
change which includes also \head, \txt etc.
To do this one could write
\startitem[alternative=head,text=…]
one could use it as synonym for \starthead or with
\startitem[alternative=symbol,text=…]
as alternative for \sym. Since references are lost with this method you can
write “reference=…” in the argument.
Wolfgang
___
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
___
Re: [NTG-context] suggestion: setups for \startitem
On 7/6/2013 12:10 PM, Wolfgang Schuster wrote: To do this one could write \startitem[alternative=head,text=…] one could use it as synonym for \starthead or with \startitem[alternative=symbol,text=…] as alternative for \sym. Since references are lost with this method you can write “reference=…” in the argument. Currently I'm a bit careful with changes as I'm using a 'copy' of context mkiv that has been adapted to a potential upcoming Lua related speedup that Luigi and I are working on. We will present most of that at the context conference (among other things). 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 - ___ 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 ___
[NTG-context] suggestion: setups for \startitem
Hi,
this is just a small suggestion for the interface: since a while, we've
had \startitem \stopitem. Would it be possible / feasible / interesting
to add a bit of configuration to it? I tried looking at the source. but
couldn't find anything. This minimal example explains what I mean:
\starttext
\startitemize
\item One
\item Two
\sym{$\Rightarrow$} Three
\stopitemize
\startitemize
\startitem
One
\stopitem
\startitem
Two
\stopitem
\startitem[sym=$\Rightarrow$]
Three
\stopitem
\stopitemize
\stoptext
How to achieve the result of #1 with the syntax in #2?
Thanks and best wishes
Thomas
___
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
___
[NTG-context] Suggestion for bibtex: command to switch between upper and lower case for title
Dear context folks, I would like to have the possibility to change between upper and lower case in titles for bibliography items, e.g. for English and German items. This is controlled by the bst-files as described in [1]. But changing these files after an update is rather annoying. Is there maybe even such a function that I do not know? Thanks, Xenia [1] http://www.ntg.nl/pipermail/ntg-context/2011/059359.html ___ 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 ___
Re: [NTG-context] Suggestion for bibtex: command to switch between upper and lower case for title
On 3/25/2013 6:10 PM, Xenia wrote:
Dear context folks,
I would like to have the possibility to change between upper and lower
case in titles for bibliography items, e.g. for English and German items.
This is controlled by the bst-files as described in [1]. But changing
these files after an update is rather annoying.
Is there maybe even such a function that I do not know?
whenever you can set a style, you can do this:
style={\setcharactercasing[WORD]}
-
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
-
___
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
___
Re: [NTG-context] Suggestion for bibtex: command to switch between upper and lower case for title
On 25.03.2013 21:05, Hans Hagen wrote:
On 3/25/2013 6:10 PM, Xenia wrote:
Dear context folks,
I would like to have the possibility to change between upper and lower
case in titles for bibliography items, e.g. for English and German items.
This is controlled by the bst-files as described in [1]. But changing
these files after an update is rather annoying.
Is there maybe even such a function that I do not know?
whenever you can set a style, you can do this:
style={\setcharactercasing[WORD]}
I don't understand what exactly that does and how to use it. Where do I
have to add this line?
___
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
___
[NTG-context] Suggestion for formula numbering
Hi, as of actual need I summed up all kinds of formula numbering - some basics are working. You can find this list on my user talk page: http://wiki.contextgarden.net/User_talk:Zenlima As I also found a note in str-math.mkiv that it needs to be rewritten and the example syntax which leaded me to confusion in the past, I worked out a suggestion for a more intuitive syntax for formula numbering. In sum it ends with: All three commands: \NR \placeformula \formualanumber will share the same attributes: * sublevel (maybe better: formulalevel or just level?) to define and concrete the (sub-)level of the formula * listlabel (maybe textlabel? the numberlabel is still needed) to add a entry in the list of formulas * reference just a classic reference in order to link to it so that the syntax is more intuitive during the writing. Also. this way the commands: placesubformula placenamedformula placenamedsubformula startstopsubformulas subformulanumber will become needless. For the why and examples please look at: http://wiki.contextgarden.net/User_talk:Zenlima#Suggestion_for_new_syntax I hope you will find parts you like and feel free to add your opinion. :-) H. ___ 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 ___
Re: [NTG-context] Suggestion
Anyway, I highly respect the ConTeXt and LuaTeX's work. But if Taco and Hans can : - use a proper regexp library (like lrexlib?), not the silly lpeg PEG are not silly at all. PEG *include* regex, but not viceversa, and it seems to have the same power of CFG, so you can build a parser for pratically anything (and you can not do this with regex) . Perhaps the reverse sentence has more sense: drop the silly (?) regex, use the new peg. For what I know the reverse side of lpeg is that a file must be loaded in memory completly. - more powerful multi columns (maybe not through gird typesetting?) Maybe columnset can do more, or we need more examples from hans . - full support of xslt:) why not xquery too? Are mkiv supposed to be a full xml processor ? A bit of xslt can be done with lpeg (and not regex), but usually it's better to prepare a xml to typeset before processing with mkiv (use the right tool for the right task). Things might be a lot better... and worse too . Things are now a lot better than before ,IMMO . -- 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 ___
Re: [NTG-context] Suggestion
On Fri, Jun 19, 2009 at 2:29 PM, luigi scarsoluigi.sca...@gmail.com wrote: Anyway, I highly respect the ConTeXt and LuaTeX's work. But if Taco and Hans can : - use a proper regexp library (like lrexlib?), not the silly lpeg PEG are not silly at all. PEG *include* regex, but not viceversa, and it seems to have the same power of CFG, so you can build a parser for pratically anything (and you can not do this with regex) . Perhaps the reverse sentence has more sense: drop the silly (?) regex, use the new peg. For what I know the reverse side of lpeg is that a file must be loaded in memory completly. Well, I don't like to know what kind of thing is superior ... micro kernel is superior than monolithic kernel, but... The key reason for this is, more people are familiar with regexp. so if you can build a 100% compatible regexp module on top of lpeg in ConTeXt, it will be ok, or even better... - more powerful multi columns (maybe not through gird typesetting?) Maybe columnset can do more, or we need more examples from hans . yes. but columnset requires more strict rules (e.g., grid stuffs) why not build a version of columnset on top of normal TeX page building? (grid can be a option, should not be a requirement) - full support of xslt:) why not xquery too? Are mkiv supposed to be a full xml processor ? No. I mean the user can have an option to convert an xml (that is, a context document) using (maybe external) xslt tool. This won't be too difficult to implement ... A bit of xslt can be done with lpeg (and not regex), a bit == far from all but usually it's better to prepare a xml to typeset before processing with mkiv (use the right tool for the right task). Things might be a lot better... and worse too . Things are now a lot better than before ,IMMO . it should be. -- 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 ___ ___ 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 ___
Re: [NTG-context] Suggestion
On Fri, Jun 19, 2009 at 9:06 AM, Yue Wang yuleo...@gmail.com wrote: On Fri, Jun 19, 2009 at 2:29 PM, luigi scarsoluigi.sca...@gmail.com wrote: Anyway, I highly respect the ConTeXt and LuaTeX's work. But if Taco and Hans can : - use a proper regexp library (like lrexlib?), not the silly lpeg PEG are not silly at all. PEG *include* regex, but not viceversa, and it seems to have the same power of CFG, so you can build a parser for pratically anything (and you can not do this with regex) . Perhaps the reverse sentence has more sense: drop the silly (?) regex, use the new peg. For what I know the reverse side of lpeg is that a file must be loaded in memory completly. Well, I don't like to know what kind of thing is superior ... micro kernel is superior than monolithic kernel, but... Wrong paragon . From *mathematical* point of view, the set of all regular languages are a subset of PEG languages . PEG are more powerful than regex --it's not an opinion, it's a fact. The key reason for this is, more people are familiar with regexp. so if you can build a 100% compatible regexp module on top of lpeg in ConTeXt, it will be ok, or even better... We already have lua for simple string manipulation, and lpeg for other stuffs . Again we don't need regex . - full support of xslt:) why not xquery too? Are mkiv supposed to be a full xml processor ? No. I mean the user can have an option to convert an xml (that is, a context document) using (maybe external) xslt tool. This won't be too difficult to implement ... hmm, external tools call for platform /SO issue ... Personally xsltproc in linux it's OK -- I don't need an integration , I prefear separations of concerns. A bit of xslt can be done with lpeg (and not regex), a bit == far from all It's enough for simple xml processing . If you need more, are you sure that you are using the right tool ? Things might be a lot better... and worse too . Things are now a lot better than before ,IMMO . it should be. It is . -- 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 ___
Re: [NTG-context] Suggestion
The key reason for this is, more people are familiar with regexp. so if you can build a 100% compatible regexp module on top of lpeg in ConTeXt, it will be ok, or even better... There *is* a regexp module on top of LPeg. It's written by Roberto Ierusalimschy, the Lua and LPeg author. Just use it if you want. http://www.inf.puc-rio.br/~roberto/lpeg/re.html Arthur ___ 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 ___
Re: [NTG-context] Suggestion
On Mon, Jun 15, 2009 at 7:55 PM, Arun Devarundv...@gmail.com wrote: Hi, You can increase the popularity of ConTeXt by eliminating the need to install Perl and Ruby. MKIV does not dependent on Perl and Ruby. I think Hans has plan to convert the MKII scripts to Lua language. Anyway, I highly respect the ConTeXt and LuaTeX's work. But if Taco and Hans can : - use a proper regexp library (like lrexlib?), not the silly lpeg - make font loading faster (by massive fontforge change or replace it with ft2+libotf. we need more efficient solution esp for big fonts) - support TeX line-break-like page break - support arbitrary text-flow maybe via mplib (example: The ultimate (?) float problem + How could a typesetting system be today? on mailing list ) - make processing conditional-aware (see two newbie questions about conditional processing on the mailing list) - fix the bug of focus=standard - more powerful multi columns (maybe not through gird typesetting?) - full support of xslt:) Things might be a lot better... ___ 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 ___ ___ 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 ___
[NTG-context] Suggestion
Hi, You can increase the popularity of ConTeXt by eliminating the need to install Perl and Ruby. ___ 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 ___
Re: [NTG-context] Suggestion
On Mon, 15 Jun 2009 17:25:32 +0530 Arun Dev arundv...@gmail.com scribit: Hi, You can increase the popularity of ConTeXt by eliminating the need to install Perl and Ruby. I dont think so. - Perl, Ruby, Python and others are installed per default on most working computers, - TeX alone has not enough power. What is needed is documentation : I dont know the meaning of [...1...][...2 ...] René B. -- ___ 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 ___
Re: [NTG-context] Suggestion
R. Bastian wrote: - Perl, Ruby, Python and others are installed per default on most working computers, - TeX alone has not enough power. luatex does have that power. What is needed is documentation : I dont know the meaning of [...1...][...2 ...] This is actually explained in chapter one of the manual: http://www.pragma-ade.com/general/manuals/cont-eni.pdf Best wishes, Taco ___ 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 ___
Re: [NTG-context] suggestion for \startitemize.
Dear John, There is no need to change anything, it is already there: \starttext \setupitemize[1][symbol=n] \setupitemize[2][symbol=a] \setupitemize[3][symbol=A] \setupitemize[4][symbol=R] \startitemize \item One \startitemize \item Second level \startitemize \item Capitals at third level \startitemize \item Roman numerals at fourth level \stopitemize \stopitemize \stopitemize \item Two \stopitemize \stoptext Kind regards Willi John R. Culleton wrote: It is possible to nest \startitemize sequences, But each level requires a different parameter in the \startitemize statement. OTOH the \orderedlist command in eplain.tex uses 1,2,3 for the outside list, then a,b,c for the first nest, roman numerals for the next nest and finally * for the innermost list. A similar automatic sequence or sequences would be useful in Context. ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
