From: "Idris Samawi Hamid ادريس سماوي حامد" <Idris.Hamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Referencing footnotes by SECTION
Date: Mon, 02 Jul 2018 06:34:30 -0600 [thread overview]
Message-ID: <op.zliyj1rmejo439@desktop-mt1m160> (raw)
In-Reply-To: <5B39CD24.6030106@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4139 bytes --]
Hi Wolfgang,
On Mon, 02 Jul 2018 00:58:44 -0600, Wolfgang Schuster
<schuster.wolfgang@gmail.com> wrote:
> Hi Idris,
>
> you can enable the display of chapter numbers with the prefix-key:
>
> \setupnotation
> [footnote]
> [prefix=yes,
> %prefixsegments=chapter,
> way=bychapter]
Many thanks for this. There is an unwanted side-effect: Let
marker = main-text footnote marker
header = numeral for footnote header
reference = reference numeral
The prefix appears in three places, e.g.,
marker - II.1
header - II.1
reference - II.1
but we only want the prefix in the reference, not anywhere else, e.g.,
marker - 1
header - 1
reference - II.1
The prefix in the main-text marker and in the footnote header are
superfluous, e.g., the reader already knows which chapter one is reading.
But to reference a footnote from a later chapter, a prefix is needed to
let the reader know which chapter.
So the question is: Can the prefix be made to apply only to the reference
and not the marker or notation header?
==============
Observation:
For endnotes at the end of a book having the prefix in the header is also
useful, i.e.,
marker - 1
header - II.1
reference - II.1
So a general mechanism to set the prefix for each of the above three would
be useful.
If not currently supported, would like to make this a feature request.
==============
Thank you again, Wolfgang.
Best wishes
Idris
>> Idris Samawi Hamid ادريس سماوي حامد <mailto:Idris.Hamid@colostate.edu>
>> 30. Juni 2018 um 23:04
>> Dear gang,
>>
>> When referencing footnotes that reset each chapter, is there a way to
>> include the chapter information? See attached and below:
>>
>> =======
>> \setuphead[chapter] [alternative=normal,conversion=R]
>> \setuphead[subsection][alternative=text]
>> \setuphead[subsection][distance=0em,
>> textdistance=0.7em,
>> sectionstopper=.,
>> criterium=local]
>>
>> \setupnotation[footnote][way=bychapter]
>>
>> \setupreferencestructureprefix [section] [default]
>> [prefixstopper=\zerowidthspace]
>>
>> \setupwhitespace[big]
>> \starttext
>>
>> \startchapter[title={First},reference={}]
>> \startsubsection[title={},reference={reference1}]
>> \input ward
>> \startfootnote[footnote1]
>> \input ward
>> \stopfootnote{}
>>
>> See \in{Footnote}[footnote2].
>> \stopsubsection
>> \startsubsection[title={},reference={reference2}]
>> \input ward
>> \stopsubsection
>> \stopchapter
>>
>> \startchapter[title={Second}]
>> \startsubsection[title={},reference={reference3}]
>> \input ward
>> \stopsubsection
>> \startsubsection[title={},reference={reference5}]
>> \input ward
>> \startfootnote[footnote2]
>> \input ward
>> \stopfootnote{}
>>
>> See \in{Footnote}[footnote1].
>> \stopsubsection
>> \stopchapter
>> \stoptext
>> =======
>>
>> If line 8 is commented -
>> \setupnotation[footnote][way=bychapter]
>> - we get what we expect. But if line 8 is activated, we get an
>> ambiguity: Both references give back
>>
>> "Footnote 1"
>>
>> Whereas what we would like is something like this:
>>
>> Footnote I.1
>>
>> i.e., Chapter I, Footnote 1 - for the first footnote; and
>>
>> Footnote II.1
>>
>> i.e., Chapter II, Footnote 1 - for the second footnote.
>>
>> Is there a straightforward way to do this?
>>
>> [[Of course, for the roman chapter numbering we also run into the
>> reference-numberconversionset issue of the other thread, where
>>
>> \definestructureconversionset[OLIE][n,R,n,n,n,n][n]
>> \setupreferencestructureprefix [section] [default]
>> [prefixstopper=\zerowidthspace,
>> numberconversionset=OLIE]
>>
>> doesn't seem to work.]]
>>
>> Thank you in advance for any guidance or pointers you can provide!
>>
>> Best wishes
>> Idris
>
--
Idris Samawi Hamid, Professor
Department of Philosophy
Colorado State University
Fort Collins, CO 80512
[-- Attachment #2: reference-footnotes.pdf --]
[-- Type: application/pdf, Size: 17284 bytes --]
[-- Attachment #3: Type: text/plain, Size: 492 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-07-02 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 21:04 Idris Samawi Hamid ادريس سماوي حامد
2018-06-30 21:04 ` Idris Samawi Hamid ادريس سماوي حامد
2018-07-02 6:58 ` Wolfgang Schuster
2018-07-02 12:34 ` Idris Samawi Hamid ادريس سماوي حامد [this message]
2018-07-02 13:21 ` Wolfgang Schuster
2018-07-02 13:41 ` Idris Samawi Hamid ادريس سماوي حامد
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=op.zliyj1rmejo439@desktop-mt1m160 \
--to=idris.hamid@colostate.edu \
--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).