From: "Martin Schröder" <martin@oneiros.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Ideas for restructuring the ConTeXt garden?
Date: Mon, 14 Mar 2011 10:17:56 +0100 [thread overview]
Message-ID: <AANLkTi=Pp+PuPx3y-0G=pmRXtEE476fVwmJKrzC-U2AD@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1103140049050.1160@ybpnyubfg.ybpnyqbznva>
2011/3/14 Aditya Mahajan <adityam@umich.edu>:
> The hard part is figuring out the values (font size, spaces after sections,
> etc) from the LaTeX code. It is difficult to look at
> http://mirror.hmc.edu/ctan/macros/latex/contrib/IEEEtran/IEEEtran.cls and
> figure out what is the title size for a 10pt document, or how much space
> should come between the author block and the start of the two column text,
> etc.
Erm - is that really needed? Today a typical journal's workflow should
accept articles in LaTeX _markup_, convert that to XML and feed it to an
XML formatter (which may well use TeX) eventually. I see ConTeXt's role
there as the XML formatter. Or it could digest LaTeX markup - but then
it would need more than just the layout.
Best
Martin
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-03-14 9:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 23:35 Henry House
2011-03-13 7:54 ` Taco Hoekwater
2011-03-13 9:00 ` Thomas Schmitz
2011-03-13 11:43 ` "latex style" (was : Re: Ideas for restructuring the ConTeXt garden?) Peter Münster
2011-03-13 20:34 ` Ideas for restructuring the ConTeXt garden? Aditya Mahajan
2011-03-14 0:07 ` Alasdair McAndrew
2011-03-14 3:12 ` Aditya Mahajan
2011-03-14 10:42 ` Philipp Gesang
2011-03-14 3:32 ` mathew
2011-03-14 4:21 ` Alasdair McAndrew
2011-03-14 4:54 ` Aditya Mahajan
2011-03-14 6:33 ` Alasdair McAndrew
2011-03-14 7:07 ` Henning Hraban Ramm
2011-03-14 9:17 ` Martin Schröder [this message]
2011-03-14 10:43 ` Alasdair McAndrew
-- strict thread matches above, loose matches on Subject: below --
2011-03-10 14:38 \setuppublications problem Jean Magnan de Bornier
2011-03-11 12:00 ` Thomas A. Schmitz
2011-03-12 7:37 ` Jean Magnan de Bornier
2011-03-12 10:09 ` Thomas Schmitz
2011-03-12 10:45 ` Florian Wobbe
2011-03-12 11:08 ` Thomas Schmitz
2011-03-12 12:21 ` Ideas for restructuring the ConTeXt garden? Florian Wobbe
2011-03-12 13:05 ` Marco
2011-03-12 14:08 ` Mojca Miklavec
2011-03-12 16:20 ` Procházka Lukáš
2011-03-12 20:02 ` Jaroslav Hajtmar
2011-03-12 20:08 ` C.
2011-03-12 23:04 ` Pontus Lurcock
2011-03-14 7:46 ` Taco Hoekwater
2011-03-14 20:26 ` Mojca Miklavec
2011-03-14 21:15 ` mathew
2011-03-13 7:01 ` Vnpenguin
2011-03-13 4:48 ` mathew
2011-03-13 5:03 ` Pontus Lurcock
2011-03-13 6:25 ` luigi scarso
2011-03-14 13:04 ` Carlos Breton Besnier
2011-03-14 15:16 ` Carlos Breton Besnier
2011-03-16 12:37 ` Vedran Miletić
2011-04-26 10:27 ` Ian Lawrence
2011-03-14 15:17 ` Carlos Breton
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='AANLkTi=Pp+PuPx3y-0G=pmRXtEE476fVwmJKrzC-U2AD@mail.gmail.com' \
--to=martin@oneiros.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).