21 December 2009
[Click to cite this article]
[hide academic citations]
AMA citation:
Jiang W. svn: Can’t convert string from ‘UTF-8′ to native encoding:. Stone Studio. 2009. Available at: http://wei-jiang.com/system/unix/svn-cant-convert-string-from-utf-8-to-native-encoding. Accessed September 6, 2010.
APA citation:
Jiang, Wei. (2009). svn: Can’t convert string from ‘UTF-8′ to native encoding:. Retrieved September 6, 2010, from Stone Studio Web site, http://wei-jiang.com/system/unix/svn-cant-convert-string-from-utf-8-to-native-encoding
Chicago citation:
Jiang, Wei, "svn: Can’t convert string from ‘UTF-8′ to native encoding:", Stone Studio, posted December 21, 2009, http://wei-jiang.com/system/unix/svn-cant-convert-string-from-utf-8-to-native-encoding (accessed September 6, 2010).
Harvard citation:
Jiang, W 2009, svn: Can’t convert string from ‘UTF-8′ to native encoding:, Stone Studio. Retrieved September 6, 2010, from <http://wei-jiang.com/system/unix/svn-cant-convert-string-from-utf-8-to-native-encoding>
MLA citation:
Jiang, Wei. "svn: Can’t convert string from ‘UTF-8′ to native encoding:." Stone Studio. 21 Dec. 2009. 6 Sep. 2010 <http://wei-jiang.com/system/unix/svn-cant-convert-string-from-utf-8-to-native-encoding>
Thank you for your interest.
Filenames containing "special characters" can cause an annoying Subversion error message:
svn: Can't convert string from 'UTF-8' to native encoding:
From the subversion book:
Errors like this typically occur when the Subversion client has received a UTF-8 string from the repository, but not all of the characters in that string can be represented using the encoding of the current locale. For example, if your locale is en_US but a collaborator has committed a Japanese filename, you’re likely to see this error when you receive the file during an svn update.
To fix this error message you have to set your current locale appropriately:
export LC_CTYPE=en_US.UTF-8
locale
svn update