similar to: Rsync and filename codepages

Hi all, I am trying to get samba to work on my system with Japanese character, and I am really stuck. can anyone help me please? first of all, i only see the codepage.932 which i want to use is 8bytes, is this right file size of this file?.. i issued the command make_smbcodepage c /usr/local/samba/source/codepages/codepage_def.932 /etc/codepage.932 and that's what I got. and i also see the

On a FC2 system (which includes kernel 2.6.5 and samba-3.0.3), I am able to use "smbmount" to mount filesystems with japanese filenames on them by specifying codepage=cp932. But when I mount with "mount.cifs" the translation from SJIS to UTF-8 isn't done right: # uname -a Linux 5nave 2.6.5-1.358 #1 Sat May 8 09:04:50 EDT 2004 i686 i686 i386 GNU/Linux # smbclient

Marvin_Arnold wrote: > > Charles Davis wrote: > > James McKenzie wrote: > > > > > vitamin wrote: > > > > > > > James McKenzie wrote: > > > > > > > > > > > > > I do think this is doable, but the appropriate variables have to be set before running Wine, just like you do in Linux (or any other UNIX for that

Hi guys, I've got a question about the API mkchar(). I have met some difficulty in parsing utf-8 string to mkchar() in R-2.7.0. I was intending to parse an utf-8 string str_jan (some Japanese characters such as?, whose utf-8 code is E381B5) to R API SEXP mkChar(const char *name) , we only need to create the SEXP using the string that we parsed. Unfortunately, I found when parsing the

Hello, I have problem that menus on windows soft under wine are garbled (mojibake.) I'm Japanese and I've just started to use wine under CentOS5 because I want to use English-Japanese dictionary viewing software. Installing wine is fine both English and Japanese locale where wine related soft displays Japanese correctly even on menus. But my dictionary viewing soft under wine has

hello Samba codepagers ... I have a linux server for XP pro and Win9x stations. I am migrating the server from RedHat9 (samba 2.2.7a) to Mandrake 10 (samba 3.0.2a) The problem : The french accents and the case options of the filenames are no longer recognized by the WinXP Pro Stations. (preserve case = no, default case = low ...) i tried a lot of CHARSET but it did nothing samba 3 seems

Background link for those unfamiliar: http://www.debian.or.jp/~kubota/unicode-symbols.html W3's suggestions for within XML: http://www.w3.org/TR/japanese-xml/ The nice thing about this document is it gives data for a bunch of different translation tables, and enumerates their differences. (This is only about Japanese encodings. I believe similar problems may exist for Chinese and Korean;

Hi list! I've been using Samba (as packaged in Debian) for years without any charset conversion issus, but now one bit me: Server: Samba 3.0.23d-2 (Debian testing), system locale en_US.UTF-8, no charset options in smb.conf specified Client-DE: MS Windows XP Pro SP2 German, locale for non-Unicode apps set to German / Austria Client-JP: MS Windows XP Pro SP2 German, locale for non-Unicode

Hello, I am trying to get rsync-3.0.0pre10 --iconv option working between two linux hosts in local network. The client host is running Fedora Core 4 (kernel 2.6.17) and is using iso8859-1 character set. LANG=en_US The daemon host is running Centos 5 (kernel 2.6.18) and is using utf-8 character set. LANG=en_US.UTF-8 Rsync is transferring files properly without --iconv switch: fc4: (connected

Hi, I would like to know how to enable samba to use the same user/passwords that those that exists in the linux machine. Best regards, Nestor Mata Cuthbert

Hello, Does anyone know anything at all about codepages and characters sets? I really need some help but no one seems interested in my post. Regards, Tom Thomas Robinson Ehbas Ltd T: 01273 234 665 F: 01273 704 499

Hi there, I just got a new machine with Redhat Enterprise Workstation and samba 3.0.0-14 pre-installed. I am trying to connect it to my existing network which has a redhat v8 samba v2 PDC controlling 16 or so win2k and winxp machines. In the nmbd log I get this error 3 times every 5 seconds or so: nmbd/nmbd_packets.c:process_nmb_request(1448) process_nmb_request: Multihomed registration

szcathay@public.szonline.net wrote: > > Hello, everyone. Could you help me to solve the problems? > > Recently I downloaded samba-2.0.4b souce and after I compiled it, I used it > as > a replace of samba-1.9.18p8. > The smb.conf file was used as before. But there are two problems to me. > 1)When I used samba-1.9.18p8, the Windows NT4.0(sp3) workstation can browse > the

Multilingual Rails v0.6 is released! Here is the changelog. Documentation and download at the homepage: http://www.tuxsoft.se/oss/rails/multilingual v0.6 - 2005-08-13 * String case-manipulation functions replaced with ruby-unicode equivalents (if ruby-unicode is installed): String#downcase, String#upcase and String#capitalize now fully handle Unicode. * String normalization

All, As some of you know, Jeroen has added support for Unicode strings in the unstable development version of FOX (version 1.5). I''m trying to plan ahead to decide how best to support this for FXRuby 1.6, but I don''t really know anything about Ruby''s support for Unicode or i18n in general. If you''re familiar with this topic (how/if Ruby deals with Unicode

Hi there, I have searched the rsync website, as well as an extensive search on google, but have been unable to come up with a definitive answer regarding whether rsync will synchronise files and directories which have Japanese characters in them. I am using an English language version of Linux, which has some directories shared via samba. Both English and Japanese language windows clients

Hello, everyone. Could you help me to solve the problems? Recently I downloaded samba-2.0.4b souce and after I compiled it, I used it as a replace of samba-1.9.18p8. The smb.conf file was used as before. But there are two problems to me. 1)When I used samba-1.9.18p8, the Windows NT4.0(sp3) workstation can browse the share names of Japanese SJIS, but now I couldn't access the shares because

I have to upgrade a 2.2.8a (Debian) installation to 3.0.14a (Debian too). I have quite everything clear but I am afraid I will get into trouble with the filename encoding on disk. The current samba installation has no explicit codepage declared for the file system, and running "testparm" gives only these settings (which are default) for codepages and charsets:

Full_Name: Ei-ji Nakama Version: R-2.5.0 OS: any Submission from: (NULL) (219.117.236.5) problem by operation of gsub in the locale of CP932 and SJIS. The inconvenient character code which used 0x5c after the first byte. --- R-2.5.0.orig/src/main/character.c 2007-04-03 11:05:05.000000000 +0900 +++ R-2.5.0/src/main/character.c 2007-06-24 22:31:06.000000000 +0900 @@ -986,6 +986,17 @@

Hi all! I'm REALLY depressed! After moving from samba 2.2.8 to 3.0.4 I can not read my files. All names are corrupted. I used NO charset options in the original (2.2.8) smb.conf (which means that all names are in cp850, doesn't it ?) No I have installed 3.0.4, libiconv also. But can not figure out what to set in smb.conf. I use Solaris 8, LC_CTYPE=ru_RU.KOI8-R. And windows XP/2000