From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/97748 Path: news.gmane.org!.POSTED!not-for-mail From: Wolfgang Schuster Newsgroups: gmane.comp.tex.context Subject: Re: Aligning subsection head with following paragraph in tagged pdf output Date: Sun, 02 Apr 2017 22:15:53 +0200 Message-ID: <58E15BF9.2080500@gmail.com> References: <87zig1jbcr.fsf@equaltext.com> <852a8eb7-4579-bf11-e466-fbd646658d78@rik.users.panix.com> <316199831.20170331221028@equaltext.com> <0aa1d6d8-4f7c-8256-c4a6-3bd1a49ea8e2@rik.users.panix.com> <32adb08f-269d-d791-ad82-9a0a5167b68b@gmx.es> <87fuhrk7wh.fsf@equaltext.com> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3213361789130944699==" X-Trace: blaine.gmane.org 1491164193 20882 195.159.176.226 (2 Apr 2017 20:16:33 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 2 Apr 2017 20:16:33 +0000 (UTC) User-Agent: Postbox 5.0.12 (Macintosh/20170323) To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Sun Apr 02 22:16:28 2017 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1culvD-0004ER-DS for gctc-ntg-context-518@m.gmane.org; Sun, 02 Apr 2017 22:16:23 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 5647B84909; Sun, 2 Apr 2017 22:16:14 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7rX4GkA0658i; Sun, 2 Apr 2017 22:16:13 +0200 (CEST) Original-Received: from zapf.ntg.nl (localhost [IPv6:::1]) by zapf.ntg.nl (Postfix) with ESMTP id A0A1084970; Sun, 2 Apr 2017 22:16:13 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 5AC45847CC for ; Sun, 2 Apr 2017 22:16:12 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tMstJfXOSqih for ; Sun, 2 Apr 2017 22:16:10 +0200 (CEST) Original-Received: from mail-wr0-f178.google.com (mail-wr0-f178.google.com [209.85.128.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id 3D53384716 for ; Sun, 2 Apr 2017 22:16:00 +0200 (CEST) Original-Received: by mail-wr0-f178.google.com with SMTP id k6so137610697wre.2 for ; Sun, 02 Apr 2017 13:16:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to; bh=P8q9DH44MMSwFSkXmbBrU+msPuAX7mxKKbQboEOsIxM=; b=nOwOLlVIIgC3tQgClTVYzfWS/W81UPdPTUBsMJCBT24cjVf88tg5aQcaBjkLnLJ/Sq Yhx3J3Sv4snWxQvgnOJ5jZXj1N9KkCDbcs9XSFrEyCO8E3kGgwrF6wdiV7UAT04DyKuQ gdhR/i57dUXW6tPC7OzCuh5nLwrsqEopRbXtI/UuNhJINTxLRYRuETcVtfMqeR3t/r4i 9jtY6FejC4OGz45hO2mw+uJa9uPS2eckZFwbOumpOXhYjcVibsmtrXMYsIJ/hOz75aYP UNRLpAkQ2SeIEfKvkiNzKdDnyTucnApxebsWkC32GhBuYLpUPxruD03xNrQGqc6psnQ3 U1Jw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to; bh=P8q9DH44MMSwFSkXmbBrU+msPuAX7mxKKbQboEOsIxM=; b=oZ8bE6Q9yg1zJpyuuXMJ2+Q9wGhvlYdsH0CwFnERFSraF8CZHZ7WOfvwPrce9oS5t3 YZnSD/tGCxGfTpN7kBjix8ZRgzQ0RTbblCquZX6lJQ3L9YtmEf9SDjPsX87XbQKBz2hO t3B1a4nfMCgOt16/cfEGuXFBj2kJLzi50jzN4rKqeD7iHOeRssYvVaRXHo7F0N6erbtU nMMbGJJnSmGcFe9n6u6yXwh57exmdnzZWzFctECSsJSfvwdbofdl9eJmmDQD/1c1FkaL cD6TnxvX6Uy2XjAblHRiF+VsbC1JE0wAyKU0RugS042XIFa5VpGytB+YUauDWh2Ld8x8 xB4g== X-Gm-Message-State: AFeK/H1xTrViQzqKwQfSkqmHzuvIzvyR7ohCKU7EqANvVbdhIewkKmw+V6hQJ9bpwLbJ0g== X-Received: by 10.223.136.92 with SMTP id e28mr11237180wre.73.1491164159668; Sun, 02 Apr 2017 13:15:59 -0700 (PDT) Original-Received: from keima.localdomain (x2f26703.dyn.telefonica.de. [2.242.103.3]) by smtp.gmail.com with ESMTPSA id g63sm11524808wme.11.2017.04.02.13.15.58 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 02 Apr 2017 13:15:58 -0700 (PDT) In-Reply-To: <87fuhrk7wh.fsf@equaltext.com> X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.16 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: "ntg-context" Xref: news.gmane.org gmane.comp.tex.context:97748 Archived-At: This is a multi-part message in MIME format. --===============3213361789130944699== Content-Type: multipart/alternative; boundary="------------060202040700010806030505" This is a multi-part message in MIME format. --------------060202040700010806030505 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit > Todd DeVries > 2. April 2017 um 01:47via Postbox > > 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 --------------060202040700010806030505 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
2. April 2017 um 01:47 via Postbox
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
--------------060202040700010806030505-- --===============3213361789130944699== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv IGh0dHA6Ly9jb250ZXh0LmFhbmhldC5uZXQKYXJjaGl2ZSAgOiBodHRwczovL2JpdGJ1Y2tldC5v cmcvcGhnL2NvbnRleHQtbWlycm9yL2NvbW1pdHMvCndpa2kgICAgIDogaHR0cDovL2NvbnRleHRn YXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f --===============3213361789130944699==--