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

Inconsistent file extension handling #2

Open
hcs64 opened this issue Jan 7, 2025 · 0 comments
Open

Inconsistent file extension handling #2

hcs64 opened this issue Jan 7, 2025 · 0 comments

Comments

@hcs64
Copy link
Owner

hcs64 commented Jan 7, 2025

The input setup will try set the input file extensions to .subcode and .toc, with the intention that it can be used with just image_name and it will find image_name.subcode and image_name.toc. But if the image name has a dot in it like image.name, then the final part gets replaced (image.subcode).

Better logic would be:

  • Try opening as-is (so it can be called, as in previous versions, with image_name.subcode)
  • If not found, try adding (not replacing) .subcode

Then to find the toc:

  • If the subcode was successfully opened in a file ending in .subcode, replace the extension with .toc
  • Otherwise probably just don't try to find the toc? Maybe try adding it?
  • Take a command line option that specifically says where to find the toc?
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

1 participant