ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ramkumar KB <ramkumarkb@gmail.com>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Missing symb-imp-was.mkiv ?
Date: Sun, 11 Jul 2021 15:55:22 +0800	[thread overview]
Message-ID: <CAMD5SRPrYpCc9RHKn245wJegED92okV3qUJPPgK-_bbuZiz-sA@mail.gmail.com> (raw)
In-Reply-To: <271ebafc-3fad-948f-3d0b-97c68eb3c5f5@xs4all.nl>


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

Hans,

Thank you very much! Let me follow your instructions and will give you
feedback.

Thanks again.

best regards,
Ramkumar

On Sun, Jul 11, 2021 at 3:46 AM Hans Hagen <j.hagen@xs4all.nl> wrote:

> On 7/10/2021 8:24 AM, Ramkumar KB wrote:
> > Hello,
> >
> > I am trying to follow the steps described here for using \usesymbols
> > <https://wiki.contextgarden.net/Command/usesymbols>[was] and details
> > described here -
> > https://wiki.contextgarden.net/Symbols/was
> > <https://wiki.contextgarden.net/Symbols/was>
> >
> > Looks like the file `symb-imp-was.mkiv` is missing from the path -
> >
> > \tex\texmf-context\tex\context\base\mkiv
> >
> > Thank you for any tips or pointers.
> The wiki page actually mentiones jmn symbols but these are by (the late)
> Januz so that should be corrected.
>
> Anyway, the wasy font symbol setup was never converted to mkiv so
> attached is a draft.
>
> Up to you to complete it. From CTAN, download the type one package and
> put the afm and pfb files under (e.g.) texmf-fonts/fonts/data/wasy (no
> need for subdirs) and run "mtxrun --generate" to update the file database.
>
> You can look in the afm files to see what names are provided.
>
> It looks like the files were updated in 2020 (taco is mentiones). Rhaban
> made the mkii file so you can consult him. I advice to stick to the
> regular symbols not the weirdly composed ones.
>
> You can patch the file and send me the result. You can 'run the file' in
> order to get the overview. You should see at least most symbols.
>
> So ... work to do ...
>
> 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
> -----------------------------------------------------------------
>

[-- Attachment #1.2: Type: text/html, Size: 2941 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 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
___________________________________________________________________________________

      reply	other threads:[~2021-07-11  7:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-10  6:24 Ramkumar KB
2021-07-10 19:46 ` Hans Hagen
2021-07-11  7:55   ` Ramkumar KB [this message]

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=CAMD5SRPrYpCc9RHKn245wJegED92okV3qUJPPgK-_bbuZiz-sA@mail.gmail.com \
    --to=ramkumarkb@gmail.com \
    --cc=j.hagen@xs4all.nl \
    --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).