March 2006 - dev-context - NTG Mailing Lists

Re: [NTG-context] What about dynamic documentation?
by Taco Hoekwater 20 Jul '06

20 Jul '06

Hi Jérôme, > However, this seems rather far from the pdf manuals and does not really > help a newbie as I am. Definately it could be improved. In IT, almost everything is suboptimal starting the second after it's birth. Perhaps we should continue this discussion on the developers list, dev-context(a)ntg.nl? It is likely we will spend some other mails on this subject, and perhaps it is better not to clutter the general list. Anybody willing to discuss/help out can easily subscribe to that list (even if just for a while). Is that OK? > More precisely: > > 0 - Category search is missing. It is well known that searching by > contents or by command name won't give the proper result if the search > request is not well formed a priori. > Each command should have a list of associated key words, allowing smart > navigation and filtering > For example, the sectionning commands (including toc, headers and so on) > could be gathered in one big category. That could be as simple as allowing users / viewers to attach one or two key words/categories to the current commands, I think. There can be a predefined set of those, and there will not be all that many. It could also easily be backported to the XML data. Patrick? > 1 - The examples oftenly need output to let the user really understand > the effect. > Moreover, the information available in the graphical output is more > obvious thus more efficient. Perhaps the examples could be fed through the Live ConTeXt, just like the wiki examples? > 2 - Missing code template(s) to paste into the source, copy/paste does > noot help when really needed. Of course, I can grab them from > contextgarden but it is there both hidden and not well formatted. I am not sure what you mean. > 3 - The description only concerns the command. > Each key should also have its own description. Yes. > Each predefined value should also have its own description. Also yes. (both have been discussed before but never implemented due to lack of manpower). > Then the user interface can provide a layout a la headerdoc or some kind > of rollup tooltips. > > 4 - The data storage model for a size range seems weird. The range 5pt > ... 12pt is coded with an ordered list of 3 values "5pt" '..." and > "12pt" whereas it means an unordered list of 8 values: "5pt", "6pt", > ..., "12pt". This latter data model obviously turns into a pop up button > with a list of sizes. It is even a bit weirder. "5pt ... 12pt" usually stands for "any font size that is already defined using \definebodyfont". Except on the command itself, of course. There it means: "any font size you wish to define for use in the other commands that use 5pt ... 12pt". I'm smiling as I write this :-) It really should be an abstract type, like "cd:dimension" instead of those three values. > 5 - The command variants might need specials (eg \setupinterlinespace). Yes, the current solution for that command is not very nice. But there are more than a few commands with such variant calling conventions, and it is hard to come up with a nice-looking solution. Suggestions for solutions are welcome. > 6 - Sometimes the acceptable values depend on the context (eg arguments > of \ref), it means that all the relevant information is not static and > the data model should provide some entry points. But at first glance > this is a very advanced feature which cost might be unaffordable. You mean crossover functionality with reftex/auctex style programs? Would be nice to have I assume, but hard to do portably, and not really worth the effort if it cannot be done in a portable manner. (always speaking from my point of view, of course. YMMV) > Finally, it seems that the underlying data model needs more entropy. Thermodynaics says it will probably move in the right direction, once it starts moving ;-) Cheers, Taco

3 8

latest beta (tests needed)
by Taco Hoekwater 03 Apr '06

03 Apr '06

Hi, Hans, you are almost there, afaik. A few notes still: * The new bibliography module. It would be more comfortable if the t-bib was in tex/context/bib like before. It is now in tex/context/third, like in my zipfile, but that is searched later, so I now had to delete the old one manually. And if you want to promote it to core status anyway ... * A small fix to verbatim (color) * The improved version of math substacks. (looks fine) * The xtag-mml patch. * The \dodoregister patch. Duncan, can you check if these last two items are ok now? Taco

3 8

Re: [dev-context] [NTG-context] modules on wiki
by Taco Hoekwater 31 Mar '06

31 Mar '06

Hi Hans, (moved to dev-context) Hans Hagen wrote: > Thi sis what we have: > > Archive: t-bib.zip > > - this on is ok Jay me! :) > Archive: t-lettrine.zip > > - doc path What do you mean by this? the files are in the 'doc' tree already? And i think those t-XXXX.pdf files tend to be the output of texexec --module t-XXXX (but they seem unnecessary). > - either we use t-name or name as subpath, but we need to be > consistent and since only t-'s go there, we can omit the t- from the > path I vote for dropping the prefix. We are in 'third' already. > - only store runtime files in context/third/somename > - always provide an doc path > > - put a file t-somename.xml in the tex path that looks like: I already have t-bib.xml and t-lettrine.xml, those contain texshow/xml syntax information. Perhaps these should be moved elsewhere? > or whatever we can agree on, but at least let's cook up a format that > can be parsed (the wiki already has something like that to generate > the modules pages, i dunno the format) How about the TPM format? It is an RDF syntax that should do all we need already. There even is a filled one for context (TL2005): http://www.tug.org/texlive/devsrc/Master/texmf-dist/tpm/context.tpm Taco

2 3

Extended unic-032 and unic-033
by Taco Hoekwater 30 Mar '06

30 Mar '06

Hi, I guess the two symb-xxx.tex files in the zip should be merged with some other stuff like math-uni.tex and (maybe?) a reinstated enco-uni.tex. Cheers, Taco

2 1

xtag-mmp.tex patch
by Duncan Hothersall 24 Mar '06

24 Mar '06

At line 492 in xtag-mmp.tex: \def\pMULTISCRIPTmmlPRE#1#2#3#4% {\ifdone \ifodd\scratchcounter ^{\naturalxmlr{#1}{#2}{#3}{#4}}{}% \else _{\naturalxmlr{#1}{#2}{#3}{#4}}% \fi \else \doif{mprescripts/}{#1}{\donetrue{}}% weak, the / here \fi \ifdone \advance\scratchcounter 1 \fi} I think the super/sub scripts are the wrong way around; suggest swapping fourth and sixth lines: \def\pMULTISCRIPTmmlPRE#1#2#3#4% {\ifdone \ifodd\scratchcounter _{\naturalxmlr{#1}{#2}{#3}{#4}}% \else ^{\naturalxmlr{#1}{#2}{#3}{#4}}{}% \fi \else \doif{mprescripts/}{#1}{\donetrue{}}% weak, the / here \fi \ifdone \advance\scratchcounter 1 \fi} According to the MathML spec http://www.w3.org/TR/2003/REC-MathML2-20031021/chapter3.html#presm.mmultisc… the syntax is <mmultiscripts> base (subscript superscript)* [ <mprescripts/> (presubscript presuperscript)* ] </mmultiscripts> Thanks from the strange world of presentational MathML, Duncan

1 0

Re: [dev-context] Cron <context@server> /var/www/aanhet.net/context/bin/cron/context-mirror
by Taco Hoekwater 22 Mar '06

22 Mar '06

Cron Daemon wrote: > receiving file list ... done > ./ > context/current/ > context/current/cont-tmf.zip Hi Hans, I've created a wiki page for this, but there is almost no news, right? http://wiki.contextgarden.net/Context_2006.03.22 Cheers, Taco

1 0

Re: [dev-context] [NTG-context] Curious blank page
by Taco Hoekwater 20 Mar '06

20 Mar '06

Hans Hagen wrote: >> > > can you check the version i uploaded a moment ago? > Hans, can you check the summary I wrote here: http://wiki.contextgarden.net/Release_Notes I am not sure I've understood everything correctly. Cheers, Taco

2 1

Re: [dev-context] kpse
by Hans Hagen 15 Mar '06

15 Mar '06

Taco Hoekwater wrote: > > Hi Hans, > > Somehow, it does not find my texmf.cnf. > > I get: > > [taco@glenlivet ruby]$ ruby tmftools.rb texnansi.enc > ./base/kpsefast.rb:650:in `basename': cannot convert nil into String > (TypeError) > from ./base/kpsefast.rb:650:in `_is_cnf_?' > from ./base/kpsefast.rb:654:in `find_file' > from ./tmftools.rb:111:in `main' > from ./tmftools.rb:110:in `each' > from ./tmftools.rb:110:in `main' > from ./tmftools.rb:168:in `send' > from ./tmftools.rb:168 > > I what environment settings do I need? I now have: > > TEXMFCNF=/opt/tex/texmf.local/web2c:/opt/tex/teTeX/texmf/web2c > TEXMFLOCAL=/opt/tex/texmf.local > TEXMFMAIN=/opt/tex/teTeX/texmf > > and > > [taco@glenlivet ruby]$ kpsewhich texmf.cnf > /opt/tex/texmf.local/web2c/texmf.cnf a better definition is: def _is_cnf_?(filename) filename == File.basename(((a)cnffiles.first rescue 'texmf.cnf')) end (is in files i sent you in aseparate mail) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1

kpse
by Hans Hagen 14 Mar '06

14 Mar '06

Hi, Attached is a zip with ruby stuff. Not perfect, also not best organized but it shows some ideas. compare kpsewhich texnansi.enc tmftools.rb texnansi-enc the first alternative is a bit faster, the second can be faster when we use a serialized hash. now, say (windows) set KPSEMETHOD=drb set KPSEPORT=7000 and run tmftools --serve and next tmftools.rb texnansi-enc since we now run kpse as a service, we have a pretty fast response. One may wonder why we need such things ... but imagine (as part of a workflow): texmfstart bin:xsltproc --output whatever.xml kpse:something.xsl whoknows.xml texmfstart rlxtools --manipulate kpse:test.rlx whatever.rlg we can now save calls to kpsewhich. texmfstart already has many built in optimizations to limit the number of calls and kpsefast also has some caching. Btw, the server serves multiple trees at the same time. (I have to reshuffle the kpse classes/modules a bit.) Other new features involve passing environment variables. In threaded scripts the problem is that the environment hash is shared. This means that one cannot easily do something ENV['TEXMF']= = "..." system("texexec ...") in treads because each thread may have different assignments to TEXMF. For this purpose, texmfstart already had: --tree=/mytex/version-1 with setuptex.tmf is part of the minimal distributions and and is just a series of assignments. This file is put in the root of a tree. (btw, this makes it easy to put several trees on the wiki and to select a version; it's juts a matter if adding the --tree switch) # usage: texmfstart --tree=f:/minimal/tex ... # # this assumes that calling script sets TEXPATH without a trailing # slash; %VARNAME% expands to the environment variable, $VARNAME # is left untouched; we also assume that TEXOS is set. TEXMFMAIN = %TEXPATH%/texmf TEXMFLOCAL = %TEXPATH%/texmf-local TEXMFFONTS = %TEXPATH%/texmf-fonts TEXMFEXTRA = %TEXPATH%/texmf-extra TEXMFPROJECT = %TEXPATH%/texmf-project VARTEXMF = %TMP%/texmf-var HOMETEXMF = TEXMFOS = %TEXPATH%/%TEXOS% # OSFONTDIR = %SYSTEMROOT%/fonts TEXMFCNF = %TEXPATH%/texmf{-local,}/web2c TEXMF = {$TEXMFOS,$TEXMFPROJECT,$TEXMFFONTS,$TEXMFLOCAL,$TEXMFEXTRA,!!$TEXMFMAIN} TEXMFDBS = $TEXMF TEXFORMATS = %TEXMFOS%/web2c/{$engine,} MPMEMS = %TEXFORMATS% TEXPOOL = %TEXFORMATS% MPPOOL = %TEXPOOL% PATH > %TEXMFOS%/bin PATH > %TEXMFLOCAL%/scripts/perl/context PATH > %TEXMFLOCAL%/scripts/ruby/context EXAMPLEROOT = %VARTEXMF% TEXINPUTS = MPINPUTS = MFINPUTS = In addition to this file, one can also feed an extra file with the --environment option. This means that one can leave most dirty details to texmfstart and keep scripts simple. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Re: [dev-context] stijlbijdrage
by Hans Hagen 14 Mar '06

14 Mar '06

Hoi, > > Ik heb de cdcover-code van Dennis van Dok (uit de laatste NTG MAPS) > bewerkt voor ConTeXt en er nog wat toeters en bellen aan toegevoegd. > Het lijkt erop dat de eerste kinderziekten er nu uit zijn (fingers > crossed). Of dat echt zo is blijkt waarschijnlijk pas als anderen het > gebruiken. > Mijn vraag: is er interesse om dit op te nemen in het thirdparty > aanbod op de Pragma site? > Zo ja dan kan ik je het bestand toezenden. Jij en Taco kunnen er dan > eerst naar kijken om te zien of je het wat vindt. > Dennis van Dok was accoord met verdere verspreiding van zijn geesteskind. third party modules are now coordinated via the wiki; i still need to set up a way to fetch the styles etc from the wiki so that we can have an additional zip; the website is generated from xml files, so i need to add entries for tp modules there (maybe we need a kind of xml description file for that as well: name, author, description, etc) so, best is to create an entry in the wiki on the third party page and then announce it; after that people from the dev team will pick it up and check the file for (for instance) low level dependencies and such the 'latest versions' are stored in the wiki and from there submitted to ctan (in a next stage we can consider to also have a third party svn branch) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

4 3