ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Capitalize first word of first line within \startlines
Date: Wed, 4 Mar 2020 17:46:03 -0800	[thread overview]
Message-ID: <CAANrE7osh-68a4UEKm7NpGdQcDOWHma53TogOrr-FO2DTQyicw@mail.gmail.com> (raw)
In-Reply-To: <df1a45f0-3a44-b09f-0538-bb985a851648@gmail.com>

If it helps, here's why I thought it would work:

https://wiki.contextgarden.net/Command/definefirstline

The wiki page shows that the macro takes a style option. The style
option links to:

https://wiki.contextgarden.net/Style_Alternatives

This page has a list of predefined styles and describes how to set up
an alternative style:

https://wiki.contextgarden.net/Style_Alternatives#Defining_a_Style_Alternative

From the wiki page:

\definealternativestyle [head:neat]       [\WORD]   []

While \definealternativestyle[PoemFirstWord][{\bf\uppercasing}][] will
work for my needs, I am concerned that it is inconsistent wrt wiki
documentation, and also appears to expose an inconsistent API, as it
were. Is there any way to make the two conform to the same usage? That
is, it was not obvious (from the wiki) that I could not use "WORD" as
an alternative style even though it is literally listed and used as an
alternative style.

Thanks again!
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2020-03-05  1:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04 16:09 Thangalin
2020-03-04 17:04 ` Hans Hagen
     [not found] ` <2d3e75b2-f5eb-91f4-85a6-f71c43861958@xs4all.nl>
     [not found]   ` <df1a45f0-3a44-b09f-0538-bb985a851648@gmail.com>
2020-03-05  1:46     ` Thangalin [this message]
2020-03-05  8:46       ` 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=CAANrE7osh-68a4UEKm7NpGdQcDOWHma53TogOrr-FO2DTQyicw@mail.gmail.com \
    --to=thangalin@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).