From: "Richard Gabriel" <rgabriel@kerio.com>
Subject: Re: Hardcoded options in the Ruby scripts
Date: Wed, 25 Oct 2006 09:00:43 +0200 [thread overview]
Message-ID: <20061025070043.1182a70f@mx1.kerio.com> (raw)
In-Reply-To: 453CB89D.3010703@wxs.nl
[-- Attachment #1.1: Type: text/plain, Size: 3466 bytes --]
Hello Hans,
thanks for the answer.
> (adding a user inferface is more that adding something to
> texexec)
I understand, but I use the English interface for all languages anyway.
Maybe I'm doing something wrong or in a non-standard way...
For processing files with ConTeXt, I have a script which does (simplified to the minimum):
texmfstart texexec --interface=cont-$1 $2
So when I started to experiment with Chinese and Japanese, for example, I naturally wanted the processing to be consistent with other languages. I've simply "cloned" the cont-en.tex format file into cont-cn.tex and cont-ja.tex and defined the default language, default encoding etc. in them. And created new formats. But I had to add these new formats into scripts/ruby/base/tex.rb in order to generate and use them. In case of ConTeXt update, I have to do this change again and again. That's the reason why I've suggested to put these definitons into a separate (user) file.
>> 2. "Make all" should make ALL the defined ConTeXt formats, not the
>> default ones.
>--all means: all patterns
Mmm, sorry... I forgot that there are many formats other than cont-*... :-/
What does "all patterns" mean?
Before altering the tex.rb script, I've tried "texexec --make --all" several times, and it had always rebuilt the 'cont-en', 'cont-nl' and 'mptopdf' formats (maybe also 'metafun'(?); I'm not completely sure...).
-Richard
_____
From: Hans Hagen [mailto:pragma@wxs.nl]
To: mailing list for ConTeXt users [mailto:ntg-context@ntg.nl]
Sent: Mon, 23 Oct 2006 14:42:05 +0200
Subject: Re: [NTG-context] Hardcoded options in the Ruby scripts
Richard Gabriel wrote:
>
> 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.
such as ...? (adding a user inferface is more that adding something to
texexec)
>
> 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". :-(
which would be quite a lot -) what do you mean with all?
>
> 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]
hm, must think about it ; i don't like too many dependencies
>
> 2. "Make all" should make ALL the defined ConTeXt formats, not the
> default ones.
--all means: all patterns
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
[-- Attachment #1.2: Type: text/html, Size: 4242 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
next reply other threads:[~2006-10-25 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 7:00 Richard Gabriel [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-23 11:24 Richard Gabriel
2006-10-23 12:42 ` 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=20061025070043.1182a70f@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).