ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Proposal: making [[article]] and [[Article]] equivalent on the wiki
Date: Mon, 24 Sep 2012 10:24:18 +0200	[thread overview]
Message-ID: <CALBOmsam3JceHJgpzZ2BaRiT-sjBm_bBYrn=osH9LdUzytXR+A@mail.gmail.com> (raw)
In-Reply-To: <CAF=dkzyohZ++W7bKCEVXP-puMh3uGr-ANLnoXDyKc+MVTVVNBQ@mail.gmail.com>

Hello,

did someone, by any chance, already make that change?

On Wed, Sep 19, 2012 at 2:11 PM, Sietse Brouwer wrote:
> Hello, all,
>
> The wiki currently has $wgCapitalLinks = false; meaning that if one
> wishes to link to e.g. [[Columns]] inside a sentence one must write
> "See the [[Columns|columns]] article." And if one links to another
> article, one must remember whether its title is lowercase, Titlecase,
> or if it doesn't matter because a redirect exists.
>
> Proposal:
> I propose we set
> $wgCapitalLinks = true;
> $wgCapitalLinkOverrides[ NS_FILE ] = false;
> This will make writing a link as [[Article]] or [[article]] both
> correct, but retain case sensitivity in the rest of the article title.
> In the file namespace, however, case sensitivity will be retained for
> the entire name, so that people won't have to download e.g.
> "T-lilypond.tex".

The setting was changed from true to false in past on purpose. I found
it very annoying that all the words were capitalized, even if there
was no reason to capitalized them. Filenames (like
http://wiki.contextgarden.net/Cont-tmf.zip,
http://wiki.contextgarden.net/First-setup.sh) are not the only cases.
"write18" is another one etc.

Even if you change that setting, you still have no idea whether a page
is "Font Tools" or "Font tools" or "font tools". You can make a link
to [[font tools]] or [[headers and footers]] inside your sentence, but
that still won't help you to get to
    http://wiki.contextgarden.net/Font_Tools
    http://wiki.contextgarden.net/Headers_and_Footers
and most article names are actually very hard to guess, and in
contrast to wikipedia, the ConTeXt wiki hardly covers any substantial
amount of common words or phrases.

> Motivation below. Comments, agreement, disagreement welcome.

Personally I'm against that change.

> Motivation:
> Redirects can (and do) solve this, and so can changing the link, but
> that is busywork that nobody should have to do.

I agree, but having filenames capitalized is even more silly.

> * article titles will consistently be displayed in Titlecase

That is not always desired.

> * for titles that should start in lowercase, such as [[texexec]] or
> [[first-setup]], we'll need to add e.g. {{DISPLAYTITLE:texexec}}.

That partially compensates, but ...

Mojca

PS: can anyone please explain me what's with
    http://wiki.contextgarden.net/First-setup.sh
it's almost "an infinite chain" of redirects ... The real page,
http://wiki.contextgarden.net/First-setup, is the one that actually
makes least sense to me.
___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2012-09-24  8:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 12:11 Sietse Brouwer
2012-09-19 12:13 ` Philipp Gesang
2012-09-24  8:24 ` Mojca Miklavec [this message]
2012-09-24  8:44   ` Sietse Brouwer
2012-09-24  9:32   ` Arthur Reutenauer
2012-09-24  9:44     ` Sietse Brouwer
2012-09-24 11:11   ` Sietse Brouwer

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='CALBOmsam3JceHJgpzZ2BaRiT-sjBm_bBYrn=osH9LdUzytXR+A@mail.gmail.com' \
    --to=mojca.miklavec.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).