From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Aligning subsection head with following paragraph in tagged pdf output
Date: Sun, 02 Apr 2017 22:15:53 +0200 [thread overview]
Message-ID: <58E15BF9.2080500@gmail.com> (raw)
In-Reply-To: <87fuhrk7wh.fsf@equaltext.com>
[-- Attachment #1.1: Type: text/plain, Size: 1940 bytes --]
> Todd DeVries <mailto:todd@equaltext.com>
> 2. April 2017 um 01:47via Postbox
> <https://www.postbox-inc.com/?utm_source=email&utm_medium=sumlink&utm_campaign=reach>
> Hello everyone,
>
> Thanks to all who helped me better understand the issues surrounding my
> question. The document style I am following requires that the
> first three headings are included in the table of contents. Headings
> one and two are easy, as they stand on lines by themself. Heading three
> must be aligned with the left margin in bold and followed by a period.
> The rest of the paragraph or paragraphs folllow.
>
> This style makes sense visually, bold text at the margin represents a
> change in topic. less so when reading or editing with audio output (My
> computer does not have a monitor attached.) Using good sectioning
> allows one to fold the document for navigation and organization.
> Consider how Org-mode in Emacs works as an analogue. I started thinking
> that life would be easier if heading level 3 sections could be both
> structural, for navigation, and visual, inline with their first
> paragraph.
>
> This idea holds true both in source text and in the pdf output.
> Properly tagged pdf documents allow one to jump by structural elements
> (heading to heading, paragraph to paragraph. In a perfect world one
> could have it both ways: a structural element like a section, but placed
> inline as though it were just another layout token. The audio using
> tagged structure indicates a topic change, while those using their eyes
> just see the bold text.
>
> Hopefully this short explanation adequately describes my reason for
> addressing the list.
The inline heading in your example doesn’t work because \startparagraph
forces the end of a paragraph for the preceding text.
As you want only tags for the content of your paragraph you can enclose
your text in \bpar … \epar instead of \startparagraph … \stopparagraph.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 3099 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 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
___________________________________________________________________________________
next prev parent reply other threads:[~2017-04-02 20:15 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
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 [this message]
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=58E15BF9.2080500@gmail.com \
--to=schuster.wolfgang@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).