From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: key=value parameters
Date: Fri, 23 Jul 2004 12:53:33 +0200 [thread overview]
Message-ID: <4100EE2D.4000906@seznam.cz> (raw)
In-Reply-To: <20040723111209.2d36bd92@glenlivet.elvenkind.com>
Thank you Taco.
>>I can imagine next solutions:
>>1) Do not use predefined keys in my macros, e.g. textWidth instead of
>> textwidth [=user unfriendly].
>
> If you decide on this solution, please use Textwidth instead (at least
> something that starts with a capital letter).
OK, but I do not like this solution.
>>2) Use original (mostly Dutch) keys inside of my macros
>> [=developer unfriendly].
>
> In this case, the "correct" solution is to use the interfaced versions
> like \c!tekstbreedte et al. inside your macros. This is unwieldy if you
> are not very familiar with the ConTeXt source, but it allows multilingual
> input (very user friendly).
That is true I was not familiar about \c!... But problem is not in
familiarity with ConTeXt source but Dutch language. One should write
\c!tekstbreedte instead of \c!textwidth. For non Dutch it means all the
time search at mult-*.tex. I know, solution is to learn Dutch... Hans
has plan to rewrite all code to English, hasn't it?
Very good idea.
Multilingual input:
- In late 90. when I met ConTeXt first time, I was very confused. Some
macros work, something was ignored. It took several days to discover
that I have to write (in my czech format) \nastavbarvy instead of
\setupcolors. After that I quickly switch to english interface.
- Multilingual interface is a nice example of ConTeXt capability, but a
bit inpractical. It keeps from source code exchange. I can imagine some
transtlators, but...
- I think there is no many ConTeXt users (even any?) that use non
English or non Dutch interface (languages in which reference manual is
written).
>>3) Define:
>> \unprotect
>> \def\getparametersALL{\dogetparameters\dosetvalueALL}
>
> Actually there is no need to define anything, you can just use \rawgetparameters
> instead of \getparameters.
Great, but unfortunately it does not work with empty parameter list [].
No I have no time but I will look for better definition of
\rawgetparameters and \rawsetparameter.
Vit Zyka
next prev parent reply other threads:[~2004-07-23 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 8:46 Vit Zyka
2004-07-23 9:12 ` Taco Hoekwater
2004-07-23 10:53 ` Vit Zyka [this message]
2004-07-23 11:07 ` Taco Hoekwater
2004-07-23 11:32 ` Re[2]: " Giuseppe Bilotta
2004-07-23 18:46 ` Hans Hagen Outside
2004-07-24 8:56 ` Vit Zyka
2004-07-24 16:10 ` Hans Hagen Outside
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=4100EE2D.4000906@seznam.cz \
--to=vit.zyka@seznam.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).