ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <hraban@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: typescript repository
Date: Thu, 26 Mar 2009 10:35:44 +0100	[thread overview]
Message-ID: <8DB150A8-010B-4828-83AA-A7145E8674E3@fiee.net> (raw)
In-Reply-To: <5E30B1C2-103D-49F8-8A6A-C33CB55B0643@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 607 bytes --]

I'd suggest to agree on a unified naming system, like
type-VENDOR-FONT.tex
or organize the typescript in directories like the fonts themselves.

I guess I should update my old public typescripts to LuaTeX soon...
WRTT: Can we agree to only provide MkIV typescripts? (I hope their  
format is stable now?)

Can we agree on some versioning? (If we keep the files in some git/svn  
repository that should be no problem, we can just checkout the latest  
version.)


Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)


[-- Attachment #1.2: Signierter Teil der Nachricht --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 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://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2009-03-26  9:35 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23 20:30 Wolfgang Schuster
2009-03-23 20:32 ` luigi scarso
2009-03-23 21:20   ` Curiouslearn
2009-03-23 21:44 ` Peter Münster
2009-03-23 21:46 ` Aditya Mahajan
2009-03-23 21:51 ` Mohamed Bana
2009-03-23 22:11   ` Wolfgang Schuster
2009-03-24 15:27     ` Bruce D'Arcus
2009-03-24 17:39       ` Wolfgang Schuster
2009-03-25  3:08         ` Bruce D\'Arcus
2009-03-25  3:31           ` Mohamed Bana
2009-03-25 11:51             ` Wolfgang Schuster
2009-03-25 13:37               ` Mohamed Bana
2009-03-25 14:33                 ` Wolfgang Schuster
2009-03-25 14:42                   ` Mohamed Bana
2009-03-26  9:35         ` Henning Hraban Ramm [this message]
2009-03-26 10:00           ` Wolfgang Schuster
2009-03-24 23:14       ` Idris Samawi Hamid ادريس سماوي حامد
2009-03-25  7:24         ` Marcin Borkowski
2009-03-25 13:52           ` Bruce D\\\'Arcus
2009-03-25 14:30             ` Marcin Borkowski
2009-03-26  9:04               ` Hans Hagen
2009-03-26  9:13                 ` Arthur Reutenauer
2009-03-26  9:23                   ` luigi scarso
2009-03-26  9:29                   ` Wolfgang Schuster
2009-03-26  9:50                   ` Hans Hagen
2009-03-25 14:40             ` Wolfgang Schuster
2009-03-23 22:00 ` Diego Depaoli
2009-03-23 22:00 ` luigi scarso
2009-03-24 10:17 ` Alan Stone
2009-03-25 20:43 ` Wolfgang Schuster
2009-03-26 18:38   ` Mohamed Bana
2009-03-26 18:44     ` Aditya Mahajan

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=8DB150A8-010B-4828-83AA-A7145E8674E3@fiee.net \
    --to=hraban@fiee.net \
    --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).