X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1347" "Wed" "26" "January" "1994" "14:43:12" "GMT" "David Carlisle" "carlisle@cs.man.ac.uk" "<199401261445.AA06657@mail.cs.tu-berlin.de>" "35" "Re: Changing default preloads" "^Date:" nil nil "1" "1994012614:43:12" "Changing default preloads" (number " " mark " David Carlisle Jan 26 35/1347 " thread-indent "\"Re: Changing default preloads\"\n") "<9401261407.AB06791@m1.cs.man.ac.uk>"]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/24.6.93) id AA09694; Wed, 26 Jan 94 15:47:00 +0100 Received: from mail.cs.tu-berlin.de by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA26593; Wed, 26 Jan 94 15:45:58 +0100 Received: from tubvm.cs.tu-berlin.de by mail.cs.tu-berlin.de with SMTP id AA06657 (5.65c8/IDA-1.4.4(mail.m4[1.12]) for <@MAIL.CS.TU-BERLIN.DE:Schoepf@SC.ZIB-BERLIN.DE>); Wed, 26 Jan 1994 15:45:56 +0100 Message-Id: <199401261445.AA06657@mail.cs.tu-berlin.de> Received: from TUBVM.CS.TU-BERLIN.DE by tubvm.cs.tu-berlin.de (IBM VM SMTP V2R2) with BSMTP id 2604; Wed, 26 Jan 94 15:45:57 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE (NJE origin MAILER@DHDURZ1) by TUBVM.CS.TU-BERLIN.DE (LMail V1.2a/1.8a) with BSMTP id 2603; Wed, 26 Jan 1994 15:45:56 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE (NJE origin LISTSERV@DHDURZ1) by VM.URZ.UNI-HEIDELBERG.DE (LMail V1.2a/1.8a) with BSMTP id 9505; Wed, 26 Jan 1994 15:45:26 +0000 Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <9401261407.AB06791@m1.cs.man.ac.uk> (message from Mike Piff on Wed, 26 Jan 1994 13:25:00 LCL) Date: Wed, 26 Jan 1994 14:43:12 GMT From: David Carlisle Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: Changing default preloads Status: R X-Status: X-Keywords: X-UID: 1304 Mike: True, I had forgotten that TeX can't read patterns, only iniTeX. But now the problem is even bigger, as all possible languages have to be pre-loaded for portability. No you dont need to load all patterns, but documents are flagged so you know when you need to build a new format. I dont plan to build German hyphenation in to my local set up (or UK English for that matter) But if I get a document that says \usepackage[german]{babel} I can tell straight away that either I need to build a new format, or put up with bad line breaks. If the German site had built in german as default, the document wouldnt have been flagged in this way, and I would not have known what to do. (I can not tell German from Dutch, having a typically English mastery of these languages). The problem is worse for UK English. If you make UK English hyphenation the default at Sheffield (and your users will forget this) then when they `hand tune' their documents to get ideal page breaks (yes people do do this) they will not work at most other sites, and it will be very hard to tell the cause, the log files will not give this information. No one objects (much) to writing \documentstyle or \documentclass at the front of every document, so why do you object to a couple of other declarations setting up encodings/languages/papersize etc ? David