Skip to content

Repeated no info available fields #634

Open
@mattgarrish

Description

@mattgarrish

Would it be possible to define a single "no-info-available" ID to use whenever the generic "No information is available" string has to be output?

Right now, each category defines its own version of this string, which from a maintenance perspective looks like a source for errors to get introduced and from a translation perspective looks like a lot of redundancy.

Only the ways of reading section tailors these messages to the output, so those would need to stay.

Metadata

Metadata

Assignees

No one assigned

    Labels

    a11y-display-guideIssue with the UX Guide principles or techniquesa11y-display-techniques-epubIssue with the epub accessibility metadata display techniquesa11y-display-techniques-onixIssue with the onix accessibility metadata display techniquesfuture work

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions