From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Proposed patch for web site: update most links to HTTPS
Date: Tue, 24 May 2016 12:42:00 -0000 [thread overview]
Message-ID: <4CF457F2-A27F-4AB9-B5D0-4F3E70B46108@etr-usa.com> (raw)
In-Reply-To: <20160523103519.GA30229@calimero.vinschen.de>
On May 23, 2016, at 4:35 AM, Corinna Vinschen wrote:
>
> using relative paths inside the Cygwin docs
> (cygwin-api, cygwin-ug-net, and faq) is not such a bright idea, because
> the docs should ideally work even if not on the cygwin.com website.
Did you mean to say “absolute paths”? If not, then you’re arguing against yourself here. Relative links within the docs *are* what allow the docs to work when hosted off cygwin.com, as in my info(1) example. Otherwise, a link that should be an internal cross-reference turns into an external web page link.
Also keep in mind that DocBook has *four* different styles of links: <link>, <olink>, <ulink>, and <xref>. They mean different things, and give different effects. Depending on the stylesheets you use, they can even change behavior between different output types.
http://www.sagehill.net/docbookxsl/CrossRefs.html
http://www.sagehill.net/docbookxsl/Ulinks.html
http://www.sagehill.net/docbookxsl/Olinking.html
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-05-24 12:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 0:05 Brian Clifton
2016-04-25 0:29 ` Andrey Repin
2016-04-25 5:50 ` Brian Clifton
2016-04-25 6:10 ` Andrey Repin
2016-04-25 13:20 ` Adam Dinwoodie
2016-04-25 17:41 ` Andrey Repin
2016-04-26 10:17 ` Csaba Raduly
2016-04-25 19:59 ` Nellis, Kenneth
2016-04-25 20:46 ` Vince Rice
2016-04-25 23:18 ` Brian Clifton
2016-04-26 19:19 ` Achim Gratz
2016-04-27 10:18 ` Linda Walsh
2016-05-20 16:36 ` Corinna Vinschen
2016-05-20 20:47 ` Warren Young
2016-05-22 0:30 ` Brian Clifton
2016-05-23 10:35 ` Corinna Vinschen
2016-05-24 12:42 ` Warren Young [this message]
2016-05-24 16:59 ` Corinna Vinschen
2016-05-24 18:55 ` Warren Young
2016-06-12 10:13 ` Brian Clifton
2016-06-14 19:20 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CF457F2-A27F-4AB9-B5D0-4F3E70B46108@etr-usa.com \
--to=wyml@etr-usa.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).