x <- c("août", "élève", "ça va")
y <- iconv(x, "UTF-8", "latin1")
x
#> [1] "août" "élève" "ça va"
y
#> [1] "août""élève" "ça va"
(note the difference in spacing)
On both R-release (mac) and R-devel (linux). nchar() and format() both look ok.
Hadley
--
http://had.co.nz/
_
On Thu, 10 Sep 2015, Richard Cotton wrote:
Thanks Luke,
On 10 September 2015 at 14:47, wrote:
Conditions have classes and the condition system is designed around
the idea that classes would be used for this sort of thing. That is
already how tryCatch and withCallingHandlers discriminate the
On 10/09/2015 9:03 AM, Richard Cotton wrote:
> Thanks Luke,
>
> On 10 September 2015 at 14:47, wrote:
>> Conditions have classes and the condition system is designed around
>> the idea that classes would be used for this sort of thing. That is
>> already how tryCatch and withCallingHandlers disc
Thanks Luke,
On 10 September 2015 at 14:47, wrote:
> Conditions have classes and the condition system is designed around
> the idea that classes would be used for this sort of thing. That is
> already how tryCatch and withCallingHandlers discriminate the
> conditions to handle.
That makes sense
Conditions have classes and the condition system is designed around
the idea that classes would be used for this sort of thing. That is
already how tryCatch and withCallingHandlers discriminate the
conditions to handle.
Designing and implementing a condition class hierarchy to support this
is ind
Two solutions:
1. Use the wrapper function is_existing_file in assertive.
2. Use standardize_path in pathological before you call file.exists.
On 27 August 2015 at 17:02, Paul Johnson wrote:
> I'm writing to ask if R Core would make file.exists more Windows
> tolerant when the argument has a
The suppressMessages and suppressWarnings functions currently suppress
all the message or warnings that are generated by the input
expression.
The ability to suppress only specific messages or warnings is
sometimes useful, particularly for cases like file import where there
are lots of things that
