[Tb] Textile for HTML export

From: Gary King <gwking__AT__cs.umass.edu> Date: Mon Oct 18 2004 - 13:33:26 EDT · >> On Oct 12, 2004, at 4:48 PM, Mark Smith wrote:

-- 
Gary Warren King, Lab Manager
EKSL East, University of Massachusetts * 413 577 0176
"I am not a number, I am a free man! "
   -- #6, The Prisoner
--Apple-Mail-10--445477296
Content-Transfer-Encoding: 7bit
Content-Type: text/enriched;
	charset=US-ASCII
I would like it if the part of Tinderbox that handles HTML generation
and import was "pluggable". I.e., that we could tell TB that export
means "run the file through this pipeline" and import means "run the
file through that pipeline" where the pipelines could be note specific
(for export) and file type specific (for import).
That would be way open and way, way cool.
On Oct 14, 2004, at 6:21 PM, David J Garbutt wrote:
<excerpt><excerpt>On Oct 12, 2004, at 4:48 PM, Mark Smith wrote:
<excerpt>Have you considered Markdown instead?
</excerpt>
I had actually considered Markdown first. I like the faux-markup
philosophy of making things look "correct" even in plain text. However,
I couldn't find any note of its ability to do good typography. I didn't
know about Smartypants, so maybe I'll have to give it another look. I'd
probably be happy with *just* smartypants, really. I didn't plan on
doing much inline markup.
Still, Textile appears to do more of this kind of thing (e.g. making
4x6 into 4__AT__#215;6). And I rather like the idea of using one
preflighting script instead of two.
Textile can do tables (not that I'm planning on it). It will also do
(C), (R), and (TM).
My *other* reason is that Red Cloth is in Ruby, which is my tinkering
project at the moment...
</excerpt>HI,
I am also playing with Ruby, and I also came across markdown and
textile.
My take is that these should be TB enhancements.
:-O (I don't meant Ruby...)
It seems to me they have major advantages over what we get now with
text and
HTML export- 
1) reversible (certainly true for markdown*). This means we could have
an
import from HTML page into a TB note with formatting that could be
regenerated again on export. This would bring a lot of leverage for
snippet
collectors.
2) much better shot at import text from other places, written on
phones etc.
3) possibility of improved layout from text export view
4) each is a simple and capable and consistent set of rules which are
easy
to learn. 
Of course I can see why Eastgate might not like this idea but perhaps
if we
say 'please do it' they will think about it carefully.
They already took the brave step of opening the TB files themselves to
XML
at a time when few applications did, and I think it is now very clear
that
that feature is a major selling point for TB.
The above initiatives are more about fixing a way to move between the
two
codings than to present one particular tool or language. So they could
be
implemented with proprietary routines
What do you think?
Dave
* the reversal program is not called markdown but something else
-- 
Dave Garbutt
Ingelsteinweg 4d
CH 4143 Dornach
+41 79 326 8970  (Home: 061 692 6349)
http://www.mybasel.ch/verkehr_regioplan_karte.cfm?ID=Strassen,14139&ParaZoom
&Zoom=3000
Peace is made with yesterday's enemies. What is the alternative?
Shimon Peres, Israeli politician
_______________________________________________
Tb mailing list
Tb__AT__lee-phillips.org
http://lee-phillips.org/mailman/listinfo/tb
</excerpt>-- 
Gary Warren King, Lab Manager
EKSL East, University of Massachusetts * 413 577 0176
"I am not a number, I am a free man! "
  --
<fontfamily><param>Verdana</param><color><param>3333,3333,3333</param><x-tad-bigger>#6,
</x-tad-bigger></color></fontfamily>The Prisoner 
--Apple-Mail-10--445477296--