Skip to content
This repository

“/* \f020 is not a valid unicode character. all shifted one down */” #268

Closed
mathiasbynens opened this Issue · 5 comments

4 participants

Mathias Bynens Matthias Kretschmann Dave Gandy Steven Levithan
Mathias Bynens

What’s with this comment? https://github.com/FortAwesome/Font-Awesome/blob/99b5966fb453e568e71e049b991a75590912b5fa/css/font-awesome.css#L123

/* \f020 is not a valid unicode character. all shifted one down */

U+F020 is just another Unicode symbol in the PUA, just like U+F021 or U+F022 (the ones that are being used instead, for some reason).

What was the reasoning here? This comment seems misinformed. /cc @lensco

Matthias Kretschmann

Would also love to hear about the reasoning. As I understand it, everything in the PUA isn't a valid unicode character so what makes U+F020 so special? Maybe @davegandy could shed some light on this?

Matthias Kretschmann

Likewise, U+F073 seems to be more problematic: #246

Dave Gandy
Owner

All, I know is, f020 didn't work in Safari. Don't know what to tell you.

Thanks for jquery-placeholder, btw. Just realized that was you.

Dave Gandy davegandy closed this
Steven Levithan

All, I know is, f020 didn't work in Safari.

Then why not say "\f020 doesn't work in Safari", or something similar?

I agree with @mathiasbynens that the current message is misleading and sounds misinformed. If you got the message from http://www.fileformat.info/info/unicode/char/f020/index.htm or similar, note that it shows that message for all Private Use Area code points, not just U+F020.

Mathias Bynens

All, I know is, f020 didn't work in Safari. Don't know what to tell you.

Thanks for the info. Would you mind changing the comment to avoid further confusion?

P.S. Glad you liked my placeholder plugin :)

Andrew Gribben andrewgribben referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.