ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Saša Janiška" <gour@atmarama.com>
To: ntg-context@ntg.nl
Subject: ConTeXt vs Beamer
Date: Mon, 25 Jan 2016 21:11:06 +0100	[thread overview]
Message-ID: <1453752666.2681.94.camel@atmarama.com> (raw)

Hello,

I have just checked that my first post to this list was more than 10yrs
ago (end of 2002). Then I was working on some full-sized books and ended
up with LyX/LaTex. Later, had few attempts to switch to ConTeXt, but as
a result I reduced even my LyX/LaTeX usage and was using light markups
like rst/AsciiDoc for my writing needs without higher-quality
typesetting.

Yesterday I had to help my wife to put together some medicine-related
presentation for the meeting at her working place and used LyX/LaTeX
with Beamer class.

Considering that there might be need to do such thing more often in the
future as well as possibility that I might have to produce lot of
presentations for my public lectures/workshops based on philosophy (iow.
 no need of math), I am again in the position to consider ConTeXt, but
this time mostly for presentations.

I'm (well) aware of ConTeXt's advantage in the sense of being complete
package without clashing of different packages which usually happens in
LaTeX world, I wonder if someone can give some piece of advice to learn
and/or switch ConTeXt for preparing presentations instead of learning
lot of LaTeX packages?

How does ConTeXt compare for the purpose vs LaTeX/Beamer?

I'm on Linux (running Debian Sid) and use Vim as my primary editor so
wonder if ConTeXt users recommend to e.g. prepare drafts of their
documents like rst/AsciiDoc/markdown and then convert them into ConTeXt
with tool(s) like Pandoc?


Sincerely,
Gour

-- 
Therefore, without being attached to the fruits of activities,
one should act as a matter of duty, for by working without
attachment one attains the Supreme.



___________________________________________________________________________________
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:[~2016-01-25 20:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 20:11 Saša Janiška [this message]
2016-01-25 20:55 ` Alan BRASLAU
2016-01-25 21:15   ` Marcin Borkowski
2016-01-26 10:16     ` Saša Janiška
2016-01-26  8:56   ` Hans Hagen
2016-01-26 11:00     ` Saša Janiška
2016-01-26 10:11   ` Saša Janiška
2016-01-25 21:56 ` Otared Kavian
2016-01-26 11:04   ` Saša Janiška
2016-01-26  7:34 ` Jan U. Hasecke
2016-01-26  8:57   ` Marcin Borkowski
2016-02-02  9:03     ` Saša Janiška
2016-01-26 10:22   ` Saša Janiška
2016-01-26 11:22     ` Jan U. Hasecke
2016-01-26 14:17 ` Aditya Mahajan
2016-01-26 15:37 Jeong Dal

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=1453752666.2681.94.camel@atmarama.com \
    --to=gour@atmarama.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).