Commit 4f505b27 authored by Gabor Kelemen's avatar Gabor Kelemen
Browse files

Fix references to subpages of other documents, use / instead of #

https://bugzilla.gnome.org/show_bug.cgi?id=689765
parent acdbc6b7
......@@ -26,7 +26,7 @@
<section id="urls-in-emails">
<title>Change which web browser websites are opened in</title>
<p>Please see <link href="help:gnome-help#net-default-browser">the GNOME Desktop Help</link>.</p>
<p>Please see <link href="help:gnome-help/net-default-browser">the GNOME Desktop Help</link>.</p>
<p>If the preferred browser is set as default application but still does not work correctly please contact your distribution via their forum or bug tracker.</p>
......@@ -43,7 +43,7 @@
<section id="urls-in-emails">
<title>Change which mail application is used to write emails</title>
<p>Please see <link href="help:gnome-help#net-default-email">the GNOME Desktop Help</link>.</p>
<p>Please see <link href="help:gnome-help/net-default-email">the GNOME Desktop Help</link>.</p>
</section>
......
......@@ -22,7 +22,7 @@
<title>Creating a GPG key</title>
<note style="advanced"><p>These steps are very technical. For average users we recommend using the <link href="help:seahorse#index"><app>Seahorse</app> application</link> for managing GPG/OpenPGP keys.</p></note>
<note style="advanced"><p>These steps are very technical. For average users we recommend using the <link href="help:seahorse/index"><app>Seahorse</app> application</link> for managing GPG/OpenPGP keys.</p></note>
<!-- TODO:POST-3-2: Update and rewrite using Seahorse. Needs a complete rewrite once https://bugzilla.gnome.org/show_bug.cgi?id=508744 is fixed. -->
<p>Before you can get or send GPG encrypted mail, you need to generate your public and private keys with GPG.</p>
......
......@@ -19,7 +19,7 @@
<title>Save messages as PDF</title>
<p>In order to save emails in the PDF file format, select <guiseq><gui>File</gui><gui>Print</gui></guiseq> and then choose <gui>Print to File</gui>. See <link href="help:gnome-help#printing">the desktop help</link> for general information on printing.</p>
<p>In order to save emails in the PDF file format, select <guiseq><gui>File</gui><gui>Print</gui></guiseq> and then choose <gui>Print to File</gui>. See <link href="help:gnome-help/printing">the desktop help</link> for general information on printing.</p>
<note style="advanced">
<p>You can also export messages as PDF by dragging and dropping them to the file manager, instead of dropping them in mbox (text) format by default.</p>
......
......@@ -25,5 +25,5 @@
<p>If this is not the case and Evolution normally works but has suddenly stopped connecting, you may have unintentionally clicked on the connection icon in the lower left corner. When connected, the icon resembles a pair of sockets joined together. If the sockets are open, there is no connection (and the <gui style="button">Send/Receive</gui> button is grayed out). Click on the icon to change its state.</p>
<p>If the problem persists and you are sure you have not clicked the icon, but you can still reach the network from other apps on your system (browsers, FTP, SSH, ping etc.) it may be that NetworkManager (NM) is not properly configured. Many Linux distributions now use NM to manage their connections, and if it is installed Evolution will use it to detect if the network is up. However NM can be installed but not properly configured, leaving the network working but not detectable by Evolution. (Note that other GNOME-based applications may also fail for the same reason.) The solution is to configure NM to manage your network interface. This is usually easy to do but is outside the scope of this document. For more information please take a look at the <link href="help:gnome-help#net">Desktop help</link> or seek help from your distribution support forums, mailing lists etc.</p>
<p>If the problem persists and you are sure you have not clicked the icon, but you can still reach the network from other apps on your system (browsers, FTP, SSH, ping etc.) it may be that NetworkManager (NM) is not properly configured. Many Linux distributions now use NM to manage their connections, and if it is installed Evolution will use it to detect if the network is up. However NM can be installed but not properly configured, leaving the network working but not detectable by Evolution. (Note that other GNOME-based applications may also fail for the same reason.) The solution is to configure NM to manage your network interface. This is usually easy to do but is outside the scope of this document. For more information please take a look at the <link href="help:gnome-help/net">Desktop help</link> or seek help from your distribution support forums, mailing lists etc.</p>
</page>
......@@ -21,5 +21,5 @@
<title>How to get help</title>
<p>To receive help on problems you can send an email to the <link href="http://mail.gnome.org/mailman/listinfo/evolution-list">Evolution mailing list</link> or talk to developers and other users in the IRC chat channel #evolution on the server irc.gimp.net. To connect to an IRC server you can for example <link href="help:empathy#irc-manage">use the internet messenger application <app>Empathy</app></link>.</p>
<p>To receive help on problems you can send an email to the <link href="http://mail.gnome.org/mailman/listinfo/evolution-list">Evolution mailing list</link> or talk to developers and other users in the IRC chat channel #evolution on the server irc.gimp.net. To connect to an IRC server you can for example <link href="help:empathy/irc-manage">use the internet messenger application <app>Empathy</app></link>.</p>
</page>
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment