Changes between Version 1 and Version 2 of SourceEncodingDetection


Ignore:
Timestamp:
Apr 25, 2006 3:24:37 PM (9 years ago)
Author:
autrijus@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SourceEncodingDetection

    v1 v2  
    44== Brief Explanation == 
    55 
    6 Haskell source code uses the Unicode character set.  However, current implementations either support only one encoding (e.g. UTF-8), or require the encoding to be signified via out-of-band means, which makes Haskell source code non-portable. 
     6Haskell source code uses the Unicode character set.  However, current implementations either support only one encoding (e.g. UTF-8), or require the encoding to be signified via out-of-band means, which makes Haskell source code outside ASCII range non-portable. 
    77 
    88This proposal outlines a detection heuristics that categorizes the source code as under UTF-8, UTF-16 or UTF-32.  A conforming Haskell-prime implementation must accept UTF-8 and UTF-16, and may fail on UTF-32 input. 
     
    6666== Pros == 
    6767 * Ensures uniform treatment of Unicode in source code. 
     68 * Disallows implicit ISO-8859-* encodings in source code, ensuring portability. 
    6869 
    6970== Cons == 
    7071 * Mandating a minimum support for UTF-8/UTF-16 places an implementation burden on compiler writers. 
     72 * Existing code relying on a non-UTF8, locale-/implementation-specific encoding will need conversion.