ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <pgesang@ix.urz.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Wiki: ConTeXt vs. LaTeX and others
Date: Thu, 4 Nov 2010 20:44:01 +0100	[thread overview]
Message-ID: <20101104194401.GA20896@aides> (raw)
In-Reply-To: <guraq7-ea4.ln1@news.jonasstein.de>


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

On 2010-11-04 <15:18:24>, Jonas Stein wrote:
> for many users it is interesting, to get an overview
> how problems are solved in ConTeXt compared to the other
> TeX-Flavours.
> 
> I like the wikimatrix for Wikis and i thought it could be 
> nice to have a simple matrix for TeX.
> 
> I started a table in the wiki to collect this knowledge [2], 
> but i am not very happy with this table yet.
> 
> Perhaps do you have ideas, how to improve it?

Hi Jonas,

thanks for extending the wiki. For a start I’d like to recommend
two things:

(1) as this comparison might grow rather large, so I guess it
    deserves its own page and a catchy lemma under which you
    would expect this information to be found;

(2) the row ‘utf8 in text’ is ambiguous: concerning mkii and
    latex2e the functionality depends on the tex engine used.
    Maybe a subdivision of this row could clarify things?

Regards, Philipp



> 
> 
> [1] http://www.wikimatrix.org/
> [2] http://wiki.contextgarden.net/What_is_ConTeXt 
> and discussion on http://wiki.contextgarden.net/Talk:What_is_ConTeXt
> 
> kind regards,
> 
> -- 
> Jonas Stein <news@jonasstein.de>
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 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
___________________________________________________________________________________

      parent reply	other threads:[~2010-11-04 19:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 14:18 Jonas Stein
2010-11-04 16:43 ` Aditya Mahajan
2010-11-04 18:43   ` Vedran Miletić
2010-11-04 19:44 ` Philipp Gesang [this message]

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=20101104194401.GA20896@aides \
    --to=pgesang@ix.urz.uni-heidelberg.de \
    --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).