#736 SciTE properties files should use UTF-8 encoding (+BOM)

Won't_Implement
open
SciTE (235)
2
2010-11-01
2010-11-01
redstun
No

I'm using SciTE 2.22 on Windows, the properties files seem to be encoded in Windows-1252, which SciTE does not have built-in support.

The consequence, in case code.page=65001 insdead of 0, the file SciTEGlobal.properties cannot be displayed correctly, specifically, it's the following line
chars.accented=...

Since SciTE has built-in support for As UTF-8, with or without BOM, It's better to encode the properties files in UTF-8 with BOM, so that they can be displayed correctly regardless current code.page

Discussion

  • Neil Hodgson

    Neil Hodgson - 2010-11-01
    • assigned_to: nobody --> nyamatongwe
    • priority: 5 --> 2
    • milestone: --> Won't_Implement
     
  • Neil Hodgson

    Neil Hodgson - 2010-11-01

    Some settings, such as chars.alpha, are a string of arbitrary bytes and so may not be valid UTF-8. Therefore, SciTE does not specify a fixed encoding for .properties files.

     
  • redstun

    redstun - 2010-11-01

    Ah, interesting to know that chars.alpha is a string of arbitrary bytes.

    But actually in default SciTEGlobal.properties. it's the following
    chars.alpha=abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ

    What I see is that all the chars in chars.alpha are pretty valid, plain old alpha,

    Therefore, may I ask they're treated that why? shouldn't it be true that regardless the in-memory presentation, they always end up to be treated as characters?

    Thanks

     
  • Neil Hodgson

    Neil Hodgson - 2010-11-03

    The implementation was simple and worked well for single byte character sets.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks