I'm picking up this very old discussion. What is the state of the art? It seems that the proposed solution by Eric Shulman
``` [[filename.pdf]] is a link to a tiddler, but [[filename.pdf|filename.pdf]] is a link to an external file And, because the link doesn't start with an /absolute/path/to/ folder/..., it is automatically handled by the browser as *relative to the current directory* (i.e, the one containing the TW document). Thus, you can also write something like: [[old version|archives/filename.jpg]] to link to a file in a *relative sub-directory*. ``` doesn't work with the current version of TiddlyWiki. I have exactly the constellation described in this example (see attached screenshot). The two links using a relative path respectively, point to a non-existing internal tiddler. The last link with the fullpath point correctly to the external PDF file. How can I use relative paths to external files nowadays? -Reinhard On Sunday, January 27, 2013 at 8:38:19 PM UTC+1 beert...@gmail.com wrote: > Hi Florencio, > > Just to make sure, I believe what Eric was trying to convey was that... > > [[my file|filename.avi] > > ...will do the trick for linking to any filename.avi that resides in the > same directory as your TW via some link that displayed as [my link]. > > Cheers, Tobias. > > > Am Sonntag, 27. Januar 2013 18:54:37 UTC+1 schrieb giraf...@gmail.com: >> >> Thanks Eric for your answer. >> >> I solved in the following way: >> >> As I used FF, I upload an extension for Firefox: LocalLink 0.5, ( >> http://locallink.mozdev.org/ ) >> and it worked fine. Also the simple way of placing the filename works >> with IE, but I did not try with other explorers. >> >> Florencio de la Torre >> >> El viernes, 25 de enero de 2013 18:24:22 UTC+1, Eric Shulman escribió: >>> >>> > the path and this command does not work: >>> > [[my file|file://filename.avi]] >>> > but with absolute path is works fine [[my file|file:///c:\my >>> > documents\filedir\filename.avi]] >>> >>> As I previously explained: >>> > > And, because the link doesn't start with an /absolute/path/to/ >>> > > folder/..., it is automatically handled by the browser as *relative >>> to >>> > > the current directory* (i.e, the one containing the TW document). >>> > > Thus, you can also write something like: >>> > > [[old version|archives/filename.jpg]] >>> > > to link to a file in a *relative sub-directory*. >>> > >>> > > Also note that the link doesn't specify either http:// or file:// >>> > > protocol. In fact, in most browsers, relative references only work >>> > > when you omit the protocol from the URL. In this case, it's an >>> > > advantage: it means that the same external PrettyLink can be applied >>> > > locally (as a filesystem reference), or remotely (as a server-side >>> > > URL), without needing any special TW code... the browser's normal >>> > > handling does it automatically. >>> >>> >>> > Is it a way to set a variable with the path where the files are >>> located? >>> > and to use this variable when naming the file to be openned? >>> >>> http://www.TiddlyTools.com/#ImagePathPlugin >>> >>> works for [img[...]], but not for general external links. >>> >>> enjoy, >>> -e >>> Eric Shulman >>> TiddlyTools / ELS Design Studios >>> >>> HELP ME TO HELP YOU - MAKE A CONTRIBUTION TO MY "TIP JAR"... >>> http://www.TiddlyTools.com/#Donations >>> >>> Professional TiddlyWiki Consulting Services... >>> Analysis, Design, and Custom Solutions: >>> http://www.TiddlyTools.com/#Contact >>> >> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/acf579f2-c645-48aa-ae14-c7c14627e745n%40googlegroups.com.
