#388 encodings

Completed
closed
Neil Hodgson
SciTE (231)
3
2011-11-02
2006-11-30
Holger Jakobs
No

SciTE recognises some kind of "cookie" like
# -*- coding: utf-8 -*-
telling that a specific file is encoded in UTF-8. So far, so good.

In case of XML files, mentioning the encoding in the XML declaration is also recognised:
<?xml version='1.0' encoding='utf-8'?>
Actually, as long as no other encoding is declard, the XML standard says the encoding has to be UTF-8. SciTE fails to obey to this rule.

It would also be best if SciTE took the encoding of all text files from the variable LANG existing at least in most Unix versions.

LANG=en_CA.UTF-8
clearly tells that the standard encoding is UTF-8, so there is no reason to use any 8-bit-encoding then.

At least there should be a way of making all new files (which of course cannot already have the above mentioned "cookie") to use UTF-8. I have not been able to find anything suitable for the properties files. Setting code.page=65001
had no effect.

Regards,
Holger
holger@jakobs.com

Discussion

  • Neil Hodgson
    Neil Hodgson
    2006-12-01

    • priority: 5 --> 3
    • assigned_to: nobody --> nyamatongwe
     
  • Neil Hodgson
    Neil Hodgson
    2006-12-01

    Logged In: YES
    user_id=12579
    Originator: NO

    The environment encoding is often different from the encoding used for source files. Many have an environment set for UTF-8 only because that is now the default for most Linux distributions but have existing files in a local encoding like ISO-8859-1. Switching encodings on these users will cause failures for them so will have to be an option that defaults to off. code.page=65001 works for me.

     
  • Neil Hodgson
    Neil Hodgson
    2011-11-02

    • milestone: --> Completed
    • status: open --> closed
     
  • Neil Hodgson
    Neil Hodgson
    2011-11-02

    Can use command.discover.properties.