Displaying 20 results from an estimated 11000 matches similar to: "WriteXLS version 5.0.0 now available"
2014 Oct 19
1
Writing UTF8 on Windows
Recent functionality in jsonlite allows for streaming json to a user
supplied connection object, such as a file, pipe or socket. RFC7159
prescribes json must be encoded as unicode; ISO-8859 (including
latin1) is invalid. Hence I would like R to write strings as utf8,
irrespective of the type of connection, platform or locale.
Implementing this turns out to be unsurprisingly difficult on windows.
2018 Feb 15
0
writeLines argument useBytes = TRUE still making conversions
I suspect your UTF-8 string is being stripped of its encoding before
write, and so assumed to be in the system native encoding, and then
re-encoded as UTF-8 when written to the file. You can see something
similar with:
> tmp <- '?'
> tmp <- iconv(tmp, to = 'UTF-8')
> Encoding(tmp) <- "unknown"
> charToRaw(iconv(tmp, to =
2018 Feb 17
0
writeLines argument useBytes = TRUE still making conversions
>From my understanding, translation is implied in this line of ?file (from the
Encoding section):
The encoding of the input/output stream of a connection can be specified
by name in the same way as it would be given to iconv: see that help page
for how to find out what encoding names are recognized on your platform.
Additionally, "" and "native.enc" both
2009 May 29
0
WriteXLS - New Version 1.7.1
The updated package has been submitted to CRAN and will propagate to
mirrors over the next day or so.
It is maintained on R-Forge at http://r-forge.r-project.org/projects/writexls
, where downloads are available as well.
Package: WriteXLS
Version: 1.7.1
Description: Cross-platform perl based R function to create Excel (XLS)
files from one or more data frames. Each data frame will be
2009 May 29
0
WriteXLS - New Version 1.7.1
The updated package has been submitted to CRAN and will propagate to
mirrors over the next day or so.
It is maintained on R-Forge at http://r-forge.r-project.org/projects/writexls
, where downloads are available as well.
Package: WriteXLS
Version: 1.7.1
Description: Cross-platform perl based R function to create Excel (XLS)
files from one or more data frames. Each data frame will be
2009 Mar 31
0
WriteXLS: New version 1.6.0 - Binary CRAN packages available and other changes
Hi all,
A new version of the WriteXLS package, 1.6.0, is making its way around
the CRAN mirrors and should be generally available in the next 24-48
hours.
The WriteXLS package provides a cross-platform perl based R function
to create Excel (XLS) files from one or more data frames. Each data
frame will be written to a separate named worksheet in the Excel
spreadsheet. The worksheet name
2009 Mar 31
0
WriteXLS: New version 1.6.0 - Binary CRAN packages available and other changes
Hi all,
A new version of the WriteXLS package, 1.6.0, is making its way around
the CRAN mirrors and should be generally available in the next 24-48
hours.
The WriteXLS package provides a cross-platform perl based R function
to create Excel (XLS) files from one or more data frames. Each data
frame will be written to a separate named worksheet in the Excel
spreadsheet. The worksheet name
2018 Feb 17
1
writeLines argument useBytes = TRUE still making conversions
Of course, right after writing this e-mail I tested on my Windows
machine and did not see what I expected:
> charToRaw(before)
[1] c3 a9
> charToRaw(after)
[1] e9
so obviously I'm misunderstanding something as well.
Best,
Kevin
On Sat, Feb 17, 2018 at 2:19 PM, Kevin Ushey <kevinushey at gmail.com> wrote:
> From my understanding, translation is implied in this line of ?file
2018 Feb 15
2
writeLines argument useBytes = TRUE still making conversions
On Thu, Feb 15, 2018 at 11:19 AM, Kevin Ushey <kevinushey at gmail.com> wrote:
> I suspect your UTF-8 string is being stripped of its encoding before
> write, and so assumed to be in the system native encoding, and then
> re-encoded as UTF-8 when written to the file. You can see something
> similar with:
>
> > tmp <- '?'
> > tmp <- iconv(tmp,
2009 Mar 10
1
suggestion/request: install.packages and unnecessary file modifications
Dear R-devel
When 'install.packages' runs, it updates all html files in all packages. Mostly, there seems to be no actual change to the html file contents, but the date/time does change. This has causing been me a bit of trouble, because I keep synchronized versions of R on several different machines, and whenever I install a package, many MB of file transfers are required; my slow upload
2009 Jun 17
0
WriteXLS - New Version 1.8.0
The updated package has been submitted to CRAN and will propagate to
mirrors over the next day or so.
It is maintained on R-Forge at http://r-forge.r-project.org/projects/writexls
, where downloads are available as well.
Package: WriteXLS
Version: 1.8.0
Description: Cross-platform perl based R function to create Excel (XLS)
files from one or more data frames. Each data frame will be written
2009 Jun 17
0
WriteXLS - New Version 1.8.0
The updated package has been submitted to CRAN and will propagate to
mirrors over the next day or so.
It is maintained on R-Forge at http://r-forge.r-project.org/projects/writexls
, where downloads are available as well.
Package: WriteXLS
Version: 1.8.0
Description: Cross-platform perl based R function to create Excel (XLS)
files from one or more data frames. Each data frame will be written
2009 Mar 26
0
New CRAN Package: WriteXLS
A new package called WriteXLS (Version 1.5.0), containing a single
function of the same name, is now available via CRAN. The package is
made available under the GPL, version >=2.
The function is based upon a Perl script that I have previously posted
on r-help, now wrapped in R for convenience. It provides a cross-
platform function to create Excel 2003 (XLS) files from one or more
2009 Mar 26
0
New CRAN Package: WriteXLS
A new package called WriteXLS (Version 1.5.0), containing a single
function of the same name, is now available via CRAN. The package is
made available under the GPL, version >=2.
The function is based upon a Perl script that I have previously posted
on r-help, now wrapped in R for convenience. It provides a cross-
platform function to create Excel 2003 (XLS) files from one or more
2013 Feb 13
1
WriteXLS: 'object not found' error within function
Dear All,
I am using WriteXLS to write tables with multiple sheets with the command:
WriteXLS("tables", ExcelFileName = fileName, SheetNames = tableList, perl = "perl",
verbose = FALSE, Encoding = c("UTF-8", "latin1"),
row.names = TRUE, col.names = TRUE,
AdjWidth = TRUE, AutoFilter = FALSE, BoldHeaderRow = FALSE,
2010 Sep 16
0
WriteXLS - New Version 2.0.1
The updated package has been submitted to CRAN and will propagate to mirrors over the next day or so.
It is maintained on R-Forge at http://r-forge.r-project.org/projects/writexls, where downloads will eventually be available as well.
Package: WriteXLS
Version: 2.0.1
Description: Cross-platform Perl based R function to create Excel 2003 (XLS) files from one or more data frames. Each data
2010 Sep 16
0
WriteXLS - New Version 2.0.1
The updated package has been submitted to CRAN and will propagate to mirrors over the next day or so.
It is maintained on R-Forge at http://r-forge.r-project.org/projects/writexls, where downloads will eventually be available as well.
Package: WriteXLS
Version: 2.0.1
Description: Cross-platform Perl based R function to create Excel 2003 (XLS) files from one or more data frames. Each data
2018 Feb 15
2
writeLines argument useBytes = TRUE still making conversions
I think this behavior is inconsistent with the documentation:
tmp <- '?'
tmp <- iconv(tmp, to = 'UTF-8')
print(Encoding(tmp))
print(charToRaw(tmp))
tmpfilepath <- tempfile()
writeLines(tmp, con = file(tmpfilepath, encoding = 'UTF-8'), useBytes = TRUE)
[1] "UTF-8"
[1] c3 a9
Raw text as hex: c3 83 c2 a9
If I switch to useBytes = FALSE, then
2020 Oct 23
0
WriteXLS Version 6.0.0 Released
Hi All,
WriteXLS version 6.0.0 has been released and is available on CRAN.
The key changes are:
1. More robust handling of embedded newline ('\n') and carriage return ('\r') characters, double quotes, and two character sequences of a backslash character ('\') followed by another character, within a data value, has been implemented. An indirect consequence of this more
2018 Feb 17
0
readLines interaction with gsub different in R-dev
I think the problem in R-devel happens when there are non-ASCII characters
in any
of the strings passed to gsub.
txt <- vapply(list(as.raw(c(0x41, 0x6d, 0xc3, 0xa9, 0x6c, 0x69, 0x65)),
as.raw(c(0x41, 0x6d, 0x65, 0x6c, 0x69, 0x61))), rawToChar, "")
txt
#[1] "Am?lie" "Amelia"
Encoding(txt)
#[1] "unknown" "unknown"
gsub(perl=TRUE,