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
The current EPUB 3.2 draft is a little bit inconsistent in that regard, but it seems to expand the scope of this attribute:
Allowed on: dc:contributor, dc:creator, dc:publisher, dc:title and meta.
It's also worth pointing out that Calibre introduced its own element for sorting titles (calibre:title_sort), probably because it had a strong use case for it, yet it felt like opf:file-as didn't allowed that (which is probably true).
Based on @dauwhe feedback, this might be eventually dropped in EPUB 3.2 but it's worth hearing from the wider community (cc @kovidgoyal, @kevinhendricks) about their need for sortable strings.
Sortable strings are primarily meant for user agents that provide a way for the user to filter and sort their publications based on such strings.
The text was updated successfully, but these errors were encountered:
Sortable strings are important for calibre. They are used when sorting on title, authors and series. This is done because there is no foolprof algorithm for generating the correct sort order for these fields, especially since the rules for sorting them vary between cultures. So calibre auto-generates a sort value for a given field but also allows users to override it, as needed.
This is based on my gap analysis between EPUB 3.2 and WP: #176 (comment)
EPUB has the concept of a sortable string through the use of
opf:file-as
.In EPUB 2.x this was limited primarily to
creator
andcontributor
.EPUB 3.0.x muddle things up since it introduces refines but it's primarily directed towards
creator
andcontributor
once again.The current EPUB 3.2 draft is a little bit inconsistent in that regard, but it seems to expand the scope of this attribute:
It's also worth pointing out that Calibre introduced its own element for sorting titles (
calibre:title_sort
), probably because it had a strong use case for it, yet it felt likeopf:file-as
didn't allowed that (which is probably true).Based on @dauwhe feedback, this might be eventually dropped in EPUB 3.2 but it's worth hearing from the wider community (cc @kovidgoyal, @kevinhendricks) about their need for sortable strings.
Sortable strings are primarily meant for user agents that provide a way for the user to filter and sort their publications based on such strings.
The text was updated successfully, but these errors were encountered: