ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Changed behavior from \convertnumber{arabicdecimals}{..} as a textcommand for note
Date: Sat, 15 Jan 2022 14:39:16 +0100	[thread overview]
Message-ID: <bb2a62f2-cc4f-0b3e-b0b6-5a237d6bf1eb@xs4all.nl> (raw)
In-Reply-To: <CAEfWR-kJdBs_dCVaWrKEV604sD2tLmum9F9gihgLqKQN53GbZQ@mail.gmail.com>

On 1/15/2022 3:03 AM, musa furber via ntg-context wrote:
> This week I updated ConTeXt minimals. Before then, I used the following 
> code so that footnotes to Arabic passages would have parenthesis around 
> them and use the digits used in Arabic texts in the Middle East (e.g. 
> ٠١٢٣٤٥٦٧٨٩).
> 
> \setupnote [arfootnote] [
>    headstyle={\switchtobodyfont[kitab]},
>    textcommand=\footnotenotenumbercommand,
>    alternative=text,
>    ]
> \define[1]\footnotenotenumbercommand{{\high{(\convertnumber{arabicdecimals}{#1})}}}
> 
> Since the update, for the 123rd footnote, I now get `(123arabic)` 
> instead of `(١٢٣)`.
> 
> Elsewhere, I do get the expected output (i.e. `١٢٣٢`) when calling
> \convertnumber{arabicdecimals}{1232}
> 
> I'm still relatively new to ConTeXt, so I'm unsure if what used really 
> is correct, or if it was wrong and I now need to find the right way to 
> do it.
> 
> Any help would be greatly appreciated.
Next time give a complete MWE with useable fonts

   \setupnotation
     [arfootnote]
      [numberconversion=arabicdecimals]

as in:

\setupbodyfont[dejavu]

\definenote
   [arfootnote]

\setupnotation
   [arfootnote]
   [numberconversion=arabicdecimals]

\setupnote
   [arfootnote]
   [headstyle={\switchtobodyfont[kitab]},
    textcommand=\footnotenotenumbercommand,
    alternative=text]

\protected\def\footnotenotenumbercommand#1{\high{(#1)}}

\starttext
     x\arfootnote{x}
\stoptext

The #1 passed can be anything that renderes the note so the converters 
sees rubish. You can see details with you add

\detokenize{#1}

in your macro.

Hans
-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2022-01-15 13:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-15  2:03 musa furber via ntg-context
2022-01-15 13:39 ` Hans Hagen via ntg-context [this message]
2022-01-17  5:33 musa furber via ntg-context

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=bb2a62f2-cc4f-0b3e-b0b6-5a237d6bf1eb@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.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).