[NTG-context] regexp for matching entire footnotes
Hi,
I have to find (highlight) footnotes with the entire footnote being
marked/highlighted.
Constructing a regexp for this is far beyond what I can write, that's
why I frankly ask for help here:
The problems are the (potentially) nested pairs of curled brackets
(like for \index, \emphasize etc etc) ...
\footnote{Vgl. zur Historie \it{Name}, „Staatssekretär\index
{Staatssekretär}}
... as the found string shouldn't stop at the first "}" that was found.
Somebody knows a syntax that ignores curled bracket pairs *included*
in footnotes and really matches the entire note?
Steffen
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Bug with type << .. >>?
On Sat, 29 Jul 2006, Hans Hagen wrote:
> Aditya Mahajan wrote:
>> On Fri, 28 Jul 2006, Hans Hagen wrote:
>>
>>
>>> Aditya Mahajan wrote:
>>>
Isn't \type<<..>> be supposed to be equivalent to \type{..} ?
\title{some \type{thing} }
works perfectly but
\title{some \type<>}
>>> << >> will not work in commands that get an argument because it is
>>> related to catcode changes
>>>
>>
>> Ah. Makes sense.
>>
>>
>>> we could use \scantokens if there was not this space-creeps-in-after
>>> \cs problem)
>>>
>>
>> Well, found a workaround. Not sure if this one is a bug or a feature
>> (is a feature to me)
>>
>> \title{some \type{\thing\{and\}}}
>>
>> However, things get real weird.
>>
>> \title{\type{$\Pr\{A\}$}}
>>
>> gives me
>>
>
> you can try:
>
> \title{\retype{$\Pr\{A\}$}}
>
> watch the space after \Pr
Thanks for the hint.
I also found out
\startbuffer
$\Pr\{A\}$
\stopbuffer
\title{\typebuffer}
which seems pretty robust.
Aditya
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] sorting commalist?
>>> I should extend that document, but I've lost the source :-( >> >> Considering this document very useful I had an idea of puting at least >> parts of it on garden. So shoud I extract the texts, make some formating >> and send it to you or put it on the wiki? > > The wiki would be great. That way, if I do not get around to doing > work on it, someone else can. > > TIA, Done. http://wiki.contextgarden.net/System_Macros The page is rather long. I leave to experienced users who are going to extend the article to rearrange it, if needed. Hopefully it still remains Taco's article, who will write part II soon ;) Few notes for Patrick et al. regarding wiki. 1. I've found strange writing \contextversion (with backslash) contextversion(without backslash) this may lead to errors, in my opinion, syntax should be the same (with backslash). I'm not sure, if there is any chance to change it on the fly everywhere nor if it is possible at all. 2. elements should point only to context user macros (not to TeX primitives nor ConText internals), right? 3. I didn't notice before that even in-line element is highlighted in backround as the block element is. On my display it is almost invisible as a part of line. If we want to highlight I suggest to use a bit darker or different color. Now it is somewhere in the middle: highlighted as well as not highlighted (dust on the screen). Jano ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Another q, about setups
All -
I have a small block which creates a "DRAFT" watermark as the page
background:
% Create "Draft" watermark for later use
\doifmode{draft}{
% Put a "DRAFT" watermark in Sun Blue
\defineoverlay[Draft][{\sunbluet
\scale[factor=max]{\rotate[rotation=60]{~DRAFT~}}}]
\setupbackgrounds[page][background=Draft]
} % End watermark
Is there a way I can put it into a "setup" or "command" so I can turn it
on/off by page/section?
--
Mark Almeida [EMAIL PROTECTED]
Solutions Architect (707)398-9524/x81132
Sun Client Solutions (707)429-0341 Home Office
(707)480-5038 Cell
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] TOC and "Contents" entry
All - Although the manual seems to imply that \completecontent will include the "Contents" page entry itself in the TOC, it does not. I would like the "Contents" page itself to be included, in both the table of contents, and the navigation entries in the generated pdf output. I normally set it up like this: \completecontent[alternative=c,pagestyle=slanted,interaction=pagenumber] Pretty simple, but it doesn't do what I'd really like. The other style \placecontent[alternative=c,pagestyle=slanted,interaction=pagenumber] doesn't do what I want either. Is there an additional option that I'm missing. I'd like something like Contents Contents..iii Section 1.1 etc Can I get this with either \completecontent or \placecontent, or will I have to use some other method? TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005 texexec : TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005 texutil : TeXUtil 9.0.1 - ConTeXt / PRAGMA ADE 1992-2006 tex : pdfeTeXk, 3.141592-1.30.5-2.2 (Web2C 7.5.5) context : ver: 2006.07.24 10:49 cont-en : ver: 2006.07.24 10:49 fmt: 2006.7.26 mes: english total run time : 1 seconds -- Mark Almeida [EMAIL PROTECTED] Solutions Architect (707)398-9524/x81132 Sun Client Solutions (707)429-0341 Home Office (707)480-5038 Cell ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Bug with type << .. >>?
Hans Hagen wrote:
>
> Question for taco: can we make such spaces optionally disappear in future
> tex's?
>
In most cases, yes.
(but not always, because something like the internal form of
"\aacute a" can not reliably be represented by adding extra
tokens like in "\aacute{}a", for example)
Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Bug with type << .. >>?
Aditya Mahajan wrote:
> On Fri, 28 Jul 2006, Hans Hagen wrote:
>
>
>> Aditya Mahajan wrote:
>>
>>> Isn't \type<<..>> be supposed to be equivalent to \type{..} ?
>>>
>>> \title{some \type{thing} }
>>>
>>> works perfectly but
>>>
>>> \title{some \type<>}
>>>
>>>
>> << >> will not work in commands that get an argument because it is
>> related to catcode changes
>>
>
> Ah. Makes sense.
>
>
>> we could use \scantokens if there was not this space-creeps-in-after
>> \cs problem)
>>
>
> Well, found a workaround. Not sure if this one is a bug or a feature
> (is a feature to me)
>
> \title{some \type{\thing\{and\}}}
>
> However, things get real weird.
>
> \title{\type{$\Pr\{A\}$}}
>
> gives me
>
you can try:
\title{\retype{$\Pr\{A\}$}}
watch the space after \Pr
Question for taco: can we make such spaces optionally disappear in future tex's?
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
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] whitespace
Hans van der Meer wrote: > Why does \startframedtext does not honor the outside setting > by \setupwhitespace? Because its contents are most often used as a kind of inline figure, where normal paragraph spacing does not apply. Greetings, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] \Word and friends
Hans van der Meer wrote:
> After \def\Example{example}
> \Word{\Example} gives example
> So I need
> \expanded{\Word{\Example}} to get Example
> but
> \WORD{\Example}} does give EXAMPLE
>
> I did not expect that.
> Is this the intended behaviour?
Well, expanding the argument of \Word automatically would not
always be safe, so I guess it is unavoidable in current \TeX
(the problem is that the \uppercase primitive is not expandable).
Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] setuphead
Steffen Wolfrum wrote:
> You mean like this?
>
> \setuphead[chapter][command=\midaligned,numbercommand=\it,inbetween=
> \crlf,textcommand=\bf]
That is what I meant but it dodn't work out too well. New approach:
\def\Sectioncommand#1#2%
{\vbox{\centerline{\it Chapter #1}%
\centerline{\bfb #2}}}
\setuphead[chapter]
[command=\Sectioncommand,
style=]
Cheers, Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
