Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An emoji is broken and printed on a paperback book. #1612

Open
youngwoos opened this issue Dec 22, 2023 · 3 comments
Open

An emoji is broken and printed on a paperback book. #1612

youngwoos opened this issue Dec 22, 2023 · 3 comments

Comments

@youngwoos
Copy link

youngwoos commented Dec 22, 2023

@hadley
Hi, I'm a translator working on your excellent book R for Data Science (2e) into Korean.

You may already know this, but while working on the translation, I found a broken emoji printout in the paperback book. They are printed on pages 243 and 244 of the paperback book. In the e-book PDF file, they are printed on pages 245 and 246.

Thank you for a great book.
Working on the translation made me understand R better.

Many thanks.

image
@monkeywithacupcake
Copy link

monkeywithacupcake commented Jan 8, 2024

This is strange.

When I run the same lines in my console, I get the emoji.
image

And it also shows up in the html when I knit the following excerpt from the book (as.Rmd)


---
title: "Untitled"
output: html_document
date: "2024-01-08"
---
 
### Other special characters
 
As well as `\"`, `\'`, and `\\`, there are a handful of other special characters that may come in handy. The most common are `\n`, a new line, and `\t`, tab. You'll also sometimes see strings containing Unicode escapes that start with `\u` or `\U`. This is a way of writing non-English characters that work on all systems. You can see the complete list of other special characters in `?Quotes`.
 
```{r}
x <- c("one\ntwo", "one\ttwo", "\u00b5", "\U0001f604")
x
stringr::str_view(x)

@hadley
Copy link
Owner

hadley commented Jan 9, 2024

That's because O'Reilly manually did the emoji translation; they must have missed that one.

@youngwoos
Copy link
Author

I would have guessed it was an O'Reilly issue. Hopefully it will be corrected in the next printing. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants