Thank you for the response. I'll keep this description in mind when looking up stuff and contribute what I can in the wiki (which is still down for me). YT 2014-07-08 4:57 GMT-03:00 Hans Hagen : > On 7/7/2014 8:51 PM, Yuri Teixeira wrote: > >> Hello, >> I'm sorry this probably is a dumb question but I'm really lost in my >> searches. I'm new to context/tex and have been learning/finding >> information in the wiki at the contextgarden.net >> for the past couple of weeks. Some of >> >> information there don't seem up to date but nothing unusual in an >> unofficial wiki. For some reason (isp/dns/something) the >> contextgarden.net has been unavailiable to me >> >> since yesterday even though some verification sites show it up and some >> show it down (http://www..isitdownrightnow.com >> >> been one of the later). That got me >> wondering if there are easy official docs. I've seen the pdfs at >> pragma-ade.com but the most general ones I tried >> >> are from 1999 (ms-cb-en.pdf) and 2001 (cont-eni.pdf). Are these up to >> date with the current developments? I belive they are compatible but >> having seen examples of changes in the wiki I a little unsure. >> Furthermore, the parameter behavior description in the command reference >> seem a bit... dry. So here's my plea for a little bit more love for the >> documentation. >> In any way, thank you very much for an awesome language, I'm glad I >> researched thoroughly before jumping into latex. >> > > When mechanisms in context are extended, we try to remain downward > compatible, at least in functionality. Therefore the old manuals are > normally okay (no need to fake updates with newer dates.) There are however > a few core mechanisms that are obsolete and/or changed and those are input > encodings (now always utf) and fonts (now always unicode - or mapped to > unicode - using features cf open type and more). > > In practice input encodings and fonts have always been complex: what input > encoding to choose and what font encoding to use, then running into > availability of fonts, differences per language, differences per user. A > bit of installation nightmare and user support as soon as it became less > standard. By the time that had become easier (tex gyre and lm project) the > move to opentype was made so most of the documentation had become somewhat > obsolete. > > So, when using old manuals, keep in mind that encodings, regimes and fonts > are less hassle now and no special commands are needed to use and combine > these properties. > > In addition some mechanisms were extended and improved in mkiv (sectioning > and so) which means that there are additional ways to configure them. > > That leaves mechanisms that are completely redone. One example is > bibliographies, but users who need them will have no real problems adapting > and these come with new manuals. > > Stick to mkiv. It's the one where the action takes place. > > 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 > ____________________________________________________________ > _______________________ >