You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What are the reasons for appstream-glib for not following the "ideally not more than 256 characters" recommendation of the standard and not allowing a dot at the end of a caption?
I haven't seen any use of captions in Software or on Flathub but I would like to use them on apps.gnome.org. However, the limitations seem a bit harsh to me.
The text was updated successfully, but these errors were encountered:
tbh, 256 characters is probably waaaaay too many for a caption. I should change the specification to recommend something like max 100/120 instead, actually. People shouldn't write tutorials and novels in short caption texts.
That's also the reason for the "no dot" rule: This is not supposed to be a full text. The AppStream reference implementation has similar checks actually, but they won't make your data invalid. You will get a notification about this though if you run appstreamcli validate.
I haven't tested this, but I think when using validate-relax even appstream-glib will not be so violent about missing dots and fail validation.
What are the reasons for appstream-glib for not following the "ideally not more than 256 characters" recommendation of the standard and not allowing a dot at the end of a caption?
I haven't seen any use of captions in Software or on Flathub but I would like to use them on apps.gnome.org. However, the limitations seem a bit harsh to me.
The text was updated successfully, but these errors were encountered: