From: Exp <exprosic@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Official file ending?
Date: Tue, 4 Feb 2020 00:31:22 +0100 [thread overview]
Message-ID: <CALy-6cHVC_cGOLyQ88cAeT4s2787g3YoAmcT0mLWqFcq=Xw6DA@mail.gmail.com> (raw)
In-Reply-To: <7db42e17-6bf1-ce8d-b6de-1830cc560ff3@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1792 bytes --]
I would suggest to advertise with the ending another trademark that is not
a zero-entropy word in the programming world when not randomly capitalized,
and, if possible, that is not an everyday English word either.
Mkiv is a good choice for the moment. If there would be no Mkvi and so on,
it is good forever.
Le lun. 3 févr. 2020 à 23:05, Wolfgang Schuster <
wolfgang.schuster.lists@gmail.com> a écrit :
> Hans Hagen schrieb am 03.02.2020 um 15:28:
> > 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
>
> Why not just <FILE>.context
>
> 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
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 3008 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:[~2020-02-03 23:31 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
2020-02-03 22:05 ` Wolfgang Schuster
2020-02-03 23:31 ` Exp [this message]
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='CALy-6cHVC_cGOLyQ88cAeT4s2787g3YoAmcT0mLWqFcq=Xw6DA@mail.gmail.com' \
--to=exprosic@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).