This is the mail archive of the
mailing list for the Cygwin project.
Re: Proposed patch for web site: update most links to HTTPS
- From: Warren Young <wyml at etr-usa dot com>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Tue, 24 May 2016 06:38:02 -0600
- Subject: Re: Proposed patch for web site: update most links to HTTPS
- Authentication-results: sourceware.org; auth=none
- References: <BL2PR03MB228A4FE7B2CCA51E5FF5163DF610 at BL2PR03MB228 dot namprd03 dot prod dot outlook dot com> <20160520163624 dot GA22065 at calimero dot vinschen dot de> <BL2PR03MB2289CA95EC0CCF0D42AB961DF4D0 at BL2PR03MB228 dot namprd03 dot prod dot outlook dot com> <20160523103519 dot GA30229 at calimero dot vinschen dot 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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple