XPost: linux.debian.bugs.dist

Package: debian-policy
Version: 4.1.0.0

Hi!

This version has lost the distinction between a single policy html and
the one with different files per chapter. This will break links.

Thanks,
Guillem

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.bugs.dist

Hello Guillem,

On Tue, Aug 22 2017, Guillem Jover wrote:

This version has lost the distinction between a single policy html and
the one with different files per chapter. This will break links.

This was intentional. The single page output is much more useful to
casual readers wanting to look something up.

I think that maybe we should reassign this bug to www.debian.org to
request rewriting of the old URIs?

--
Sean Whitton

--=-=-Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAlmcbLUACgkQaVt65L8G YkAdHA//fw0sv5Z+rulr3ijxqEilC4n+Gv/ob13avO17ob5tgYA6vH/W/WOcIf/4 IlQH78IIsHrHcqyF66JbGI5SKRpcczXWVwsTtv75eG7myG4t9rvVs3bzbcdnxwGA mD1e0XwLe/gq2vtBOe+V2GFRMshmGeGOL8EgV3jJ4CPJCxy5LbdmrejmT7t/Fb7H EFYcRxuUq3sOIdzlKZUl+agyoFqr481kyHHqrEys7mganNHaMV2zd9z/rE4vFZqc YJjsvPzYeVB36pC2iEcfdMwf48WfyXjTjyAU/nsf8HleBNDFjJ8Eo32D1pSGirXM lWKM6akOxp6RzbYs7nz0pcEvoOr8Nn8RyinidHCH9GYvaa+haMFsOe7DV9MLE9zn RpcI+by2RO9B0Nrhb/MqAoFcARKjNFh9x4hDV327bZMo4dfHf9UN0O6ncyIgqOS2 pZ4DEhZk2kVqZLikkZENjKgj/WiFMkz+68W4NDjF8mowCA5ms4zw1doEVqO4fq7V urwur878nWXBtzNwP3T9HLJiSXszwCuqFI2s+iPCevqrrBKoWv1ntaAj2fiYANfv EARFmtPLY0pPxDLc2CWjszktEtwnaQQBOeyOVEDKFASh4rOuZdbHww7vsvTqnHmO Pp0ohWNSLkL3ptU6GacIIDz2Vsd//Rtt3sDZo7CMx3vcxNWeUzo=wcMG
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.bugs.dist

Hi,

Sean Whitton wrote:

On Tue, Aug 22 2017, Guillem Jover wrote:

This version has lost the distinction between a single policy html and
the one with different files per chapter. This will break links.

This was intentional. The single page output is much more useful to
casual readers wanting to look something up.

I don't completely understand. The old rendering had both single page
and multi-page versions. If I understand what you're saying, it is a
reason that the single-page version is useful, but why does that
preclude also providing the multi-page rendering?

Thanks,
Jonathan

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.bugs.dist

Hello Jonathan,

On Tue, Aug 22 2017, Jonathan Nieder wrote:

I don't completely understand. The old rendering had both single page
and multi-page versions. If I understand what you're saying, it is a
reason that the single-page version is useful, but why does that
preclude also providing the multi-page rendering?

Ah, sorry, I think there are two bugs here:

- it would be nice to include the multi-page rendering in the package

- since we're publishing only the single-page version on www.debian.org,
we need to rewrite the links

--
Sean Whitton

--=-=-Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAlmcgawACgkQaVt65L8G YkCn5RAAglu+sFhu19RdMdt5Zad49VBo15OrcyFzmCtGVoydiBDZ2CL46aM7gXba unOccXCZEQhp3HM6Aw2c10Dbnmx0CY9WQUzkTMN14kF7zCjaFk8AUH77fsqDU0o+ 9r+EdZRREQjyMTogqNYKXA7F0CuzNe25roK7LEDLvKHJpcEgFlpOYXUk+Xwv2b7Z D0r+S5K77UHmp1Isf5e/XtHv7A2yFLsiUJvUnAZorPbp7VRX8e8pjSu8W60JTkev RRjEzYAIMOqxWYZ5H2NW8M5zAbKrPIrF/09fAoTrdWVsO6nx9bsDx2qaI9CcIYuQ oA6N+U17WQT8GTwVZzpvqhvrubIdMIK3FVT1zPnsnYFjksFzfKasp1tRacW9SXoX egPjMBeHOLyghWFB1wM8uxbGwH00SN7mHebfjoTkVmKZNg7vX4odZNno+6DSlmz0 9kJnHZaoXGtFFIc0bTMl3TdCRDbi9vzIvRkKrnjSgWjTeX2gl2xJATmYaA5vjJfg 5ME4fIFOrIj13byLjfQqdCoUmlSnwxeugt8d4DZjjAzzZfiIXtGR1aEaqHkrSZjX kGu6D1Hf0cBI530n3L20TYf/xcOO5odMyUH1uodsdT02gioqI+DFOdc8Z9tuZxk2 02m0d7ekGS9xr1zYvCGD7P+tPI/E4LDiax6iLho704nOc5IJrMI=Nvao
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.bugs.dist

On Tue, Aug 22, 2017 at 12:10:36PM -0700, Sean Whitton wrote:

- it would be nice to include the multi-page rendering in the package

More than nice, please. I don't really deal with huge single-page
documents. Besides you wrote:

The single page output is much more useful to casual readers wanting
to look something up

I deem this completely subjective, please don't assume such assertion as
facts. Also, I don't consider myself a "causual reader" and when I want
to read something up I know what's the name of the paragrah, pick it
from the index and then head to the relevant, single page.

- since we're publishing only the single-page version on www.debian.org,
we need to rewrite the links

Please do publish both.

--
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlmcjjMACgkQCBa54Yx2 K60eoBAAjq1PG/ga53gmDS24iPfEnzmmwHXS/RHjzsUnWOcCSua/VbIetdzz6akl dI/nyIw/C1OFnHUTYHAjD/Vp2vNirQ7hbv5qAf/7pXv6l/JCxht7D9yFJLu5dzTG 5LfbQLNuzoY1zXugr+06IdYvYaG1jGUWt9kH81s9NPIQeeM+TTFFJwIT8teNOdGe Qh4uxs424qazcevQ5xIns+t9QLvHL5dqzvJHKgGX/pmSIR99bYL6s4WTT0yC9tOI VLpXf5xcXgSq/T8PYeN9OLlMpEXF25ND/dnetwROHglFahlW/RS6e39lKEJWEGlB vvn0p4CFexNLnRl36LFiX2a7hRtBt4bLFJi/RpJ7bvu/aVkSzq0qDb36YlwI6my3 JyUZNlK5k2h2URvOa/0RLWnGF7pi9QnxE2WHKpWFPOmwv//WakVwYzdns4t/KsRf u9g5vbzI+B6LhNckAgrRJqYrZ/91oGBWXPR/kmVhlhzCSimG3mS9F7WoCafUdn8g UDW+cIzaTZTC8AGezW+/HrabXN5L1d28sJMHFQb4v7CXU4vEES5

XPost: linux.debian.bugs.dist

Hi!

On Tue, 2017-08-22 at 11:09:37 -0700, Jonathan Nieder wrote:

Sean Whitton wrote:

On Tue, Aug 22 2017, Guillem Jover wrote:

This version has lost the distinction between a single policy html and
the one with different files per chapter. This will break links.

This was intentional. The single page output is much more useful to
casual readers wanting to look something up.

When I want to search for something in an on-line document I also
select the single-page document if it's available. Otherwise when I
want to navigate the document or read specific parts, I find the
multi-page way more pleasant and clear, because each chapter is
contained so I know how much there is to finish it, and scrolling or
using say the Ini/End key take you to the expected boundaries, and
it tends to have a global and intrapage TOCs to go to specific parts.

I don't completely understand. The old rendering had both single page
and multi-page versions. If I understand what you're saying, it is a
reason that the single-page version is useful, but why does that
preclude also providing the multi-page rendering?

I guess there are two problems here, one is indeed completely losing
the multi-page rendering from the package. The other is the default
change in the web site. IMO the best solution, and what is customary,
is to present both (or more) rendering and let the user select:

[HTML one-page] [HTML multi-page] [PDF] [EPUB]

Thanks,
Guillem

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.bugs.dist

control: retitle -1 Include multi-page HTML in package
^ see below for explanation

Hello,

On Tue, Aug 22 2017, Mattia Rizzolo wrote:

On Tue, Aug 22, 2017 at 12:10:36PM -0700, Sean Whitton wrote:

- it would be nice to include the multi-page rendering in the package

More than nice, please. I don't really deal with huge single-page
documents. Besides you wrote:

The single page output is much more useful to casual readers wanting
to look something up

I deem this completely subjective, please don't assume such assertion as facts. Also, I don't consider myself a "causual reader" and when I want
to read something up I know what's the name of the paragrah, pick it
from the index and then head to the relevant, single page.

Right, indeed, you're not a casual reader, and we would expect you to
have the Debian package installed. I think the web version should be
tailored for people coming from outside the project who don't know that
such a package exists. For them, it's easier to have a single page.

This is subjective but that doesn't preclude me making a judgement about
what most people would prefer, based on my experience.

- since we're publishing only the single-page version on
www.debian.org, we need to rewrite the links

Please do publish both.

On Tue, Aug 22 2017, Guillem Jover wrote:

I guess there are two problems here, one is indeed completely losing
the multi-page rendering from the package. The other is the default
change in the web site. IMO the best solution, and what is customary,
is to present both (or more) rendering and let the user select:

[HTML one-page] [HTML multi-page] [PDF] [EPUB]

So you'd like https://www.debian.org/doc/debian-policy/ to be a menu?

I think that those who want this should file a bug against
www.debian.org. It's not really in our purview, since we don't maintain
the script that maintains the /doc/ directory. Hence I'm retitling this
bug to the part that is the policy editors' responsibility.

--
Sean Whitton

--=-=-Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAlmcy7gACgkQaVt65L8G YkCg1BAAlanYCDp4eKtW9woYqYy8Lbac7rOrc77Tk0TH5ZFtHqnQ20E9CRElzuDy TWRi8nfNLC91hNH3rTq5o42pV6W4r8J2BOUB13NuJPUzgCEfiLTA4OC9za2jZw4j OxKdlJpXV7Qg3nejSfdCfsQYnbBxBg7kZJPi7pM/ySongDhr8V8VXStvS5jkL1dJ tAB/h+/9oykjHP2tL+u2VFT+u2C+2LRtlzJ9pTzekGajN3EKciYm1icTAhErqj9f Gi7uXfZ1uloiQz62pvngFP6jrJYdHiNNGi/3exV+wWOml5nIK4CTO/vkQamOIic2 OqLJCbZND12UnGW/VsIXdgYaWYQ2BuJuMB9ITnLZiuJbP6HfyDb3QlcWjRcy3/nM wnWPomPwRCU0DuMvR4NLwtDD+W+y4F1aJJ6Qbp7oPIXFvuEH3lqQXjEpH9aBrHE+ 6nGrRKFKw6RkAwgPag5Laku2e66MKsI/cYb/y3Cez7XXtbHVc9e0brOwi1/w11Xy b4FNmyYB2VmbsSTZ1JEq+sadjUmbllcv3efTiXHGv2BpTlOECZmh+z5skyuaAH4Q W7pfY7XXDsjVlCW5lp3uWXocP6rv6EuY2ZKIP8BtdFHAfJlzwP5m0NGdBneCP3Kt kLbZ/AVOR2mv/yt1l1roVHbtMdt32i6xEAenlghsi1MerQNGotU=GqDd
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.bugs.dist

Control: tags -1 pending

Guillem Jover <[email protected]> writes:

This version has lost the distinction between a single policy html and
the one with different files per chapter. This will break links.

Okay, I think this is fixed in Git and Policy should now ship both the single-file and the multi-file versions in the same directories they were
in before the conversion to reStructuredText. The multi-file version is
in policy.html and the single-file version is policy-1.html.

This also required adding _static and _images to the top-level of the usr/share/doc directory because single-file from Sphinx isn't strictly
single file (and we have images now), but I think it should all work. The tricky part will be on the debian-www side in copying things over. I'll
give them a warning that more changes are coming.

--
Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.bugs.dist

On Tue, 2017-08-22 at 17:26:32 -0700, Sean Whitton wrote:

On Tue, Aug 22 2017, Guillem Jover wrote:

I guess there are two problems here, one is indeed completely losing
the multi-page rendering from the package. The other is the default
change in the web site. IMO the best solution, and what is customary,
is to present both (or more) rendering and let the user select:

[HTML one-page] [HTML multi-page] [PDF] [EPUB]

So you'd like https://www.debian.org/doc/debian-policy/ to be a menu?

No, <https://www.debian.org/doc/devel-manuals#policy> which already
contains such menu. I'd rather see no change to the default and just
see the multi-page one added as an additional "format", so that we do
not break links etc. It's very common, and it's been so for people to
post URLs to the multi-page URLs BTW. I think having to add lots of
redirects would be counter-producive.

Thanks,
Guillem

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)