Skip to content

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

@erkyrath

Description

@erkyrath

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions