Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad encoding on export #113

Closed
jwise-mfg opened this issue Jun 27, 2024 · 3 comments · Fixed by #114
Closed

Bad encoding on export #113

jwise-mfg opened this issue Jun 27, 2024 · 3 comments · Fixed by #114
Assignees

Comments

@jwise-mfg
Copy link
Member

Saving a Profile locally results in an Encoding that is not compatible with tools like Prosys Forge. Changing the text encoding from UTF-8-BOM to UTF-8 would solve this issue.

@jwise-mfg
Copy link
Member Author

Although the text in the XML claims UTF-8, examining the document with a tool like Notepad++ shows its not actually encoded that way.
WrongEncoding

@scoxen1 scoxen1 self-assigned this Jul 16, 2024
@scoxen1
Copy link
Collaborator

scoxen1 commented Jul 16, 2024

This appears to happen when trying to download a profile that the user has created within Profile Designer. A fix has been applied and is in stage site for testing.

Note: When downloading a Cloud library profile, this does not appear to be a problem because that type of download is likely pulling the original XML file produced by Cloud Library.
Note: I did confirm in notepad++ that the encoding is correct but did not test in Prosys Forge.

@scoxen1 scoxen1 linked a pull request Jul 16, 2024 that will close this issue
scoxen1 added a commit that referenced this issue Jul 30, 2024
@scoxen1
Copy link
Collaborator

scoxen1 commented Jul 30, 2024

Deployed to live site. Marking done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants