ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Roger Mason <rmason@mun.ca>
To: Jonas Baggett <jonas17b@gmail.com>
Cc: ntg-context@ntg.nl
Subject: Re: WYSIWYM editor on top of ConTeXt / Lout
Date: Thu, 07 Dec 2017 09:12:35 -0330	[thread overview]
Message-ID: <y65shcm3e10.fsf@mun.ca> (raw)
In-Reply-To: <f0f03599-1795-318f-1825-cae61f412432@gmail.com> (Jonas Baggett's message of "Thu, 7 Dec 2017 07:42:21 +0100")

Hello Jonas,

Jonas Baggett <jonas17b@gmail.com> writes:

> Thank you for the suggestion. I was first thinking about incrementally
> creating a custom format that evolves as features are implemented. And
> for translating the custom format into a backend format, I was
> thinking of creating files with translations rules for each backend so
> that anyone can add support for a new backend or update an existing
> backend to add more feature or to make it compatible with a newer
> version of the backend, without needing to modify the editor code. A
> translation rule is e.g. start_section[title=<the_title>,
> back_ground_color=<the_color>] => @startsection(title ->
> {<the_title>}, bg_color -> {<the_color>}) which will convert a start
> section command of the document format into the same command for a
> backend format.

Skribilo uses an abstract syntax internally and the different output
engines process that into the target language.  In essence each engine
is the collection of rules appropriate to that target.

> At first glance that way seems to be the easiest way for me, but
> Skribilo looks interesting as a fallback option, although I find its
> syntax to be weird, if I find out that the idea with translation rules
> isn't working as expected.

There are two input syntaxes, a simple one a bit like Emacs' outline
mode and the more Scheme-like syntax.  The former has limitations
documented on the Skribilo web-site, the latter is far more complete.  I
an guessing it is the Scheme-like syntax that you find weird.  I have
played around a a little this week on using Wisp
(http://www.draketo.de/proj/wisp/) and Readable
(http://readable.sourceforge.net/) to write Skribilo in a less
parenthesis rich style.  Although not able to complete the work owing to
time constraints, it looks acheivavble.

Cheers,
Roger

Off topic
========

My goal would be to have an output ConTeXt (or Lout) document, with
fallback to LaTeX or XML if a publisher insists.  If this could be
combined with Emacs org-mode to document, store and run (or compile-run)
source code, then a very complete and versatile system for reproducible
reasearch could be constructed.


___________________________________________________________________________________
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:[~2017-12-07 12:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-02  7:42 Jonas Baggett
2017-12-02  8:40 ` Brian Ballsun-Stanton
2017-12-02 10:57   ` Gour
2017-12-03  8:25     ` Jonas Baggett
2017-12-03  7:57   ` Jonas Baggett
2017-12-02  9:47 ` Siep Kroonenberg
2017-12-02 12:55 ` Henning Hraban Ramm
2017-12-03  7:23   ` Jonas Baggett
2017-12-03 13:21 ` Roger Mason
2017-12-07  6:42   ` Jonas Baggett
2017-12-07 11:19     ` Floris van Manen
2017-12-07 12:26       ` Aditya Mahajan
2017-12-07 12:42     ` Roger Mason [this message]
2017-12-07 13:55       ` William Adams
2017-12-07 13:56         ` William Adams
2017-12-03 17:00 ` Aditya Mahajan
2017-12-05 17:42   ` Jonas Baggett
2017-12-05 23:01 ` Jan Tosovsky
2017-12-06 19:33   ` Marcin Borkowski
2017-12-06 21:03     ` Jan Tosovsky
2017-12-07  6:32       ` Marcin Borkowski

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=y65shcm3e10.fsf@mun.ca \
    --to=rmason@mun.ca \
    --cc=jonas17b@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).