similar to: Re : The chinese problem in sammount !

Dear All, I have installed the latest wine and run Visual Foxpro progams under wine However Chinese data retreived cannot display correctly I know under Windows, Foxpro display them correctly using an option in Control Panel "Use program for Non-unicode program" and choosing say "Chinese TW" Is there such option under Wine ? or can we modify the default codepage on wine to

Thank you for the report and initial debugging. I am not sure what is going wrong, we may have to rely on your help to debug this (I do not have a system to reproduce on). A user-targeted advice would be to use RGui (Rgui.exe). Does the problem also exist in R-devel? https://cran.r-project.org/bin/windows/base/rdevel.html Your example? print("ABC\u4f60\u597dDEF") is printing two

Hi, I am using SME server 6.0 which has samba preconfigured on it. We upgraded from MS Windows 2000 server. I am using the server in China and so many of the users wish to create files with Chinese characters in their names. File names with Chinese characters seem to cause all sorts of problems. They have trouble creating them, and files which are copied off backup (from the W2K system)

XML is a good tool reading data from web within R. But I wonder how could get the encoding correctly. library(XML) url <- 'http://www.szitic.com/docc/jz-lmzq.html' xml <- htmlTreeParse(url, useInternal=TRUE) q <- "//tbody/tr/td" dat <- unlist(xpathApply(xml, q, xmlValue)) df <- as.data.frame(t(matrix(dat, 4))) dt<-as.character(df[15,1]) The first column of df

Hello everyone, I am new to R and I have experienced some bugs when using Rterm on Windows. Chinese characters in the console output are discarded by Rterm, and trying to type them into the console will crash the Rterm application. ---ENVIRONMENT--- Platform = x86_64-w64-mingw32 OS = Windows 10 Pro 1709 chs R version = 3.4.3 Active code page = 936 (Simplified Chinese) ---STEPS TO

Dear Sir, rcom is a great package of R. Yet it seems that there is some problem of Chinese character supporting. comGetPropery() always get the part of the Chinese character. Any suggestion would be appreciated. Thanks. Michael > library(rcom) Loading required package: rscproxy > txe<-comCreateObject("Excel.Application") > comSetProperty(txe,"Visible",TRUE);

i mount a windows share like this: mount -t smbfs -o iocharset=gb2312,codepage=936,username=administrator //192.168.10.27/cvs /mnt/windows and try to copy file from /mnt/windows . but it always told me "cp: con't creat normal file , invalid argument." and here is my locale: LANG=zh_CN LC_CTYPE="zh_CN" LC_NUMERIC="zh_CN" LC_TIME="zh_CN"

Thanks for the update. I believe I've fixed a part of the problem you have reported, the crash while entering Chinese characters to the console (e.g. via Pinyin, the error message about invalid multibyte character in mbcs_get_next). The fix is in R-devel 74693 - Windows function ReadConsoleInputA no longer works with multibyte characters (it is not documented, probably a Windows bug,

i mount a windows share like this: mount -t smbfs -o iocharset=gb2312,codepage=936,username=administrator //192.168.10.27/cvs /mnt/windows and try to copy file from /mnt/windows to my local disk. but if came to file with chinese name it always told me "cp: can't creat normal file , invalid argument." by the way i can see the file name (in chinese), and here is my locale: LANG=zh_CN

Dear Yihui, Thanks a lot for your help! Unfortunately, I was not able to reproduce this. I've tried creating files with Chinese characters in their names and populating them with valid UTF-8 and valid non-UTF-8 text, but R seems to be able to list them all in my case. I'm running a US English evaluation ISO image of a slightly newer build of Windows 10, and I also compiled R-4.3.1 from

When running smbd chrooted it crashes when clients attempt to browse shares with the following error (debug level 10): switch message SMBtrans2 (pid 13594) setting sec ctx (22078, 505) - sec_ctx_stack_ndx = 0 1 user groups: 505 change_to_user uid=(0,22078) gid=(0,505) vfs_ChDir to /home/tester call_trans2qfsinfo: level = 1007 ===============================================================

I am running Centos 6.6 US version and occasionally need to write emails and documents in Chinese using simplified characters. I have installed the ibus input system but do not find it very efficient having used the Google Pinyin keyboard on my Android phones and tablet. Which input system is recommended for writing Simplified Chinese? Hakan

Hi Tomas, Sorry for the delayed response. I have tested the problem on the latest R-devel build (2018-04-27 r74651), and it still exists. RGui is always fine with Chinese characters, but some IDEs rely on the CLI version of R (e.g. Visual Studio Code with R plugin). >Your example print("ABC\u4f60\u597dDEF") is printing two Chinese characters, right? Yes. U+4F60, U+597D or C4E3,

The Wine development release 1.6-rc4 is now available. What's new in this release (see below for details): - Bug fixes only, we are in code freeze. The source is available from the following locations: http://prdownloads.sourceforge.net/wine/wine-1.6-rc4.tar.bz2 http://mirrors.ibiblio.org/wine/source/1.6/wine-1.6-rc4.tar.bz2 Binary packages for various distributions will be available

Hello all, Thank you very much for viewing the letter. This is Haowei (English name: Cyrus Evans) from China, who is a professiona IT editor and English interpretor. As I have gained more than 3 years' experience of localizatioin work and so much experience opensource software (including mybboard, smf etc.). As an experienced contributor, I wirte this letter to apply for joining

Yes, I participated in the discussion. Basically dir() failed to list all files since R 4.3.0 when filenames start with Chinese characters. I don't have a Windows machine to test it, but this might be a minimal reproducible example: file.create("????.R") dir() The OP said dir() would return "????.R" in R.4.2.2 but not in R 4.3.0. In the same discussion another person

Hi all, There is a small bug at the new Unicode support. I didn't follow the consequences of this bug, but this _is_ a bug ;-). The bug stands on wrong charset name. Instead of KOI8-R (this is right) it's called KOI-R (this is wrong). (I'm afraid the long lines wrap, but it shows the picture) 1. Makefile.in --- Makefile.in Thu Feb 17 16:00:33 2000 +++ Makefile.in Thu Feb 17

Hi! All: I'm working on add unicode support in samba. However, I meet a question = as the following description, please advise me. My smb.conf sets: dos charset =3D UTF8 display charset =3D UTF8 unix charset =3D UTF8 I use smbmount //share /path -o username=3Duser,passwd=3D1234 to mount a = directory to a user's home dir. Original I use ASCII charset, and find

Hi, every one, I have translated <An Introduction to R > into simplified Chinese and traditional Chinese. You can browse them from these two URL: simplified Chinese: http://www.biosino.org/pages/newhtm/r/schtml/index.html#Top traditional Chinese: http://www.biosino.org/pages/newhtm/r/tchtml/ I have distributed these document in HTML format. That is because there is something wrong with

Hello, I tried but not exists with the following non-exist error. Please advise. Thanks. # yum groupinstall "Chinese Support" Failed to set locale, defaulting to C Loaded plugins: fastestmirror, langpacks There is no installed groups file. Maybe run: yum groups mark convert (see man yum) base | 3.6 kB 00:00:00 extras | 3.4 kB 00:00:00 updates | 3.4 kB 00:00:00 Loading