Logged In: YES
The Google translator couldn't decipher this.
Logged In: YES
check the encoding when open. if unicode then use unicode to display,if not,use the default encoding of OS.
When open the file,Determine whether the coding for unicode,if so, to display the text use of unicode,Otherwise,use the default encoding of the system
SciTE currently checks the file for a Unicode BOM and if present opens the file in the correct Unicode mode. If there is no BOM, it checks the start of the file for a Unicode coding cookie and if present will open the code in UTF-8 mode.
For English, this is not a problem.But,for Chinese or Japanese, this is a problem. When "
code.page=65001" ,I Open the a non-unicode file,Garbled! "code.page=932" can solve the problem.
Does it work for you now?
People have to change the configuration file when they open files of different encoding,I just feel that is trouble.I hope that this process is automated.I do not mean that Scite can automatically change the configuration file but to accord with their own encoding of file to display.
Web Browser and notepad on this point done a good job.
Automated encoding determination is inaccurate. If a good implementation is offered then it could go in as an option. Most programs are written in a single encoding so can set the encoding as wanted on a directory or project basis.
Can use a script to determine encoding with command.discover.properties.
Log in to post a comment.