ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Asciidoc --> ConTeXt for presentations
Date: Fri, 14 Oct 2016 20:54:33 +0200	[thread overview]
Message-ID: <30b475f0-6e2f-498b-509f-d82b203f4a7d@wxs.nl> (raw)
In-Reply-To: <87eg3iyg3o.fsf@atmarama.com>

On 10/14/2016 7:50 PM, Saša Janiška wrote:
> Hans Hagen <pragma@wxs.nl> writes:
>
>> Before we started with context we uses ascii based markup (i still
>> have printouts of the code used for pagination, figure placement, tocs
>> around somewhere) ...
>
> That’s very interesting…
>
>> but as the input becomes more complex it makes no sense any more to
>> use such formats and tex (or nowadays xml) starts looking clean and
>> simple in comparison
>
> Hmmm…do you use XML as *source* authoring format? I did try to play with
> some XML editors in the past and a bit with XSL stylesheets, but never
> found it as pleasnt experience, so I’m really curios to know more about
> your XML format usage?

We are involved in e.g. typesetting math schoolboooks and for some 
authors just edit the xml in an 'ascii' editor (scite) .. all a matter 
of keeping your source clean (clever xml editor environments sometimes 
mess up). As with tex documents one just hits a button to get a preview. 
(These projects need pdf and html, all kind of products from one source 
or collection of sources).

>> where
>>
>> \startglossary[reference=terms,title={List of Terms}]
>>
>> is not that more coding. Anyway, using some asciidoc (should be utfdoc
>> i guess) converted to some kind of xml is probably the easiest to deal
>> with.
>
> I must admit that in one sense ConTeXt (TeX) is a clear winner. After I
> did two books using LyX/LaTeX I am simply spoiled with TeX’s typestting
> quality and cannot easily settle for less. Moreover, ConTeXt is
> certainly superior to LaTeX (despite of possible lack of more docs), so
> on one hand I can imagine that producing one presentation every two week
> would probably (hopefully) make me quite skillful in using ConTeXt (maybe
> even MetaPost/MetFun), at least, presentation-wise[1]…iow. the more I’d use
> ConText, the possibly initial (steeper) learning curve will pay off in
> the long term.

just look at the presentation styles in the distribuition. Many of them 
you can just process to get an example

then start making your own ... such styles are rather simple and not 
much coding in the document source is needed .. just develop your own 
look and feel after a while

(i'll clean up all these styles some day and i have a bunch on my 
machine used for recent presentations that can become modules too)

> Let me say that few days ago I stumbled upon interesting thread
> (http://lists.gnu.org/archive/html/auctex/2016-09/msg00001.html) on the
> AUCTeX mailing list disccussing about possibility to improve general
> user experince when writing ConTeXt using that Emacs package…Here is one
> message which can be interesting not only for Hans:
>
> http://lists.gnu.org/archive/html/auctex/2016-09/msg00010.html
>
>
> Sincerely,
> Gour
>
> Footnotes:
> [1]  Btw, are special presentation effects (animation, transitions etc.)
> available for non-Acrobat-reader PDF viewers?

mupdf should be able to do some of that but i never tested it

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2016-10-14 18:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13 10:35 Saša Janiška
2016-10-13 18:06 ` Pablo Rodriguez
2016-10-13 20:40   ` Saša Janiška
2016-10-13 21:07     ` Pablo Rodriguez
2016-10-13 22:03       ` Saša Janiška
2016-10-13 20:57 ` Mica Semrick
2016-10-13 21:12   ` Saša Janiška
2016-10-13 21:27     ` Pablo Rodriguez
2016-10-13 22:05       ` Saša Janiška
2016-10-14  8:10         ` Hans Hagen
2016-10-14 17:50           ` Saša Janiška
2016-10-14 18:54             ` Hans Hagen [this message]
2016-10-16 10:25               ` Saša Janiška
2016-10-16 11:07                 ` Hans Hagen
2016-10-16 11:32                   ` Saša Janiška
2016-10-16 14:16                 ` Alan BRASLAU
2016-10-16 15:53               ` Saša Janiška
2016-10-13 21:20   ` Pablo Rodriguez
2016-10-15 16:54     ` Mica Semrick
2016-10-14  0:52 ` Russell Urquhart
2016-10-14 17:30   ` Saša Janiška
2016-10-15 14:09     ` Russell Urquhart
2016-10-16 10:33       ` Saša Janiška
2016-10-16 15:11         ` Russell Urquhart
2016-10-16 15:29           ` Saša Janiška
2016-10-16 17:36             ` Russell Urquhart
2016-10-16 18:02               ` Saša Janiška

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=30b475f0-6e2f-498b-509f-d82b203f4a7d@wxs.nl \
    --to=pragma@wxs.nl \
    --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).