ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: languages
Date: Sun, 18 Jul 2021 21:37:10 +0200	[thread overview]
Message-ID: <9dcd8377-e695-b371-4c43-0db84167dbf0@gmail.com> (raw)
In-Reply-To: <3DC2AB5C-197E-495F-A74C-1D04BD576A83@ziggo.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1392 bytes --]

Hans van der Meer schrieb am 18.07.2021 um 16:39:
> Here is something I think that should be added to the documentation.
>
> /In the ConTeXt garden (page Command/mainlanguage) the description is:/
>
> mainlanguage Set the language of auto-generated language elements, 
> like the title of the table of contents or the appendix.
>
> /On the Command/language page:/
>
> Change the hyphenation rules, quotation marks, all that sort of thing, 
> to that of a different language. (The default language is English.)
>
> Testing showed that \mainlanguage sets both \currentlanguage and 
> \currentmainlanguage to the same value, while \language sets 
> \currentlanguage only.
>
> My suggestion is to add info to this behaviour to the mainlanguage 
> page, reflecting the fact that \mainlanguage does set both 
> \currentlanguage and \currentmainlanguage.Which is not apparent from 
> the current documentation.

It's a wiki, it's possible to add the information yourself.

> Another solution would be to separate \language and \mainlanguage 
> completely. An option I would prefer for clarity, because now the 
> order of calling \language and \mainlanguage makes a difference.

1. You're breaking nearly every existing document.

2. \language is only needed when you use more than 1 language in a 
document, otherwise \mainlanguage is enough to change labels and 
hyphentation patterns.

Wolfgang


[-- Attachment #1.2: Type: text/html, Size: 2705 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2021-07-18 19:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18 14:39 languages Hans van der Meer
2021-07-18 19:37 ` Wolfgang Schuster [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-23 17:23 languages Hans Hagen
2005-02-24 11:02 ` languages Vit Zyka
2005-02-24 18:38   ` languages Willi Egger
2005-02-25  3:09 ` languages Mojca Miklavec
2005-02-25 10:04   ` languages Hans Hagen
2005-02-25 21:48 ` languages VnPenguin
2005-02-27 10:23   ` languages h h extern
2002-02-06 16:34 Languages Giuseppe Bilotta
2002-02-06 18:41 ` Languages Henning Hraban Ramm
2002-02-07  0:00 ` Languages Bruce Horrocks
2002-02-07  6:34   ` Languages Dan Seracu
2002-02-07 19:52 ` Languages Alberto Nespoli
2000-05-31  8:41 Languages Dan Seracu
2000-05-31 10:01 ` Languages 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=9dcd8377-e695-b371-4c43-0db84167dbf0@gmail.com \
    --to=wolfgang.schuster.lists@gmail.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).