ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mohammad Hossein Bateni <bateni@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Footnote rules for bidi document
Date: Fri, 8 Jan 2016 21:15:13 -0500	[thread overview]
Message-ID: <CAMHZ1dZ602KQthtTeXhQnayx4bW3tf2mk4yC+yT69NvjhH3xfg@mail.gmail.com> (raw)
In-Reply-To: <CAMHZ1dbboLgANXUc3_G=dbM_h6BigJu1TX7vbpW4WOr7DFUAnQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1593 bytes --]

I updated the documentation on context garden.  Hans, I hadn't noticed that
you updated the macros on the same day as your last message!

I had another question regarding the definition of notes/footnotes.  It is
not that important but I am curious: is it possible to define two notes
that are essentially the same except for some of their stylistic
definitions?  Let me give an example.

some text \Afootnote{A}
more text \Bfootnote{B}
some more text \Afootnote{C}

And I want the result at the bottom of the page to read:

1 A
2 B
3 C

However, I'd like to have the power to control how the numbers are typeset
in the text and at the bottom, as well as determine the fonts, etc. of
\Afootnote and \Bfootnote separately.

On Mon, Jan 4, 2016 at 11:21 AM, Mohammad Hossein Bateni <bateni@gmail.com>
wrote:

> That said, I'm not asking for this to be the default. I only want to
>>> know how it can be achieved. The code will be put in my style file or
>>> module.
>>>
>>
>> i'll add rule=paragraph (i.e. listen to the first following paragraph if
>> possible) ... you need to document it as for sure i forget about it
>>
>
> Awesome!  Thanks, Hans!  Once this becomes available and I test it, I'll
> update the documentation for Footnotes on Context Garden.
>
>
>> Is it possible to determine the direction of the first line of footnote
>>> block while typesetting the footnote rule? I imagine it should not be
>>> difficult in Lua. Note that this may be the leftover from a long
>>> footnote that started on some previous page.
>>>
>>
> —MHB
>

[-- Attachment #1.2: Type: text/html, Size: 2750 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
___________________________________________________________________________________

  reply	other threads:[~2016-01-09  2:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-03 18:22 Mohammad Hossein Bateni
2016-01-03 19:58 ` Mohammad Hossein Bateni
2016-01-03 22:25   ` Hans Hagen
2016-01-04  0:00     ` Mohammad Hossein Bateni
2016-01-04 14:36       ` Hans Hagen
2016-01-04 16:21         ` Mohammad Hossein Bateni
2016-01-09  2:15           ` Mohammad Hossein Bateni [this message]
2016-01-09 13:07             ` Hans Hagen
2016-01-09 15:21               ` Mohammad Hossein Bateni

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=CAMHZ1dZ602KQthtTeXhQnayx4bW3tf2mk4yC+yT69NvjhH3xfg@mail.gmail.com \
    --to=bateni@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).