mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-26 01:26:00 +03:00
[GH-ISSUE #1077] Bug: Chrome headless HTML snapshots mangle unicode during saving despite <meta charset="utf-8"> header #3694
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#3694
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @llagerlof on GitHub (Jan 3, 2023).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1077
Describe the bug
Accented characters are being incorrectly decoded in DOM viewer. The singlefile viewer is working fine.
Steps to reproduce
In web interface add some URL where its contents should have accented characters, like this one:
https://www.band.uol.com.br/bandnews-fm/rio-de-janeiro/noticias/prefeitura-divulga-aumento-de-passagens-em-transportes-publicos-municipais-16572221Open the DOM viewer in web interface.
Accents are screwed.
Screenshots or log output
URL accessed directly:

Archived URL:

ArchiveBox version
@pirate commented on GitHub (Jan 4, 2023):
That page has a
<meta charset="utf-8">header which should be present in the archived version as well, can you post the top part of youroutput.htmlfile for that snapshot so we can make sure it has<meta charset="utf-8">at the top too?@llagerlof commented on GitHub (Jan 5, 2023):
Here is the beginning of
output.html.meta charsetis defined before the<title>.Looking at the
<title>text, I realized the utf-8 accents were destroyed, probably in the process of converting the original source tooutput.html.Maybe the title of this issue should change again. :-)
@pirate commented on GitHub (Jan 5, 2023):
Ah thanks, thats strange. Maybe we're missing some magic incantation of chrome headless CLI flags to get it to write unicode properly during
archive.save_dom.@llagerlof commented on GitHub (Jan 5, 2023):
Does the singlefile is generated the same way? Because accents are fine there.
@pirate commented on GitHub (Jan 6, 2023):
No, SingleFile uses an entirely different tool and process.