ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Yuri Teixeira <yuriteixeira235@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: documentation
Date: Tue, 8 Jul 2014 14:56:51 -0300	[thread overview]
Message-ID: <CACnORsdw7ZR3i+35wDtZDdtCHEvkrtgKcyPA6zriErXhrAgpyA@mail.gmail.com> (raw)
In-Reply-To: <53BBA44E.1020706@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 3984 bytes --]

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 <pragma@wxs.nl>:

> 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
>> <http://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 <http://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
>>
>> <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 <http://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
> ____________________________________________________________
> _______________________
>

[-- Attachment #1.2: Type: text/html, Size: 5794 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2014-07-08 17:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07 18:51 documentation Yuri Teixeira
2014-07-07 19:10 ` documentation Philipp Gesang
2014-07-08 19:13   ` documentation Mojca Miklavec
2014-07-08  7:57 ` documentation Hans Hagen
2014-07-08 17:56   ` Yuri Teixeira [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-09-16 14:54 Documentation Alain Delmotte
2009-09-17 12:04 ` Documentation luigi scarso
2009-09-17 14:15 ` Documentation Hans Hagen
2009-09-18 12:30   ` Documentation Alain Delmotte
2002-03-07  8:57 Documentation Nigel King
2002-03-07 22:32 ` Documentation Hans Hagen
2002-03-08 15:42   ` Documentation Nigel King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACnORsdw7ZR3i+35wDtZDdtCHEvkrtgKcyPA6zriErXhrAgpyA@mail.gmail.com \
    --to=yuriteixeira235@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).