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

Should Babel have general support for UUID://...// convention? #4

Open
erkyrath opened this issue Jan 19, 2022 · 1 comment
Open

Should Babel have general support for UUID://...// convention? #4

erkyrath opened this issue Jan 19, 2022 · 1 comment

Comments

@erkyrath
Copy link
Member

This is the idea that, if all else fails, you should scan the file for the literal text "UUID://...//". Several existing formats work this way (Z-code, Glulx, Alan, HTML as a fallback) but it's never discussed as a general rule.

If we adopted it as a general rule, then new IF formats could provide IFID information to babel without having to go through a formal process of updating the spec and the babel source.

Secondary question: all files, or just files that babel doesn't recognize? In other words, should we add this as a fallback for Hugo, Adrift, TADS, etc? I don't expect this case would ever arise in real life, but it would make the implementation simpler.

@curiousdannii
Copy link
Member

Perhaps also ifid:...? possibly with a space after the colon.

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