[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ruby-talk
Subject:    =?UTF-8?Q?Re=3A_Office=2ETXT_=2D_The_Free_Writer=E2=80=99s_Command_Line_To?= =?UTF-8?Q?ol_Suite_=2D_
From:       Gerald Bauer <gerald.bauer () gmail ! com>
Date:       2017-07-25 10:54:52
Message-ID: CAAxEZd9+vLOYYZKgC6Hq3neFbdJdVrC7tDeN1E77GjXvYOv6xQ () mail ! gmail ! com
[Download RAW message or body]

Hello,

    Thanks for the detailed write-up on real-world usage.  Text with
Instructions (.texti) is trying to "fix" at least some of the road
blocks.

> Semantic markup beats the structural markup.


   In Texti you can use semantic markup with macros (called templates
like in Wikipedia markup) e.g. {{ fig | pic.gif }}  or {{ tip |
aynthing here including other {{ table | ... }}}} and so on.

    {{ fig }}  is just a reference to the _fig.texti or
_includes/fig.texti or "inline" (written in ruby) template. In all
templates you can use a "variant" of Liquid scripting too (which you
cannot in Wikipedia markup - it's just a text building block /
template).



> There is a useful concept named "admonitions".

  That's an easy one. In Texti there is a "generic" division block e.g.

:: Note:  This is an admonition.

That's the short form. The long form is:

:: Note :::::::::::::::
  Anything goes

  And so on
:::::::::::::::::::::::::::

  And there's even an Unicode (Ascii-style) Art version (actually like
in ruby - many styles, actually).



> I have experimented with M4 to get a macro system ontop of Markdown

  Again Text w/ Instructions (.texti) will include a macro system
out-of-the-box. It's part of the markup language (following mostly
Wikipedia markup templates)  e..g. {{ macro | para1 | para2 }}  plus
"simplified" Liquid for templating e.g. {{ param[0] }} becomes  §1 §
(uses  § because $ is "reserved" for math-mode).


   Anyways, if anyone wants to help in evolving (fixing) markdown and
merging it with Wikipedia markup while also making it easy to use
LaTeX as a first-class (output) citizen (besides HTML) join the Text
w/ Instructions (.texti) [1] and post your ideas, road blocks, etc.


    "Real" languages like Ruby are living languages and evolve. Let's
evolve the "frozen" Markdown ;-)

  Cheers.

[1] https://texti.github.io

Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>

[prev in list] [next in list] [prev in thread] [next in thread]