-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Unexpected response from /rest/getIndexes endpoint #184
Comments
Hello! Yes indeed it is currently implemented this way. |
Excellent question and I am not sure what the correct answer is. Sorting (and by extension creating an Index) for non-Latin characters is a widespread challenge. However, what I have seen other programs do is rely on the Other non-default tag combos include So for example:
That would also address names that are in RTL scripts such as Arabic:
So I guess the logic would be if there is an Thoughts? |
First of all, really like this software - especially since it is the only Subsonic compatible server software that I have found that correctly parses multi-value attributes for the Artist tag - so thanks for that!
While investigating some weird behavior on a client app - specifically iSub on IOS - I noticed that the result of the
/rest/getIndexes
endpoint was not what I was expecting. Put simply, all of the returned artists were showed<index name="?">
instead of being broken up into separate letters.I confirmed this by doing a curl command to the server - specifically this command:
The result is this - sample.xml
Expected result
This is the result that I expected - expected.xml
Is the expected result a correct assumption?
I am using the epoupon/lms Docker container of version 3.27.0 for amd64, digest 5ab9b8f92072.
Thoughts? Thanks!
The text was updated successfully, but these errors were encountered: