ninetydegrees: Drawing: a girl's face, with a yellow and green stripe over one eye (Default)
Ninety Degrees (90d) 🌻 ([personal profile] ninetydegrees) wrote in [site community profile] dw_dev_training2015-07-10 07:45 pm

Errors when updating

error htdocs/scss/components/pickadate/datetime.scss (Line 11 of htdocs/scss/components/pickadate/_base.scss: Invalid US-ASCII character "\xE2")
error htdocs/scss/components/pickadate/time.scss (Line 6: Invalid US-ASCII character "\xE2")
error htdocs/scss/skins/celerity.scss (Line 107 of htdocs/scss/skins/_nav.scss: Invalid US-ASCII character "\xE2")
error htdocs/scss/skins/gradation/gradation-horizontal.scss (Line 107 of htdocs/scss/skins/_nav.scss: Invalid US-ASCII character "\xE2")
error htdocs/scss/skins/gradation/gradation-vertical.scss (Line 107 of htdocs/scss/skins/_nav.scss: Invalid US-ASCII character "\xE2")

Is is just me?
alierak: (Default)

[personal profile] alierak 2015-07-10 06:36 pm (UTC)(link)
Well, those really are invalid US-ASCII characters... Looks like there is some Unicode in the comments, like \x{2019} (\xE2 \x80 \x99 in utf8), right single quotation mark.
alierak: (Default)

[personal profile] alierak 2015-07-10 06:43 pm (UTC)(link)
The one in htdocs/scss/skins/_nav.css is different, it adds a bullet between <li> items, so it seems integral to the functioning of the thing. I guess a better approach would be to figure out what's requiring this to be US-ASCII and see if it can be convinced to accept Unicode.
alierak: (Default)

[personal profile] alierak 2015-07-10 09:30 pm (UTC)(link)
[personal profile] kareila says probably something (compass?) changed with the upgrade and will take a look later if no one else has.
kareila: (Default)

[personal profile] kareila 2015-07-11 04:39 am (UTC)(link)
This has been filed as

Thanks for discovering this! It looks like the relevant production server didn't receive the upgrades that would produce the error when updating the live site.
alierak: (Default)

[personal profile] alierak 2015-07-11 04:49 am (UTC)(link)
Opened #1483. I found where people had run into the same problem on other projects and fixed it by adding '@charset "UTF-8"', so that's what I'd suggest we try.

It looks like we haven't hit this in production because we're doing all the build steps on the admin box, which hasn't been upgraded.