From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
"Philipp A." <flying-sheep@web.de>
Subject: Re: Official file ending?
Date: Mon, 3 Feb 2020 15:28:25 +0100 [thread overview]
Message-ID: <29c5f537-a747-0e9b-14a6-fc95e4bf2f41@xs4all.nl> (raw)
In-Reply-To: <CAN8d9gkG6UwhsE+C7JkgqjhvzELbrc6n8yK6foTCR59frqznLg@mail.gmail.com>
On 2/3/2020 3:07 PM, Philipp A. wrote:
> Hi!
>
> Most text editors have LaTeX specific syntax highlighting, so it makes
> sense to give your ConTeXt file a ending it can be distinguished with.
> Is there a blessed one?
>
> * .ctx: Would mirror the semi-common .ltx, but is used for XML files
> inside of ConTeXt itself
context ctx files are xml files indeed
> * .mkiv: Is that just for ConTeXt or all LuaTeX stuff? Would it make
> sense to give text documents that extension?
you can do that (or mkvi or lmtx or ...)
> * Something else? (.tex doesn’t count, it’s shared with LaTeX files
> and plain TeX files)
so then use mkiv
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2020-02-03 14:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 14:07 Philipp A.
2020-02-03 14:28 ` Hans Hagen [this message]
2020-02-03 22:05 ` Wolfgang Schuster
2020-02-03 23:31 ` Exp
2020-02-03 23:48 ` Floris van Manen
2020-02-04 15:15 ` Philipp A.
2020-02-04 15:34 ` Pablo Rodriguez
2020-02-04 16:57 ` Pablo Rodriguez
2020-02-04 19:27 ` kaddour kardio
2020-02-04 19:39 ` Henning Hraban Ramm
2020-02-04 20:14 ` Floris van Manen
2020-02-05 9:18 ` Hans Hagen
2020-02-05 9:25 ` Philipp A.
2020-02-05 9:24 ` Hans Hagen
2020-02-05 10:00 ` Henning Hraban Ramm
2020-02-05 10:28 ` 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=29c5f537-a747-0e9b-14a6-fc95e4bf2f41@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=flying-sheep@web.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).