Import from GG problem - Wrong rendering

[pmario]

Have a look at this post here: See: [tw5] Task for today on journal tiddler - #5 by pmario

and at GG: https://groups.google.com/g/tiddlywiki/c/KCByy1vqlOA/m/AauEFKARBgAJ

I did post the code

<$set name=expression filter="[<currentTiddler>search-replace:g[-],[]]">
<ul>
<$list filter="[sameday:scedule<expression>]"><li><$link/></li> </$list>
</ul>
</$set>

but Discourse shows it as:

<$set name=expression filter="[search-replace:g[-],[]]">

<$list filter="[sameday:scedule]">
• <$link/>

GitHub has the same problem, since the markdown parser tries to show the elements.

If we want to import the GG history, we need to fix this problem somehow. … So may be the content form GG should be shown as plain text and not rendered with markdown

Just a thought.
-.mario

[boris]

I think, but haven’t tried it myself yet, that code fencing would fix this, using three backticks?

<$list filter="[sameday:scedule<expression>]"><li><$link/></li> </$list>

I’ll do a test by email.

Also this looks relevant:

[tw5] Expect GG2TW Updates Coming Up!

Hi all, A while back, I presented to you the GG2TW tool to convert GoogleGroups conversations to Tiddler JSON files. Since then, I have not done much with the tool, but with the announcement of migration by Jeremy a few days ago, I have decided to revamp the tool. What to Expect: the tool will take as an argument URL’s of Google Groups conversations, which it will then convert. JSON output will be the same/similar, but with maybe a bit-nicer look (no left newline chars, etc.) Possibly an op…

I think GG history import is a pretty major project, any way you look at it. Running the two systems in parallel for a while will give people some experience in the differences.

I’ll mention it in the community call tomorrow.

[boris]

OK, I tested it:

Code fencing via email

I am putting some code in an email that gets turned into a forum post. First test without code fencing: <$set name=expression filter="[search-replace:g[-],[]]"> <$list filter="[sameday:scedule]"><$link/> Now with code fencing (which is three backticks on their own line at the beginning and end of the code): <$set name=expression filter="[<currentTiddler>search-replace:g[-],[]]"> <ul> <$list filter="[sameday:scedule<expression>]"><li><$link/></li> </$list> </ul> </$set>

Hooray! Looks like adding three backticks around code will render correctly via email.

And yes, your original point still stands @pmario – any GG import would be good to handle this correctly.