hi
i have a visio file with numerous pages id like to publish to the web. there are links all over the file from one page to another
One requirement is that once published I have a direct link to any of the pages so something lke
webpage/visiochart.htm?pagename=theMainDrawing
does anyone know how?
thanks in advance
Hi,
That's pretty much it...
Should be: ?page=MyPageName
Have a look at this post for more details:
http://visualsignals.typepad.co.uk/vislog/2009/04/save-as-web-url-parameters.html (http://visualsignals.typepad.co.uk/vislog/2009/04/save-as-web-url-parameters.html)
Hope that helps.
Best regards
John
thanks mate
does this work on most browsers that you know?
thanks again
A small point to bear in mind, the first entry in a parameter string list begins with a "?=", subsequent parameters use an "&", but the "&" is a special character and should be written in URLs as "&".
In terms of browsers, I think this will only work for VML and XAML output. I've not managed to get it to work (out of the box) with secondary formats such as gif or png. There's no reason why it shouldn't but the current Save As Web output doesn't appear to set the page correctly (even though it still parses the query string properly).
So if you're using XAML output then IE and Firefox will work and if you're using VML then IE only (v5 or above).
Paul - I hadn't come across the first equals character or & requirement. Are you talking about constructing the urls in the ShapeSheet? For example the following works ok (including the '%20' in place of the space):
http://www.visualsignals.co.uk/blogresources/41/OtherFormatsExample.htm?page=Row%201%20Rack%201&shape=Server.116 (http://www.visualsignals.co.uk/blogresources/41/OtherFormatsExample.htm?page=Row%201%20Rack%201&shape=Server.116)
Best regards
John
Small correction to what I said, the & is fine in a URL, e.g. as pasted into a web browser address bar or as a shape hyperlink but when used within a webpage i.e. with HTML the & is a special character (HTML entity) and must be represented as &
http://en.wikipedia.org/wiki/HTML_entity (http://en.wikipedia.org/wiki/HTML_entity)
It may work without this encoding but down that path lay future bugs and problems.