Currently, a number of R APIs do the wrong thing on Windows with UTF-8 strings. In many cases, this is because R attempts to roundtrip UTF-8 strings through the system encoding, which can often fail. These problems pop up most frequently when interacting with the file system, but also in other respects -- some simple examples:
The filesystem issues could potentially be handled by creating a separate R package, providing a new filesystem API for use within R, but it would be wonderful if these issues could be resolved in R itself. However, one could imagine producing a file system API that is more consistent / featureful / opinionated in a number of ways.
Would it be possible for an R Consortium funded effort to spearhead this?
Currently, a number of R APIs do the wrong thing on Windows with UTF-8 strings. In many cases, this is because R attempts to roundtrip UTF-8 strings through the system encoding, which can often fail. These problems pop up most frequently when interacting with the file system, but also in other respects -- some simple examples:
path.expand()
list.files()
data.frame()
The filesystem issues could potentially be handled by creating a separate R package, providing a new filesystem API for use within R, but it would be wonderful if these issues could be resolved in R itself. However, one could imagine producing a file system API that is more consistent / featureful / opinionated in a number of ways.
Would it be possible for an R Consortium funded effort to spearhead this?