ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Procházka Lukáš Ing. - Pontex s. r. o." <LPr@pontex.cz>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: [wiki] fake account spam
Date: Fri, 26 Apr 2013 08:31:01 +0200	[thread overview]
Message-ID: <op.wv4xpzvktpjj8f@lpr> (raw)
In-Reply-To: <517973BD.60804@uni-bonn.de>

Hello,

On Thu, 25 Apr 2013 20:19:41 +0200, Thomas A. Schmitz <thomas.schmitz@uni-bonn.de> wrote:

> On 04/25/2013 07:31 PM, Sietse Brouwer wrote:
>> Hi Taco,

>> I think it's a good idea to update the security questions --- it's
>> easy to do, it'll probably work, and we can always move on to stronger
>> measures that require more work. Below are some replacemetn questions.
>
> Yes, I had already contacted Mojca a couple of weeks ago. I think we
> should demand that all questions be answered in Dutch. Every serious
> ConTeXter has to know some Dutch,

even though I consider myself a serious Ctx user, Dutch is still Greek to me.

> and nothing better than asking "What
> is the ConTeXt keyword for a two-sided layout" and expecting
> "dubbelzijdig" as an answer.

Goggle translator would help in this case (http://translate.google.com/#en/nl/doublesided);
but having a "more complicated keyword/option" may mean a unanswered/unanswerable question...

How about to prompt the user to encode a displayed math, e.g. "b/a2^3" to be answered "$\frac{b}{a_2^3}$"?

Best regards,

Lukas


> If that doesn't help, we make them
> pronounce it...
>
> Thomas


-- 
Ing. Lukáš Procházka [mailto:LPr@pontex.cz]
Pontex s. r. o.      [mailto:pontex@pontex.cz] [http://www.pontex.cz]
Bezová 1658
147 14 Praha 4

Tel: +420 244 062 238
Fax: +420 244 461 038

___________________________________________________________________________________
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:[~2013-04-26  6:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 13:43 Philipp Gesang
2013-04-05 13:59 ` Mojca Miklavec
2013-04-05 14:09   ` Arthur Reutenauer
2013-04-06  1:18     ` Leo Arnold
2013-04-05 14:40   ` Alan BRASLAU
2013-04-06 14:53   ` Philipp Gesang
2013-04-25 17:31     ` Sietse Brouwer
2013-04-25 17:46       ` Aditya Mahajan
2013-04-25 21:52         ` Sietse Brouwer
2013-04-26  8:57           ` Alan BRASLAU
2013-04-26  9:32             ` Wolfgang Schuster
2013-04-26  9:44             ` Hans Hagen
2013-04-25 18:19       ` Thomas A. Schmitz
2013-04-25 21:07         ` Alan BRASLAU
2013-04-26  6:31         ` Procházka Lukáš Ing. - Pontex s. r. o. [this message]
2013-04-26  6:55           ` Thomas A. Schmitz
2013-04-26  7:37             ` Taco Hoekwater
2013-04-26  7:48               ` luigi scarso
2013-04-26  8:41             ` Alan BRASLAU

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=op.wv4xpzvktpjj8f@lpr \
    --to=lpr@pontex.cz \
    --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).