Looking at the textprimatives
http://www.tiddlytools.com/insideTW/#config.textPrimitives
My interpretation is that if I add txt2tags-style links, I may have to
change some of those linkregex's, and they look a tad complicated!

Otherwise there's "unWikilink" ~ and this makes me concerned about the
"raw" syntax.
I think I'm correct in seeing that txt2tags ""raw"" syntax is equal to
the tiddly """nowiki""" syntax.  I think that the unWikilink primative
doesn't effect this syntax at all (in neither tw syntax nor txt2tags
syntax) so hopefully this isn't a problem (I'll just leave unWikilink
as-is).

On Mon, Sep 20, 2010 at 1:34 PM, David Young <[email protected]> wrote:
> Thanks for spotting this. I wouldn't have thought that syntax regex's
> were outside of the formatters!  I'll have to skim the whole codebase
> for regular expressions to see where else they creep in.  Looks like
> I'll have to replace that whole function (since the regular
> expressions are local to the function, at least that is my <1week
> javascript interpretation) and maybe a couple of the members in
> config.textPrimitives.  I'll definitely add this to my todo, but it
> will probably be put on the "nice to have list" if transclusion of
> whole tiddlers still works properly without the change- It would be
> nice to have for completeness's sake, that is.
>
> On Mon, Sep 20, 2010 at 11:51 AM, PMario <[email protected]> wrote:
>> hi David,
>>
>> If you want to use <<tiddler abc##section>> transclusion _and_ if you
>> want to change
>> !section to
>> = section =
>>
>> go on reading. Otherwise ignore the post.
>>
>> ======
>> I had a short look at insideTw about section, slice handling in
>> getTiddlerText [1]. Since it is a main part of <<tiddler
>> abc##section>> transclusion handling. And it uses tw header syntax for
>> identification.
>>
>> Have a look at the source.
>> http://www.tiddlytools.com/insideTW/#TiddlyWiki.prototype.getTiddlerText
>>
>> So there will be some side effects. May be you need to take care of
>> this.
>>
>> -m
>>
>>
>> On Sep 20, 3:46 pm, David Young <[email protected]> wrote:
>>> > Can you post a pointer to your txt2tags syntax description.
>>> > -m
>>>
>>> Of course! That completely slipped my mind from the beginning. Here's
>>> a general listing of the txt2tags 
>>> markup:http://txt2tags.sourceforge.net/markup.html
>>>
>>> It has some formatting in common with tiddly.  Note that the linked
>>> document doesn't cover a popular beta markup for "tagged text":
>>>
>>> ''' a full line of <b>tagged</b> stuff.
>>>
>>> '''
>>> a whole block of <b>tagged</b> stuff.
>>> '''
>>>
>>> a few words on a single line of ''<b>tagged</b>'' stuff.
>>>
>>> Tags are functionally equivalent to <html></html> markup in tiddlywiki.
>>>
>>> Another confusing markup is "raw" which uses " instead of ' and simply
>>> bypasses the txt2tags parsing of text- though any tags inside are
>>> hidden from the output document. RAW wouldn't convert **bold** to
>>> <b>bold</b>.  RAW would still convert the input text <b>bold</b> into
>>> &lt;b&gt;bold&lt;\b&gt; , thereby "preserving" the output text.
>>>
>>> My biggest concerns are the table syntax and the img/url syntax.  I
>>> think I'll be leaving the tiddly table formatter intact and see if I
>>> can manage support for basic txt2tags table functionality.  The same
>>> for img/url syntax- though their syntax is so very similar that I
>>> don't know if I will be able to have formatters for both
>>> tiddly/wikiwords AND txt2tags img/url markup.  In that case, I would
>>> leave the tiddlywiki formatter in place. I don't think I can fully
>>> replace either tables or img/url markup without having to replace
>>> most/all of the shadow tiddlers. The same with <<macro>>, but
>>> in-general any markup that has no equivalent in txt2tags will be left
>>> in place.
>>>
>>> I may end up with an odd pidgin of txt2tags markup for all of the
>>> "simple" text formatting things, and leave tiddly's markup alone for
>>> the more complex/background stuff, but this is mostly intended to be
>>> an easy plugin so that I and others like me who are used to the
>>> txt2tags markup can use tiddly with minimal modifications to an
>>> empty.html tiddlywiki.  If I did a full replacement, I'd probably have
>>> to keep track of tiddlywiki's development and modify my plugin much
>>> more frequently- maybe requiring I make a derived tiddlywiki
>>> implementation instead of a simple plugin! All for much less "reward"
>>> in the form of markup compatibility.
>>>
>>> --
>>> David Young
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWikiDev" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to 
>> [email protected].
>> For more options, visit this group at 
>> http://groups.google.com/group/tiddlywikidev?hl=en.
>>
>>
>
>
>
> --
> David Young
>



-- 
David Young

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/tiddlywikidev?hl=en.

Reply via email to