From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: Aligning subsection head with following paragraph in tagged pdf output
Date: Sat, 1 Apr 2017 11:32:18 -0400 [thread overview]
Message-ID: <0aa1d6d8-4f7c-8256-c4a6-3bd1a49ea8e2@rik.users.panix.com> (raw)
In-Reply-To: <316199831.20170331221028@equaltext.com>
On 2017-04-01 00:10, Todd DeVries wrote:
> Thanks for your assistance. Was unaware of using the setupheads
> command incorrectly. Good information to have. I am still not
> able to produce an automatic period (.) at the end of the section
> title using the after keyword. is this correct?
Seems to be. While before= is honored, after= is not. This looks like an
inconsistency that can be addressed.
>
> On Friday, March 31, 2017, 7:01:28 PM, Rik writes:
>
>> alternative=text is working, but \startparagraph is starting a
>> new paragraph after the heading. \start\stopparagraph is not
>> happy with the text alternative.
> I am wondering if this is just not going to work with the tagging
> subsystem. The subsection aligns if I remove the start/stop
> paragraph following the heading. But if I add a second paragraph
> in that subsection it breaks again.
Example, please. I have no problem adding a start/stopparagraph after
your knuth. (Note that the knuth has to be terminated in a \par or a
blank line. That is because of the construction of that input file.)
> I use tagged pdfs for output
> because they are more accessible with my screen reader. Without
> tagging, all one gets is long blocks of undifferentiated text.
> With the correct tags, paragraphs, headings, lists, and tables
> get created that make more sense with auditory output. To my
> knowledge, ConTeXt is the only alternative for producing
> accessible pdfs beyond working with Acrobat pro or MS. Word.
> After writing a 70-page academic project in Word, I'm seeking
> alternatives!
>
> Perhaps one can just use in-paragraph bolding and mark that text
> for the table of contents as an alternative. This is required
> for heading level 3 content in APA style.
For now that might be best as long as you do not need to reference them
in a table of contents (not required by APA, as I read the standard,
although perhaps an added requirement from your publisher).
> Thanks for your assistance. I'm a newbie and appreciate the
> help.
>
> Todd
>
--
Rik
___________________________________________________________________________________
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:[~2017-04-01 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 23:05 Todd DeVries
2017-04-01 1:01 ` Rik Kabel
2017-04-01 4:10 ` Todd DeVries
2017-04-01 15:32 ` Rik Kabel [this message]
2017-04-01 18:20 ` Pablo Rodriguez
2017-04-01 19:58 ` Alan Braslau
2017-04-01 23:47 ` Todd DeVries
2017-04-02 20:15 ` Wolfgang Schuster
2017-04-02 23:09 ` Todd DeVries
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=0aa1d6d8-4f7c-8256-c4a6-3bd1a49ea8e2@rik.users.panix.com \
--to=context@rik.users.panix.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).