search for: sjis

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 @@ char *p = repl; n = strlen(repl) - (regmatch...

...; > What did you use? If you tacked on a .utf8, then of course it didn't > > work! On Mac OS, you have to put a dash between the "UTF" and the "8": > > ja_JP.UTF-8. (Or you can type ja_JP.utf-8.) And if you want Shift-JIS, > > then you need to tack on a .SJIS: ja_JP.SJIS. > > > > Chip > > > > > > > > James McKenzie > > > > > > > > > > > Charles, that did the trick! (LANG=ja_JP.SJIS) My wine now talks Japanese! > > Thank you very much! > B?LhFT?D~YH > > M:A: S...

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

...Public/MAPPINGS/OBSOLETE/EASTASIA/, as well. We can't mandate the use of a specific table. That's just too burdonsome for programmers. It's reasonable to suggest them, however. The major example is CP932: MS's version of Shift-JIS. Windows' conversion functions will convert SJIS 0x5C (yen symbol) to U+005C (backslash, aka REVERSE SOLIDUS.) This is for compatibility with things like filenames and C escapes; Japanese Windows systems use yen symbols for those. We don't have that compatibility problem; Ogg tags (and probably metadata, too) are best off converting SJIS 0x...

...68 /usr/lib/R/library/stats/libs/stats.so 00339000-00352000 r-xp 00000000 fd:00 15959326 /usr/lib/R/modules/R_X11.so 00352000-00353000 rwxp 00018000 fd:00 15959326 /usr/lib/R/modules/R_X11.so 00353000-0035f000 rwxp 00353000 00:00 0 00480000-00496000 r-xp 00000000 fd:00 15303387 /usr/lib/gconv/SJIS.so 00496000-00498000 rwxp 00015000 fd:00 15303387 /usr/lib/gconv/SJIS.so 0056e000-00598000 r-xp 00000000 fd:00 16452204 /usr/lib/R/lib/libRblas.so 00598000-00599000 rwxp 00029000 fd:00 16452204 /usr/lib/R/lib/libRblas.so 00848000-00851000 r-xp 00000000 fd:00 15204401 /lib/libnss_files-2.4.s...

...68 /usr/lib/R/library/stats/libs/stats.so 00339000-00352000 r-xp 00000000 fd:00 15959326 /usr/lib/R/modules/R_X11.so 00352000-00353000 rwxp 00018000 fd:00 15959326 /usr/lib/R/modules/R_X11.so 00353000-0035f000 rwxp 00353000 00:00 0 00480000-00496000 r-xp 00000000 fd:00 15303387 /usr/lib/gconv/SJIS.so 00496000-00498000 rwxp 00015000 fd:00 15303387 /usr/lib/gconv/SJIS.so 0056e000-00598000 r-xp 00000000 fd:00 16452204 /usr/lib/R/lib/libRblas.so 00598000-00599000 rwxp 00029000 fd:00 16452204 /usr/lib/R/lib/libRblas.so 00848000-00851000 r-xp 00000000 fd:00 15204401 /lib/libnss_files-2.4.s...

...userenv<elf>" a lot lines or somthing. And I also don't know how to change language enviornment without controll panel, maybe some registory key? If someone know how to display multi byte character menus on widget, could you tell me a direction. I tested locales ja_JP.eucjp, ja_JP.sjis and ja_JP.utf8 when start wine. Thanks in advance. Akihiro Moriguchi

...de on linux (redhat 8) and I am running cygwin (latest version) on a mixture of win2k and winxp machines for Japanese users. When I Rsync from windows rsync complains about a no. of Japanese filenames (not all of them) and this is due, as far as I can work out, to incompatibilities/clashes between SJIS filename encoding (which Windows uses) and certain character sequences in linux filenames that are invalid. So I'd like to switch linux to be using UTF-8, does Rsync use the locale/LANG settings to convert filenames? Maybe I need to patch it and merge in a version of the useful linux util &qu...

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 --version Version 3.0.3-5 # mount.cifs --version mount.cifs version: 1.2 # # smbmount //my-server/share /mnt/my-server -o codepage=cp932 Password...

...to -E write messages to stderr instead of stdout -U username set the network username -W workgroup set the workgroup name -c command string execute semicolon separated commands -t terminal code terminal i/o code {sjis|euc|jis7|jis8|junet|hex} -D directory start from directory Perhaps there is something else I need to do? Again, the old smbmount works perfectly every time with: smbmount //server/share /mnt/samba-share -c CLIENT -U user -P passwd \ -u nobody -g nobody -f 666 -d 777 thanks, -b...

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

...gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets $(MAKE)... yes checking "character sets"... default: latin1, collation: latin1_swedish_ci; compiled in: latin1 latin1 utf8 big5 cp1250 cp932 eucjpms euckr gb2312 gbk latin1 latin2 sjis tis620 ucs2 ujis utf8 checking whether to compile national Unicode collations... yes checking whether build environment is sane... yes checking whether make sets $(MAKE)... (cached) yes checking for gawk... (cached) awk checking for gcc... /usr/bin/gcc-4.0 checking for C compiler default output fil...

I am running samba version 1.9.18p4 on a sinix machine (unix svr4). My NT workstations use the german code page 850. In earlier versions of samba (1.9.17p2) the character mapping worked just fine, using character set = iso8859-1 client code page = 850 in my smb.conf. Since upgrading to samba 1.9.18p4 this don't work any more. Is this a known problem? I tripple-checked my smb.conf entries,

Hi! updated to p4 the other day, and now the "character set = iso8859-1" option doesn't work anymore. I didn't change anything in the smb.conf file but this: unix password sync = True time server = yes and it worked in 1.9.18p3 :/ Has anyone else seen this? Samba runs on FreeBSD 2.2.6 from the ports collection. (I don't think that password sync works for this

Hallo you, I previously worked with Samba 2.0.4b (with SuSE Linux 6.1) and have a Windows NT 4.0 Server as PDC in my Domain. I set the security level to DOMAIN in samba.cfg. Now I upgraded the version of Samba to 2.0.5 an the security level DOMAIN doesn't work anymore. Everytime I try to reach a share of my Samba server, he asks me for a username and password. So I set

...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 the names appeared to be unreadable by Japanese Windows NT 4.0 in spite of the "client code page = 932" was set in smb.conf. The strange thing is that Windows 95 can access the shares which contains Japanese Characters. 2)To avoid the abov...

...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 > the names appeared to be unreadable by Japanese Windows NT 4.0 in spite of > the "client code page = 932" was set in smb.conf. The strange thing is that > Windows 95 can access the shares which contains Japanese Characters....

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

...n 1.7.1 and 1.8.0 in ActionMailer... mail.body = NKF.nkf(''-Sj -m0'', mail.quoted_body) # sigh. Notifications.deliver(mail) class Notifications < ActionMailer::Base @@default_charset = "iso-2022-jp" @@encode_subject = false # and set Ruby option -Ks (Kcode is SJIS). # uses Base64 encoding (default in TMail). def invoice(sent_on = Time.now, options = {}) @subject = "in Japanese ..." @body = options @recipients = ''rcpt-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org'' @from = ''from-hcDgGtZH8xNBDgjK...

Nicholas: Regarding your problem: "The SGI server is only serving files, no home directories, no printers (we have separate NT servers for each of those functions), and it is using "SERVER" level security. Encryption is on. Guest logins are disabled ... I'm confused greatly by this - one day, a user's login will work, another day, it'll suddenly stop working. "