#247: Needless license warning on PublicDomain
+---
Reporter: guest |Owner:
Type: defect | Status: new
Priority: low|Milestone:
Component: Cab
On Sun, Feb 24, 2008 at 08:49:04PM +, Duncan Coutts wrote:
> On Sun, 2008-02-24 at 18:28 +, Ross Paterson wrote:
> > text/plain output (used by cabal upload) will need some work, though.
> > I'm not sure what the deal is with charset negotiation.
>
> Yeah, me neither. I know it's possible
On Sun, 2008-02-24 at 18:28 +, Ross Paterson wrote:
> On Sun, Feb 24, 2008 at 05:46:35PM +, Duncan Coutts wrote:
> > So what about hackage? It now has to assume the Strings in the package
> > description etc are proper Haskell Unicode Strings and convert to UFT8
> > output. Distribution.Si
On Sun, Feb 24, 2008 at 05:46:35PM +, Duncan Coutts wrote:
> So what about hackage? It now has to assume the Strings in the package
> description etc are proper Haskell Unicode Strings and convert to UFT8
> output. Distribution.Simple.Utils exports toUTF8 for this purpose.
XHTML output should
Sun Feb 24 10:00:38 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Convert to using readTextFile as appropriate
Added readBinaryFile for on use (uploading .tar.gz files)
Remove readURI as it was not being used.
M ./Hackage/Config.hs -4 +4
M ./Hackage/Fetch.hs -12
M ./Hackage/Uploa
Sun Feb 24 09:55:24 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Switch all file read/writes and process output to use UTF8
Added readTextFile and writeTextFile which use UTF8. rawSystemStdout now
assumes the programs are producing output in UTF8 encoding.
M ./Distribution/PackageDescri
On Sun, 2008-02-24 at 14:44 +, Ross Paterson wrote:
> On Sat, Feb 23, 2008 at 10:49:59AM -0800, Duncan Coutts wrote:
> > Sat Feb 23 10:40:25 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
> > * First pass at parsing .cabal files as UTF8
> > Also print output and error messages etc in UTF8.
>
On Sat, Feb 23, 2008 at 10:49:59AM -0800, Duncan Coutts wrote:
> Sat Feb 23 10:40:25 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
> * First pass at parsing .cabal files as UTF8
> Also print output and error messages etc in UTF8.
On the input side, wouldn't it be better to do this on the boundar
