Menu

#623 Encoding names don't match IANA versions

open
5
2012-07-13
2012-07-13
Talvo
No

The encoding names used in Tcl (as returned by [encoding names]) don't match the official IANA encoding names - for instance, Tcl uses iso8859-1 while the IANA name is iso-8859-1. I'm not sure whether this is actually a bug or there's a good reason for it that I'm not aware of, but it makes attempting to match encoding names against those given by most real-world applications - for example, the charset used by web servers - a pain. (It's not too hard to work around, but the fact you need to know every charset which has the 'wrong' name, and which it should map to, is problematical.)

Discussion

  • Jan Nijtmans

    Jan Nijtmans - 2012-07-13

    Java made the same change:
    <http://www.websina.com/bugzero/kb/java-encoding-charset.html>

     
  • Jan Nijtmans

    Jan Nijtmans - 2012-07-13
    • labels: 104246 -->
     
  • Jan Nijtmans

    Jan Nijtmans - 2012-07-13
    • labels: --> 16. Commands A-H
     
  • Donal K. Fellows

    This was meant to be the focus of the dkf-alias-encoding branch, but it's been a bit sidelined for the past few months.

     
  • Donal K. Fellows

    • assigned_to: nobody --> dkf
     
  • Don Porter

    Don Porter - 2012-07-16

    Dup of 1374695 ?

     
  • Talvo

    Talvo - 2012-07-16

    Does seem to be a duplicate, yeah - I must've missed that when I searched before adding this one, sorry.

     
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.