<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Apr 18, 2020, 08:32 Karl Kleinpaste <<a href="mailto:karl@kleinpaste.org">karl@kleinpaste.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div><font face="FreeSerif">Just to be
clear... You folks are in fact suggesting excising the current
integrated editor, to replace it with another integrated editor,
just one that speaks a different editing scheme. You're walking
the center line, between fixing the current nightmare-to-upgrade
editor vs. removing it in favor of reduction to linkage to an
entirely external editor.<br></font></div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Yes. I think editing in the app is the best approach and best UX for people.</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><font face="FreeSerif">
<br>
That's fine. I mean, I suppose I can roll either way, I guess. I
just thought folks would be happier with reducing Xiphos'
involvement with editing from "we do everything in editing" to
mere external linkage at start ("here's the initial [usually
empty] doc") and end ("let me now inhale the result of your
editing").<br></font></div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">I think, for the casual user, this would feel strange. We power users and developers are accustomed to that workflow. But most people aren't. </div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><font face="FreeSerif">
<br>
For the record, I would have never suggested literally using
$EDITOR. Joe Random doesn't want to do styled editing in an
ordinary text editor, as is usually indicated by $EDITOR.<br>
</font><br>
On 4/18/20 5:53 AM, Greg Hellings wrote:<br>
</div>
<blockquote type="cite">
<div>* Links are pretty trivial</div>
</blockquote>
<font face="FreeSerif"><br>
Bear in mind that links in such docs are not just external
http-style links to external sites. The important aspect is
cross-referential links, that is, internal links to other Sword
modules. See <a href="http://karl.kleinpaste.org/xiphos/" target="_blank" rel="noreferrer">http://karl.kleinpaste.org/xiphos/</a>
and look at link-genbook*, especially -3. (Once upon a time, those
images were a brief tutorial on how to do a link in Xiphos.) These
create links like these:<br>
<br>
1. Direct linkage to any other Sword module:<br>
</font><tt><A
HREF="sword://Josephus/%2FThe+Antiquities+of+the+Jews%2FBook+18%2FChapter+3%2FSection+3">jos.18.3.3</A></tt></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">In MarkDown this becomes:</div><div dir="auto"><br></div><div dir="auto">[jos.18.3.3](sword://Josephus/%2FThe+Antiquities+of+the+Jews%2FBoom+18%2FChapter+3%2FSection+3)</div><div dir="auto"><br></div><div dir="auto">Very easy for us to programmatically walk people through.</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><font face="FreeSerif"><br>
2. Scripture xref through the verse list:<br>
</font><tt><A
HREF="passagestudy.jsp?action=showRef&amp;type=scripRef&amp;module=&amp;value=Genesis+2%3A24">Genesis
2:24</A></tt></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Same here. This becomes:</div><div dir="auto"><br></div><div dir="auto">[Genesis 2:24](passagestudy.jsp?action=showRef&amp;type=scripRef&amp;module=&amp;value=Genesis+2%3A24)</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><font face="FreeSerif"><br>
<br>
This takes advantage of the HTML nature in ThML's essence as
HTML-plus-goodies. ("Goodies" are <note>, <sync>, and
<scripRef>.) The latter example exploits internal habit of
how the engine's filters generate xref from scripRef; the former
is simply an odd protocol, "sword://". No, these are not concepts
that are portable to other Sword apps. Er, well, sword:// is
known in some corners other than Xiphos, and xiphos-nav operates
on its basis.<br>
<br>
I wish I could have done xrefs as actual ThML <scripRef>,
avoiding the post-filter appearance of such links, but that wasn't
possible.<br></font></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">It's not likely to be possible here, either. HOWEVER, someone can enter them directly as scripRef if we support md, and they'll be inserted to the module that way. When they come back out, they can either stay as ThML or we can render them to HTML and from there into MD.</div><div dir="auto"><br></div><div dir="auto">Nothing says we would have to parse the result into HTML first, though. That's part of the beauty of markdown. We can edit however we want, and let users use a combo if they desire.</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><font face="FreeSerif">
<br>
And no, these features aren't reflective of my personal bias re:
ThML. It's just that an editor's HTML result is best interpreted
by Sword as ThML, exactly because of HTML-plus-goodies. HTML
content makes no sense as any other Sword-grasped content type. If
we could add an MD filter set to Sword directly, we could walk
away from round trip MD to HTML and HTML to MD. But that's not
going to happen.</font></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">We can skip the HTML entirely and leave the user editing the ThML->markdown as is. Then things like the rendered out links aren't an issue.</div><div dir="auto"><br></div><div dir="auto">And adding a MarkDown filter to the engine probably isn't very difficult at all. MD is very simple.</div><div dir="auto"><br></div><div dir="auto">--Greg</div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br>
</div>
_______________________________________________<br>
xiphos-devel mailing list<br>
<a href="mailto:xiphos-devel@crosswire.org" target="_blank" rel="noreferrer">xiphos-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/xiphos-devel" rel="noreferrer noreferrer" target="_blank">http://www.crosswire.org/mailman/listinfo/xiphos-devel</a><br>
</blockquote></div></div></div>