Opened 15 years ago
Closed 15 years ago
#410 closed defect (fixed)
scriptindex aborts with "Unknown Exception"
| Reported by: | wb | Owned by: | Olly Betts |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.0.18 |
| Component: | Omega | Version: | 1.0.17 |
| Severity: | normal | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Operating System: | All |
Description
scriptindex aborts with "Unknown Exception" when trying to "unhtml" XSLT files containing a template embedding the line "<meta HTTP-EQUIV="Content-Type" content="text/html; charset=utf-8">". After removing this line scriptindex succeeds.
As usual the 1st line of the affected XSLT files contain also their own encoding declaration "<?xml version="1.0" encoding="UTF-8" ?>".
Attachments (3)
Change History (7)
comment:1 by , 15 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
comment:2 by , 15 years ago
| Resolution: | worksforme |
|---|---|
| Status: | closed → reopened |
| Version: | 1.0.11 → 1.0.17 |
The uploaded file bug410-2.dump is a sample for the XSLT files still triggering the exception (now with Xapian 1.0.17) at our site.
comment:3 by , 15 years ago
| Milestone: | → 1.0.18 |
|---|---|
| Operating System: | Linux → All |
Thanks. The issue is that we end parsing (due to </body> on a document where the character set was specified in the body).
Fixed in trunk r13720. Marking for backport for 1.0.18.
comment:4 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Fixed in 1.0 branch r13725.
Works for me with Xapian 1.0.16 - I'll attach the example files I used. Command was:
If you're able to reproduce this with 1.0.16, please attach a small example which fails, and reopen this ticket.