Hi, You can increase the popularity of ConTeXt by eliminating the need to install Perl and Ruby.
On Mon, 15 Jun 2009 17:25:32 +0530
Arun Dev
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. --
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
On Mon, Jun 15, 2009 at 7:55 PM, Arun Dev
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 ___________________________________________________________________________________
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
On Fri, Jun 19, 2009 at 2:29 PM, luigi scarso
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 ___________________________________________________________________________________
On Fri, Jun 19, 2009 at 9:06 AM, Yue Wang
On Fri, Jun 19, 2009 at 2:29 PM, luigi scarso
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
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
participants (6)
-
Arthur Reutenauer
-
Arun Dev
-
luigi scarso
-
R. Bastian
-
Taco Hoekwater
-
Yue Wang