From: "Procházka Lukáš Ing. - Pontex s. r. o." <LPr@pontex.cz>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: "Page-breakable" \subsubsubject?
Date: Tue, 12 Oct 2010 10:45:19 +0200 [thread overview]
Message-ID: <op.vkgfxttrwshuv7@lpr> (raw)
In-Reply-To: <AANLkTimD=EpE_DMAuoq85GpctOEiNk9tPax5BAonNNgy@mail.gmail.com>
On Tue, 12 Oct 2010 10:40:19 +0200, luigi scarso <luigi.scarso@gmail.com> wrote:
>>> • the ctx file extension has a special meaning for context (file for
>>> proprocessing in xml format).
>>
>> - OK, I'm planning to use .tex for Ctx files in the future. Now I'm using
>> LaTeX and ConTeXt both, so I use .ctx extension for Ctx sources. Moreover,
>> till I'm trying to achieve the same things in Ctx as I'm used to do in
>> LaTeX, I may have <a-file>.tex (for LaTeX) and <a-file>.ctx (for ConTeXt) in
>> the same directory. I initially don't know whether I'll succeed with Ctx
>> version (I'm still Ctx beginner and, although many things may be made more
>> easily in Ctx, they work for me in LTX in the moment but still not in Ctx).
> You can also use .mkiv for ConTeXt MKIV
Yes, it sounds better. I noticed .mkiv files in Ctx installation tree but I thought this extension is "reserved" for a kind of files rather than .ctx.
> and .tex for LaTeX and ConTeXt MKII
(It allows .mkii for "old style" Ctx as well.)
Lukas
___________________________________________________________________________________
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:[~2010-10-12 8:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 7:13 Procházka Lukáš Ing. - Pontex s. r. o.
2010-10-12 8:03 ` Wolfgang Schuster
2010-10-12 8:13 ` Peter Münster
2010-10-12 8:18 ` Wolfgang Schuster
2010-10-12 8:35 ` Procházka Lukáš Ing. - Pontex s. r. o.
2010-10-12 8:40 ` luigi scarso
2010-10-12 8:45 ` Procházka Lukáš Ing. - Pontex s. r. o. [this message]
2010-10-12 8:49 ` luigi scarso
2010-10-12 9:30 ` Alan BRASLAU
2010-10-12 9:35 ` Hans Hagen
2010-10-12 9:36 ` Taco Hoekwater
2010-10-12 10:12 ` Alan BRASLAU
2010-10-12 11:15 ` Hans Hagen
[not found] ` <AANLkTi=P23N-Z3-99G1=+zEFDN04uiKj-zcH372c6PHP@mail.gmail.com>
2010-10-12 9:45 ` luigi scarso
2010-10-12 10:18 ` Alan BRASLAU
2010-10-12 9:17 ` Khaled Hosny
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=op.vkgfxttrwshuv7@lpr \
--to=lpr@pontex.cz \
--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).