zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: <zsh-workers@sunsite.auc.dk>
Subject: Re: Doc fixes - US vs. British spelling
Date: Thu, 17 Jun 1999 15:10:08 +0000	[thread overview]
Message-ID: <990617151008.ZM5289@candle.brasslantern.com> (raw)
In-Reply-To: <4FBF540FF16FD1119D9600A0C94B2B51F29E8F@napier.logica.co.uk>
In-Reply-To: <9906171233.AA33604@ibmth.df.unipi.it>
In-Reply-To: <19990617092507.A27680@argo.cit.nih.gov>

On Jun 17,  9:45am, Kiddle, Oliver wrote:
} Subject: Doc fixes - US vs. British spelling
}
} Following is a small patch to the documentation. Mostly it is changing
} 'initialise' to 'initialize'. If British spelling is generally prefered
} then I can create a patch to do the change the other way. I just think
} that we should be consistent.

This came up once before, soon after Zoltan had become coordinator IIRC.
The zsh-workers archive seems to be down right now; my local copy only
finds discussion of whether Clive should clean up the original zsh.texi.

I think the conclusion was that people from both sides of the pond are
going to be adding new snippets of doc, so inconsistent spellings are
bound to slip in again at some point, and therefore why bother ...

The only problem is that you have to remember to use i[sz]e in searches.

On Jun 17,  2:33pm, Peter Stephenson wrote:
} Subject: Re: Doc fixes - US vs. British spelling
}
} On the other hand, I'm not sure I can bring myself to face `honor' and
} `color'.  Luckily, they don't occour, err, occur; we'd better keep it that
} way to avoid an incident.

There's an instance of "honoured" in the 3.0.6 documentation.

On Jun 17,  9:25am, Anthony.Iano-Fletcher@nih.gov wrote:
} Subject: Re: Doc fixes - US vs. British spelling
}
} Didnt I see mention of colour support in zsh?

Yes, and Greg's patch handles both ZLS_COLORS and ZLS_COLOURS as special
parameters, so we'd end up with both spelling in the doc even if PWS will
have to keep looking away on that page.

} How does the Babelfish site
} 	http://babelfish.altavista.digital.com/cgi-bin/translate?
} do on the zsh manual?

Oh, my ... apart from the fact that it would probably take a week to
process it, I'll bet the results would be truly hilarious.  (That aside,
the problem would be that you can't stop it from translating the names
of the builtin commands and other keywords.)

Recognize this?

1. * Verschachtelter Ersatz *
     wenn mehrfache verschachtelte ${...}-Formulare anwesend sind, wird
     Ersatz vom Innere außerhalb durchgeführt. an jed Stufe, d Ersatz
     berücksichtigen ob d aktuell Wert sein ein scalar oder ein Reihe,
     ob d vollständig Ersatz sein in doppelt Anführungsstrich, und was
     Markierungsfahne sein angeben zu d aktuell Stufe von Ersatz, gerade
     als ob d verschachteln Ersatz sein d äußerst. Die Markierungsfahnen
     werden nicht bis zum Umgeben des Ersatzes fortgepflanzt; der
     verschachtelte Ersatz bringt entweder einen Scalar oder eine Reihe
     zurück, wie durch die Markierungsfahnen festgestellt, vielleicht
     eingestellt auf die Veranschlagung. Alle folgenden Jobsteps finden
     statt, wo anwendbar auf allen Stufen des Ersatzes. Beachten Sie,
     daß, es sei denn Markierungsfahne des `(P)' anwesend ist, die
     Markierungsfahnen und alle mögliche Tiefzeichen direkt auf den
     Wert des verschachtelten Ersatzes zutreffen; z.B., die Expansion
     ${${foo}} benimmt sich genau dasselbe wie ${foo}.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1999-06-17 15:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-17  8:45 Kiddle, Oliver
1999-06-17 11:18 ` Geoff Wing
1999-06-17 12:49 ` Anthony.Iano-Fletcher
1999-06-17 12:33   ` Peter Stephenson
1999-06-17 13:25     ` Anthony.Iano-Fletcher
1999-06-17 15:10       ` Bart Schaefer [this message]
1999-06-17 13:13 Sven Wischnowsky

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=990617151008.ZM5289@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).