ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Richard Gabriel" <rgabriel@kerio.com>
Subject: Hardcoded options in the Ruby scripts
Date: Mon, 23 Oct 2006 13:24:54 +0200	[thread overview]
Message-ID: <20061023112454.9e201cbe@mx1.kerio.com> (raw)


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

Hello Hans,

I'm still wondering why there are certain formats hardcoded in your scripts and how the "make all formats" feature does (not work).

See scripts/ruby/base/tex.rb:

Lines 131-137:
Here are a few languages predefined which texexec "knows". If I want to add a format for another language, I have to add a new line here.

Line 339: 
Here are the "default" TeX formats defined. No problem to consider something as default ;-), but the point is that "texexec --make --all" actually does "make all DEFAULT formats", NOT "make all AVAILABLE formats". :-(

Anyway, the main problem I see is altering of a script which comes with the ConTeXt distribution - the changes made into this scripts must be done again and again after each update.

My suggestion is:
1. To put the format definition into a separate file (like user.rb or so) which won't be owerwritten in any case. 
[Note: cont-usr.tex is a good analogy to this]

2. "Make all" should make ALL the defined ConTeXt formats, not the default ones.

Thanks,
Richard

[-- Attachment #1.2: Type: text/html, Size: 1339 bytes --]

[-- Attachment #2: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

             reply	other threads:[~2006-10-23 11:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-23 11:24 Richard Gabriel [this message]
2006-10-23 12:42 ` Hans Hagen
2006-10-25  7:00 Richard Gabriel

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=20061023112454.9e201cbe@mx1.kerio.com \
    --to=rgabriel@kerio.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).