Changed encoding used by IntegrityCheck #8359
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #8022.
Previous method used
System.getProperty("file.encoding")
to get the current character encoding).Changed to use,
bibDatabaseContext.getMetaData().getEncoding()
preferencesService.getGeneralPreferences().getDefaultEncoding()
Todo:
I don't think it can distinguish GBK from UTF-8CHANGELOG.md
described in a way that is understandable for the average user (if applicable)Tests created for changes (if applicable)Screenshots added in PR description (for UI changes)Refs issue #5850 and PR #7639