The exact situation... is not-ascii object name makes none-ascii named image files, and It makes every problem.
None of your links work for me, and your explanation is not very clear.
Sorry for that, recently I moved many files... and more...
== What is the exact problem ==
Now I know by experience, The problem is only related to file names, as mindfaQ said.
== On dothome.kr, hosting service ==
* Korean exported one - Chrome was able to load correctly, but others not. (FF, IE) but now, chrome can't load it too.
* English renamed & exported one - All works fine.
* ??.html on dothome - Can't loat at any browsers. :(
* smiley.html on dothome
Yes, dothome can't load not-asciied one, because of their server problem.
== On dropbox ==
All works fine.
* Korean exported one
* English renamed & exported one
* .capx file in korean-object-named
* .capx file within renamed-object
== Doing ludei 's Cloud compiling for Android, play store ==
* Exported files & stuffs with korean-named images - fail
* Exported files & stuffs with renamed stuffs - success
First one fails because of their file name. second one compiles well.
Hi,
your compilation of ER_proto seems to have failed, here's the information we have about the problem:
Some filename in the submitted ZIP file has invalid characters. File path: .png
This is an automatically generated email, so please do not reply.
Ludei Team
Are you suggesting that C2 renames files just because some servers don't recognize your language?
Almost. In exactly,
* In Ludei 's cloud one (It is their problem),
* My hosting site (and It is too),
* Not chrome (yeah, It is their's, too...)
but Too many? At least on my think, Avoiding to make problem is valueable one....
If so, I would say that it's not really up to Scirra to fix such a thing. You should use a naming convention that is compatible with as many systems as possible.
Agree in partially, but I think avoiding to use of their (... in this case, my) own language in easy-going tool... especially naming objects, makes accessibility lower.
As far as I am aware, Construct 2 correctly handles unicode.
Yes, you're exactly right, And I like it very much. But, ... wait, What I saying is, Non-ascii problems happen all the ways in other fields... especially in this case, filename.
I'm also not sure if we can automatically rename files without possibly causing naming conflicts. I also don't want to make Construct 2 rename things if the problem is just with the server.
Yes, now I think It's their problem, But is renaming file names on export that hard? maybe then, I'm requesting too much thing...
And Why I suggested to rename all stuffs in project Is because of messing around to make not-readable one. In these days, I think doing all that are not important. I was too short to say that. sorry.
But still I suggests feature that renaming file name on export, especially image files.