February 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

\dodoregister bug
by Duncan Hothersall 22 Feb '06

22 Feb '06

With latest ConTeXt: -- \starttext This is a paragraph of text with an index term at the very end of it. This is a paragraph of text with an index term at the very end of it. \index{test} This is another paragraph. This is another paragraph. This is another paragraph. \stoptext -- These two paras run together. If I remove the recent fix (which I requested - sorry Hans!) to \dodoregister in core-reg: \def\dodoregister[#1]#2#3% {\doprocesspageregister[#1]{#2}{#3}} % intead of %% \def\dodoregister[#1]#2#3% %% {\doflushatpar{\doprocesspageregister[#1]{#2}{#3}}} This makes things work correctly again, but of course it also removes the nice fix which stopped \index calls at the start of paras causing additional white-space. I suggest that this is reverted though, because this is probably a more serious and common problem than the one we were trying to fix. Duncan

2 1

bfm math bug?
by Adam Lindsay 18 Feb '06

18 Feb '06

compare the following formulae with your favourite working bold math setup (confirmed with CM, Iwona, Lucida here): \startformula % this works \sin{\frac{{\bfm \pi}}{2}}=\sqrt{\bfm2} \stopformula \startformula % this doesn't \sin{\frac{{\bfm \pi}}{2}}=\sqrt{2} \stopformula % \startformula % this crashes % \sin{\frac{\bfm \pi}{2}}=\sqrt{2} % \stopformula I can't claim to know about all the family magic that goes on behind the scenes with bold math, but I'm fairly confident I can configure things properly. Smells like a bug. In other news, these will make bold numbers, if you need them: \definemathcharacter [48] [nothing] [mr] ["30] \definemathcharacter [49] [nothing] [mr] ["31] \definemathcharacter [50] [nothing] [mr] ["32] \definemathcharacter [51] [nothing] [mr] ["33] \definemathcharacter [52] [nothing] [mr] ["34] \definemathcharacter [53] [nothing] [mr] ["35] \definemathcharacter [54] [nothing] [mr] ["36] \definemathcharacter [55] [nothing] [mr] ["37] \definemathcharacter [56] [nothing] [mr] ["38] \definemathcharacter [57] [nothing] [mr] ["39] Again, checked on my limited test cases and knowledge of mathematics. I'm sure there will be unanticipated side effects. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl(a)comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

2 5

[Fwd: Re: [NTG-context] gnuplot mode]
by Taco Hoekwater 16 Feb '06

16 Feb '06

Hi Mojca, Can you tell/send me what I need to get (and where) to compile a GNUplot from source with your terminal in it (on linux)? Cheers, taco -------- Original Message -------- And a final word: I finally installed "something to compile gnuplot with" yesterday. I have the first pre-alpha ;) "set terminal context" working and I will need both Hans and Taco's hand as well as gnuplot/metafun users to help me with suggestions/requests/brainstorming about how to implement certain parts, so that the output will remain highly configurable regarding fonts, colors & styles, but more about that in another mail.

2 1

TUG Lucida
by Adam Lindsay 16 Feb '06

16 Feb '06

I've finally gotten around to completing the Lucida-TUG typescripts, to enable using the TUG-distributed Lucida fonts 1) without renaming the files on installation and 2) with the Lucida Basic option. I've enclosed the TeX files, but you can check out the unremarkable PDFs at: http://homepage.mac.com/atl/tex/TUGLucida.zip http://homepage.mac.com/atl/tex/TUGLucidaTeXOnly.zip Comments? Questions? Testers? -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl(a)comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

1 0

dependencies
by Hans Hagen 15 Feb '06

15 Feb '06

Hi Taco & Patrick, Attached is version of ctxtools that provides ctxtools --dependencies it takes the context.tex file and analyzes in the order of loading what macros are defined (we can probably throw away the names that match \\.[!?@]) by default i generate an xml file; taco suggested that maybe patrick can use this file as a prelude to an api interface (crosslinking sources) when i have time i will use this analysis to check dependencies in the loading order (i'm sure that some forward referencing has crept in, if only because of splitting files) 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

new upload
by Adam Lindsay 15 Feb '06

15 Feb '06

I'm trying out a new way running the minimal trees, and just updated to today's 17:41 version... (/Users/Shared/mintex/texmf-local/tex/context/patterns/lang-de.pat ! Bad \patterns. \dobuildtextaccent #1#2->{ \let \char \normalaccent #1\let \char \normalchar #2} l.113 .ge5r[odiaeresis] Does anyone else get this, or did I screw something up along the way? adam -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl(a)comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

1 1

Re: [dev-context] Cron <context@server>(new release)
by Taco Hoekwater 15 Feb '06

15 Feb '06

Hi, I have no time now to document everything in this release, there are changes all over the place so i will need a bit of time. Cheers, Taco Cron Daemon wrote: > receiving file list ... done > context/current/ > context/current/cont-exa.zip > context/current/cont-ext.zip > context/current/cont-fnt.zip > context/current/cont-img.zip > context/current/cont-mpd.zip > context/current/cont-ppc.zip > context/current/cont-tmf.zip > context/current/cont-win.zip

1 0

Release testing issues
by Taco Hoekwater 07 Feb '06

07 Feb '06

Hi all, Over the past ten days, there have been 7 new context releases, of which probably only three would have been necessary if there would not have been silly bugs embedded in the new code. In fact, we are still awaiting an eight upload (for that extra space after \quote and \quotation). When there is a bug found or a request made on the mailing list, usually Hans (and sometimes me) will post a bit of code that *should* remove a bug or implement a new feature. We both expect the original requestor to test that bit of code for side-effects (since we usually do not have enough time to do thorough testing ourselves). And that's where it goes wrong, of course. Beginners at ConTeXt are often incapable to test anything except the immediate intended effect (and not always even that). I wanted to bring this up because I hope that some of you can find a way to help testing those new bits (or find other ideas to solve the problem without placing too much of a burden on Hans' time). A possible side-effect could be the organic growth of a set of regression test files, an idea that has been talked about before. Greetings, Taco

1 0

itemization bug
by Taco Hoekwater 07 Feb '06

07 Feb '06

This is supposed to wrok, right? (it did before) \setupitemize[n] \starttext \startitemize[start=2] \item Test % I want 2. , not 1. \stopitemize \stoptext Cheers, Taco

1 0