similar to: special latin1 do not print as glyphs in current devel on windows

Displaying 20 results from an estimated 400 matches similar to: "special latin1 do not print as glyphs in current devel on windows"

2017 Aug 01
2
special latin1 do not print as glyphs in current devel on windows
Thank you!. My apologies again for not including the console output in my message before. I sent another e-mail with the output in the meantime, so it should be a bit clearer now, what I am seeing. In case I missed something, please let me know. Yes, I am using latin1 and cp1252 interchangebly here, mostly because Encoding() is reporting the encoding as "latin1". You presumed correctly
2017 Aug 01
0
special latin1 do not print as glyphs in current devel on windows
You seem confused about Latin-1: those characters are not in Latin-1. (MicroSoft code pages are a proprietary encoding, some code pages such as CP1252 being extensions to Latin-1.) You have not given the 'at a minimum information' asked for in the posting guide so we have no way to reproduce this, and without showing us the output on your system, we have no idea what you saw. [As a
2017 Sep 14
2
special latin1 do not print as glyphs in current devel on windows
This is a follow-up on my initial posts regarding character encodings on Windows (https://stat.ethz.ch/pipermail/r-devel/2017-August/074728.html) and Patrick Perry's reply (https://stat.ethz.ch/pipermail/r-devel/2017-August/074830.html) in particular (thank you for the links and the bug report!). My initial posts were quite chaotic (and partly wrong), so I am trying to clear things up a
2017 Sep 14
0
special latin1 do not print as glyphs in current devel on windows
This particular issue has a simple fix. Currently, the "R_check_locale" function includes the following code starting at line 244 in src/main/platform.c: #ifdef Win32 { char *ctype = setlocale(LC_CTYPE, NULL), *p; p = strrchr(ctype, '.'); if (p && isdigit(p[1])) localeCP = atoi(p+1); else localeCP = 0; /* Not 100% correct, but CP1252 is a
2003 Jan 17
2
Samba Internationalization
Hello, I used with happiness Samba 2.2.3. Everything works perfectly but I noticed two problems with accented characters; the first one on Samba, the other one on Swat. I work with a win98 client and a Debian server. Win98 use codepage 850 but I noticed, in fact, it use codepage 1252 and I suppose that conversion is made with a file called 12520850.cpx. On my Linux box I set up codepage
2020 Jun 22
2
Possible Bug: file.exists() Function. Due to UTF-8 Encoding differences on Windows between R 4.0.1 and R 3.6.3?
Hi Tomas, I received a report about R 4.0.0 in the knitr package (https://github.com/yihui/knitr/issues/1840), and I think it is related to the issue here. I created a minimal reproducible example below: owd = setwd(tempdir()) z = 'K\u00e4sch.txt' file.create(z) list.files() file.exists(list.files()) setwd(owd) Output: > owd = setwd(tempdir()) > z = 'K\u00e4sch.txt' >
2013 Apr 29
3
[Announce] Samba 3.6.14 Available for Download
============================================================= "Just play. Have fun. Enjoy the game." Michael Jordan ============================================================= Release Announcements ===================== This is is the latest stable release of Samba 3.6. Major enhancements in Samba 3.6.14 include: o Certain xattrs cause Windows error 0x800700FF
2013 Apr 29
3
[Announce] Samba 3.6.14 Available for Download
============================================================= "Just play. Have fun. Enjoy the game." Michael Jordan ============================================================= Release Announcements ===================== This is is the latest stable release of Samba 3.6. Major enhancements in Samba 3.6.14 include: o Certain xattrs cause Windows error 0x800700FF
2009 Apr 10
1
linux Rsync + windows rsync + unexpected connection close
Hello all I cannot sync my windows box with my linux box because of the following error. rsync: connection unexpectedly closed (0 bytes received so far) [receiver] I run rsync version 3.0.4 ( protocol 30) on both machines (cwRsync binaries on windows). i sync over ssh. Ssh command works fine from windows. Same rsync command from the linux box works fine. Only the rync command from windows
2011 Feb 26
3
hivex: some issues (key encoding, ...) and suggested fixes
Hi, libhivex seems to do a great job at parsing hives most of the time, but there are some issues with a few registry keys. These can be worked around in the application that uses libhivex, but I think it'd be better if libhivex handled these itself. 1. UTF16 string in REG_SZ that has garbage after the \0\0 There is code in hivex.c to handle this already but I think it has a typo: /*
2010 May 02
2
Set encoding when load()-ing workspaces?
Hi all, I hope that there is someone that can help me out here. I am trying to load() a workspace on os x (R 2.11.0) that was saved in windows XP (R 2.9). In that workspace, there's a data.frame with names that contain swedish characters. These characters become garbled, which is a major problem. >From the R windows FAQ, I read: "Note though that character data in a workspace will be
2014 May 05
3
recycle: ... returned No such file or directory
Hi, recently I see lots of logs like this. I figured, that many have umlaute in their name - but not all. My local FS displays the umlaute correctly - but it is not displayed correctly in the logfiles. Also, when I browse through shares via Windows or MacOSx all files with umlaute seem to be displayed correctly. May 5 08:27:54 Storage-01 smbd[39207]: recycle: stat for
2011 Nov 09
1
Rsync with special characters
Hi, I'm having problem using rsync from an Ubuntu server to a Windows machine using cygwin and rsync. It works whenever I have a share name that doesn't include a special character like ?, ? or ?. My full command is: "rsync -avz -e 'ssh -p specialport' user at windowsmachine:/cygdrive/c/?test --iconv=CP1252,utf-8 (Also tride ISO8859-1 and utf-8)" I thought that iconv
2014 Feb 08
4
force group does not work
Hi I set up a samba 4.1.4 server on the latest FreeBSD RELEASE 10. Unfortunately it doesn't seem to consider the option force group. After hours ofresearch I couldn't figure out what I'm still missing. unix extensions is set to no. Setting the debug level up to 10 also didn't help ;( Is this a bug or is there simply a mistake in my setup? When *valid users = @Groupname* is
2020 Jun 22
0
Possible Bug: file.exists() Function. Due to UTF-8 Encoding differences on Windows between R 4.0.1 and R 3.6.3?
Hi Yihui, list.files() returns file names converted to native encoding by Windows, so one needs to use only characters representable in current native encoding for file names. If one wants to be safe, it makes sense to be much stricter than that (only ASCII, and only a subset of it, there is a number of recommendations that can be found online). Using more than that is asking for trouble.
2016 Oct 24
3
invalid NTLMSSP_MIC / SPNEGO login failed: NT_STATUS_INVALID_PARAMETER
Hello, since I upgraded my NT4 domain Samba 4.2.11 to 4.2.14 I can no longer authenticate when I access any share. After that I even upgraded to Samba 4.4.5 but still get the same error: [2016/10/15 04:42:19.786198, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password) check_ntlm_password: authentication for user [xx] -> [xx] -> [xx] succeeded [2016/10/15 04:42:19.789933, 1]
2003 Dec 01
0
No subject
8. You have join to this mail a text file with the few characters that don't = match. On Swat, it's easier. = I use Swat from my win98 box. When I write a share comment with some chara= cters, there are not translated properly inside smb.conf file. = When I read my smb.conf file, I noticed that for example a cp1252 characte= r like (0xC1) has been changed onto an ISO8859-15 character
2015 Feb 26
4
Native characterset is wrong for unicode builds for Windows
When I send some outlandish characters through enc2native (or format) in R 3.1.2 on Ubuntu trusty it works quite well: > "?????" [1] "?????" > enc2native("?????") [1] "?????" > Encoding(enc2native("?????")) [1] "UTF-8" In Windows the result is different: > "?????" [1] "?????" >
2015 Apr 27
1
Fwd: Cross Building Tcl using Mingw32-gcc (4.9.2)
I posted this to the comp.lang.tcl newsgroup, but it might relate to a possible bug in the Mingw32 cross-build environment under CentOS 6 (or EPEL). Forwarded Message: From: Robert Heller <heller at deepsoft.com> Subject: Cross Building Tcl using Mingw32-gcc (4.9.2) Newsgroups: comp.lang.tcl Message-ID: <Nc-dnd1wRNTsy6PInZ2dnUU7-b-dnZ2d at giganews.com> Date: Mon, 27 Apr 2015
2015 Feb 27
2
Native characterset is wrong for unicode builds for Windows
Am 27.02.2015 um 03:13 schrieb Duncan Murdoch: > On 26/02/2015 6:34 PM, maillist at tlink.de wrote: >>> On 26/02/2015 3:09 PM, maillist at tlink.de wrote: >>>> When I send some outlandish characters through enc2native (or format) in >>>> R 3.1.2 on Ubuntu trusty it works quite well: >>>> >>>> > "?????" >>>> [1]