#5553 closed defect (fixed)

Single Page HTML Manual is encoded in ISO-8859-1

Reported by: chrism Owned by: pramsey
Priority: medium Milestone: PostGIS 3.5.0
Component: documentation Version: master
Keywords: Cc:

Description

This is OK when opening as a file in a browser, although it in theory it restricts the characters that could be used, but a problem if accessing from a web server that is configured to mark all content as UTF-8.

It's a limitation of the DocBook XSL, switching to HTML5 resolves this and avoids the legacy HTML.

Suggested implementation: https://github.com/postgis/postgis/pull/743

Change History (8)

comment:1 by strk, 15 months ago

I've pushed an html5 branch to see if bots are happy with it

comment:2 by Sandro Santilli <strk@…>, 15 months ago

Resolution: fixed
Status: newclosed

In 40502f8/git:

Publish the manual in HTML5

This enables the single page manual to be encoded in UTF-8 instead of
ISO-8859-1, and allows browsers to process the pages without resorting
to quirks mode.

Closes #5553

comment:3 by robe, 15 months ago

Component: postgisdocumentation

comment:4 by strk, 15 months ago

This change resulted in Debbie's built documentation being corrupted, see #5559

comment:5 by strk, 15 months ago

Resolution: fixed
Status: closedreopened

We need to use a stylesheet customization layer to do utf8, see http://www.sagehill.net/docbookxsl/OutputEncoding.html

I'm reopening this ticket as I plan to revert the commit closing it

comment:6 by robe, 15 months ago

Version: 3.4.xmaster

comment:7 by robe, 15 months ago

The single page ones seem to be fine I think, but date reads Friday which seems wrong since I regenerated.

https://postgis.net/docs/manual-3.5/postgis-en.html

The hash looks right c65bbfb that is the last commit in master

Version 1, edited 15 months ago by robe (previous) (next) (diff)

comment:8 by strk, 15 months ago

Resolution: fixed
Status: reopenedclosed

I guess we can re-close this until otherwise proved this was the cause of failure. Locally I don't see a problem with rendering the xhtml generated after this change.

Let's continue the discussion in #5559

Note: See TracTickets for help on using tickets.