Edgewall Software

Ticket #1466 (closed defect: fixed)

Opened 3 years ago

Last modified 2 years ago

Missed charset detection in mimeviewer enscript.py

Reported by: vyt@… Owned by: cboos
Priority: normal Milestone: 0.10
Component: version control/browser Version: devel
Severity: normal Keywords: unicode utf-8 enscript
Cc: vyt@…

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

Change History

Changed 3 years ago by cmlenz

  • milestone set to 0.9.1

Changed 3 years ago by cmlenz

  • milestone changed from 0.9.1 to 0.9.2

Changed 3 years ago by cmlenz

  • milestone changed from 0.9.3 to 0.9.4

Changed 2 years ago by cmlenz

  • milestone changed from 0.9.4 to 0.10

Bah, enscript doesn't even support UTF-8:

http://www.tldp.org/HOWTO/Unicode-HOWTO-5.html

So we'd have to transcode to Latin1 first… postponing this.

Changed 2 years ago by cboos

  • keywords unicode utf-8 enscript added
  • owner changed from jonas to cboos

I'll try to perform some tests to see how enscript behaves with r3092...

Changed 2 years ago by cboos

This makes me think that the charset information about the source, when available, should be conveyed to the converter.

Changed 2 years ago by jonas

  • status changed from new to closed
  • resolution set to fixed

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.

Add/Change #1466 (Missed charset detection in mimeviewer enscript.py)

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.