Skip to content

Add config option to limit which string literal encodings are used#356

Merged
LagoLunatic merged 9 commits into
encounter:mainfrom
LagoLunatic:encoding-config
Jun 1, 2026
Merged

Add config option to limit which string literal encodings are used#356
LagoLunatic merged 9 commits into
encounter:mainfrom
LagoLunatic:encoding-config

Conversation

@LagoLunatic
Copy link
Copy Markdown
Collaborator

@LagoLunatic LagoLunatic commented May 31, 2026

Adds a new "Preferred string encoding" dropdown option to specify which encoding objdiff should try to use for decoding all string literals.
image

The default option is "Auto" which retains the current behavior of displaying strings with every supported encoding. If any other option is selected, then only that one encoding will be displayed. This also affects diffing results, and specifying the correct encoding can help prevent false mismatches from appearing.

It's recommended to force this option via per-project objdiff settings. For example, dtk-template projects can put the following in configure.py to use Shift JIS encoding:

# Optional extra arguments to `objdiff-cli report generate`
config.progress_report_args = [
    "--config preferredStringEncoding=shift_jis",
]

Comment thread objdiff-core/config-schema.json Outdated
let rect = rect.shrink(4.0);
let color = ui.visuals().text_color();
let line_stroke = Stroke::new(1.0, color);
let line_stroke = Stroke::new(1.0_f32, color);
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

was this a clippy thing or something

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Owner

@encounter encounter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@LagoLunatic LagoLunatic merged commit 8b1b4a9 into encounter:main Jun 1, 2026
23 checks passed
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 this pull request may close these issues.

2 participants