From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Why are pretty printer names uppercased?
Date: Wed, 26 Aug 2009 11:47:07 +0200 [thread overview]
Message-ID: <4A95049B.5030307@wxs.nl> (raw)
In-Reply-To: <20090826093704.GQ12901@katherina.student.utwente.nl>
Matthijs Kooijman wrote:
> Hi Hans,
>
>
>>> according to the wiki, and the current code, the arguments to
>>> \installprettytype should be uppercased. E.g.:
>>>
>>> \installprettytype [PHP] [PHP]
>> because want uppercase
>>
>> \startTEX
>> \stopTEX
>
> Well, those would be coming from the first argument of definetyping. AFAIU,
> neither argument to installprettytype is related to these commands.
sure but they are somewhat related (also with the color palets then)
>>> \definetyping[PHP] [option=PHP]
>
>> indeed. as i don't like casing in filenames, and function names
> Agreed, me neither.
>
>> actually, the advice is that user definitions use uppercase
>>
>> \definehead[MySection][section]
>>
>> etc, just to avoid clashes with built in commands
> That makes sense for commands, which is not what I'm proposing to change. I
> would propose making it look like the following:
>
> \installprettytype [php] [php]
> \definetyping [PHP] [option=php]
>
> Here, the second "php" refers to "pret-php.lua", the first and last "php"
> refer to each other and to the "php" in newvisualizer("php").
>
> The command defined is still \startPHP, but now the values that refer to other
> lowercase things (filename, pretty printer name) are lowercase consistently.
>
> How's this?
in order to get that working and remain compatible, we'd also need to
redefine
\definepalet [TEXcolorpretty] [colorpretty]
\definepalet [TEXgraypretty] [graypretty]
(ans use some nasty trickery to let texcolorpretty and TEXcolorpretty
both be valid)
etc and as users themselves seldom see the low level definitions it's
not worth the trouble
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2009-08-26 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 8:52 Matthijs Kooijman
2009-08-26 9:11 ` Hans Hagen
2009-08-26 9:37 ` Matthijs Kooijman
2009-08-26 9:47 ` Hans Hagen [this message]
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=4A95049B.5030307@wxs.nl \
--to=pragma@wxs.nl \
--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).