PrimalScript 2011 creates Unicode files by default. There are some exceptions, like XML files, which are created as UTF-8 files. While generally Unicode is the way to go with international characters and mixed languages and so forth there are some occasions where another encoding has to be used. Once you have a file opened in […]
Tag: Unicode
Code pages, batch files and localization
PrimalScript 2011 treats everything as Unicode files, so when you open an ASCII file it will be converted to Unicode and then converted back to ASCII when saving. Any conversion to and from Unicode requires a code page, which tells the converter which characters get converted to what. The default Windows code page is 1252 […]
PowerShell unable to run Unicode files without BOM
A recent change in PrimalScript’s packager converts all files packaged and executed to Unicode files. If your script is a standard ANSI file it will be converted to Unicode before being packaged. Under normal circumstances you should never see any problem arising from that process except for a little hiccup that we recently encountered. If […]