-
Notifications
You must be signed in to change notification settings - Fork 725
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
[Bug] Control characters in javascript source files #1146
Comments
Generating PR now :) |
Any chance to merge this please ? |
Hi, angular.js:12783Error: [$parse:lexerr] Lexer Error: Unexpected next character at columns 13-13 [Â] in expression ['NOT_FOUND' |Â translate]. |
Confirm: bug is still exists, rolling back to previous ng-admin release in production |
[RFR] Remove instances of {0xC2, 0xA0} in source files
It looks like some dodgy control characters have made it into the source files since
0.9.1
.Specific pages within the application will fail when rendering affected templates with an error similar to the following:
Using
hexdump
it is possible to see the characters in the source files:The character sequence
0xc2 0xa0
should be0x20
.This occurs in several files in the project where templates have been updated for translation.
Easy fix, but logging here because the PR is going to be confusing without an explanation.
The text was updated successfully, but these errors were encountered: