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

Suggestion: Automatically normalise archive names #3

Open
mariomadproductions opened this issue Apr 17, 2023 · 2 comments
Open

Suggestion: Automatically normalise archive names #3

mariomadproductions opened this issue Apr 17, 2023 · 2 comments

Comments

@mariomadproductions
Copy link

As DoM only supports ASCII/windows-filesystem-compatible filenames.

@mariomadproductions mariomadproductions changed the title Feature request: Automatically normalis archive names to ascii Feature request: Automatically normalise archive names Apr 17, 2023
@DarkMatterCore
Copy link
Owner

This is gonna be a little bit tricky, specially for Cyrillic and Asian strings. Special characters out of the ASCII range can just be removed or replaced with something else, I guess.

If there's some sort of library or module to handle string romanization, it'd be the best course of action.

@mariomadproductions
Copy link
Author

Sometimes its just something like a long-dash, or trademark sign - those can be converted to short dat and removed, respectively. But for Cyrillic and Asian scripts, yeah a romanisation library would need to be used - they do exist. Additionally, the user could pass in the No-Intro dat file, so that it could re-use already-romanised titles, in cases where the base title id already exists in the dat file.

@mariomadproductions mariomadproductions changed the title Feature request: Automatically normalise archive names Suggestion: Automatically normalise archive names Apr 17, 2023
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

No branches or pull requests

2 participants