Differences between version 25 and previous revision of UnicodeNotes.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 25 | Last edited on Monday, January 15, 2007 11:46:33 pm | by JohnMcPherson | Revert |
| Older page: | version 24 | Last edited on Thursday, December 28, 2006 4:57:31 am | by JohnMcPherson | Revert |
@@ -171,7 +171,9 @@
</verbatim>
fixed my problem. Thanks to [the Unicode/charsets section of the Samba HOWTO|http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/unicode.html].
-For the "opposite" problem --- that is, you have a windows machine with a share that is samba-mounted onto a linux client, and the non-ascii characters are getting munged --- you need to give samba some mount options: <tt>iocharset=utf-8
</tt> tells samba to use a utf-8 encoding when presenting filenames to linux applications, and <tt>codepage=<i>foo</i></tt> tells samba which encoding the windows machine is using. If your accents are getting screwed up, try <tt>codepage=850</tt>.
+For the "opposite" problem --- that is, you have a windows machine with a share that is samba-mounted onto a linux client, and the non-ascii characters are getting munged --- you need to give samba some mount options: <tt>iocharset=utf8
</tt> tells samba to use a utf-8 encoding when presenting filenames to linux applications, and <tt>codepage=<i>foo</i></tt> tells samba which encoding the windows machine is using. If your accents are getting screwed up, try <tt>codepage=850</tt>.
+eg:
+ smbmount //servername/sharename /mnt/point -o codepage=cp850,iocharset=utf8,password=$p
----
CategoryNotes
