#1
|
|||
|
|||
Importing from Treepad
I've got a couple of whopper treepad databases I'd like to convert. It's easy enough to get the basic import function to execute but my links to external files are messed up. You can see the link text underlined, but there's no underlying link information or it's invalid and doesn't activate when you click on it. Is there a trick to this? I'm wondering if UR supports proper URIs as links in documents or whether links specs should just be Windows/DOS-style relative paths?
|
#2
|
|||
|
|||
How are these file links stored in TreePad? Please ZIP and send to support@kinook.com or post a TreePad database (and resulting UR import) which demonstrates the problem. Thanks.
|
#3
|
|||
|
|||
Hi,
Sorry to have been less than clear. I've attached an example of a Treepad database and an UltraRecall database with attempted import in the "Imported Items" folder. The Treepad database contains a single node with a relative link to an external file that I've also included. If you hilite the link text in the imported UR item and right-click to get the context menu, you'll see that you can only try "insert link". That dialog shows that the actual link is in there but it's smushed into the link text and the link itself is empty. Thanks for looking at this. tim |
#4
|
|||
|
|||
That is not a real RTF hyperlink, it's just underlined text. Treepad would need to store it as a true RTF hyperlink in order for it to work in other applications like UR, Word, WordPad, etc.
|
#5
|
|||
|
|||
Rats
Thanks for this.
Can you easily tell me what the spec for a RTF hyperlink is? I'd like to try to fix the links in the treepad file (en masse, with a text editor) so that I don't have to re-import a couple hundred links I've already carefully input once. |
#6
|
|||
|
|||
I don't think it's actually spelled out in the spec. We reverse engineered it by saving as RTF from Word. It looks something like this:
{{\field{\*\fldinst{HYPERLINK "c:\\\\boot.ini"}}{\fldrslt{\cf1\ul link}}}} |
|
|