ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Patrick Gundlach" <patrick@gundla.ch>
Subject: Re: customizing footnote numbers
Date: 6 Apr 2005 10:38:17 +0200	[thread overview]
Message-ID: <m2ll7wnvuu.fsf@levana.de> (raw)
In-Reply-To: <20050405225257.GB24022@localhost.localdomain> (Paul Tremblay's message of "Tue, 5 Apr 2005 18:52:57 -0400")


[...]


>>We are in a fully programmable environment,
>> and it is extremely unConTeXtish to hack the visual appearance. 
>
> I am an XML author, so am pretty amazed to hear that one should not mix
> appearance and content in ConTeXt. Most of a ConTeXt document involves
> visual appearance. What is one saying when one writes \blank[12pt]?

This is visual appearance, of cource. But I am not talking about one
single instance of \blank anywhere, I am talking about changing a
reaeated statement (like the footnotes) by visual means. And
formatting instructions have no right to exist there (in fact they
should be filtered out by \sanitizelogigalmarkup{\footnote...}. This
is one of the great advantages of using a high level language such as
LaTeX or ConTeXt (and ConTeXt so much more than LaTeX) that we can
define layout in this way.

Since you come from an XML background and only have to change your
stylesheet, the hackary is doable, nobody ever sees it. But this
hackery is not to be used when using Context directly.

> Yes, that would be nice.  But until I see a concrete solution, I will
> continue to use and post my solution. A rule of etiquette is that if you
> don't have a better solution, or don't want to document it, don't attack
> the current solution, not matter how impure. 

Sorry, but I strongly disagree. It is not nice to teach/show other
people such code. They will take it for granted and put in their
documents. I have seen far too many LaTeX documents where exactly this
procedure leaded to unmaintainable code. It took me hours to extract
and correct those ugly hacks. One example: a person learned how to
remove indentation from a paragraph by saying \noindent. So every
paragraph had a \noindent before the paragraph (instead of doing it
right by saying \noindent0pt). And it was a long
document (and the \noindent was just one of the stupid things). So my 
advice is not to publish such code without several dangerous bend
signs.

Patrick
-- 
ConTeXt wiki: http://contextgarden.net

  reply	other threads:[~2005-04-06  8:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-03 19:58 Paul Tremblay
2005-04-04  6:10 ` Paul Tremblay
2005-04-04  8:29   ` Hans Hagen
2005-04-04 10:14     ` Patrick Gundlach
2005-04-04 20:30       ` Thomas A.Schmitz
2005-04-05  1:27         ` Paul Tremblay
2005-04-05 11:28           ` Patrick Gundlach
2005-04-05 15:52             ` Paul Tremblay
2005-04-05 16:17               ` Patrick Gundlach
2005-04-05 22:52                 ` Paul Tremblay
2005-04-06  8:38                   ` Patrick Gundlach [this message]
2005-04-06 12:21                     ` Hans Hagen
2005-04-06 20:03                     ` Patrick Gundlach
2005-04-04 17:12     ` Paul Tremblay
2005-04-04 19:40       ` 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=m2ll7wnvuu.fsf@levana.de \
    --to=patrick@gundla.ch \
    --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).