dev-context December 2005

dev-context@ntg.nl

3 participants
7 discussions

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

cont-en.xml
by Patrick Gundlach 05 Jan '06

05 Jan '06

Hi, I'll be away for some days over christmas and I know I'll get bored once or twice, so I can have a look into the new texshow. What applications (besides mine) use the xml defintion file? * quick references (pdf) * the perl/tk based browser (can't remember its name, sorry) * ? I am not sure what I want to do yet, but there are cleanups to be done, such as the bodyfont=5...12pt thing, style=normal,...,command. I guess that these should be substituted by a special tag 'you can use a bodyfont instruction' such as cd:fontinstr or cd:style for the other one. But I don't promise anything. Patrick -- ConTeXt wiki and more: http://contextgarden.net

3 14

hw and cg fonts
by Taco Hoekwater 22 Dec '05

22 Dec '05

Hi Hans (esp), Since I was having some trouble getting the chancery to work, I thought: let's have a closer look at that. And I got a bit confused, almost immediately. Have a look at the two grep commands below. Should there really be both "Calligraphic" and "Calligraphy" as well as "handwriting" vs. "handwritten"? And if so, why? :-) (and math-lbr definately has a typo) Cheers, Taco [taco@glenlivet base]$ grep \\\Wcallig * | grep -v ':%' font-ini.tex:\def\cal{\mathortext{\fam\purefamily{calligraphic}}{\symbolicfont{Calligraphic}}} font-ini.tex:\def\calligraphic#1{\mathortext\domathtext\donothing{\cal#1}} font-ini.tex:\definefontstyle [\c!cg,\v!calligraphic] [\c!cg] math-eul.tex:\definefamilysynonym [eul] [calligraphic] [sy] math-lbr.tex:\definefamilysynonym [lbr] [calligrapahy] [sy] math-tex.tex:\definefamilysynonym [default] [calligraphic] [sy] mult-con.tex: calligraphic: calligrafie calligraphic mult-con.tex: calligrafico caligrafic type-buy.tex:\starttypescript [calligraphy] [lucida] [name] type-buy.tex:\starttypescript [calligraphy] [lucida] [texnansi,ec,8r] type-enc.tex:\starttypescript [calligraphy] [chancery] [ec,texnansi,8r] type-enc.tex:\starttypescript [calligraphy] [chancery] [qx] type-exa.tex:\definetypeface[lucida][cg][calligraphy][lucida][default][encoding=\typescripttwo] type-siz.tex:\starttypescript [calligraphy] [default] [size] type-syn.tex:\starttypescript [calligraphy] [chancery] [name] type-xtx.tex:\starttypescript[serif,calligraphy][applechancery][uc] type-xtx.tex:\starttypescript[calligraphy][applechancery][name] type-xtx.tex:\starttypescript [calligraphy] [lucida] [uc] [taco@glenlivet base]$ grep \\\Whandw * | grep -v ':%' font-ini.tex:\definefontstyle [\c!hw,\v!handwritten][\c!hw] mult-con.tex: handwritten: handschrift handwritten type-buy.tex:\starttypescript [handwriting] [lucida] [name] type-buy.tex:\starttypescript [handwriting] [lucida] [texnansi,ec,8r] type-exa.tex:\definetypeface[lucida][hw][handwriting][lucida][default][encoding=\typescripttwo] type-ghz.tex:\starttypescript[serif,handwriting][zapfino][texnansi,ec,8r]%todo:handwriting type-siz.tex:\starttypescript [handwriting] [default] [size] type-xtx.tex:\starttypescript[serif,handwriting][zapfino][uc] type-xtx.tex:\starttypescript[handwriting][zapfino][name] type-xtx.tex:\starttypescript[handwriting][lucida][uc]

1 0

latin modern
by Taco Hoekwater 14 Dec '05

14 Dec '05

Hi, I just noticed that ConTeXt's cont-lmt.zip has 0.99.2 while 0.99.3 is on CTAN now. Me fix and e-mail you new zip, Hans? Taco

2 2

contextgarden is down?
by Taco Hoekwater 13 Dec '05

13 Dec '05

See subject :-) Taco

1 0

[Fwd: Re: [NTG-context] Where is \typescriptthree documented?]
by Taco Hoekwater 08 Dec '05

08 Dec '05

Patrick, Perhaps it is easiest if you start simple that 'api' subdivision in texshow-web first. Than i can start adding stuff at any time I have a minute or so to spare. Creating a big preprocessed cont-api.xml file is unlikely for (at least) the next month. Cheers, Taco Forwarded message from Hans: > David Arnold wrote: > >> All, >> >> I don't understand \typescriptthree. Where is it documented? What >> does it mean? > > > I'm not sure that it is documented, but it is the value of the > third argument of \starttypescript, and it valid until \stoptypescipt. > If the actual argument was a list, then context will loop over each > item in the list, each time with the next value in \typescriptthree. > > Similar commands are available for \typescriptone and \typescripttwo. taco: this is probably something for the api documentations, isn't it? (i forgot how we're goint to organize that -) Hans _______________________________________________ ntg-context mailing list ntg-context(a)ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context

2 2

\startbackground vs. \definetextbackground
by Taco Hoekwater 06 Dec '05

06 Dec '05

Hans Hagen wrote: > Now, concerning backgrounds: i need to fix that for the first case (use > \openlineheight instead of lineheight in calculations) [you may enter an > bug entry in the collector] > Hans, Would it be possible to add the 'framed' functionality of \startbackground to \definetextbackground? Should be doable using some extra metafont macros, right? Then \startbackground could be flagged as obsolete. ;-) Taco

2 3

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

dev-context December 2005