[NTG-context] problem with t-gnuplot.tex
Using the new beta from context-minimal
This is LuaTeX, Version beta-0.75.0-2013030308 (rev 4589)
\write18 enabled.
(/Users/jin/pkgs/ConTeXt/tex/texmf-context/tex/context/base/cont-yes.mkiv
ConTeXt ver: 2013.03.20 21:07 MKIV fmt: 2013.3.21 int: english/english
system > 'cont-new.mkiv' loaded
(/Users/jin/pkgs/ConTeXt/tex/texmf-context/tex/context/base/cont-new.mkiv
system > beware: some patches loaded from cont-new.mkiv
)
system > files > jobname 'bulk_trans', input 'bulk_trans', result
'bulk_trans'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
(bulk_trans.tex
resolvers > modules > 'gnuplot' is loaded
(/Users/jin/pkgs/ConTeXt/tex/texmf-modules/tex/context/third/gnuplot/t-gnuplot.tex
loading > Gnuplot module
! Undefined control sequence.
log
system > tex > error on line 99 in file
/Users/jin/pkgs/ConTeXt/tex/texmf-modules/tex/context/third/gnuplot/t-gnuplot.tex:
Undefined control sequence ...
...:= \@@GNUPLOT@term@context@linejoin
; gp_use_dashed :=
\@@GNUP...
\meta_start_extensions ...extensions("#1",\!!bs #2
\!!es )}
l.99 \stopMPextensions
?
This happens with context running on a file generated by gnuplot 4.6.1. I
have been using context in the texlive 2012 without any problem.
___
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] synctex problem
On 3/20/2013 6:24 PM, Ulrike Fischer wrote: Is it possible to tell context to create a .synctex file instead of a .synctex.gz? I've added --synctex=unzipped (or zipped or 1 or -1 or anything boolean). No upload yet. (Or alternativly does someone know how to get sumatra (on windows) to handle a synctex.gz?) 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] Breaking ligatures
On Wed, 20 Mar 2013 14:22:31 -0600, Hans Hagen wrote:
quite a claim ... afaik devanagari also needs them
Ah, interesting!
anyhow, just don't enable ligatures if in doubt (some fonts have
language dependent ligatures) ... it's somewhat arbitrary to have only
'f' related ligs anyway
On Wed, 20 Mar 2013 14:22:35 -0600, Wolfgang Schuster
wrote:
\definefontfeature[liga][liga=yes]
\starttext
fi {\feature[-][liga]fi \feature[+][liga]fi}
\stoptext
This is just for having a control to make sure the test file I'm preparing
for a \feature wiki entry is actually working right, so naturally I can't
use \feature for the control :-)
But that is a nifty example, Wolfgang, so I may include that one on the
wiki too!
Thanks Hans, Wolfgang, and
Best wishes
Idris
--
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
___
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] date handling maltreated?
On 3/20/2013 4:26 PM, H. van der Meer wrote: I strongly ask that ConTeXt abstains from changing the definition of \month and reverts to the exact result as given by plain TeX, i.e. a number in the range [1-12]. Because the change makes it impossible to do calculations on the month. well, it has been the case for ages ... other commands also have a different meaning, like \language, and \unexpanded is actually in tex speak \protected (but we had an \unexpanded long before that one showed up) and \\expanded is a macro in context and a primitive in tex ... etc as Wolfgang pointed out: use \normaldate 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] etexshow and generation of cont-en.xlm (cont-XX.xml)?
On 3/20/2013 5:22 PM, Jonathan Barchi wrote:
Is that scite code free software? I'd love to take a look at how you generate
the files for it, and/or how its lexer is implemented.
it's all in context/data/scite (if only because I use it on a daily basis)
I'm still figuring this part out. Emacs is quite modular, so I'm not
sure what the
best approach is yet. AUCTEX implements syntax highlighting internally, in
a sub-package called font-latex (that does work reasonably well for ConTeXt
too), but there is also more sophisticated support for LaTeX that doesn't cross
over to context.
best start from scratch .. too many differences .. the easy way is just
to color symbols special
red: {}$
green: \. \
blue: []()#=<>"
yellow: %^_&-+/`|
that should be doable i guess
next figure out how to read in list with known \commands
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] next beta
On 3/20/2013 5:36 PM, Jonathan Barchi wrote:
Just to be clear: CT provides an alternate method to colorize the
text, instead of
using the standard \color[foo]{bar} - right? There is already a
section on using
the \color command to colorize the text, so I want to make sure I'm adding this
correctly as a complementary mechanism, or fix it if I misunderstood.
indeed, a quick way to color a whole column
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] Breaking ligatures
Am 20.03.2013 um 21:12 schrieb Idris Samawi Hamid ادريس سماوي حامد
:
> Dear Knights,
>
> What is the canonical way to break a ligature in MkIV? The canonical TeX way,
> e.g.
>
> f{}i
>
> does not work if the feature liga=yes.
>
> The zero-width joiner or non-joiner will do it but that seems ad hoc or
> abusive ;-) since those are really for cursive scripts like Arabic and Syriac.
\definefontfeature[liga][liga=yes]
\starttext
fi {\feature[-][liga]fi \feature[+][liga]fi}
\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
___
Re: [NTG-context] Breaking ligatures
On 3/20/2013 9:12 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
Dear Knights,
What is the canonical way to break a ligature in MkIV? The canonical TeX
way, e.g.
f{}i
that's more a side effect of the old engine where lig building happened
interwoven with the parser (optimization) while in luatex this is nicely
separated (cleaner) you can put a kern in between but then of course you
wont get kerning with the other chars
does not work if the feature liga=yes.
The zero-width joiner or non-joiner will do it but that seems ad hoc or
abusive ;-) since those are really for cursive scripts like Arabic and
Syriac.
quite a claim ... afaik devanagari also needs them
anyhow, just don't enable ligatures if in doubt (some fonts have
language dependent ligatures) ... it's somewhat arbitrary to have only
'f' related ligs anyway
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] Breaking ligatures
Dear Knights,
What is the canonical way to break a ligature in MkIV? The canonical TeX
way, e.g.
f{}i
does not work if the feature liga=yes.
The zero-width joiner or non-joiner will do it but that seems ad hoc or
abusive ;-) since those are really for cursive scripts like Arabic and
Syriac.
Best wishes
Idris
--
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
___
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] framedtext and margin
Immediately downloaded the latest beta. Great! And just in time. Works not only in my minimal example, but even in the more complex environment in which I am using it. Hans van der Meer On 20 mrt. 2013, at 19:35, Wolfgang Schuster wrote: > > Am 20.03.2013 um 19:29 schrieb "H. van der Meer" : > >> As can be seen in the following example, within an itemized list the >> framedtext sticks out to the right, instead of having its right edge aligned >> with the outer ones. >> Is there a simple remedy or is it an unwanted effect? >> I would like the right edges line up perfectly. > > This was fixed a few days ago. > > 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 > ___ ___ 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] Subjects on this list - general request
Hi Robert, I see no advantage in your suggestion. just search the subject. As for the [***Spam***] that is inroduce by mail servers. A user should maybe remove it to avoid it. But a nuisance, yes, a problem no. regards Keith. Am 20.03.2013 um 16:12 schrieb Robert Blackstone : > Dear all, > Considering all complaints about the difficulties to find, in the Garden, or > in the NTG mail archive, answers to specific problems, wouldn't it be a good > idea to ask everybody to clearly state the subject of their message, > preferably starting with the most important keyword, and in particular to > avoid (no subject) or [***SPAM***], and similar things as subjects. > Also, if you forgive me, subjects like "upto current" or "Bug in \column" > are not really helpful when on tries to search in the archive for a solution > to a specific problem. In the last-mentioned example, wouldn't "\column, Bug > in - " or even "\column, Bug in \column" be better? > More specific subject titles in the mails might save some of us hours of > unfruitful searching and lots of teeth grinding. > This is probably not the first request on this topic but, if so, I thought it > would do no harm to repeat it. > > Thanks in advance. > > Best regards, > > Robert Blackstone > > ___ > 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 > ___ ___ 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] framedtext and margin
Am 20.03.2013 um 19:29 schrieb "H. van der Meer" : > As can be seen in the following example, within an itemized list the > framedtext sticks out to the right, instead of having its right edge aligned > with the outer ones. > Is there a simple remedy or is it an unwanted effect? > I would like the right edges line up perfectly. This was fixed a few days ago. 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] framedtext and margin
As can be seen in the following example, within an itemized list the framedtext sticks out to the right, instead of having its right edge aligned with the outer ones.Is there a simple remedy or is it an unwanted effect?I would like the right edges line up perfectly. Hans van der Meer \starttext\startframedtext[width=local]\input tufte\stopframedtextBefore list.\startitemize\startitem item one\stopitem\startitem item two\startframedtext[width=local]\input tufte\stopframedtext\stopitem\startitem item three\stopitem\stopitemizeAfter list.\startframedtext[width=local]\input tufte\stopframedtext\stoptext frameplace.pdf Description: Adobe PDF document ___ 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
OOOsss!
Do I have to kill myself! ;-)))
Would like to have a reference for this kind of stuff!
regards
Keith.
Am 20.03.2013 um 10:40 schrieb Hans Hagen :
>
> For Wolfgangs eyes only:
>
> \installcolumnbreakmethod \s!multicolumn \v!yes
> {\penalty\c_page_mix_break_forced\relax}
>
> Maybe that one works ok.
>
___
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
Am 20.03.2013 um 09:25 schrieb Marcin Borkowski : > Dnia 2013-03-20, o godz. 09:12:21 > "Keith J. Schultz" napisał(a): > >> [snip, snip] >> My suggestion would be to have garden have a manuals download >> area where one can get the up to date manuals from Pragma and >> where one can discern how old the others are. It should be also, easy >> to find. >> >> regards >> Keith. > > That is quite true, though not that easy. In essence, I think someone > would have to be paid for tracking the mailing list and updating > manuals. AFAIK, Sietse does a great job updating the wiki, but the > wiki is not necessarily the easiest thing to go to for newbies (as you > have noticed). > > It is quite obvious for me that Pragma won't fund such an enterprise > (not that I'm claiming it should - of course not!). I think the only > body which might do it is either TUG, either some other UG - but then, I > guess they are already funding LaTeX3 (which is kind of a competitor - > albeit friendly - to ConTeXt), either font projects (TeX Gyre!), which > are quite beneficial to the ConTeXt ecosystem, too. I do not get you here. Garden just needs a little redesigning or more correctly cleaning up. I see no need for funding. I am not into wikis or I would offer to do it. regards Keith. ___ 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] synctex problem
Is it possible to tell context to create a .synctex file instead of a .synctex.gz? (Or alternativly does someone know how to get sumatra (on windows) to handle a synctex.gz?) -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ 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] etexshow and generation of cont-en.xlm (cont-XX.xml)?
Dnia 2013-03-20, o godz. 12:22:55 Jonathan Barchi napisał(a): > BNF grammar descriptions, but some reading suggests that this can't > be done for *TeX. Don't listen to that. While it's technically true, (a) most users don't redefine catcodes or internal macros anyway (and imho there are fewer reasons to do such hacking in ConTeXt than in LaTeX) and (b) for the sake of syntax highlighting/parsing by external tools, you have to assume some sanity anyway (so that you don't have to reimplement full TeX instead of writing some parser). That said, I know little about regular languages, BNF notations etc. (with the exception of some _practical_ experience with regexen), so I'm not sure about what I've written above. But I would guess that if you make some (reasonable) assumptions about catcodes and command syntax, writing a BNF style grammar for (at least some part of) ConTeXt might be pretty doable. Regards, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Adam Mickiewicz University ___ 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 Wed, Mar 20, 2013 at 4:43 AM, Hans Hagen wrote:
> On 3/20/2013 8:14 AM, Keith J. Schultz wrote:
>>
>> Hi Hans, All,
>>
>> I find this nomenclature confusing and a little confusing from a design
>> standpoint!
>>
>> 1) Color of the text background should be separate from the rest
>>of the cell background
>>
>> 2) the names should reflect to what they apply
>>
>> That said we should have:
>> CTBGC == Cell text background color
>> CTC == Cell text color
>>
>> CBGC == Cell background color
>>or
>> CC == Cell color
>>
>> CBGCR == Cell background color in the space right of text
>> CBGCM == Cell background color in space middle of cell( above
>> below text)
>> CBGCL == Cell background color in the space right of text
>>
>> True, these are a lot of options/parameters, yet it offers the most
>> flexibility and
>> a cleaner interface. Furthermore, one can understand the names of the
>> parameters.
>
>
> preamble scanning is already quite tricky and there was already CR CM CL so
> adding CT was a few lines of extra code
>
> (i will probably make a key/val based variant some day but that is no fun
> either ... 10 lines of setup per table instead of a one line preeamble)
>
> (and i'm forbidden to fundamentally change an important mechanism like
> tabulate right now as for sure it will break some things)
Further, the declaration of a tabulate environment already tends to be pretty
tight on space, so IMO a little bit of obscurity in these parameters - provided
they stay documented - is an acceptable price to pay for keeping the keys to
two letters (three would probably be OK too, esp. for less frequently used
ones).
>> Another, advantage is that one could and at a later point a feature for
>> inverting the
>> color of the text according cell color and/or text background color.
>>
>> regards
>> Keith.
>>
>> Am 19.03.2013 um 23:46 schrieb Sietse Brouwer :
>>
i.e. we already had CL CM and CR, so CT is new .. should be wikified.
I've added this to the wiki.
Just to be clear: CT provides an alternate method to colorize the
text, instead of
using the standard \color[foo]{bar} - right? There is already a
section on using
the \color command to colorize the text, so I want to make sure I'm adding this
correctly as a complementary mechanism, or fix it if I misunderstood.
- Jon
>>> 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,
>>>
>>
>>
>> ___
>> 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
>>
>> ___
>>
>
>
> --
>
> -
> 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
> ___
___
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] Subjects on this list - general request
I would agree with the (no subject) or SPAM titles, but if your search tool can't tell the difference between "\column, Bug in - " - "\column, Bug in \column" and "Bug in \column" then you probably need to find a new search tool. I subscribe to the list in non-digest format, e.g. I get every email. I used to get it in digest, but I found that made my searching tougher. I use gmail and have all the list messages skip my inbox and go directly to a tag. This has helped a ton! -Mica On Wed, Mar 20, 2013 at 8:12 AM, Robert Blackstone < blackstone.rob...@gmail.com> wrote: > Dear all, > > Considering all complaints about the difficulties to find, in the Garden, > or in the NTG mail archive, answers to specific problems, wouldn't it be > a good idea to ask everybody to clearly state the subject of their message, > preferably starting with the most important keyword, and in particular to > avoid (no subject) or [***SPAM***], and similar things as subjects. > > Also, if you forgive me, subjects like "upto current" or "Bug in \column" > are not really helpful when on tries to search in the archive for a > solution to a specific problem. In the last-mentioned example, wouldn't > "\column, > Bug in - " or even "\column, Bug in \column" be better? > > More specific subject titles in the mails might save some of us hours of > unfruitful searching and lots of teeth grinding. > > This is probably not the first request on this topic but, if so, I thought > it would do no harm to repeat it. > > Thanks in advance. > > > Best regards, > > > Robert Blackstone > > > > ___ > 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 > > ___ > ___ 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] date handling maltreated?
On 20 mrt. 2013, at 16:45, Wolfgang Schuster
wrote:
>
> Am 20.03.2013 um 16:40 schrieb H. van der Meer :
>
>> Trying to do some date and time processing myself, I ran into problems
>> caused by ConTeXt makeing it incompatibel with the original plain TeX itself!
>>
>> In the TeX-book, Appendix B one finds
>>
>> (Some parameters are set by TeX itself as it runs, so it is inappropriate to
>> initialize them: \time, \day, \month, and year are established at the
>> beginning of a job; ..
>>
>>
>> Now the results in ConTeXT with a minimal example, put into the log for
>> easier copying into the mail:
>> \starttext
>> \writestatus{}{\meaning\date -> \date}
>> \writestatus{}{\meaning\day -> \the\day}
>> \writestatus{}{\meaning\month -> \month WHY NOT monthname?}
>> \writestatus{}{\meaning\year -> \the\year}
>> \writestatus{}{\meaning\time -> \the\time}
>> \stoptext
>>
>> Result:
>> > \protected macro:->\dodoubleempty \syst_converters_date -> \date
>> > \day-> 20
>> > macro:#1->\ctxcommand {monthname(#1)}-> \labeltext {unknown}HY NOT
>> > monthname?
>> > \year-> 2013
>> > \time-> 989
>>
>> Plain TeX here gives:
>> \message{\meaning\day -> \the\day}
>> \message{\meaning\month -> \the\month}
>> \message{\meaning\year -> \the\year}
>> \message{\meaning\time -> \the\time}
>> \end
>>
>> Result:
>> (./plaindates.tex \day-> 20 \month-> 3 \year-> 2013 \time-> 991 )
>>
>> I strongly ask that ConTeXt abstains from changing the definition of \month
>> and reverts to the exact result as given by plain TeX, i.e. a number in the
>> range [1-12]. Because the change in ConTeXt makes it impossible to do
>> calculations on the month.
>>
>> Furthermore I encountered problems with defining expanded macros for
>> currentdate and currenttime. This seems impossible to accomplish, at least
>> in a simple manner. See the results from these to examples:
>> \edef\thedate{\currentdate}\writestatus{}{\meaning\thedate -> \thedate}
>> \edef\thetime{\currenttime}\writestatus{}{\meaning\thetime -> \thetime}
>> giving:
>> > macro:->\currentdate -> \currentdate
>> > macro:->\currenttime -> \currenttime
>>
>> This is most unhappy, because one really should be able to put the
>> expansions of these macros somewhere.
>> I hope the next beta will have solutions for these problems.
>
> TeX primitives are available under \normal…
>
> Wolfgang
>
That is most unfortunate. Why not keep compatibility with plain TeX where
possible? I see that \time, \day and \year have been left untouched. So why
messing up \month? Sorry for the expression, no offense meant, but in my eyes
this is unnecessary tinkering with established macros.
What speaks against keeping \month as is? And doing the translation through
\monthname? It looks to me even more transparent and it could use the \language
for translation.
No, this shouldn't have happened and I strongly urge that the original meaning
returns to ConTeXt.
___
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] etexshow and generation of cont-en.xlm (cont-XX.xml)?
On Mon, Mar 18, 2013 at 7:16 PM, Hans Hagen wrote: > On 3/18/2013 11:35 PM, Jonathan Barchi wrote: >> >> Hi all, >> >> I'm using the emacs package etexshow to provide a quick ConTeXt >> command reference in EMACS. This utility parses the interface file >> cont-en.xml (for english, in my case) and uses the contents to provide >> a basic dictionary of available commands. >> >> In the documentation for etexshow, there is a reference to being able >> to generate a complete interface description (the aforementioned xml >> file) like so: >> >> ";; There is still an xml-file shipped with this code. Usually you would >> ;; generate the xml-file with 'texexec'ing the file setupe.tex. Then you >> ;; will get the cont-en.xml file that can (could) be used as an input for >> ;; this etexshow. But for now, this won't work. It will work rsn." >> >> It is not clear whether that file (setupe.tex or setup.tex) is/was >> supposed to be shipped with etexshow or was supposed to be a part of >> context. I've searched and found a few references to this problem, but >> never a definitive answer, so if anyone knows the answer to these >> questions I would love to know!! >> >> 1. Is the referenced setup(e).tex a file that was previously shipped >> with ConTeXt - presumably mkii since the author refers to texexec - or >> would this be something the author would have included with etexshow >> itself? >> >> 2. Is the interface file, e.g. cont-en.xml, auto-generated from all of >> the defined macros in ConTeXt, or is that file hand-written as >> metadata to accompany the source-code definitions? > > > the xml file is the master file (but I admit that it's a bit behind) > > if you only need the commands then the mult-def.lua files are better, also > because they contain low level commands and primitives (it's what I use to > generate files for scite where we have a rather advanced lexer) I'll take a look at those files, thanks! Is that scite code free software? I'd love to take a look at how you generate the files for it, and/or how its lexer is implemented. >> 3. Since self-documentation is a goal of the project, is it possible >> to generate something akin to the interface file that presents a >> snapshot of all commands known to context at a given time, for use in >> things like etexshow or other tools? If so, is it possible to do this >> with modules loaded to see what they additionally define? > > > we can add a --emacs to mtx-interfaces.lua if something other than xml is > needed .. so, what does emacs need? I'm still figuring this part out. Emacs is quite modular, so I'm not sure what the best approach is yet. AUCTEX implements syntax highlighting internally, in a sub-package called font-latex (that does work reasonably well for ConTeXt too), but there is also more sophisticated support for LaTeX that doesn't cross over to context. There are more general solutions for lexing, like semantic, which might be the better way to go. Semantic has an internal port of bison that can use BNF grammar descriptions, but some reading suggests that this can't be done for *TeX. It can also be fed tags by a regexp parser or an external utility like ctags. I'm quite new to all this, so if anyone out on the mailing list with more experience wants to jump in with advice or corrections I'm all ears! I'm also working on my dissertation, so time is limited (at least for the next couple months). - Jon >> Thanks in advance for any help! I'm hoping to use any information I >> get to update etexshow, if possible, and maybe update the ConTeXt >> support in AUCTEX as well. I think it would be really cool if AUCTEX >> could reach out at compile or run time and pull in macro definitions >> from the installed environment, for example. > > > 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] date handling maltreated?
Am 20.03.2013 um 16:40 schrieb H. van der Meer :
> Trying to do some date and time processing myself, I ran into problems caused
> by ConTeXt makeing it incompatibel with the original plain TeX itself!
>
> In the TeX-book, Appendix B one finds
>
> (Some parameters are set by TeX itself as it runs, so it is inappropriate to
> initialize them: \time, \day, \month, and year are established at the
> beginning of a job; ..
>
>
> Now the results in ConTeXT with a minimal example, put into the log for
> easier copying into the mail:
> \starttext
> \writestatus{}{\meaning\date -> \date}
> \writestatus{}{\meaning\day -> \the\day}
> \writestatus{}{\meaning\month -> \month WHY NOT monthname?}
> \writestatus{}{\meaning\year -> \the\year}
> \writestatus{}{\meaning\time -> \the\time}
> \stoptext
>
> Result:
> > \protected macro:->\dodoubleempty \syst_converters_date -> \date
> > \day-> 20
> > macro:#1->\ctxcommand {monthname(#1)}-> \labeltext {unknown}HY NOT
> > monthname?
> > \year-> 2013
> > \time-> 989
>
> Plain TeX here gives:
> \message{\meaning\day -> \the\day}
> \message{\meaning\month -> \the\month}
> \message{\meaning\year -> \the\year}
> \message{\meaning\time -> \the\time}
> \end
>
> Result:
> (./plaindates.tex \day-> 20 \month-> 3 \year-> 2013 \time-> 991 )
>
> I strongly ask that ConTeXt abstains from changing the definition of \month
> and reverts to the exact result as given by plain TeX, i.e. a number in the
> range [1-12]. Because the change in ConTeXt makes it impossible to do
> calculations on the month.
>
> Furthermore I encountered problems with defining expanded macros for
> currentdate and currenttime. This seems impossible to accomplish, at least in
> a simple manner. See the results from these to examples:
> \edef\thedate{\currentdate}\writestatus{}{\meaning\thedate -> \thedate}
> \edef\thetime{\currenttime}\writestatus{}{\meaning\thetime -> \thetime}
> giving:
> > macro:->\currentdate -> \currentdate
> > macro:->\currenttime -> \currenttime
>
> This is most unhappy, because one really should be able to put the expansions
> of these macros somewhere.
> I hope the next beta will have solutions for these problems.
TeX primitives are available under \normal…
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] date handling maltreated?
Trying to do some date and time processing myself, I ran into problems caused
by ConTeXt makeing it incompatibel with the original plain TeX itself!
In the TeX-book, Appendix B one finds
(Some parameters are set by TeX itself as it runs, so it is inappropriate to
initialize them: \time, \day, \month, and year are established at the beginning
of a job; ..
Now the results in ConTeXT with a minimal example, put into the log for easier
copying into the mail:
\starttext
\writestatus{}{\meaning\date -> \date}
\writestatus{}{\meaning\day -> \the\day}
\writestatus{}{\meaning\month -> \month WHY NOT monthname?}
\writestatus{}{\meaning\year -> \the\year}
\writestatus{}{\meaning\time -> \the\time}
\stoptext
Result:
> \protected macro:->\dodoubleempty \syst_converters_date -> \date
> \day-> 20
> macro:#1->\ctxcommand {monthname(#1)}-> \labeltext {unknown}HY NOT monthname?
> \year-> 2013
> \time-> 989
Plain TeX here gives:
\message{\meaning\day -> \the\day}
\message{\meaning\month -> \the\month}
\message{\meaning\year -> \the\year}
\message{\meaning\time -> \the\time}
\end
Result:
(./plaindates.tex \day-> 20 \month-> 3 \year-> 2013 \time-> 991 )
I strongly ask that ConTeXt abstains from changing the definition of \month and
reverts to the exact result as given by plain TeX, i.e. a number in the range
[1-12]. Because the change in ConTeXt makes it impossible to do calculations on
the month.
Furthermore I encountered problems with defining expanded macros for
currentdate and currenttime. This seems impossible to accomplish, at least in a
simple manner. See the results from these to examples:
\edef\thedate{\currentdate}\writestatus{}{\meaning\thedate -> \thedate}
\edef\thetime{\currenttime}\writestatus{}{\meaning\thetime -> \thetime}
giving:
> macro:->\currentdate -> \currentdate
> macro:->\currenttime -> \currenttime
This is most unhappy, because one really should be able to put the expansions
of these macros somewhere.
I hope the next beta will have solutions for these problems.
Hans van der Meer
___
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] date handling maltreated?
Sorry, not yes finished, accidently sent away too soon. Hans van der Meer On 20 mrt. 2013, at 16:26, "H. van der Meer" wrote: > Trying to do some date and time processing myself, I ran into problems caused > by ConTeXt makeing it incompatibel with the original plain TeX itself! > > In the TeX-book, Appendix B one finds > ___ 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] date handling maltreated?
Trying to do some date and time processing myself, I ran into problems caused
by ConTeXt makeing it incompatibel with the original plain TeX itself!
In the TeX-book, Appendix B one finds
(Some parameters are set by TeX itself as it runs, so it is inappropriate to
initialize them: \time, \day, \month, and year are established at the beginning
of a job; ..
Now the results in ConTeXT with a minimal example, put into the log for easier
copying into the mail:
\starttext
\writestatus{}{\meaning\date -> \date}
\writestatus{}{\meaning\day -> \the\day}
\writestatus{}{\meaning\month -> \month WHY NOT monthname?}
\writestatus{}{\meaning\year -> \the\year}
\writestatus{}{\meaning\time -> \the\time}
\stoptext
Result:
> \time-> \time
> \protected macro:->\dodoubleempty \syst_converters_date ->
\date
> \day-> 20
> macro:#1->\ctxcommand {monthname(#1)}-> \labeltext
{unknown}RROR
> \year-> 2013
> \time-> 982
I strongly ask that ConTeXt abstains from changing the definition of \month and
reverts to the exact result as given by plain TeX, i.e. a number in the range
[1-12]. Because the change makes it impossible to do calculations on the month.
Hans van der Meer
___
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] Subjects on this list - general request
Dear all, Considering all complaints about the difficulties to find, in the Garden, or in the NTG mail archive, answers to specific problems, wouldn't it be a good idea to ask everybody to clearly state the subject of their message, preferably starting with the most important keyword, and in particular to avoid (no subject) or [***SPAM***], and similar things as subjects. Also, if you forgive me, subjects like "upto current" or "Bug in \column" are not really helpful when on tries to search in the archive for a solution to a specific problem. In the last-mentioned example, wouldn't "\column, Bug in - " or even "\column, Bug in \column" be better? More specific subject titles in the mails might save some of us hours of unfruitful searching and lots of teeth grinding. This is probably not the first request on this topic but, if so, I thought it would do no harm to repeat it. Thanks in advance. Best regards, Robert Blackstone ___ 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] date problem
Am 20.03.2013 um 15:29 schrieb "Meer H. van der" :
> I see. But this is not working too. Following your suggestion I now get:
> \edef\thisdate{\ctxcommand{currentdate("month, ,day, ,
> year","\currentlanguage")}}\writestatus{***}{\meaning\thisdate}
> *** > macro:->\labeltext {march} 20 2013
> The problem is essentially the same.
\starttext
\writestatus{***}{\cldcontext{os.date("\letterpercent Y\space\letterpercent
m\space\letterpercent d")}}
\stoptext
> I am most unhappy with this, because fixing the current date in some macro
> shouldn't be impossible.
\starttext
\writestatus{***}{\number\normalyear \space \number\normalmonth \space
\number\normalday}
\stoptext
> And why all those extra ,s in month, ,day, , year?
This should be “month,space,day,space,year”, “space” in this list is a keywords
to add a space between the entries.
> I would suggest that besides \currentdate one should be able to also use
> \currentdate[month][day][year][language],
> \currentdate[day][mont][year][language],etc. And then be able to store the
> expansion in a macro. Is it possible to incorporate this in the next beta?
http://wiki.contextgarden.net/Command/date
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] Endnotes - How to place all endnotes in a separate chapter?
Dear list, How can I collect, in a separate (unnumbered) chapter at the end, or in the Backmatter, of a book, all endnotes from the previous chapters, as lists per chapter (for example in sections in this chapter "Notes", with, preferably, the chaptertitles as sectiontitles of that chapter) My setupfile contains, on the subject of notation, only: \setupnotation[endnote][way=bychapter,bodyfont=10pt] and each chapter now ends with: \placenotes[endnote][height=\textheight] which neatly gives a list at the end of each chapter. Thanks in advance for any advice. Best regards, Robert Blackstone___ 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] (no subject)
> This is more of a follow-up question than an answer: wouldn't
> \blank[nowhite] be better?
Quite possibly. When I read "I want to be able to adjust the vertical
white space" my mind went towards adding whitespace instead of
removing it, but that was just an assumption. I admit that I didn't
look up the original thread. :-)
Cheers,
Sietse
On 20 March 2013 13:09, Marcin Borkowski wrote:
> Dnia 2013-03-20, o godz. 12:35:11
> Sietse Brouwer napisał(a):
>
>> non-null wrote:
>> > I want to be able to adjust the vertical white space between the
>> > list introduction text and the list of items. How can this be
>> > accomplished?
>>
>> Probably \setupitemgroup[itemize][before={\blank[0em]}] will do what
>> you want. For a complete list of parameters:
>> http://wiki.contextgarden.net/Command/setupitemgroup
>
> This is more of a follow-up question than an answer: wouldn't
> \blank[nowhite] be better?
>
> Best,
>
> --
> Marcin Borkowski
> http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
> Adam Mickiewicz University
> ___
> 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
> ___
___
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] date problem
I see. But this is not working too. Following your suggestion I now get:
\edef\thisdate{\ctxcommand{currentdate("month, ,day, ,
year","\currentlanguage")}}\writestatus{***}{\meaning\thisdate}
*** > macro:->\labeltext {march} 20 2013
The problem is essentially the same.
I am most unhappy with this, because fixing the current date in some macro
shouldn't be impossible.
And why all those extra ,s in month, ,day, , year?
I would suggest that besides \currentdate one should be able to also use
\currentdate[month][day][year][language],
\currentdate[day][mont][year][language],etc. And then be able to store the
expansion in a macro. Is it possible to incorporate this in the next beta?
By the way, the \time and \currenttime pose the same problem, here even
\rawtime seems nonexistent.
Hans van der Meer
On 20 mrt. 2013, at 15:11, Wolfgang Schuster
wrote:
>
> Am 20.03.2013 um 14:52 schrieb Meer H. van der :
>
>> One step further, thanks.
>> But why does
>> \edef\thedate{\rawdate[]}\writestatus{***}{\meaning\thedate}
>> result in
>> ** > macro:->unknown march 2013
>> instead of 20 march 2013?
>
> Provide a *working* minimal example because when I run this example
>
> \starttext
> \rawdate[]
> \stoptext
>
> I get “march unknown, 2013” as output.
>
>
> When I use now (instead of \currentlanguage you can also use a language tag,
> e.g. "nl")
>
> \starttext
> \ctxcommand{currentdate("month, ,day, , year","\currentlanguage")}
> \stoptext
>
> I get as output “March 20 2013”. The problem with \rawdate is that no
> language is passed
> and context doesn’t convert the labels for the month/years and also the day
> results in
> a default string, i.e. it produces the “unknown” string.
>
> 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
> ___
___
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] date problem
Am 20.03.2013 um 14:52 schrieb Meer H. van der :
> One step further, thanks.
> But why does
> \edef\thedate{\rawdate[]}\writestatus{***}{\meaning\thedate}
> result in
> ** > macro:->unknown march 2013
> instead of 20 march 2013?
Provide a *working* minimal example because when I run this example
\starttext
\rawdate[]
\stoptext
I get “march unknown, 2013” as output.
When I use now (instead of \currentlanguage you can also use a language tag,
e.g. "nl")
\starttext
\ctxcommand{currentdate("month, ,day, , year","\currentlanguage")}
\stoptext
I get as output “March 20 2013”. The problem with \rawdate is that no language
is passed
and context doesn’t convert the labels for the month/years and also the day
results in
a default string, i.e. it produces the “unknown” string.
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] date problem
One step further, thanks.
But why does
\edef\thedate{\rawdate[]}\writestatus{***}{\meaning\thedate}
result in
** > macro:->unknown march 2013
instead of 20 march 2013?
Hans van der Meer
On 20 mrt. 2013, at 14:39, Wolfgang Schuster
wrote:
>
> Am 20.03.2013 um 14:26 schrieb H. van der Meer :
>
>> There is a nasty problem when defining the \date.
>>
>> First approach:
>> *** > macro:->\date
>> \def\thedate{\date}\writestatus{***}{\meaning\thedate}
>> Alas, I get lateron a luatex error on \date:
>> ! LuaTeX error [string "\directlua "]:1: invalid escape sequence near '\d'.
>>
>> Second approach, use \edef to get an expanded value.
>> \edef\thedate{\date}\writestatus{***}{\meaning\thedate}
>> *** > macro:->\date
>> Alas, the date is still the unexpanded macro and not something like 20 march
>> 2013.
>>
>> How to?
>
> All commands with optional argument aren’t expandable and \date *has* two
> optional argument.
>
> To get now the date in the output you can either use the expandable
> \rawdate[] command (the brackets are necessary) or you use
> \ctxcommand{currentdate(,)} (language can also be
> "false").
>
> 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
> ___
___
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] date problem
Am 20.03.2013 um 14:26 schrieb H. van der Meer :
> There is a nasty problem when defining the \date.
>
> First approach:
> *** > macro:->\date
> \def\thedate{\date}\writestatus{***}{\meaning\thedate}
> Alas, I get lateron a luatex error on \date:
> ! LuaTeX error [string "\directlua "]:1: invalid escape sequence near '\d'.
>
> Second approach, use \edef to get an expanded value.
> \edef\thedate{\date}\writestatus{***}{\meaning\thedate}
> *** > macro:->\date
> Alas, the date is still the unexpanded macro and not something like 20 march
> 2013.
>
> How to?
All commands with optional argument aren’t expandable and \date *has* two
optional argument.
To get now the date in the output you can either use the expandable \rawdate[]
command (the brackets are necessary) or you use
\ctxcommand{currentdate(,)} (language can also be
"false").
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] date problem
There is a nasty problem when defining the \date.
First approach:
*** > macro:->\date
\def\thedate{\date}\writestatus{***}{\meaning\thedate}
Alas, I get lateron a luatex error on \date:
! LuaTeX error [string "\directlua "]:1: invalid escape sequence near '\d'.
Second approach, use \edef to get an expanded value.
\edef\thedate{\date}\writestatus{***}{\meaning\thedate}
*** > macro:->\date
Alas, the date is still the unexpanded macro and not something like 20 march
2013.
How to?
Hans van der Meer
___
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] (no subject)
Dnia 2013-03-20, o godz. 12:35:11
Sietse Brouwer napisał(a):
> non-null wrote:
> > I want to be able to adjust the vertical white space between the
> > list introduction text and the list of items. How can this be
> > accomplished?
>
> Probably \setupitemgroup[itemize][before={\blank[0em]}] will do what
> you want. For a complete list of parameters:
> http://wiki.contextgarden.net/Command/setupitemgroup
This is more of a follow-up question than an answer: wouldn't
\blank[nowhite] be better?
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
___
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] (no subject)
non-null wrote:
> I want to be able to adjust the vertical white space between the list
> introduction text and the list of items. How can this be
> accomplished?
Probably \setupitemgroup[itemize][before={\blank[0em]}] will do what
you want. For a complete list of parameters:
http://wiki.contextgarden.net/Command/setupitemgroup
\starttext
\setupitemgroup[itemize][before={\blank[0em]}]
\starttext
\startitemize[packed]
asdf asdf asdf asdf
\item asdf
\item asdf
\item asdf
\stopitemize
\stoptext
\stoptext
___
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] Mixed columns
Hi, after the problem with the \column command with the normal columns environment I tried if the original problem can be solved with mixed columns. While the \column command works there a unwanted space appeared at the begin of the second column. In the following example you can see space from the \blank in the first column is ignored while in the second column it appears in the output. \starttext \showframe \startmixedcolumns \blank text \column \blank text \stopmixedcolumns \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 ___
Re: [NTG-context] Bug in \column
Am 20.03.2013 um 10:40 schrieb Hans Hagen :
> For Wolfgangs eyes only:
>
> \installcolumnbreakmethod \s!multicolumn \v!yes
> {\penalty\c_page_mix_break_forced\relax}
>
> Maybe that one works ok.
No it doesn’t work, the penalty is ignored and text from the first column
appears in the second column because the columns are balanced.
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] next beta (tabulate)
On 3/20/2013 8:24 AM, Alan BRASLAU wrote:
On Tue, 19 Mar 2013 23:46:35 +0100
Sietse Brouwer wrote:
[1] http://wiki.contextgarden.net/Tabulate
There is \starttabulate and \starttable.
I understand that they use different mechanisms, even though their
syntax are parallel. The wiki page [1] warns against the use of macros
in tabulate, but this seems a bit obscure. Also, Tables_Overview
recommends tabulate for simple tables and flags both table and tables as
depreciated. I hesitate to add this information at the top of the wiki
pages: Tabulate, Table and Tables as I am not clear about the status
of these three mechanisms...
The obscurity comes from the fact that a tabulate is typeset multipass
so macro definitions might have changed between first and last columns /
rows. This is probably less of an issu ein mkiv.
One question: is it possible to span columns using tabulate as in
table: \Use{n}[format]{data}?
no. okay, I sometimes cheat: \rlap{data} works out well
-
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
On 3/20/2013 10:28 AM, Wolfgang Schuster wrote:
Am 19.03.2013 um 20:50 schrieb Xan :
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?
I have to agree that the current situation with the \column command isn’t
perfect but each solution has it’s own problems.
The example below uses three different definitions for the \column command, the
first and third result in a empty column when there is to much text in the
first column while the second definition ignores the command and balances the
text of both columns.
\starttext \showframe
% Default method
\blank[force,12cm]
\startcolumns
\dorecurse{16}{a\par}
\column
b
\stopcolumns
\page
% Method 1
\unprotected\installcolumnbreakmethod \s!multicolumn \v!yes
{\scratchdimen\dimexpr\pagegoal/2\relax
\vskip \scratchdimen
\penalty-200 % we can mark and intercept this
\vskip-\scratchdimen}
\blank[force,12cm]
\startcolumns
\dorecurse{16}{a\par}
\column
b
\stopcolumns
\page
% Method 2
\unprotected\installcolumnbreakmethod \s!multicolumn \v!yes
{\scratchdimen\dimexpr\pagegoal/2+\lineheight\relax
\vskip \scratchdimen
\penalty-200 % we can mark and intercept this
\vskip-\scratchdimen}
\blank[force,12cm]
\startcolumns
\dorecurse{16}{a\par}
\column
b
\stopcolumns
\stoptext
For Wolfgangs eyes only:
\installcolumnbreakmethod \s!multicolumn \v!yes
{\penalty\c_page_mix_break_forced\relax}
Maybe that one works ok.
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 3/20/2013 10:27 AM, Mojca Miklavec wrote: On Wed, Mar 20, 2013 at 9:40 AM, Hans Hagen wrote: On 3/20/2013 7:05 AM, Otared Kavian wrote: 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. if it doesn't work that way something is wrong ... mtxrun (to which context is an alias) is selfcontained and will generate its own file database and then context will generat eits own format (even after an update) so ... Yes, this seems a bit weird. ConTeXt in TeX Live 2012 might have had bugs, but it should have at least worked out of the box. It is possible that your copy actually became problematic *after* issuing those few commands. In particular, running "texexec --make en" would create a new format at a different location than the system would put it. As a consequence all further updates become shadowed by the old manually created format and you would need to run "texexec --make en" manually for every update, else MKII becomes broken (not that there were many updates, but this could serve as an example). this is indeed an issue ... recently I spend a few hours tracking down an issue just to find out that for whatever reason a file had ended up in a local path .. hard to track down .. one should also keep in mind that tds is set up in a way that more or less assumes that there are no files in the tree with the same name (at least not in the same category) because at some point the order of dir entries start to matter 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
Am 19.03.2013 um 20:50 schrieb Xan :
> 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?
I have to agree that the current situation with the \column command isn’t
perfect but each solution has it’s own problems.
The example below uses three different definitions for the \column command, the
first and third result in a empty column when there is to much text in the
first column while the second definition ignores the command and balances the
text of both columns.
\starttext \showframe
% Default method
\blank[force,12cm]
\startcolumns
\dorecurse{16}{a\par}
\column
b
\stopcolumns
\page
% Method 1
\unprotected\installcolumnbreakmethod \s!multicolumn \v!yes
{\scratchdimen\dimexpr\pagegoal/2\relax
\vskip \scratchdimen
\penalty-200 % we can mark and intercept this
\vskip-\scratchdimen}
\blank[force,12cm]
\startcolumns
\dorecurse{16}{a\par}
\column
b
\stopcolumns
\page
% Method 2
\unprotected\installcolumnbreakmethod \s!multicolumn \v!yes
{\scratchdimen\dimexpr\pagegoal/2+\lineheight\relax
\vskip \scratchdimen
\penalty-200 % we can mark and intercept this
\vskip-\scratchdimen}
\blank[force,12cm]
\startcolumns
\dorecurse{16}{a\par}
\column
b
\stopcolumns
\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
___
Re: [NTG-context] upto current
On Wed, Mar 20, 2013 at 9:40 AM, Hans Hagen wrote: > On 3/20/2013 7:05 AM, Otared Kavian wrote: > >> 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. > > if it doesn't work that way something is wrong ... mtxrun (to which context > is an alias) is selfcontained and will generate its own file database and > then context will generat eits own format (even after an update) so ... Yes, this seems a bit weird. ConTeXt in TeX Live 2012 might have had bugs, but it should have at least worked out of the box. It is possible that your copy actually became problematic *after* issuing those few commands. In particular, running "texexec --make en" would create a new format at a different location than the system would put it. As a consequence all further updates become shadowed by the old manually created format and you would need to run "texexec --make en" manually for every update, else MKII becomes broken (not that there were many updates, but this could serve as an example). Mojca ___ 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/20/2013 9:12 AM, Keith J. Schultz wrote: Hi Hans, All, The biggest crux in using ConTeXt is its documentation. True, things have gotten a lot better in the past year! Yet, there is no ONE definitive place to get comprehensive and EASY to find documentation. 1) Garden is really not that easy to navigate 2) Garden is loaded with a mixture of mkii and mkiv and it is not always clear if the page one is on is for mkii or mkiv or quite outdated. i wonder how easy it is to split that ... we could move mkii stuff to s separate place (or always at the bottom below a "MKII" subtitle) 3) PRAGMA does have up to date manuals. 4) These manuals are quite unfinished in many parts, as are all many of the older manuals. Very frustrating Most of the old manuals are not that faulty. Maybe incomplete with respect to the latest features, but most in it should still work. With respect to unfinished: yesterday i wondered if I should put the intermediate but unfinished font manual on the website but it looks like I can better not do that. 5) The newer manuals should be part of the standalone. ( I hate going online to look for a manual when it should be installed already) Up to others. 6) Reference manuals are fine for the advanced user, but for the beginner or intermediate they are not much help. Especially, if if one does not understand TeX, or Typesetting, and one really does not need to use all those options. That's up to users ... it has been said before, but this is where the internet backfires: a lot of tex tutorials started out as articles i.e. users writing down experiences. I simply have no more time left to write down more than I do now. My suggestion would be to have garden have a manuals download area where one can get the up to date manuals from Pragma and where one can discern how old the others are. It should be also, easy to find. So maybe you can help Mojca with that .. someone needs to do it and keep doing it (descriptions, copies cq. links, 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] (no subject)
Am 20.03.2013 um 03:22 schrieb non-null : > Here is a simple example: > > \starttext > \startitemize[1,packed] Introduction text to the list below. > \item some item text1 > \item some item text2 > \stopitemize > > I want to be able to adjust the vertical white space between the list > introduction text and the list of items. How can this be > accomplished? \starttext Introduction text to the list below. \startitemize[1,packed,joinedup] \item some item text1 \item some item text2 \stopitemize 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] next beta
On 3/20/2013 8:14 AM, Keith J. Schultz wrote: Hi Hans, All, I find this nomenclature confusing and a little confusing from a design standpoint! 1) Color of the text background should be separate from the rest of the cell background 2) the names should reflect to what they apply That said we should have: CTBGC == Cell text background color CTC == Cell text color CBGC == Cell background color or CC == Cell color CBGCR == Cell background color in the space right of text CBGCM == Cell background color in space middle of cell( above below text) CBGCL == Cell background color in the space right of text True, these are a lot of options/parameters, yet it offers the most flexibility and a cleaner interface. Furthermore, one can understand the names of the parameters. preamble scanning is already quite tricky and there was already CR CM CL so adding CT was a few lines of extra code (i will probably make a key/val based variant some day but that is no fun either ... 10 lines of setup per table instead of a one line preeamble) (and i'm forbidden to fundamentally change an important mechanism like tabulate right now as for sure it will break some things) Another, advantage is that one could and at a later point a feature for inverting the color of the text according cell color and/or text background color. regards Keith. Am 19.03.2013 um 23:46 schrieb Sietse Brouwer : 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, ___ 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 ___ -- - 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 3/20/2013 7:05 AM, Otared Kavian wrote: 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. if it doesn't work that way something is wrong ... mtxrun (to which context is an alias) is selfcontained and will generate its own file database and then context will generat eits own format (even after an update) so ... 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
Dnia 2013-03-20, o godz. 09:12:21 "Keith J. Schultz" napisał(a): > Hi Hans, All, > > > The biggest crux in using ConTeXt is its documentation. > True, things have gotten a lot better in the past year! > > Yet, there is no ONE definitive place to get comprehensive > and EASY to find documentation. > > 1) Garden is really not that easy to navigate > 2) Garden is loaded with a mixture of mkii and mkiv > and it is not always clear if the page one is on is for > mkii or mkiv or quite outdated. > > 3) PRAGMA does have up to date manuals. > 4) These manuals are quite unfinished in many parts, > as are all many of the older manuals. > > Very frustrating > > 5) The newer manuals should be part of the standalone. > ( I hate going online to look for a manual when it >should be installed already) > > 6) Reference manuals are fine for the advanced user, but for > the beginner or intermediate they are not much help. > Especially, if if one does not understand TeX, or > Typesetting, and one really does not need to use all those options. > > My suggestion would be to have garden have a manuals download > area where one can get the up to date manuals from Pragma and > where one can discern how old the others are. It should be also, easy > to find. > > regards > Keith. That is quite true, though not that easy. In essence, I think someone would have to be paid for tracking the mailing list and updating manuals. AFAIK, Sietse does a great job updating the wiki, but the wiki is not necessarily the easiest thing to go to for newbies (as you have noticed). It is quite obvious for me that Pragma won't fund such an enterprise (not that I'm claiming it should - of course not!). I think the only body which might do it is either TUG, either some other UG - but then, I guess they are already funding LaTeX3 (which is kind of a competitor - albeit friendly - to ConTeXt), either font projects (TeX Gyre!), which are quite beneficial to the ConTeXt ecosystem, too. And there are books - but then, you have to pay for them (which also seems right, since it is quite an undertaking to write a book, especially about a "moving target" like ConTeXt...) So basically: unless there is some significant funding, I'm rather a skeptic. Regards, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Adam Mickiewicz University ___ 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
Hi All, Am 20.03.2013 um 07:05 schrieb Otared Kavian : > > 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, > [snip, snip] > 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). I find it interesting, that here and in other posts that is mention that publishers are reluctant to accept ConTeXt files. O.K. Understandable! But, my experience has been that they will accept PDFs, or prefer PDF over TeX-source files or Word files. regards Keith. ___ 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
Hi Hans, All, The biggest crux in using ConTeXt is its documentation. True, things have gotten a lot better in the past year! Yet, there is no ONE definitive place to get comprehensive and EASY to find documentation. 1) Garden is really not that easy to navigate 2) Garden is loaded with a mixture of mkii and mkiv and it is not always clear if the page one is on is for mkii or mkiv or quite outdated. 3) PRAGMA does have up to date manuals. 4) These manuals are quite unfinished in many parts, as are all many of the older manuals. Very frustrating 5) The newer manuals should be part of the standalone. ( I hate going online to look for a manual when it should be installed already) 6) Reference manuals are fine for the advanced user, but for the beginner or intermediate they are not much help. Especially, if if one does not understand TeX, or Typesetting, and one really does not need to use all those options. My suggestion would be to have garden have a manuals download area where one can get the up to date manuals from Pragma and where one can discern how old the others are. It should be also, easy to find. regards Keith. Am 19.03.2013 um 19:16 schrieb Hans Hagen : > Hi, > [snip, snip] > 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 ___ 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 20 mrt. 2013, at 07:05, Otared Kavian wrote: > > 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, > > > 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. > Being a fan of ConTeXt, I strongly agree with the above plea to make ConTeXt a painless experience for most users. I think of myself as someone who knows a bit of computers and programming. But even then I can feel sometimes something of what others must experience when nothing seems to work and no idea why. The best advocate for ConTeXt is an "invisible" ConTeXt for all those out there who just want their stuff made printer ready without hassles. ConTeXt deserves a wider use. Hans van der Meer ___ 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 (tabulate)
On Tue, 19 Mar 2013 23:46:35 +0100
Sietse Brouwer wrote:
> [1] http://wiki.contextgarden.net/Tabulate
There is \starttabulate and \starttable.
I understand that they use different mechanisms, even though their
syntax are parallel. The wiki page [1] warns against the use of macros
in tabulate, but this seems a bit obscure. Also, Tables_Overview
recommends tabulate for simple tables and flags both table and tables as
depreciated. I hesitate to add this information at the top of the wiki
pages: Tabulate, Table and Tables as I am not clear about the status
of these three mechanisms...
One question: is it possible to span columns using tabulate as in
table: \Use{n}[format]{data}?
Alan
___
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
Hi Hans, All, I find this nomenclature confusing and a little confusing from a design standpoint! 1) Color of the text background should be separate from the rest of the cell background 2) the names should reflect to what they apply That said we should have: CTBGC == Cell text background color CTC == Cell text color CBGC == Cell background color or CC == Cell color CBGCR == Cell background color in the space right of text CBGCM == Cell background color in space middle of cell( above below text) CBGCL == Cell background color in the space right of text True, these are a lot of options/parameters, yet it offers the most flexibility and a cleaner interface. Furthermore, one can understand the names of the parameters. Another, advantage is that one could and at a later point a feature for inverting the color of the text according cell color and/or text background color. regards Keith. Am 19.03.2013 um 23:46 schrieb Sietse Brouwer : >> i.e. we already had CL CM and CR, so CT is new .. should be wikified. > > The wiki [1] describes these \C* commands: > > \CRcolor is applied to the background of the text and the remaining > space on the right; > \CCcolor is applied to the background of the text only; > \CMcolor is applied to the background of the text and the remaining > space on both sides; > \CLcolor 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, > ___ 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 ___
