From b8c8bb11b416ff6e8b7bfae919328fcd60838306 Mon Sep 17 00:00:00 2001 From: Vladimir Glazunov Date: Wed, 31 Mar 2010 12:42:44 +0200 Subject: native0: Help changes - transplanted from eebd7b934c4b@native0 --- helpcontent2/source/text/shared/guide/hyperlink_rel_abs.xhp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'helpcontent2/source/text') diff --git a/helpcontent2/source/text/shared/guide/hyperlink_rel_abs.xhp b/helpcontent2/source/text/shared/guide/hyperlink_rel_abs.xhp index 48d1ffaf79..f94ada5bef 100644 --- a/helpcontent2/source/text/shared/guide/hyperlink_rel_abs.xhp +++ b/helpcontent2/source/text/shared/guide/hyperlink_rel_abs.xhp @@ -59,7 +59,7 @@ An absolute path such as "C:\homepage\graphics\picture.gif" would no longer function on the provider server. Neither a server nor the computer of a reader needs to have a C hard drive: operating systems such as Unix or MacOS do not recognize drive letters, and even if the folder homepage\graphics existed, your picture would not be available. It is better to use relative addressing for file links. -A link to a web page, for example, "www.sun.com" or "www.myprovider.com/mypage/index.html" is an absolute link. +A link to a web page, for example, "www.example.com" or "www.myprovider.com/mypage/index.html" is an absolute link. $[officename] also reacts differently, depending on whether the file referred to in the link exists, and where it is located. $[officename] checks every new link and sets a target and protocol automatically. The result can be seen in the generated HTML code after saving the source document. -- cgit