git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Specify UK English for the documentation source files.

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 30, 2013, 16:40 UTC
Message-ID
<7vppu0vw4m.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1375197114-10742-1-git-send-email-marcnarc@xiplink.com>
Marc Branchaud <marcnarc@xiplink.com> writes:
Show 9 quoted lines
> This will hopefully avoid questions over which spelling and grammar should
> be used.  Translators are of course free to create localizations for other
> English dialects.
>
> Signed-off-by: Marc Branchaud <marcnarc@xiplink.com>
> ---
>
> Although I'm Canadian I figured en_CA would be a little too parochial.  I
> don't have a strong preference for en_UK over en_US though.

If we were to specify one, I would have to say we should standardise on en_US. Like it or not, that is the lingua franca in the CS world (I'd also admit that most of the extra 'u' in words like "behaviour" are my typoes, not even coming from a conscious decision to choose en_UK).

I'd appreciate "typofix" patches to address genuine typoes like "s/filesytem/filesystem/" done separately, so that we do not even have to get into language bikeshedding. Even if we did decide to stick to en_US, the typofix patches and en_US patches should be separate to ease reviews.

Previous: Fredrik GustafssonNext: Marc Branchaud
Message 6 of 12 in “Documentation: fix typos in man pages”
  1. Documentation: fix typos in man pagesØystein Walle, Jul 29, 2013
  2. Marc BranchaudJul 30, 2013
  3. Junio C HamanoJul 30, 2013
  4. Specify UK English for the documentation source files.Marc Branchaud, Jul 30, 2013
  5. Fredrik GustafssonJul 30, 2013
  6. Junio C HamanoJul 30, 2013
  7. Provide some linguistic guidance for the documentation.Marc Branchaud, Aug 1, 2013
  8. Marc BranchaudAug 1, 2013
  9. Junio C HamanoAug 1, 2013
  10. Provide some linguistic guidance for the documentation.Marc Branchaud, Aug 1, 2013
  11. Jonathan NiederAug 2, 2013
  12. Marc BranchaudAug 2, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.