Modify ↓
Opened 19 years ago
Closed 18 years ago
#1466 closed defect (fixed)
Missed charset detection in mimeviewer enscript.py
| Reported by: | Owned by: | Christian Boos | |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.10 |
| Component: | version control/browser | Version: | devel |
| Severity: | normal | Keywords: | unicode utf-8 enscript |
| Cc: | vyt@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I use trac trunk from 22 april 2005.
Please, add charset detection for file content and pass it with enscript parameter "—encoding=".
PS I think that charset detection should be common code for all trac components.
Attachments (0)
Change History (7)
comment:1 by , 18 years ago
| Milestone: | → 0.9.1 |
|---|
comment:2 by , 18 years ago
| Milestone: | 0.9.1 → 0.9.2 |
|---|
comment:3 by , 18 years ago
| Milestone: | 0.9.3 → 0.9.4 |
|---|
comment:4 by , 18 years ago
| Milestone: | 0.9.4 → 0.10 |
|---|
comment:5 by , 18 years ago
| Keywords: | unicode utf-8 enscript added |
|---|---|
| Owner: | changed from to |
I'll try to perform some tests to see how enscript behaves with r3092…
comment:6 by , 18 years ago
This makes me think that the charset information about the source, when available, should be conveyed to the converter.
comment:7 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
cmlenz, I think the part about enscript not supporting utf-8 only applies when generating postscript output…
As far as I can tell enscript-previews works just fine with utf-8 now, so I'm closing this ticket.
Note:
See TracTickets
for help on using tickets.
Bah, enscript doesn't even support UTF-8:
So we'd have to transcode to Latin1 first… postponing this.