Strange symbol in file name

[Anonymous]

We received some files from customer as a zip file 

In that all diameter symbols in file name showing like ¥ instead of Ø

Due to this assembly showing missing links please see the attached image 

Kindly suggest how can i solve the symbol problem.

If same file will open at customer location it showing correct symbol

[-niels-]

Welcome to the community!

If you resolve all the missing links to the filename with the strange character and save it, it will work like it should.

What I'd suggest is renaming the files to something that doesn't use a special character... like changing the "ø" to "d" for diameter.
That way it will always resolve properly, no matter who you send it to.
(so maybe let your customer know this as well...)

In early windows days (man that makes me feel old...) it wasn't allowed to have special characters in filenames, even spaces weren't allowed.
It might be nice that we can use those now, but it can cause problems like this.

Hope this helps.

[Roelof.Feijen]

I agree with @-niels- that it is better to not use these symbols in file names. 

If have seen the same problem with other customers in the past. 

But the advice, of not using these symbols in file names, doesn't solve your problem. 

I wonder if anyone else have a suggestion how to solve this. 

Is it Windows related? Missing fonts? Regional settings? Unicode?

[Anonymous]

Thanks for your reply Mr. @-niels-,  @Roelof.Feijen

If i save with strange symbol "¥" i dont have any problem to work but same file i have to submit to customer.

at customer location (Computer) the file name automatically updating to "ø" and asking link with "¥"(in my computer viseversa)

i can't change the file name because we received from customer and it is generated default program (Published by contentcenter)

I am working from India and my customer location is the Netherlands. 

So I hope this is Windows related? Missing fonts? Regional settings? Unicode? @Roelof.Feijen

for example attached here one simple assembly as a zip file for your reference.

In my computer file name look like below snap

Please let us know while opening the attached file at your location whether it asking for resolve link with file or not and the symbol updating or not.

My goodness you are also from the Netherlands location(same as my customer).

Please suggest which settings i have to change.

Regards,

Naresh Manda

[mdavis22569]

Are you using a Vault .. on your end? 

If not, consider it for the re-naming/path part of it. Let it do the work for you.

However I have worked with a customer in another country, had this issue, and left it alone and just kept working. Especially if you guys will be sharing models and you need to keep renaming. 

[stuart_smith82]

Hi,

I think your client has created a file name in the content centre or an iPart with a character or symbol that windows cannot create and when the file is generated in windows explorer it is substituted. I have seen this issue a lot with customisation of the content centre and illegal characters. Other scenarios where I have seen this is not having the correct language fonts installed.

Thanks

Kind Regards

Stuart Smith

Group Data Management Consultant

[email protected] | www.graitec.co.uk

Blog: http://www.graitec.co.uk/blog/blogger/smith

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.

[-niels-]

---

@Anonymous wrote:

Please let us know while opening the attached file at your location whether it asking for resolve link with file or not and the symbol updating or not.

My goodness you are also from the Netherlands location(same as my customer).

Please suggest which settings i have to change.

---

@Anonymous,

I opened your zip package and it contained a filename with the diameter symbol and the example.iam.

When i opened the example.iam it asked to resolve to a file with the yen symbol.

So if you packaged it with a yen symbol, it got changed back to diameter for me.

Other than the inconvenience of having to resolve the files it should not pose any problems for your dutch customer if you leave the filenames as they are.

(assuming you didn't change the symbol, ofcourse)

It is probably related to your computer's regional settings as @Roelof.Feijen suggested, but i'm not sure if changing that is convenient for you as it might change too many things.

So, i'd suggest that you ask your customer if they have a problem with having to resolve their files because of this.

Just explain that it's most likely a regional settings issue and that it has no influence on the actual data as long as you don't change the filenames.

If they do have an issue with it, then suggest to them to change the diameter symbol do a letter so it can't go wrong.

This might involve them having to change their content center libraries, which would be more work then just resolving a few files.

These are my personal opinions, it could well be that company policies dictate otherwise for your situation but i hope this helps.

[Roelof.Feijen]

@Anonymous

I see the same issues as @-niels-.

Do you use SmarTeam?

If so, can we do a little test to see if this is caused by SmarTeam.

I know a customer in the Netherlands, using Inventor and SmarTeam, having the same issue.

If I analyse your Assembly with VBA I see a FullFileName with the diameter symbol.

Please create an Assembly and Part (with diameter symbol in the file name) outside SmarTeam.

I don't want any interaction with SmarTeam, just to see if this is caused by the SmarTeam integration.