I wonder if anyone can help me with this. We are using perforce for version control. Every time I check in a script and someone else syncs that script, the font get changed to what looks like Chinese, and everything breaks. Does anyone have any idea why this would be happening?
If you create a script file with notepad (foo.cs) and add it to p4, then sync it, does it have the same problem?
Monodevelop is a bit spotty putting the BOM at the top of files (ie., during certain operations such as find/replace in files, it incorrectly adds or removes a gratuitous BOM), but I can’t imagine it turning your text into garbage. That seems a bit of a fetch for what a bad BOM can do.
Can you show us what the corrupted data looks like?
Also:
http://answers.perforce.com/articles/KB/3488
Though it should be utf-8, just looking up errors for perforce corrupting text.
Here’s another talking about it corruption:
http://answers.perforce.com/articles/KB/3096
They both talk about line endings, which I know I often have issues with. I’ll sometimes open files from MonoDevelop in Visual Studio, or vice versa, and it bitches about malformed line endings. Because Window prefers the cr/lf format.
Anyways, this is a possibility. We don’t use perforce though, so I don’t much else.
Can you share the Perforce settings on the script files i.e. text, binary, etc. As shown in the p4v GUI/properties.
Also can you tell if the script file is a plain ASCII file or BOM encoded
Can you share the Perforce client/workspace settings for both users to see how line endings are being translated.