Re: [NTG-context] upto current
On 19 mars 2013, at 19:47, Aditya Mahajan wrote: > […]Although most active users use ConTeXt standalone and are willing to > update frequently, TL still plays an important role in introducing new users > to ConTeXt. An experienced TeX user who wants to try ConTeXt is more likely > to try ConTeXt distributed as part of TL rather than ConTeXt standalone. When > there are serious bugs with ConTeXt TL, it gives the impression that ConTeXt > is not a mature macro package. Hi, To support what suggests Aditya, I would like to say that the main issue with the current state of ConTeXt in TeXLive (either mkii or mkiv) is that most « lambda » users of TeX whom I know in the mathematics world and in accademia, that is: --- users who are not familiar with what should be changed in TeXLive, --- users who don't even know TeX and LaTeX are not synonyms, --- users who don't know that there exist another environments and macro packages for typesetting tex-files, --- users who don't know that using ConTeXt one can do better typesetting, and that it has better features, all those users are not going to install a stand alone ConTeXt. They would use TeXLive, they would try everything in it, but all they want is to write a paper and typeset it with a TeX package with a single command (or in the case of Mac users, from within TeXShop or another editor). Most of them do not even know where TeXLive sits on their computer, and they don't know how to install something new. Unfortunately, the ConTeXt in TeXLive does not work out of the box: the user has to issue a few commands before he can typeset a file with ConTeXt, either mkii or mkiv (for instance on my installation of TeXLive, after having issued a few commands, which I don't remember right now, I can use ConTeXt with LuaTeX, that is mkiv, but I cannot use mkii). For my part I have been advocating ConTeXt among my colleagues (especially for course materials and books, since submitting a paper to a journal is essentially impossible if it is a ConTeXt file). Most of them agree that ConTeXt gives a much better result, but when it comes to how to use ConTeXt from TeXLive they are afraid and don't go further. For some of them I have installed a stand alone ConTeXt, but most of them do not update their installation, since they would not use the most recent features or improvements (for most of day to day typesettings, when one does not use complexe features, even a beta version is sufficiently stable for such users). So my pledge is this: make any stable version of ConTeXt in TeXLive so that it works and typesets a tex-file « out of the box », without needing to issue any command other than: context myfile.tex This is the case with LaTeX inside TeXLive, and so I cannot see any strong reason for ConTeXt not having the same behavior. Best regards: OKs ___ 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] upto current
On Tue, 19 Mar 2013, Hans Hagen wrote: On 3/19/2013 7:47 PM, Aditya Mahajan wrote: So, I'd like to suggest that for a few weeks before the TL freeze, we do a ConTeXt-beta freeze with only changes being bug fixes. We can try .. I have no plans for drastic changes (and no time for it the next weeks anyway). We depend on users to notice things that are broken (let's forget about things that could be improved): fonts not rendering, files not being found, crashes due to typos, etc. As long as you don't have too much time, we should be OK :) Sometimes the trouble is that you make changes at a faster rate than the rate at which we users can test it! Aditya ___ 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] next beta
On 3/19/2013 11:46 PM, Sietse Brouwer wrote: i.e. we already had CL CM and CR, so CT is new .. should be wikified. The wiki [1] describes these \C* commands: \CR color is applied to the background of the text and the remaining space on the right; \CC color is applied to the background of the text only; \CM color is applied to the background of the text and the remaining space on both sides; \CL color is applied to the background of the text and the remaining space on the left. [1] http://wiki.contextgarden.net/Tabulate What does CT do differently than CC? It's not quite clear from the example. CT is the text color (foreground so to say) - 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] next beta
> i.e. we already had CL CM and CR, so CT is new .. should be wikified. The wiki [1] describes these \C* commands: \CR color is applied to the background of the text and the remaining space on the right; \CC color is applied to the background of the text only; \CM color is applied to the background of the text and the remaining space on both sides; \CL color is applied to the background of the text and the remaining space on the left. [1] http://wiki.contextgarden.net/Tabulate What does CT do differently than CC? It's not quite clear from the example. Cheers, Sietse ___ 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] next beta
Hi
The next beta will have this (I needed it for a manual):
\starttext
\starttabulate[||CL{darkred}|CM{darkgreen}CT{white}|CR{darkblue}||]
\NC first \NC left \NC middle \NC
right \NC last \NC \NR
\NC first \NC \color[white]{left} \NC middle \NC
\color[white]{right} \NC last \NC \NR
\NC first \NC left \NC middle \NC
right \NC last \NC \NR
\stoptabulate
\stoptext
i.e. we already had CL CM and CR, so CT is new .. should be wikified.
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
___
Re: [NTG-context] Bug in \column
Al 18/03/13 22:34, En/na Wolfgang Schuster ha escrit:
Am 18.03.2013 um 19:32 schrieb Xan :
Hi,
I found a possibly bug (I attached the doc). With bigskip twocolumns work but
with \column it does not. That is, with the diff:
98c98
< \bigskip
---
%\bigskip
100c100
< %\column
---
\column
it does not work: the last exercise is shown in the first column.
The default value to fill the column (\vskip\textheight) does only work
when you start the columns at the top of the page but not when you start
them in the middle of page. When this fixed value is replaced with
\pagegoal it does also work in the middle of the page.
% \installcolumnbreakmethod \s!multicolumn \v!yes
% {\vskip\textheight
%\penalty-200 % we can mark and intercept this
%\vskip-\textheight}
\unprotect
\installcolumnbreakmethod \s!multicolumn \v!yes
{\vskip .5\pagegoal
\penalty-200 % we can mark and intercept this
\vskip-.5\pagegoal}
\protect
\starttext
\startcolumns
a
\column
b
\stopcolumns
\page
\blank[force,12cm]
\startcolumns
a
\column
b
\stopcolumns
\stoptext
Wolfgang
Can you modify it for working? By the user perspective it's an annoying
bug. A clean command should not produce that, isn't it?
Xan.
___
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] upto current
On 3/19/2013 7:47 PM, Aditya Mahajan wrote: On Tue, 19 Mar 2013, Hans Hagen wrote: One these days there will be a first iteration of this years 'current' release. This has to do with the texlive code freeze. Are there any plans to do an actual development freeze a few weeks before the TL code freeze to ensure that the TL version is not beta quality. The code freeze is in about a month. In principle Mojca/Taco can use the current beta as starting point for testing. I have no clue if there are issues but as context is rather independent there shouldn't be many I have just one (flat) source tree here so freezing current also means freezing beta. Afaik Mojca never figured out how to have a current alongside a beta in her git setup, otherwise someone could push fixes from beta into the current branch. I have no time to look into that kind of stuff. Although most active users use ConTeXt standalone and are willing to update frequently, TL still plays an important role in introducing new users to ConTeXt. An experienced TeX user who wants to try ConTeXt is more likely to try ConTeXt distributed as part of TL rather than ConTeXt standalone. When there are serious bugs with ConTeXt TL, it gives the impression that ConTeXt is not a mature macro package. Sure. Although mkiv, certainly at that time, was a bit more beta, even the then 'current' -) As anecdotal evidence, I used ConTeXt TL for my most recent article for tugboat. There were some serious bugs in ConTeXt TL (multi-column footnotes not working, marking styles not working, wrong font scaling, etc.) and I had to struggle to get everything to work correctly. Most of these bugs were fixed in the latest beta. But if I were a new user, I would not have the patience to download and test the latest beta when a supposedly stable release has serious bugs. Last year we froze too soon. In retrospect we should have pushed the beta (also because we froze about the time the new luatex came out). In retrospect frozen could have been less frozen then. We even had the weird situation that the generic font code was frozen in current but the last versions were taken for non context use instead of the frozen code. But that's out of our control anyway. So, I'd like to suggest that for a few weeks before the TL freeze, we do a ConTeXt-beta freeze with only changes being bug fixes. We can try .. I have no plans for drastic changes (and no time for it the next weeks anyway). We depend on users to notice things that are broken (let's forget about things that could be improved): fonts not rendering, files not being found, crashes due to typos, etc. 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 ___
Re: [NTG-context] upto current
On Tue, 19 Mar 2013, Hans Hagen wrote: One these days there will be a first iteration of this years 'current' release. This has to do with the texlive code freeze. Are there any plans to do an actual development freeze a few weeks before the TL code freeze to ensure that the TL version is not beta quality. Although most active users use ConTeXt standalone and are willing to update frequently, TL still plays an important role in introducing new users to ConTeXt. An experienced TeX user who wants to try ConTeXt is more likely to try ConTeXt distributed as part of TL rather than ConTeXt standalone. When there are serious bugs with ConTeXt TL, it gives the impression that ConTeXt is not a mature macro package. As anecdotal evidence, I used ConTeXt TL for my most recent article for tugboat. There were some serious bugs in ConTeXt TL (multi-column footnotes not working, marking styles not working, wrong font scaling, etc.) and I had to struggle to get everything to work correctly. Most of these bugs were fixed in the latest beta. But if I were a new user, I would not have the patience to download and test the latest beta when a supposedly stable release has serious bugs. So, I'd like to suggest that for a few weeks before the TL freeze, we do a ConTeXt-beta freeze with only changes being bug fixes. Aditya ___ 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] upto current
Hi,
One these days there will be a first iteration of this years 'current'
release. This has to do with the texlive code freeze. As usual the
current is paired with a version of luatex and mplib, of which there
also will be a frozen version soon. This year we also have luajittex.
Among the biggest differences between this and the previous current are:
- More low level tex code has been made mkiv compliant. This had a side
effect of introducing bugs. As expected more flexibility an potential
for extensions has not resulted in slower runs.
- Some mechanisms have been rewritten, some even from scratch (a new
table mechanism, multi columns). We tried to remain compatible but where
possible inconsistencies have been removed.
- Of course bugs have been removed also thanks to Wolfgang and others.
Like before users have been very patient and willing to test. The
updated wiki and good examples that show up on sites are an indication
that mkiv has mostly replaced mkii.
- There is some new math magic under the hood. We switched to tex gyre
and latin modern open math as defaults.
- Lua code has been optimized: leaner, meaner, less dependent, version
5.2 etc. There is more helper code available pending future extensions
to mkiv. Basic code can be used in stock Lua.
- The 2013 current performs significantly faster than previous versions
and (certainly) on complex jobs mkiv outperforms mkii. Lots of time went
into identifying and removing bottlenecks.
- When luajittex is used, thanks to the faster virtual machine, mkiv
benefits a lot: 20-490% faster runs are possible. I usually test with
manuals I'm working on, but a nice base test is \dorecurse {1000}
{test\page} which now runs 20% faster with stock luatex and 50% faster
with luajittex.
- The font database generator is made more efficient and unless you do a
full reload take hardly any time to regenerate after an update. This
means that updating betas is more convenient. In general all logging to
the terminal and log file is faster due to several optimizations.
- Some mtx scripts have been extended, some more will show up.
- We ship a set of advanced scite lexers (tex, lua, cld, mp, w, xml,
etc. plus a context setup) that can serve as benchmark for syntax
highlighting context code. To some extent this also determines the way
mkiv is coded.
I probably forgot a lot. After the current is done, we can start
thinking of what to do next. Here are some thoughts:
- Improving the output routines. This is non-trivial. Maybe I'll rewrite
the columnsets code. The mixed column figure placement can be improved too.
- Some mechanism will get support for setups alongside commands, like
sections and list related mechanisms already has.
- Parts of the xml handling can be cleaned up, although the current code
performs rather well already.
- Support for sql might get more integrated into the core (a side effect
of projects I'm working on).
- I might pickup the metatex thread: a generic base with special purpose
subsets of code. It might not be worth the trouble, but it's good to
have a proper dependency tree.
- I will continue making some of the Lua code more generic (maybe by
introducing some additional namespaces).
- I need to cleanup all the s-* files: namespaces, mkii->mkiv, etc. A
tedious job. Clean up all mkiv presentation styles. (Something for rainy
days or cold winter nights with stacks of new cd's to make that effort
bearable.)
- Play with a partial css simulator (relates to export), but only when
I'm really bored or need it (getting css itself right is already enough
of a challenge).
- Pick up on ideas with respect to math dictionaries. Add some support
for breaking large math formulas. Kick out more old code.
- Play with alternative par builders, i.e. finally add the mkiv Lua
parbuilder that I have around for years into the distribution. This
relates to a drastic cleanup of expansion code in the luatex front- and
backend.
- Include some third party modules into the core distribution.
- Remove bottlenecks in mkiv where possible (user input is needed for
this).
Then there are the documents:
- Update the xml descriptions (Wolfgang has been working on this, and
there is the wiki).
- Finish the 'cld' manual (mostly done).
- Update the 'xml' mkiv manual (doable, maybe users have examples too).
- Finish the updated 'mathml' manual (done but needs checking but then I
might overhaul the whole lot again).
- Finish the more technical 'mkiv font' manual (tedious job but okay).
- Pickup the 'stylistics' manual (also nice to do but a bit tedious).
- Turn 'hybrid' into a more finished document (the second part of the
history of mkiv/luatex).
- Add more to the 'about' series (the third part).
Of course this is too ambitious but it's good to remind myself that some
work needs to be done. And ... users might have ideas of what needs to
be done as well.
Hans
-
Re: [NTG-context] [***SPAM***] What am I doing wrong?
Am 19.03.2013 um 13:24 schrieb d.henman :
>
>
> While reading the ConTeXt Manual I tried the following two commands, which
> didn't work.
> Here is the sample souce.
>
> \starttext
> First line.
> %\hskip With text here, this causes an compile time error.
> \hskip3em Indented?\crlf
> \hskip 3em Indented?\crlf
> \hskip3cm Indented?\crlf
>
> %\sym{on} This causes an error.
> %\sym{$\diamond$} This causes an error.
> %\sym{$\diamondsuit$} This causes an error.
>
> Last line.
> \stoptext
>
> What happened to \hskip and \sym ? Or what am I doing wrong?
1.a: Tex ignores a skip at the begin of a paragraph but when you force
horizontal mode with \dontleavehmode it works.
\dontleavehmode\hskip …
1.b: ConTeXt provides the \hspace command which can be used instead of \hskip.
\definehspace[myspace][3em]
\starttext
\dontleavehmode\hspace[myspace] …
\stoptext
2: The \sym command was removed but this shouldn’t be a problem because you can
use either a itemize environment with the \txt command or use a a description
command.
> One further question. I tried nopping \before, \after, \between, and the
> none, and joinedup option but could not suppress white space occurring after
> \startitemize and the 1st \item. I tried looking in the garden as well, but
> had no luck. I believe th
> e information is in there but I couldn't find it after a hour or so. So
> please inform me as to how can tell ConTeXt how much space, including none,
> to place between the an item header (or none) and the list???
Provide a example for this.
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] [***SPAM***] What am I doing wrong?
While reading the ConTeXt Manual I tried the following two commands, which
didn't work.
Here is the sample souce.
\starttext
First line.
%\hskip With text here, this causes an compile time error.
\hskip3em Indented?\crlf
\hskip 3em Indented?\crlf
\hskip3cm Indented?\crlf
%\sym{on} This causes an error.
%\sym{$\diamond$} This causes an error.
%\sym{$\diamondsuit$} This causes an error.
Last line.
\stoptext
What happened to \hskip and \sym ? Or what am I doing wrong?
One further question. I tried nopping \before, \after, \between, and the none,
and joinedup option but could not suppress white space occurring after
\startitemize and the 1st \item. I tried looking in the garden as well, but had
no luck. I believe th
e information is in there but I couldn't find it after a hour or so. So
please inform me as to how can tell ConTeXt how much space, including none, to
place between the an item header (or none) and the list???
I'd appreciate the assistance in learning who to do this.
___
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] \recurselevel inside \bTABLE\eTABLE
Am 17.03.2013 um 22:58 schrieb Willi Egger :
> Thank you again!
>
> Sorry for misspelling your name Aditya!
>
> I was surprised, that the solution of Wolfgang does not work, with
> \expanded{\recurselevel}, though it sounds reasonable. Still all rows are
> marked 0. Alan's suggestion gives me the desired result.
See my change, you have to put \expanded before \bTD because when you write
\bTD \expanded{\recurselevel} \eTD
context will store “\expanded{\recurselevel}” which is expanded
after all cells are created and \recurselevel has its default value.
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
___
