May 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

Register allocation handling
by Taco Hoekwater 23 May '06

23 May '06

Hi, I've just committed a new version to the repository that uses omega-style (flat array) register allocation instead of etex-style (sparse array). This means that luatex now has 65536 (2^16) of each of the registers \newcount \newskip \newmuskip \newdimen \newtoks \newbox \newmarks The marks code is completely new, and not very optimized yet, but it should not be much worse than pdfetex for a 'normal' document (when no more than 50 or so separate mark classes). Cheers, Taco

1 1

Turkish hyphenation patterns
by Mojca Miklavec 22 May '06

22 May '06

Hello Hans, Considering the Turkish hyphenation patterns (which don't seem to be EC-encoded): I tried to decipher them, although some native speaker should probably take a look. I'm sending the original documentation and a kind of list of replacements. I would suggest to replace the following letters (see the attached file): i,i:,o:,u:,a=,i=,o=,c:,g=,s: and to ignore the first three patterns and all those containing any of the following sequences (they seem to be there just for the sake of Arabic transliteration): @,#,g:,z:,d!,h!,k!,s!,t!,z!,d=,n=,t=,z=,h=,s= (Or to regenerate the patterns with from scratch with a ruby script, which might be faster :) ftp://tug.ctan.org/pub/tex-archive/language/turkish/hyphen/turk_hyf.c Mojca

1 0

new beta
by Taco Hoekwater 18 May '06

18 May '06

Hans, Your new beta only has some openmath/content-mathml related fixes, correct? Will you have a look at Aditya's math requests, or should I? Taco

2 1

version 2006.05.16 18:35
by Taco Hoekwater 17 May '06

17 May '06

Hi, I just finished a page on that release: http://wiki.contextgarden.net/Context_2006.05.16 I take it there will be a new release shortly, so I am not going to announce this version. Taco

1 0

[Fwd: Supelec-Foundry Project Approved]
by Taco Hoekwater 11 May '06

11 May '06

-------- Original Message -------- Subject: Supelec-Foundry Project Approved Date: Thu, 11 May 2006 14:11:11 +0200 From: noreply(a)foundry.supelec.fr To: taco(a)metatex.org Your project registration for Supelec-Foundry has been approved. Project Full Name: ConTeXt Manuals Project Unix Name: contextman CVS Server: cvs.contextman.foundry.supelec.fr Shell/Web Server: contextman.foundry.supelec.fr Your DNS will take up to a day to become active on our site. While waiting for your DNS to resolve, you may try shelling into shell.foundry.supelec.fr and pointing CVS to scm.foundry.supelec.fr If after 6 hours your shell/CVS accounts still do not work, please open a support ticket so that we may take a look at the problem. Please note that all shell/CVS accounts are closed to telnet and only work with SSH. Your web site is accessible through your shell account. Please read site documentation (see link below) about intended usage, available services, and directory layout of the account. If you visit your own project page in Supelec-Foundry while logged in, you will find additional menu functions to your left labeled 'Project Admin'. We highly suggest that you now visit Supelec-Foundry and create a public description for your project. This can be done by visiting your project page while logged in, and selecting 'Project Admin' from the menus on the left (or by visiting http://foundry.supelec.fr/project/admin/?group_id=22 after login). Your project will also not appear in the Trove Software Map (primary list of projects hosted on Supelec-Foundry which offers great flexibility in browsing and search) until you categorize it in the project administration screens. So that people can find your project, you should do this now. Visit your project while logged in, and select 'Project Admin' from the menus on the left. Enjoy the system, and please tell others about Supelec-Foundry. Let us know if there is anything we can do to help you. -- the Supelec-Foundry crew

1 0

metafun troubles
by Taco Hoekwater 10 May '06

10 May '06

Hi Hans, I still have trouble with the metafun mem when using the newtexexec. Missing specials, to be precise, because the runtime mpost reads different values from texmf.cnf from the ini mpost. The root of the problem is that texexec --make metafun runs the following command: mpost -progname=metafun --ini -translate-file=natural.tcx metafun But texexec talk runs: mpost -progname=mpost -mem=metafun -translate-file=natural.tcx \ talk-mpgraph.mp (I have separate settings in texmf.cnf for mpost, metafun, and mpplain). Cheers, taco

2 1

new release pages
by Taco Hoekwater 09 May '06

09 May '06

Hi, I hope these make sense: http://wiki.contextgarden.net/Context_2006.05.08 http://wiki.contextgarden.net/Context_2006.05.08b Is there going to be another release today or tomorrow, or should I announce this version? (I am not sure about those problems that were reported on the list). Cheers, taco

1 0

scripts/context/stubs/unix/texmfstart.bat?
by Christopher Creutzig 09 May '06

09 May '06

Salve Hans, I doubt there is a unix system where scripts/context/stubs/unix/texmfstart.bat cum suis will work, those are DOS/Win/CP/M batch files. Regards, Christopher

2 1

Font switching in XeTeX
by Mojca Miklavec 05 May '06

05 May '06

Hello Hans and Adam, Which are the high-level font switching commands for XeTeX? Documentation in font-ini states that something like \definedfont["cmtt10" at 40pt] should work, but if I try to play with \definedfont["Latin Modern Roman" at 40pt] I get the message that TFM files for "Latin Modern Roman" do not exist. \font\A="Latin Modern Roman" at 40pt works OK. I have some problems with the default Type1 lmr font - it doesn't know that there are any "ccarons" present in the font (with OpenType lmr it works OK), but I have to inspect that a bit anyway. There should be a way to "preload" the lm fonts so that they would work OK with diacritical marks. Mojca

1 0