Displaying 8 results from an estimated 8 matches for "u00e4".
Did you mean:
00e4
2013 Apr 11
2
(no subject)
Dear all,
Is there a quick and easy way of converting utf characters to the \uxxxx
form (necessary e.g. for packages)? I mean something working like this:
> utf2uxxxx("õäöü")
[1] "\u00f5\u00e4\u00f6\u00fc"
It is easy to program but perhaps someone already has implemented this. (I
couldn't find anything useful from searches incl RSiteSearch).
Thanks in advance,
Kenn
-- P.S. Apologies if this is double posted - there was a network error and
the first message doesn't seem...
2014 Jan 15
0
[PATCH 2/4] hivex: python: Fix encoding for "special" test script
...):
+ return x
import os
import hivex
@@ -13,16 +22,20 @@ assert h
root = h.root ()
assert root
-ns = [ n for n in h.node_children (root) if h.node_name(n) == u"abcd_äöüß" ]
+# "abcd_äöüß"
+ns = [ n for n in h.node_children (root) if h.node_name(n) == u("abcd_\u00e4\u00f6\u00fc\u00df") ]
assert len (ns) == 1
-vs = [ v for v in h.node_values (ns[0]) if h.value_key(v) == u"abcd_äöüß" ]
+# "abcd_äöüß"
+vs = [ v for v in h.node_values (ns[0]) if h.value_key(v) == u("abcd_\u00e4\u00f6\u00fc\u00df") ]
assert len (vs) == 1
-ns = [...
2018 Dec 08
2
Possible encoding bug in sub()
...d in Windows (no
UTF-8 locale there). The second sub() produces a correct result,
although for some reason it is converted to the native Encoding in
Windows.
I think the best result would be UTF-8 output marked as such.
foo <- c("a", "b")
foo <- sub("a", "\u00e4", foo)
print(Encoding(foo))
## [1] "unknown" "unknown"
foo <- sub("b", "\u00f6", foo)
print(Encoding(foo))
## [1] "unknown" "unknown" # Windows
## [1] "unknown" "UTF-8" # Linux
print(foo)
## [1] "??"...
2014 Jan 15
4
[PATCH 1/4] hivex: Python 2.6 does not have sysconfig.
---
configure.ac | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure.ac b/configure.ac
index 6785037..203f34f 100644
--- a/configure.ac
+++ b/configure.ac
@@ -329,8 +329,8 @@ AS_IF([test "x$enable_python" != "xno"],
AC_MSG_CHECKING([for Python extension suffix (PEP-3149)])
if test -z "$PYTHON_EXT_SUFFIX"; then
2018 Dec 10
0
Possible encoding bug in sub()
...ond sub() produces a correct result,
> although for some reason it is converted to the native Encoding in
> Windows.
> I think the best result would be UTF-8 output marked as such.
> foo <- c("a", "b")
> foo <- sub("a", "\u00e4", foo)
> print(Encoding(foo))
> ## [1] "unknown" "unknown"
> foo <- sub("b", "\u00f6", foo)
> print(Encoding(foo))
> ## [1] "unknown" "unknown" # Windows
> ## [1] "unknown" "...
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?
...acters 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.
Unicode "\u00e4" is a Latin-1 character, so representable in CP1252. On
my Windows running in CP1252 as C locale and system code page, your
example works fine, file.exists() returns TRUE, and this is the expected
behavior (tested in R-devel and R4.0).
Your example was run in CP1252 as C locale but CP936 a...
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'
> file.create(z)
[1] TRUE
> list.files()
[1] "K?sch.txt"
> file.exists(list.files())
[1] FALSE
> setwd(owd)
I wonder if it is e...
2020 Jun 24
3
Possible Bug: file.exists() Function. Due to UTF-8 Encoding differences on Windows between R 4.0.1 and R 3.6.3?
...urrent 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.
>
> Unicode "\u00e4" is a Latin-1 character, so representable in CP1252. On
> my Windows running in CP1252 as C locale and system code page, your
> example works fine, file.exists() returns TRUE, and this is the expected
> behavior (tested in R-devel and R4.0).
>
> Your example was run in CP1252 as...