X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=Hd43KQ2kUYA8bqj5HMR18jiF0ZZk
	SMtcwwfrslbSTydRysq6Lycc4daGZAnlFd78w5dhnHAiRhTescMNh4PT8IjOlfTo
	3KhH3O7bOEucnISXD4Te64jYKZW8JuKZuxzO2cY5zrquPOKurdQ97E9zLp8nYqFr
	GOqwkmGGPqMioWw=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; s=default; bh=cedb78HqitdpHU/QVLS8YfFwCbM=; b=QK
	v78Sqoj0oXMWKEDm0pFEAOcuACbkzp/vVP7JgTIEgp5isWB5STWY1jCva1XSByaO
	S6pwgr4faH+eXaSykGtArDO7uFtsPPpi4yEgloA8asLW6zjGRL7q73Qnm9qDfOVT
	GUB5lrlUgMiyk5nSYjDfeaY5zE2FyzpcgJaNsZElQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=H*m:usa, website, H*r:envelope-sender, site
X-HELO: etr-usa.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Proposed patch for web site: update most links to HTTPS
From: Warren Young <wyml@etr-usa.com>
In-Reply-To: <20160523103519.GA30229@calimero.vinschen.de>
Date: Tue, 24 May 2016 06:38:02 -0600
Message-Id: <4CF457F2-A27F-4AB9-B5D0-4F3E70B46108@etr-usa.com>
References: <BL2PR03MB228A4FE7B2CCA51E5FF5163DF610@BL2PR03MB228.namprd03.prod.outlook.com> <20160520163624.GA22065@calimero.vinschen.de> <BL2PR03MB2289CA95EC0CCF0D42AB961DF4D0@BL2PR03MB228.namprd03.prod.outlook.com> <20160523103519.GA30229@calimero.vinschen.de>
To: The Cygwin Mailing List <cygwin@cygwin.com>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u4OCl2ix022714

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