Displaying 10 results from an estimated 10 matches for "u20ac".
Did you mean:
20ac
2017 Sep 14
2
special latin1 do not print as glyphs in current devel on windows
...hich might
be a (slightly) different problem, but I will get to that later.)
> print(x)
[1] "\u0080" "\u009e" "\u009a" "?"
"?", "?", and "?" are printed as (incorrect) unicode escapes. "?" for
example should be \u20ac not \u0080.
(In R 3.4.1, print(x) shows the glyphs and not the unicode escapes.
Apparently, as of v3.5, print() calls enc2utf8() (or its equivalent in C
(translateCharUTF8?))?)
> print("\u20ac")
[1] "?"
The characters in x are marked as "latin1".
> Encodin...
2017 Aug 01
2
special latin1 do not print as glyphs in current devel on windows
...eserve encoding!
>
I am not interested in preserving encodings. What I am worried about is
that the encoding is not marked anymore, i.e. that Encoding() returns
"unknown".
In cp1252 encoding on Windows (note that I am using the cp1252 escape
"\x80" and not the Unicode "\u20AC")
> x_utf8 <- enc2utf8(c("?", "\x80"))
> Encoding(x_utf8)
[1] "UTF-8" "UTF-8"
> x_nat <- enc2native(x_utf8)
> Encoding(x_nat)
[1] "unknown" "unknown"
See also Kirill's message to this list: "ASCII strings...
2017 Sep 14
0
special latin1 do not print as glyphs in current devel on windows
...different problem, but I will get to that later.)
>
> > print(x)
> [1] "\u0080" "\u009e" "\u009a" "?"
>
> "?", "?", and "?" are printed as (incorrect) unicode escapes. "?" for
> example should be \u20ac not \u0080.
> (In R 3.4.1, print(x) shows the glyphs and not the unicode escapes.
> Apparently, as of v3.5, print() calls enc2utf8() (or its equivalent in
> C (translateCharUTF8?))?)
>
> > print("\u20ac")
> [1] "?"
>
> The characters in x are marked...
2017 Aug 01
3
special latin1 do not print as glyphs in current devel on windows
Upon further inspection, I think these are at least two problems.
First the issue with printing latin1/cp1252 characters in the "80" to "9F"
code range.
x <- c("?", "?", "?")
Encoding(x)
print(x)
I assume that these are Unicode escapes!? (Given that Encoding(x) shows
"latin1" I'd rather expect latin1/cp1252 escapes here, but
2010 Mar 22
1
add euro sign to a plot
hi,
Is it possible to add special characters like the euro sign to a plot?
thanks!
2014 Jan 15
0
[PATCH 2/4] hivex: python: Fix encoding for "special" test script
...oot) if h.node_name(n) == u("weird\u2122") ]
assert len (ns) == 1
-vs = [ v for v in h.node_values (ns[0]) if h.value_key(v) == u"symbols $£₤₧€" ]
+# "symbols $£₤₧€"
+vs = [ v for v in h.node_values (ns[0]) if h.value_key(v) == u("symbols \u0024\u00a3\u20a4\u20a7\u20ac") ]
assert len (vs) == 1
--
1.8.5.2
2017 Aug 01
0
special latin1 do not print as glyphs in current devel on windows
...t lost with the enc2*
> functions
As you are changing encodings, you do not want to preserve encoding!
> x_utf8 <- enc2utf8(x)
> Encoding(x_utf8)
> x_nat <- enc2native(x_utf8)
> Encoding(x_nat)
In an actual Latin-1 locale on Linux
> x_utf8 <- c("??", "\u20ac", "\u2013")
> Encoding(x_utf8)
[1] "latin1" "UTF-8" "UTF-8"
> enc2native(x_utf8)
[1] "??" "<U+20AC>" "<U+2013>"
> Encoding(.Last.value)
[1] "latin1" "unknown" "unknown&q...
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
2006 Sep 19
4
How to draw a per mille symbol?
Dear list,
Following advice posted to this list a while back by Prof Ripley [1], I
have been trying to draw a per mille character [2] in an axis label.
This should give the correct character:
plot(1:10, ylab = "\u2030")
but all I get is '"S'. I'm running linux (FC5) and have fonts installed
that have the correct character (viewed in the Gnome character map at
least).
2014 Aug 16
7
[hivex] [PATCH 0/6] Python fixes for node_set_value
Hi,
This patch series is based on a prior patch[1], splitting off changes as
requested and incorporating feedback from Richard Jones. It introduces type
validation to avoid segmentation faults (instead, it reports an exception) and
fixes handling of the bytes type in Python 3.
Major changes since that series:
- Drop newly introduced support for integer types for DWORD/QWORDS
- Reject Unicode