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

Repeated no info available fields #634

Open
mattgarrish opened this issue Jan 29, 2025 · 2 comments
Open

Repeated no info available fields #634

mattgarrish opened this issue Jan 29, 2025 · 2 comments

Comments

@mattgarrish
Copy link
Member

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.

@GeorgeKerscher
Copy link
Collaborator

I think this would be dood to do.

@gregoriopellegrino
Copy link
Collaborator

We have a problem: in techniques we use the HTML id attribute for strings, which must be unique for each document.
Possible solution, switch to a data-* attribute, as we did for principles.

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

3 participants