Re: Proposal: move forward to Sphinx

On Sun, Jun 25, 2017 at 11:40:00AM +0900, Hideki Yamane wrote: > Yes, exactly what Russ says, converting to DocBook could make it > happen. So, it doesn't mean any waste of time and effort, DocBook > format is **necessary** for next step. Ah, I see what you mean. That's great. It is especially

Re: RFC: draft text for Policy sprint at DebCamp

On Sat, Jun 24, 2017 at 03:48:35PM -0700, Russ Allbery wrote: > Looks great to me! And we're probably coming up on time for that new > d-d-a email. I've created Teams/Policy/bits on gobby.debian.org to draft this. I've written some text about the sprint. Perhaps you could write up the introduct

Bug#865713: Declaring a charset of UTF-8 for policy files

On Sat, Jun 24, 2017 at 8:07 PM, Paul Hardy wrote: > On Sat, Jun 24, 2017 at 7:12 PM, Paul Wise wrote: >> On Sun, Jun 25, 2017 at 8:54 AM, Simon McVittie wrote: >> >>> For what it's worth, I agree that declaring the correct charset in HTTP >>> metadata is a better solution than prepending U+FEFF

Bug#865713: Declaring a charset of UTF-8 for policy files

On Sat, Jun 24, 2017 at 8:13 PM, Russ Allbery wrote: > > That's one of the things that confuses me a bit -- why not just use the > existing HTML files? ... > > I assume you're looking at: > > https://www.debian.org/doc/devel-manuals#policy I did a StartPage search for "debian upgrade checkli

Bug#865713: Declaring a charset of UTF-8 for policy files

On Sat, 2017-06-24 at 20:48 -0700, Russ Allbery wrote: > Can't we just set the character set for the text files that come from > Debian Policy?  At least with Apache you can set character sets with > whatever granularity you want. Doesn't look like there are any files within the Debian Policy dir

Bug#865713: Declaring a charset of UTF-8 for policy files

Paul Wise writes: > On Sat, 2017-06-24 at 20:07 -0700, Paul Hardy wrote: >> 2) Set the HTTP headers for charset="UTF-8" > FYI, there are 1018 non-UTF-8 out of 2605 total *.txt files on the > Debian website and 9 non-UTF-8 out of 1102 total *.txt files in the > Debian archive mirrors. It seems fe

Bug#865713: Declaring a charset of UTF-8 for policy files

On Sat, 2017-06-24 at 20:07 -0700, Paul Hardy wrote: > Three possibilities seem to exist, and I am fine with any one being chosen: > > 1) Use the UTF-8 signature in UTF-8 text files If this triggers browsers to use the right encoding, it seems reasonable to add it in the situation where the file

Bug#865713: Declaring a charset of UTF-8 for policy files

Paul Hardy writes: > If using the UTF-8 signature in a document is too aesthetically > distateful (and I don't disagree), and if setting the HTTP header to > denote a UTF-8 charset is not a universal solution because it will only > have effect on Debian's servers, would a tool that converted such

Bug#865713: Declaring a charset of UTF-8 for policy files

On Sat, Jun 24, 2017 at 7:12 PM, Paul Wise wrote: > On Sun, Jun 25, 2017 at 8:54 AM, Simon McVittie wrote: > >> For what it's worth, I agree that declaring the correct charset in HTTP >> metadata is a better solution than prepending U+FEFF ZERO WIDTH NO-BREAK >> SPACE >> (aka the "byte-order mark

Re: Proposal: move forward to Sphinx

Hi Sean and Russ, On Sat, 24 Jun 2017 15:39:33 -0700 Russ Allbery wrote: > > Are you aware that the transition to docbook was only completed about > > one month ago? I am not sure there is the energy to attempt another > > complete transition of the manual, once again invalidating all submitted

Bug#865713: Declaring a charset of UTF-8 for policy files

On Sun, Jun 25, 2017 at 8:54 AM, Simon McVittie wrote: > For what it's worth, I agree that declaring the correct charset in HTTP > metadata is a better solution than prepending U+FEFF ZERO WIDTH NO-BREAK SPACE > (aka the "byte-order mark") in the file content. Forcing every text file to UTF-8 isn

Bug#865713: Declaring a charset of UTF-8 for policy files

On Sat, 24 Jun 2017 at 15:04:41 -0700, Russ Allbery wrote: > Stéphane Blondon writes: > > pabs added such configuration few days ago for Apache configuration: > > https://anonscm.debian.org/cgit/mirror/dsa-puppet.git/commit/?id=5bcf8431d6b375d211a29f9d2c338e4400332e1a > > Paul, does this resolve

Bug#639663: marked as done (upgrading-checklist on www.debian.org, links from it to debian-policy)

Your message dated Sat, 24 Jun 2017 16:09:45 -0700 with message-id <87podt2dae@hope.eyrie.org> and subject line Re: Bug#639663: [debian-policy] Please provide upgrading-checklist via web has caused the Debian Bug report #639663, regarding upgrading-checklist on www.debian.org, links from it to

Bug#47438: marked as done (Update Policy copyright)

Your message dated Sat, 24 Jun 2017 16:07:43 -0700 with message-id <87tw352dds@hope.eyrie.org> and subject line Re: Bug#47438: Copyright Information (Debian Policy Manual) has caused the Debian Bug report #47438, regarding Update Policy copyright to be marked as done. This means that you claim

Re: RFC: draft text for Policy sprint at DebCamp

Sean Whitton writes: > I just created this page: > Please review the text. How can we build momentum and excitement for > this sprint? It could be of huge benefit to Policy, and Debian more > broadly. Backlogs and outdated docs kill motivati

Re: Proposal: move forward to Sphinx

Sean Whitton writes: > Thank you for these links. > Are you aware that the transition to docbook was only completed about > one month ago? I am not sure there is the energy to attempt another > complete transition of the manual, once again invalidating all submitted > patches. > (Sorry to be o

Re: Proposal: move forward to Sphinx

Hideki Yamane writes: > I want to discuss with you about making policy doc much modern > with Sphinx. > Here's my opinion and PoC > > https://www.slideshare.net/henrich_d/challenge-convert-policy-doc-from-docbook-to-sphinx-77172587 > > and sample output with Sphinx > http://www.ma-aya.t

Bug#865713: Declaring a charset of UTF-8 for policy files

Stéphane Blondon writes: > pabs added such configuration few days ago for Apache configuration: > https://anonscm.debian.org/cgit/mirror/dsa-puppet.git/commit/?id=5bcf8431d6b375d211a29f9d2c338e4400332e1a > The reason is a bad display in some browser for UTF-8 encoded txt file. > The start of thi

debian-policy_4.0.0.3_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 24 Jun 2017 14:11:19 -0700 Source: debian-policy Binary: debian-policy Architecture: source all Version: 4.0.0.3 Distribution: unstable Urgency: medium Maintainer: Debian Policy List Changed-By: Russ Allbery Desc

Processing of debian-policy_4.0.0.3_amd64.changes

debian-policy_4.0.0.3_amd64.changes uploaded successfully to localhost along with the files: debian-policy_4.0.0.3.dsc debian-policy_4.0.0.3.tar.xz debian-policy_4.0.0.3_all.deb debian-policy_4.0.0.3_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian

Bug#865713: Declaring a charset of UTF-8 for policy files

Le 24/06/2017 à 20:44, Russ Allbery a écrit : > debian-www folks, is there a way to declare UTF-8 as the charset for all > the *.txt files that originate from the debian-policy package and are > served by www.debian.org? I can guarantee that all the text files shipped > as part of the Policy packa

Bug#865685: marked as done (debian-policy: typo in upgrading-checklist)

Your message dated Sat, 24 Jun 2017 21:49:22 + with message-id and subject line Bug#865685: fixed in debian-policy 4.0.0.3 has caused the Debian Bug report #865685, regarding debian-policy: typo in upgrading-checklist to be marked as done. This means that you claim that the problem has been d

Bug#865713: Please Start UTF-8 debian-policy Text Files with UTF-8 Signature

Russ Allbery writes: > I did a bit more research, and apparently this approach has become more > blessed again. I'm glad I looked it up! As of Unicode 5.0, the > standard explicitly recommended against doing this, but the latest > version of the standard is moderately positive about it (althoug

Processed: tagging 865685

Processing commands for cont...@bugs.debian.org: > tags 865685 + pending Bug #865685 [debian-policy] debian-policy: typo in upgrading-checklist Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 865685: http://bugs.debian.org/cgi-bin/bugreport.c

Re: Proposal: move forward to Sphinx

Dear Hideki, On Thu, Jun 22, 2017 at 08:23:58PM +0900, Hideki Yamane wrote: > Here's my opinion and PoC > > https://www.slideshare.net/henrich_d/challenge-convert-policy-doc-from-docbook-to-sphinx-77172587 > > and sample output with Sphinx > http://www.ma-aya.to/~henrich/debian/policy/ Tha

Bug#865713: Declaring a charset of UTF-8 for policy files

debian-www, not debian-web. Colin Watson writes: > On Fri, Jun 23, 2017 at 11:49:20PM -0700, Russ Allbery wrote: >> I'm still a bit dubious about this, since I don't believe editors and >> generators normally add it, but given how we generate the text versions >> of the documents, it's relativel

Bug#865769: Second data package including some machine-readable data

Package: debian-policy Version: 4.0.0.2 Severity: wishlist A discussion in #865720 got me thinking that there is some data maintained in Policy that would be useful to have in a machine-readable format. The things that have occurred to me so far are: - The list of registered virtual packages - T

Bug#865713: Declaring a charset of UTF-8 for policy files (was: Re: Bug#865713: Please Start UTF-8 debian-policy Text Files with UTF-8 Signature)

Colin Watson writes: > On Fri, Jun 23, 2017 at 11:49:20PM -0700, Russ Allbery wrote: >> I'm still a bit dubious about this, since I don't believe editors and >> generators normally add it, but given how we generate the text versions >> of the documents, it's relatively easy to add a leading BOM a

Bug#865713: Please Start UTF-8 debian-policy Text Files with UTF-8 Signature

Paul Hardy writes: > Alternatively, if convenient, you could convert the non-breaking space > characters to a plain space in that text file in a script. That will > avoid the problem until you need some other non-ASCII character in the > file other than non-breaking space. You could convert all

Bug#865713: Please Start UTF-8 debian-policy Text Files with UTF-8 Signature

On Sat, Jun 24, 2017 at 2:51 AM, Colin Watson wrote: > On Fri, Jun 23, 2017 at 11:49:20PM -0700, Russ Allbery wrote: >> I'm still a bit dubious about this, since I don't believe editors and >> generators normally add it, but given how we generate the text versions of >> the documents, it's relativ

Bug#865713: Please Start UTF-8 debian-policy Text Files with UTF-8 Signature

On Fri, Jun 23, 2017 at 11:49:20PM -0700, Russ Allbery wrote: > I'm still a bit dubious about this, since I don't believe editors and > generators normally add it, but given how we generate the text versions of > the documents, it's relatively easy to add a leading BOM and seems > harmless. I'll t