ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: "Thomas A. Schmitz via ntg-context" <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: TUG 2023
Date: Wed, 4 Jan 2023 19:04:11 +0100	[thread overview]
Message-ID: <bbb23708-394e-03f0-1d5f-860b2aac0d1f@fiee.net> (raw)
In-Reply-To: <509a5ccc-c9a3-cce2-765a-35c977db8bfd@uni-bonn.de>

Hi Thomas,

Am 04.01.23 um 17:50 schrieb Thomas A. Schmitz via ntg-context:
> an excellent year 2023 to all of you...

The same to you!

> is any of the developers going (Hans?)?

I’m not a dev but I’ll be there.

> Since the public will be 99 % LaTeX-centric: I had the 
> idea of showing (off) how ConTeXt can typeset xml and produce different 
> outputs from the same source (similar to what I've done in Bassenge in 
> 2019). Those of you who have been to TUG conferences before: would that 
> be of interest even to people who know little to nothing about ConTeXt 
> yet are familiar with other forms of TeX? I guess I just what to get a 
> feeling what to expect at a TUG conference.

I’ve never been to a TUG conference, but it’s also a DANTE conference, 
and I wouldn’t hesitate to talk about ConTeXt – your example is a good 
one to get people interested, I think.

I’ll probably show how I make our architectural guides for Bonn – I 
suggested to have a guided tour to one of the HICOG settlements (that 
were built for the American forces and their German employees) with the 
group that’s behind the guides (Werkstatt Baukultur Bonn).

Since I’ll be there on company time (I’m now working for my former main 
customer), I’ll probably also help presenting our LaTeX3-based 
documentation workflow.

Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2023-01-04 18:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 16:50 Thomas A. Schmitz via ntg-context
2023-01-04 18:04 ` Henning Hraban Ramm via ntg-context [this message]
2023-01-04 18:10 ` Joseph Wright via ntg-context
2023-01-05 17:20 ` Hans Hagen via ntg-context
2023-01-07  2:40   ` Alan Braslau via ntg-context
2023-01-06 14:42 ` Ulrike Fischer via ntg-context

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=bbb23708-394e-03f0-1d5f-860b2aac0d1f@fiee.net \
    --to=ntg-context@ntg.nl \
    --cc=texml@fiee.net \
    /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).