https://github.com/hrbrmstr/bom
Tools to Identify and Work with Byte Order Marks in R
https://github.com/hrbrmstr/bom
bom byte-order-mark r rstats
Last synced: about 1 month ago
JSON representation
Tools to Identify and Work with Byte Order Marks in R
- Host: GitHub
- URL: https://github.com/hrbrmstr/bom
- Owner: hrbrmstr
- Created: 2016-10-01T12:52:58.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2016-10-01T13:27:45.000Z (over 8 years ago)
- Last Synced: 2025-03-27T03:02:33.221Z (2 months ago)
- Topics: bom, byte-order-mark, r, rstats
- Language: C++
- Size: 415 KB
- Stars: 4
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.Rmd
- Changelog: NEWS.md
Awesome Lists containing this project
README
---
output: rmarkdown::github_document
---
`bom` : Tools to Identify and Work with Byte Order Marks
Byte order marks (BOM) appear at the beginning of a file or buffer and provide information about the encoding of the contents. R provides facilities to work with files and connections with BOMs but there are situatons where these facilities are not sufficient. Tools are provided to identify the presence and type of byte order marks in files and R objects as well as remove them.
The following functions are implemented:
- `file_bom_type`: Get BOM type (file)
- `file_has_bom`: Test if a file has a BOM
- `raw_bom_type`: Get BOM type (raw vector)
- `raw_has_bom`: Test if a raw vector has a BOM
### TODO
- [ ] Convert to S3 methods
- [ ] BOM removal functions
- [ ] Mechanism to return a `connection` sans BOM or identify there is a BOM
### Installation
```{r eval=FALSE}
devtools::install_git("https://gitlab.com/hrbrmstr/bom.git")
```
```{r message=FALSE, warning=FALSE, error=FALSE}
options(width=120)
```
There are some basic examples in the [Usage](#Usage) section, but this may be a better illustration. Say you have a CSV file:
```{r}
fil <- system.file("examples", "stop_times.txt", package="bom")
```
And, say you want to read it in with a more modern CSV reader:
```{r}
library(readr)
df <- read_csv(fil)
```
Let's look at that file:
```{r}
print(df, n=1)
```
Hrm…why are those backticks around `trip_id`? Isn't it just a regular string?
```{r}
print(colnames(df)[1])
```
It sure _looks_ that way, but looks can be deceiving:
```{r}
print(charToRaw(colnames(df)[1]))
```
Those strange characters at the beginning are a byte order mark (BOM). We can test for it being there and work around it:
```{r}
library(bom)
if (file_has_bom(fil)) {
n <- switch(file_bom_type(fil), `UTF-8`=3, 2)
df <- read_csv(readBin(fil, "raw", file.size(fil))[-(1:n)])
}
print(df, n=1)
charToRaw(colnames(df)[1])
```
Note that the built-in `read.csv()` can be used with `encoding="UTF-8-BOM"` and you can even use that encoding on non-binary connections, but you end up having to type convert and tibble convert that object so you're basically rewriting (badly) `readr::read_csv()`.
### Usage
```{r message=FALSE, warning=FALSE, error=FALSE}
library(bom)
# current verison
packageVersion("bom")
file_has_bom(system.file("examples", "stops.txt", package="bom"))
file_has_bom(system.file("examples", "stop_times.txt", package="bom"))
raw_has_bom(readBin(system.file("examples", "stop_times.txt", package="bom"), "raw", 4))
file_bom_type(system.file("examples", "stops.txt", package="bom"))
file_bom_type(system.file("examples", "stop_times.txt", package="bom"))
raw_bom_type(readBin(system.file("examples", "stop_times.txt", package="bom"), "raw", 4))
```
### Test Results
```{r message=FALSE, warning=FALSE, error=FALSE}
library(bom)
library(testthat)
date()
test_dir("tests/")
```