[suggest] rename image files on export

First of all, sorry for bad english :D

get the .capx file

Story ::

I dont' know well about server, and I uses hosting site (www.dothome.co.kr) for initial share of my project.

C2 preview and local test are work fine, But When I upload... :(

See the result

(I checked chrome for article, and It worked fine, but others...)

<img src="http://img507.imageshack.us/img507/3113/problemlo.png" border="0">

and CocoonJS cloud compilation made me same problem.

Title : Your compilation contains errors

???? (sender)

    : cocoonjsiyf@ludei.com 13.02.27 14:48

Hi,

your compilation of run! 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

Join our newsletter ludei.com/tech/newsletter.

devsupport@ludei.com

Why ::

BECAUSE My language is 2-byte-type. (korean.) and I used OBJECT NAME in My language for convenience. and Exported Project has same-name-images... Although It can't be loaded somewhere!

(* When I renamed all sprites/image using objects and exported to english, It worked fine on dothome.co.kr hosting site)

(Dropbox works well in this situation. weird. lol)

(see the dropbox uploaded project)

(detail : dothome.co.kr can't load korean-named files at all in firefox & ie. chrome loads half of them... (in direct-file access test of filename "??.html", Chrome failed to load. 404 error...)

But I can't give up convinience of naming objects in my language...

thus...

Suggesting ::

I'm suggesting "Automatically rename objects (,file names, variable names, etc...) to roman words on export" feature. and It can add a little security to exported projects!

thank you for reading this! :D

Any ideas? No response makes me not using my language on C2 and I think It reduces accessability of C2...

Is it tl;dr? In short, for security and compatibility reason, I think C2 needs an option that does change all 2-byte words to ASCII compatible and not-readable words... in exporting dialog, that means on-export time.

Manually doing that is quite dizzy stuff if you have many objects in own language. D: and... if you did your object naming to 2-byte, You will need changing it sometime!

Am I only person that think it's needed? Is there no 2-byte language people using C2, and feeling alike me?

None of your links work for me, and your explanation is not very clear.

Are you suggesting that C2 renames files just because some servers don't recognize your language?

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.

As far as I am aware, Construct 2 correctly handles unicode. It exports everything including the Javascript contents and filenames in UTF-8. Perhaps there is a server configuration issue that is causing a problem; if the server is trying to use a different codepage, it might corrupt the file contents or fail to locate files. It's hard to comment further without an up-to-date example.

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.

Hello,

everything works for me - korean text, korean project files, korean variable names.

Example project:

dinorpgtools.netii.net/1

capx that was exported: s000.tinyupload.com/index.php

tested and works in Opera, Chrome and IE.

The biggest problem are probably file names, as older browser or unfitting server configuration might have problem with unicode characters like Hangul, so it should be a good idea to rename them in your project. Auto-rename as extra option probably wouldn't hurt.

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.

Since it works fine on Dropbox, this strongly suggests Construct 2 is exporting everything correctly and the dothome.kr host and CocoonJS incorrectly handle unicode. So the correct solution is for these other services to fix their bugs, not to change anything in Construct 2.

You should report the unicode problems to Ludei and dothome.kr.