Local Links are a significant security exposure and are blocked by recent browsers. so the client must be part of the Windows domain and have access to the file. 
It's the client that reads the file, not the server.Earlier versions of WysiwygPlugin might cause issues. WysiwygPlugin Version 1.13 properly preserves the %20 encoded spaces and will also encode spaces when saving the topic.Explicit HTML tags must have embedded spaces encoded.
] does not need to be encoded because it has the explicit link text. Simple square bracket links without link text must have embedded spaces encoded. Under some conditions, embedded spaces must be encoded as %20. It's probably safer to use the 3 slash format. Some browsers appear to auto-convert a single slash file:/some/file to the required 3-slashes file:///some/file. Technically the forward slash should be used throughout the link, but the backslash works on windows platforms. 
Write the link using file:/// (3 forward slashes), followed by the UNC name \\server\path\filename. Windows shares can be referenced in a link, with some restrictions / considerations: How do I enter file paths into a link? (Both local and UNC Names) The "correct" link format is file:/// followed by the path to the file, using forward slashes throughout:
0 kommentar(er)
