From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Hans Hagen <j.hagen@xs4all.nl>
Cc: "Jairo A. del Rio" <jairoadelrio6@gmail.com>
Subject: Re: About Latex compatibility module
Date: Mon, 25 May 2020 19:34:05 +0200 [thread overview]
Message-ID: <9382b283-a699-742d-b822-ef12c506306f@gmail.com> (raw)
In-Reply-To: <616d0bfd-ecce-f7c2-44ab-d9bd6d88a320@xs4all.nl>
Hans Hagen schrieb am 25.05.2020 um 17:54:
> On 5/24/2020 1:43 AM, Jairo A. del Rio wrote:
>> Hi everyone! I was reading some old posts on TeX.SX about LaTeX
>> support on ConTeXt and I found the following:
>>
>> https://web.archive.org/web/20110822085249/https://modules.contextgarden.net/LaTeX
>>
>>
>> However, not only the module seems to be deprecated, but there's no
>> more info about the module now (links are broken and the like). Btw
>> the test file (latextest.tex) included fails to compile:
>>
>> > tex error on line 165 in file t-ltmsen.tex: ! Undefined control
>> sequence
>>
>> >> \newskip\@rightskip \@rightskip \z@skip
>
> looks like someplace one has to define \z@skip to be 0pt (in this case
> it's actually redundant code because a newskip is likely to be zero)
In many cases one can replace the old name with @ with current names,
e.g. \z@skip will become \zeroskip.
>> Is it possible to make it work? I think it would be nice if some
>> minimal LaTeX macros were supported. Thank you in advance!
> Depends. It's not that hard to define some basic 'handle some latex
> cases' module but the question is "for what purpose?". When I look at
> those decade old files in that archive I see a lot of messy code that
> one needs to isolate and even then we can assume that users use more
> than a few commands. When they only use the top-ten commands, no
> problem, but when they start setting lengths or so ... why use context
> then. I have no problem mapping a few commands so that new users can
> cut-n-paste some code as a starter but somehoen has to come up with the
> list of commands and minimal test files then.
>
> Apart from the (probably a bit boring) challenge I think it doesn't pay
> off. Also, the systems are conceptually too different I think.
In the end you have to port the base commands of LaTeX which includes
- lists
- floats
- references
- font switches
- math
- etc.
and just another one (and another one ...).
It's just not worth the effort and we should spend the time to improve
ConTeXt and add missing features.
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-05-25 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 23:43 Jairo A. del Rio
2020-05-25 15:54 ` Hans Hagen
2020-05-25 17:34 ` Wolfgang Schuster [this message]
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=9382b283-a699-742d-b822-ef12c506306f@gmail.com \
--to=wolfgang.schuster.lists@gmail.com \
--cc=j.hagen@xs4all.nl \
--cc=jairoadelrio6@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).