From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LuaTeX 64bit
Date: Sun, 19 Apr 2009 11:55:24 +0200 [thread overview]
Message-ID: <49EAF50C.9020903@wxs.nl> (raw)
In-Reply-To: <6faad9f00904181444u6e21fd3aob82e1b83d670ff82@mail.gmail.com>
Mojca Miklavec wrote:
> On Sat, Apr 18, 2009 at 23:09, Mohamed Bana wrote:
>> One more question, how do I only create the formats for British English
>> only? No Dutch, American English etc.. I'm going to argue on the list
>> that the en_GB should be the default ;), but I'll save that for another day.
>
> There is only one English format that you can generate with "texexec
> --make en". If you're speaking about how to generate only that one
> with first-setup.sh, then you should be, at least in theory, able to
> generate only the chosen formats with --formats switch or my modifying
> the lua file that gets generated, but I imagine that it doesn't work
> or at least I have never tested it so far.
>
>> do you know if first-setup.sh only downloads the files /only if/ they're are
>> changes? i mean could a simple checksum do the job?
>
> Yes, it only downloads the modified files, but it doesn't use
> checksums since using them is much slower. You could add an additional
> -c switch, but you will not notice any difference (apart from a few
> files that Hans recreates every time when he uploads a new zip, but
> that's neglectable). Rsync checks for date+size. Only if these two are
> different it fetches the file. You could add checksum checking, but I
> guess that you don't gain anything.
>
> The only critical component where I really do need to change this are
> luatex and metapost source, but this only concerns binary builders,
> not users.
there has been a time that this was possible, but inpractice it's not
that handy ... specifying the language should be part of the document
preamble; in that time we had no gyre and as language is related to
patterns + font encodings in mkii it was even more tricky
one thing that you can do is add \mainlanguage[gb] to cont-sys.tex
default to brittish english so that on your system it always starts that
way; the overhead is nil
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
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2009-04-19 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 19:23 Mohamed Bana
2009-04-17 9:40 ` Mojca Miklavec
2009-04-18 21:09 ` Mohamed Bana
2009-04-18 21:44 ` Mojca Miklavec
2009-04-18 21:49 ` Mojca Miklavec
2009-04-19 9:55 ` Hans Hagen [this message]
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=49EAF50C.9020903@wxs.nl \
--to=pragma@wxs.nl \
--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).