From: Pawel Urbanski via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Pawel Urbanski <urbanski.pawel@gmail.com>
Subject: Re: ConTeXt features in pandoc 3
Date: Sat, 21 Jan 2023 00:48:03 +0100 [thread overview]
Message-ID: <CADUDiDFj+CDCvf4y01tOaBbnqw3wGXwh3x_m2CZCzDsRZqOpxw@mail.gmail.com> (raw)
In-Reply-To: <87sfg4lwly.fsf@zeitkraut.de>
[-- Attachment #1.1: Type: text/plain, Size: 1388 bytes --]
>
>
> Hi Albert,
Fantastic news. Thanks to Pandoc and completions in editors I can create
great looking documents at the speed of light...
Since you've asked for ideas or suggestions here are a few:
** Create a Pandoc markdown directive that woulc allow for document
includes - in the style and spirit of Context components.
** Add the ability to place a pandoc.yaml file in the folder so it can be
picked by Pandoc to get options for this folder and contained documents,
** Use LUA to run something like pipes inside Pandoc itself - LUA could be
the format for the 'pandoc' file I've mentioned,
** Something Context and accessibility related:
Screen readers allow to navigate quickly by element type, for example:
heading / list / form elements. Headings are very useful to quickly move
around the document but htere is one corner case. Context splits the
heading number and heading itself into separate parts.
When doing this quick navigation the user hears for example: 1.2 or 3.4 and
need to reach for the arrow keys to scroll to the next logical line to read
the very heading.
I don't know if it is possible at the tagging level to combine the number
and the heading tible togehter wiht a space in between, os htey are not
stringed together in an unnatural way. Taggs are a bit like a parallel
universe.
Please drop a line if you would like to digg further...
All the best,
Pawel
[-- Attachment #1.2: Type: text/html, Size: 1729 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-01-20 23:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 21:00 Albert Krewinkel via ntg-context
2023-01-20 23:48 ` Pawel Urbanski via ntg-context [this message]
2023-01-22 15:11 ` Saša Janiška via ntg-context
2023-01-23 7:22 ` juh via ntg-context
2023-01-23 8:24 ` luigi scarso via ntg-context
2023-01-24 6:22 ` Saša Janiška via ntg-context
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=CADUDiDFj+CDCvf4y01tOaBbnqw3wGXwh3x_m2CZCzDsRZqOpxw@mail.gmail.com \
--to=ntg-context@ntg.nl \
--cc=urbanski.pawel@gmail.com \
/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).