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
Currently, the customZimTitle field that we send to the zimfarm is copied directly from the Builder name, which has no restrictions on its length, besides being truncated to 255 characters in the database. ZIM titles, on the other hand, can only be 30 characters max.
A couple of options:
Inherit the ZIM restriction and limit Builder titles to 30 characters
Truncate the Builder title when creating a ZIM
I tend to prefer the second option, because I don't see why the limitations of a ZIM should limit the entire WP1 UI.
The text was updated successfully, but these errors were encountered:
For me option 2 is not very good, because it means that we can get ZIM titles with a last word truncated in the middle (kind of ugly) and also duplicate ZIM titles (for different selections) due to identical first 30 chars among them.
I tend to prefer either option 1 (with a clear warning for the user) or a third option: add the ZIM title to information the user must input when creating a ZIM (just like description and long description) and automatically populate it based on the truncated Builder title. This way, the user will be able to do whatever is needed to make it look good.
Yes I like this new "option 3" as well: query for a separate ZIM title on the ZIM creation page, that is auto populated with a (possibly truncated) version of the Builder name. Then the user can decide how best to untruncate it.
Currently, the
customZimTitle
field that we send to the zimfarm is copied directly from the Builder name, which has no restrictions on its length, besides being truncated to 255 characters in the database. ZIM titles, on the other hand, can only be 30 characters max.A couple of options:
I tend to prefer the second option, because I don't see why the limitations of a ZIM should limit the entire WP1 UI.
The text was updated successfully, but these errors were encountered: