Links to Markdown images stored in the database do not work in external editors.
The problem is: Users are referred to external editors when they complain about Devonthink’s built-in editor. If we are directed to external editors, I think Devonthink’s should provide links in a way that they can be used in external editors without additional steps (like creating x-devonthink links and pasting them manually).
Of course, I would be most happy to get a modern Markdown editor in Devonthink that lets me choose a font, line height, margins etc. in source view as well
The only links that work across all applications are local file URLs/paths or http(s) URLs. But improved support for text bundles which include images (just like RTFD does) is planned for future releases.
file:///<path to image> works (file:///Users/me/Desktop/whatever.png)
<absolute path to image> works (/Users/me/Desktop/somethingelse.jpg)
<relative path to image> does not work (folder/foobar.webp)
The last case is (kind of) obvious because for documents in DT, there is no clear relationship between their locations in the file system. So, for relative paths, DT interprets the folder names as group hierarchy in the current database.
I’m wondering, though, how that plays out for indexed documents? Intuitively, I’d expect relative paths to work as usual in that case, because they (and possibly the images they refer to) have defined locations in the file system.
It seems logical to me. Documents in the database are stored in folders that have no relation to the groups in Devonthink. So when I set a link to “images/filename.png” in the database, Devonthink knows what to do and shows the image. But the file is, in fact, located in another folder in the file system, and of course, external editors do not know that when the link is to a group, not to the actual folder.
Of course, having the option to use the actual path (given in the info panel anyway) to the image instead of the group might be one solution.
… just found this older thread (as I am dealing with the image issue as well). And, in light of the many spread-out, inconclusive discussions around TextBundle-format, I wonder whether this (by now ‘older’) statement on intended inclusion of Textbundle-format is still official policy, resp. part of any (internal) roadmap?
Thanks already for any updates and/or clarification on this!
I tried to understand this answer in the horizon of the original assertion “is planned for future releases” (from Aug 2023). But I really can´t read it in any orienting way as your answer doesn´t seem to give any dimensionality alongside (timelines, versions, priorities, commitments etc.). I guess this is the intention.
Used to more direct communication, I was a little lost, admittedly.
So, I asked my friend Claude. His reading:
"Key Implications:
1. The feature isn’t officially cancelled
2. There’s no current commitment to develop it
3. It may never actually be implemented
4. The response is a diplomatic way to avoid saying “no” directly
Think of it as the corporate equivalent of “We should definitely get coffee sometime!”
– Maybe this helps others here, still invested in this topic (see other discussions), getting expectations set correctly.
I trust Claude on this one and put the topic aside/to rest, and grab a coffee .
[Disclosure: the prompt was “What is the meaning, most likely reading of the one-line “It‘s still planned but not for the next feature releases.” given by developers being asked about stated plans to introduce a feature?]
Never trust AI responses This was NOT a diplomatic way to say “no”, it’s still on the to-do list (like many many other things) but not part of the next releases.
I mostly trust people I (can) have coffee with.
But thanks for re-igniting unspecified hopes here! I´ll send the therapists bills to DevonTechnologies…
OK. We´ll see where things are heading… We live in times where it´s best and most sane to not expect anything in particular, anyways
(Everyone else: find your own reading here. Neither me nor Claude can really help in this … )
.
This was NOT a diplomatic way to say “no”, it’s still on the to-do list (like many many other things) but not part of the next releases.
