While voices uses a fairly elaborate sort by default, we'd still like to make sure that implementers have full control over that by exposing the following means of sorting voices:
- quality
- name
- language
- region
- gender
On language and region, an optional parameter should also allow implementers to support some languages/regions at the top by passing the equivalent of navigator.languages.
The typical use case for that would be that if my device returns en-us and fr-fr, then sorting all voices by language with this optional parameter should return English and French at the top, before every other language ordered by alphabetical order.
While sorting by regions on a list of voices filtered by English should put the US at the top, before every other region ordered by alphabetical order.
Ideally we would also support the ability to sort languages/region either based on:
Switzerland is a good example of that since its code is "CH".
While voices uses a fairly elaborate sort by default, we'd still like to make sure that implementers have full control over that by exposing the following means of sorting voices:
On language and region, an optional parameter should also allow implementers to support some languages/regions at the top by passing the equivalent of
navigator.languages.The typical use case for that would be that if my device returns
en-usandfr-fr, then sorting all voices by language with this optional parameter should return English and French at the top, before every other language ordered by alphabetical order.While sorting by regions on a list of voices filtered by English should put the US at the top, before every other region ordered by alphabetical order.
Ideally we would also support the ability to sort languages/region either based on:
Switzerland is a good example of that since its code is "CH".