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

Get help using Construct 2

Post » Tue Jan 13, 2015 8:21 pm

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...?
Last edited by condolent on Thu Jan 15, 2015 7:02 pm, edited 1 time in total.
Website Twitter Indie Developer
B
20
S
6
G
4
Posts: 206
Reputation: 2,954

Post » Wed Jan 14, 2015 11:17 am

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.
ImageImageImageImageImage
B
19
S
5
G
1
Posts: 614
Reputation: 2,542

Post » Thu Jan 15, 2015 4:55 pm

@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)?
Website Twitter Indie Developer
B
20
S
6
G
4
Posts: 206
Reputation: 2,954

Post » Thu Jan 15, 2015 5:05 pm

It looks like bad news for you -> utf-8-charset-problem-ejecta-tested_t120468
ImageImageImageImageImage
B
19
S
5
G
1
Posts: 614
Reputation: 2,542

Post » Thu Jan 15, 2015 7:02 pm

@TheWyrm no problem, solved it by setting the encoding language to something else in xcode for data.js
Website Twitter Indie Developer
B
20
S
6
G
4
Posts: 206
Reputation: 2,954


Return to How do I....?

Who is online

Users browsing this forum: Baidu [Spider], dop2000 and 37 guests