From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: underbar/margin text
Date: Wed, 21 Nov 2012 10:02:50 +0100 [thread overview]
Message-ID: <CAG5iGsD7OeUkXDg=a+t05Yx3cumXa4RLFF1yN+p-U0dHRKCC-w@mail.gmail.com> (raw)
In-Reply-To: <B025E83B-3817-4CAE-AEF6-19B2CB871719@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1702 bytes --]
On Wed, Nov 21, 2012 at 9:52 AM, Wolfgang Schuster <
wolfgang.schuster@gmail.com> wrote:
>
> Am 21.11.2012 um 09:42 schrieb luigi scarso <luigi.scarso@gmail.com>:
>
>
>
>
> On Wed, Nov 21, 2012 at 9:36 AM, Wolfgang Schuster <
> wolfgang.schuster@gmail.com> wrote:
>
>>
>> Am 03.09.2012 um 13:08 schrieb Daniel Schopper <daniel.schopper@aon.at>:
>>
>> > Hi,
>> > I have to typeset some underlined text with margin notes by its side.
>> Is there a way to prevent the notes themself to get underlined? I tried
>> putting the note-command in a group, simplifying its content etc. (In my
>> real file I use \defineinmargin, btw.)
>> >
>> > \starttext
>> > \underbar{Test Test Test\footnote{footnote}~Test Test Test\par
>> > Test\inleft{marginal} Test Test Test Test Test \par}
>> > \stoptext
>> >
>> > (As one can see, there’s also an issue with the footnote-sign breaking
>> the continued line, which is not urgent for me, at least by now.)
>>
>> Footnotes disable the rule with the \resetallattributes command but it’s
>> up to Hans to add it to the margin notes.
>>
>> but you can add by hand
> \starttext
> \underbar{%
>
> Test Test Test\footnote{footnote}~Test Test Test\par
> Test\inleft{\resetallattributes \color[red]{\overbar{marginal}}}
> Test Test Test Test Test \par
> }
>
> \stoptext
>
>
> and disable features which rely on attributes :)
>
> \starttext
> Test\inleft[color=blue]{\resetallattributes marginal} Test
> \stoptext
>
>
exactly, that's the meaning of my prev. line
\inleft{\resetallattributes \color[red]{\overbar{marginal}}}
"reset all attributes and turn on some of them."
Can help in some situations.
[-- Attachment #1.2: Type: text/html, Size: 2831 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-11-21 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 11:08 Daniel Schopper
2012-11-20 13:07 ` Daniel Schopper
2012-11-21 7:50 ` luigi scarso
2012-11-21 8:36 ` Wolfgang Schuster
2012-11-21 8:42 ` luigi scarso
2012-11-21 8:52 ` Wolfgang Schuster
2012-11-21 9:02 ` luigi scarso [this message]
2012-11-21 9:12 ` Daniel Schopper
2012-11-21 9:18 ` Wolfgang Schuster
2012-11-21 12:08 ` 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='CAG5iGsD7OeUkXDg=a+t05Yx3cumXa4RLFF1yN+p-U0dHRKCC-w@mail.gmail.com' \
--to=luigi.scarso@gmail.com \
--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).