contents do not match the encoding when sharing a project to
When sharing a project, we have some files that are using a different
encoding and we receive the error "<file> has character encoding Cp1252 but the contents do not match the encoding. Change the encoding of the file or the default for the project." on a handful of files being shared. These files are flat text files for different language versions of a license... in the case of the errors, they are all Asian languages. I suppose the proper way to handle this is to set the properties on each of these files to the appropriate encoding, but I'm surprised the "importer" can't figure that out based on the content of the file. To work around the issue, I updated the file properties preferences indicating to treat these as binary files (if I knew the proper encoding to use for each file, I'd set it). I assume this is OK as I don't expect they will ever by edited and we can always set the encoding later on. Is this valid thinking? Thanks, Brian |
One answer
Ideally you would find out the encoding. Setting the line delimiter to NONE is a reasonable thing to do. If you decide to edit them (and merge them) you will need to know the encoding. You may also have difficulties viewing them via the web.
When sharing a project, we have some files that are using a different |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.