close Warning: Error with navigation contributor "AccountModule"

Changes between Version 3 and Version 4 of CharacterEncoding


Ignore:
Timestamp:
Jan 12, 2008, 5:02:39 PM (10 years ago)
Author:
chris
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CharacterEncoding

    v3 v4  
    3838Windows, however, does not have a default encoding. The encoding used will depend on the language that you select in Windows and a number of other system properties. In their infinite wisdom, Microsoft have chosen a different solution to this problem, which is to use [http://en.wikipedia.org/wiki/UTF-16 UTF-16] encoding instead, whose characters use 16 bits instead of 8. Because of that, Box Backup would require a major redesign to support these native characters properly, and that has not happened yet.
    3939
    40 What we actually do works well most of the time. We try to read native file names in UTF-16 everywhere and convert them to UTF-8. Most of Box Backup uses UTF-8 internally on Windows. We also convert messages sent to the Windows Event Log back to UTF-16, so you should see to correct characters there. However, Box Backup is a console application and the console does not properly support UTF-16. So Box Backup's console messages, and console tools such as `bbackupquery`, may still display characters incorrectly.
     40What we actually do (on Windows) works well most of the time. We try to read native file names in UTF-16 everywhere and convert them to UTF-8. Most of Box Backup uses UTF-8 internally on Windows. We also convert messages sent to the Windows Event Log back to UTF-16, so you should see to correct characters there. However, Box Backup is a console application and the console does not properly support UTF-16. So Box Backup's console messages, and console tools such as `bbackupquery`, may still display characters incorrectly.
    4141
    4242We never convert file contents. That is your responsibility. We provide a faithful backup of the 8-bit binary data contained in each file.