similar to: will it break the system files?

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

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"

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

Murray, Your commits earlier this evening to zh_CN.GB18030 fixed that -STABLE breakage, but zh_CN.GBK appears still to be missing, which causes 'make installworld' to fail. Can you please fix this as well? install -m 644 -o root -g wheel uk_UA.KOI8-U.out /usr/share/locale/uk_UA.KOI8-U/LC_CTYPE install -m 644 -o root -g wheel zh_CN.eucCN.out /usr/share/locale/zh_CN.eucCN/LC_CTYPE

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

Hi, I'm not sure what's going on ;-( updated a .vimrc file in my home directory with some customized settings last week. I'm looking at my home directory now, that .vimrc file disappeared for no reason and I saw a file called vimrc and .viminfo in the home directory. Of course, it didn't take my customized settings when I used vim. Is that a normal behavior? Am I missing

From: rhy2k4@hotmail.com To: samba@lists.samba.org Subject: language charset problem£¡ Date: Sun, 17 May 2009 02:10:45 +0000 dear all£¬ I port samba 3.0.0 to board ,and it is almost ok. but there still some problem about file display can't be resolved. I use charset C 1 chinese name file display wrong. I confiure the smb.conf to cp936 char set as followed. ... display charset

The clang patches are now applied, so vim auto completion now works mostly out-of-the-box -- just build clang, set up your PATH for clang and clang++, and copy utils/vim/vimrc to ~/.vimrc (or symlink, or do your own thing). To configure the clang command-line, look for the g: configuration variables in the vimrc file. I'm open to suggestions about the handling of function parameters. One

Here is my code. there are three method to get text to be parded by htmlParse function. 1.file on mycomputer options(encoding="gbk") library(XML) xmltext1 <- htmlParse("/home/tiger/Desktop/27174.htm" ) #/home/tiger/Desktop/27174.htm is the file of http://www.jb51.net/article/27174.htm downloaded on my computer. 2.url options(encoding="gbk")

I tried it on R 4.4.1 on Linux Mint 21.3 just before I posted it, and I just tried it on R 3.4.2 on Ubuntu 16.04 and R 4.3.2 on Windows 11 just now and it works on all of them. I don't have a big-endian machine to test on, but the Unicode spec says to honor the BOM and if there isn't one to assume that it is big-endian data. But in this case there is a BOM so your machine has a buggy

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,

Thanks, Journeyer. I applied the patch with r176235. In future, you can submit patches to the llvm-commits mailing list. :) -bw On Feb 27, 2013, at 9:03 PM, Journeyer J. Joh <oosaprogrammer at gmail.com> wrote: > Hello list, > > I use LLVM's vimrc and found that this setting below is useful when > editing of reStructuredText file. > > > llvm/utils/vim/vimrc

Hello list, I use LLVM's vimrc and found that this setting below is useful when editing of reStructuredText file. llvm/utils/vim/vimrc " Enable syntax highlighting for reStructuredText files. To use, copy " rest.vim (http://www.vim.org/scripts/script.php?script_id=973) " to ~/.vim/syntax . augroup filetype au! BufRead,BufNewFile *.rst set filetype=rest augroup END

On 2024-09-07 7:37 p.m., Jeff Newmiller wrote: > I tried it on R 4.4.1 on Linux Mint 21.3 just before I posted it, and I just tried it on R 3.4.2 on Ubuntu 16.04 and R 4.3.2 on Windows 11 just now and it works on all of them. > > I don't have a big-endian machine to test on, but the Unicode spec says to honor the BOM and if there isn't one to assume that it is big-endian data.

On 2024-09-07 4:52 p.m., Jeff Newmiller via R-help wrote: > When you specify LE in the encoding type, you are logically telling the decoder that you know the two-byte pairs are in little-endian order... which could override whatever the byte-order-mark was indicating. If the BOM indicated big-endian then the file decoding would break. If there is a BOM, don't override it unless you have to

I have installed CentOS 4.5 and 5 on 2 separate machines, and both have default installs of vim-enhanced on each of them. I noticed that I can get syntax highlighting as a regular user, sudo and as root in C4.5. In C5 I only get highlighting as a regular user. I diff'ed my /etc/vimrc files between each install there is no changes and neither root ~ has a .vimrc file. I had put "# vim:

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,

my user.reg contains the following external fonts Software\\Wine\\Fonts\\External Fonts] 1139540729 "Bitstream Vera Sans Bold (TrueType)"="VeraBd.ttf" "Bitstream Vera Sans Bold Oblique (TrueType)"="VeraBI.ttf" "Bitstream Vera Sans Mono Bold (TrueType)"="VeraMoBd.ttf" "Bitstream Vera Sans Mono Bold Oblique

On Oct 21, 2010, at 2:11 PM, Tobias Grosser wrote: > Hi, > > I have been watching the vim/clang autocompletion in utils/vim/vimrc for a while. What is the status of this work? The last information I got is, that there where still some patches missing, but this was before the clang-2.8. > Any updates? Is it supposed to work with clang-2.8? It requires a clang patch, which I

On 10/29/2016 04:32 PM, Alice Wonder wrote: > On 10/29/2016 03:06 PM, Alice Wonder wrote: >> On 10/29/2016 02:49 PM, Frank Cox wrote: >>> On Sat, 29 Oct 2016 14:39:03 -0700 >>> Alice Wonder wrote: >>> >>>> How do I get it to stop doing that? >>> >>>