cdaven / tiddlywiki-stuff Goto Github PK

Can I export markdown with the link syntax in the original text? This way, for some people who move to other markdown editors, like obsidian, the linking effect can still be maintained. Instead of adding them again.

As I asked in the talk tiddlywiki forum (https://talk.tiddlywiki.org/t/first-version-of-markdown-export-plugin/3324/20?u=arunnbabu81)

Can there be an additional option like a Realtime Markdown Convertor tiddler

1. At the top of this convertor tiddler, there shall be a tiddler selector with search box (where we can type the tiddler name) or select widget option to select the tiddler converted to be markdown.
2. Once the tiddler is selected, a side by side editor opens up below the selector showing the wikitext format on the left side and markdown format on the right side.
3. At the bottom, there shall be a export as md or copy to clipboard buttons.

Is it doable?

I've made some (small) patches to the install and test PowerShell scripts so that it runs on Mac (and probably Linux as well, but haven't tested yet).

Are you interested in a PR with the changes?

The end result is that if you export a tiddler with a table rendered with headers under a thead row, the entire row is absent from the exported Markdown.

Steps to reproduce:

1. Import Table Export Example.json as a tiddler in the example wiki at https://cdaven.github.io/tiddlywiki/index.html
2. Click the export button and choose "Markdown".

The rendered markdown will render:

Here is an example:

| ASDF |
|------|

Which turns the first data row into the header and removes the header entirely.

This isn't really an issue when using WikiText because TiddlyWiki places header rows under tbody, but if you use the Markdown plugin and use Markdown headers, you'll get header rows in thead. (As a digression, I use Markdown export on Markdown tiddlers to handle transclusion, widgets, and wiki links that are allowed in Markdown tiddlers).

And would it be possible to export the filtered entries as a folder with a lot of small mmrmrakdown files instead of a whole extra large file? It would be better to save it that way.

Originally posted by @dongrentianyu in #3 (comment)

Empty markdown file (“tiddlers.md”) is exported with “export all”, or the “Export tiddlers” with “filter” tab in AdvancedSearch. The same holds whether exported from a Tiddlywiki hosted on Tiddlyhost or stored locally. I am working on Windows, and Firefox. No message outputed to browser console.

When exporting with the TW CLI I get dates in the frontmatter formatted differently from when I use TW in the browser.

For example, I added a new tiddler "TestPage/FrontMatter" and expected the following:

title: 'TestPage/FrontMatter'
date: '2024-06-23T08:30:50.917Z'
tags: ['Another Tag', 'Tag2', 'TestData']
created: '2024-06-23T08:22:18.552Z'

When using TW in the browser to export to Markdown I get that data. But when I use TW using the CLI I get:

title: 'TestPage/FrontMatter'
tags: ['Another Tag', 'Tag2', 'TestData']
created: 'Sun Jun 23 2024 18:22:18 GMT+1000 (Australian Eastern Standard Time)'

Attaching a modified test.ps1 to contains this test case: test.ps1.txt (had to rename to ".txt" for GH to let me upload it :-) -- can also find here)

I am looking into it but so far don't understand the root cause. The render-rules.ts file is definitely calling .toISOString() on the appropriate field, so JS has parsed it as a date just fine. Just for some reason in a node.js context the date is not actually ISO formatted. The other thing to note is the missing date field, that seems to be because it's not an instanceof Date but again that only happens when running from CLI.

Any ideas? In the meantime I will keep digging...