Skip to main content
Jun 13, 2016 12:56 PM UTC
Question

Unicode characters support in filenames

While testing unicode characters support in filenames (since I'm from Poland where we use them quite intensively and I was really happy to see Creo finally getting support of them) I've come across a rather unconventional behavior:

- when entering filename in all lowercase letters, all characters are converted into uppercase equivalents (as it worked since forever). All except non-ascii characters, like it's seen on screenshots.

new_object_small_letter.png

small_titlebar.png small_model_tree.png

- when entering filename in all caps, everything works as expected, with every letter displayed in uppercase.

new_caps.png

caps_titlebar.png  caps_model_tree.png

What's more, Creo considers both files as different models, while semantically both have the same name:

windows_utf.png

I think that can lead to potentially unwanted situations, where people will type model name with no regard for upper/lower case and in result will get two different models with what's seems to be same name. Also when saving both models from session, both are saved to the file with the same name (there is just one file łukasz.prt on disk, for example), so it can lead to situations where someone might involountarily overwrite previous model with new one.

What I'd expect when dealing with non-ascii characters is consistent behavior of converting lowercase special letters to their uppercase equivalents, so there won't be confusion in model names.

2 replies

Jun 13, 2016 1:14 PM UTC

Lukasz

thanks for your feedback.

I have forwarded this to R&D.

In particular it seems strange to me that I don't see the same behavior when trying it with German Umlaut characters.

For them, the conversion to uppercase always works as expected.

So, good catch. Thanks for your input, again.

Martin

Jun 14, 2016 12:39 PM UTC

Yes, we have the same problem with Czech letters in file names and features.

letters_high.png

Folder_letters_high.png