How do I fix the UTF-8 bug with ejecta? [Solved]

Post reply

❤Follow Topic(2)

0 favourites

5 posts

From the Asset Store

Bug Match

$5 USD

Match same tiles with each other as fast as you can and earn more score during a limited time!

01smile

- condolent
- - Joined 25 Feb, 2013
  - 61 topics • 206 posts
- 1
- 13 Jan, 2015
- Quote
I just recently updated my CO2 from r170 to r190. When I exported my app with ejecta, I noticed that it somehow didn't allow UTF-8 characters and just made some weird characters instead. (UTF-8 characters like åäö). Even images including åäö doesn't load when testing the app in xcode. And the text just makes some really weird characters instead.

Is this a ejecta/construct 2/xcode issue?

Anyone know how to fix this? Or do I have to stay on r170 forever...?
- TheWyrm
- - Joined 9 May, 2014
  - 86 topics • 613 posts
- 1
- 14 Jan, 2015
- Quote
Depends when it was lost. If it's fine when it's exported from C2 you can open the offending file in something Like notepad++, set it to the right UTF characters and then save it before continuing onto the next step.
- condolent
- - Joined 25 Feb, 2013
  - 61 topics • 206 posts
- 1
- 15 Jan, 2015
- Quote
TheWyrm I checked data.js with notepad++ before and it was in the UTF-8 encoding. Maybe it's supposed to be in UTF-8 (without BOM)?
- TheWyrm
- - Joined 9 May, 2014
  - 86 topics • 613 posts
- 1
- 15 Jan, 2015
- Quote
It looks like bad news for you ->
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- condolent
- - Joined 25 Feb, 2013
  - 61 topics • 206 posts
- 1
- 15 Jan, 2015
- Quote
TheWyrm no problem, solved it by setting the encoding language to something else in xcode for data.js