From: Atsuhito Kohda <atsu10.kohda@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: feature request
Date: Sat, 6 Jul 2019 08:44:03 +0900 [thread overview]
Message-ID: <CABHwazUxaS5joSP=JGN4kE__YxvKrXkeOgfJ3cJxWGOLZryBGQ@mail.gmail.com> (raw)
In-Reply-To: <20190704095456.7395c4ca@poo.hsd1.co.comcast.net>
[-- Attachment #1.1: Type: text/plain, Size: 2392 bytes --]
Hi Alan,
> 1) when new to Context, coming from LaTeX and learning a new system;
...
> One gets over the first case rather quickly and then there is no
> going back: the philosophies are so different.
Hmm, I'll make an effort to be a LaTeX user and also ConTeXt user.
Best regards,
Atsuhito Kohda
2019年7月5日(金) 0:56 Alan Braslau <braslau.list@comcast.net>:
> On Thu, 4 Jul 2019 11:16:22 -0400 (EDT)
> Aditya Mahajan <adityam@umich.edu> wrote:
>
> > > BTW, I constantly convert Beamer documents into ConTeXt's
> > > simpleslide documents recently and it is very convenient
> > > if I can use \pmatrix{a&b\cr c&d\cr} style because it is similar
> > > to LaTeX documents.
> >
> > You can create a private module with the definitions that you need.
> > If these are general enough, then you can also release it as a third
> > party module for others to use. I don't see the value of adding (and
> > maintaining!) a module that provides LaTeX compatibility as part of
> > the core.
>
> LaTeX compatibility is desired (by some)
> 1) when new to Context, coming from LaTeX and learning a new system;
> 2) for ConTeXt users who are *required* to sometimes use LaTeX,
> for example in submissions to journals etc. that accept LaTeX but
> cannot handle Context sources.
>
> One gets over the first case rather quickly and then there is no
> going back: the philosophies are so different.
>
> In the second case, I restrict myself to a strict use of the journal's
> own template (for example with revtex), never asking for anything more
> nor anything less.
>
> In a third situation of editors who give lip service to accepting TeX
> submissions, I give them plain text for they are going to re-key in
> everything in any case. I provide them with a pdf that they can use
> to correct their markup.
>
> Alan
>
> ___________________________________________________________________________________
> 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 : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 3401 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-07-05 23:44 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 6:00 Atsuhito Kohda
2019-07-03 6:35 ` Henri Menke
2019-07-03 6:42 ` Henri Menke
2019-07-04 5:18 ` Atsuhito Kohda
2019-07-04 5:48 ` Henri Menke
2019-07-05 23:31 ` Atsuhito Kohda
2019-07-04 15:16 ` Aditya Mahajan
2019-07-04 15:54 ` Alan Braslau
2019-07-05 23:44 ` Atsuhito Kohda [this message]
2019-07-05 23:35 ` Atsuhito Kohda
-- strict thread matches above, loose matches on Subject: below --
2011-11-11 15:34 Steffen Wolfrum
2011-11-11 15:53 ` Andreas Harder
2011-11-11 15:57 ` Wolfgang Schuster
2011-11-11 16:01 ` Wolfgang Schuster
2011-11-11 18:47 ` Idris Samawi Hamid ادريس سماوي حامد
2011-11-13 10:55 ` Steffen Wolfrum
2011-11-13 21:33 ` Andreas Schneider
2011-11-14 7:57 ` Steffen Wolfrum
2011-11-14 8:07 ` Hans Hagen
2011-11-14 9:22 ` Steffen Wolfrum
2011-11-14 18:38 ` Idris Samawi Hamid ادريس سماوي حامد
2011-11-15 22:03 ` Idris Samawi Hamid ادريس سماوي حامد
2011-11-15 22:11 ` Wolfgang Schuster
2011-11-15 22:28 ` Aditya Mahajan
2011-11-15 22:47 ` Idris Samawi Hamid ادريس سماوي حامد
2011-11-14 8:47 ` Aditya Mahajan
2011-11-14 14:03 ` Hans Hagen
2011-11-15 3:35 ` Aditya Mahajan
2011-11-15 5:43 ` Aditya Mahajan
2011-11-15 8:56 ` Hans Hagen
2007-07-05 17:41 Feature request John R. Culleton
2007-07-05 21:37 ` Patrick Gundlach
2007-07-05 22:27 ` John R. Culleton
2007-07-06 8:09 ` Patrick Gundlach
2005-07-27 9:58 Steffen Wolfrum
2005-07-27 22:16 ` Hans Hagen
[not found] <a06210200bf0958f2bc0f@87.193.3.198>
2005-07-26 16:20 ` Mojca Miklavec
2005-07-26 22:56 ` Hans Hagen
2005-07-27 5:15 ` luigi.scarso
2005-07-26 15:33 Steffen Wolfrum
2005-07-26 22:38 ` Hans Hagen
2005-07-26 15:00 Steffen Wolfrum
2005-07-26 13:32 Steffen Wolfrum
2005-07-26 14:21 ` Hans Hagen
2005-07-26 14:32 ` Hans Hagen
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='CABHwazUxaS5joSP=JGN4kE__YxvKrXkeOgfJ3cJxWGOLZryBGQ@mail.gmail.com' \
--to=atsu10.kohda@gmail.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).