Wrong text encoding on "Outliners & Programming" page

Open
#311 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
html
Domain
web-dev

Research direction

Inspect the archived page at http://scripting.com/outlinersProgramming.html, starting with its HTTP headers and HTML source to determine where the text encoding is missing. The work is done when the quotation marks render correctly in current browsers without manually selecting Mac OS Roman encoding.

Written by the indexing model from the issue text.

Description

Hi Dave, I saw your post the other day linking to your page Outliners & Programming. Great read, thanks!

Small issue on that page: I noticed that the quotation marks in the phrase “the halceon days are yet to come.” do not render correctly in my browsers.

  • On Firefox (Mac), it renders as Òthe halceon days are yet to come.Ó
  • On Safari (Mac), it renders as �the halceon days are yet to come.�
    • If I manually switch Safari to use the Mac OS Roman text encoding, the quotes render correctly as “the halceon days are yet to come.”

It looks like neither the HTTP headers nor the HTML code specify the text encoding:

$ curl --head "http://scripting.com/outlinersProgramming.html"
HTTP/1.1 200 OK
Date: Tue, 27 Aug 2024 12:54:06 GMT
Content-Type: text/html
Content-Length: 18900
Server: AmazonS3
Last-Modified: Wed, 02 Jan 2013 00:05:59 GMT
ETag: "14eb000fc596155005eb9b6f68a86500"
…

PS: I realize that page is a part of an archived site and it might not be easy for you to fix this, but I thought I'd let you know. Feel free to disregard and close this issue.

Dominant language
HTML
Stars
134
Forks
10
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.