|
#1
|
|||
|
|||
Unicode in build script
Hi,
I looked at a build script containing accented characters using UltraEdit. It seems VBP will use Unicode in portions of the build script as required, but not the entire .bld file. I tested converting the whole .bld to Unicode and VBP reads it fine, even a Save As will keep the whole script in Unicode. Is my understanding of the behavior correct? Shouldn't the tool save completely in Unicode? or offer the option to use Unicode to save the .bld? |
#2
|
|||
|
|||
VBP saves .bld files in UTF-8 [1] encoding (but without a byte order mark [BOM]). Most text editors provide a way to change how they process non-BOM files (to use UTF-8 instead of ANSI or the system code page) or to explicitly specify UTF-8 when opening a file. VBP is also capable of loading UTF-16 [2]encoded .bld files, but it always saves them as UTF-8.
UTF-8 and UTF-16 are two different ways to store (encode) Unicode text, so .bld files are completely Unicode [3]. [1] http://www.faqs.org/rfcs/rfc3629.html [2] http://www.faqs.org/rfcs/rfc2781.html [3] http://www.unicode.org/faq/basic_q.html#19 |
|
|