[NeoCZ]

In MobileSheets if song starts with special characters linke ž ř č é, these songs are sorted last in the library after "Z". Would it be possible to have them sorted after "main character - for example č after c, é after e, etc.? Or would it be possible to make your own sorting rules where you can set where will these characters appear?

[Zubersoft]

Adding sorting rules would be quite difficult to implement, but I'm already planning on using a collator during sorting that applies rules specific to each locale. Hopefully after I add this, the special characters will be handled correctly. I will need user feedback to know for certain though.

Thanks,
Mike

[zissakos]

I absolutely support this since I am having the exact same problem with greek characters (as mentioned in the other thread).

I will be very happy to help testing this. Just contact me.

[FiddlerJeanne]

And a related request for searching: I'd love it if searching ignored special characters by treating them as the unmodified equivalent (as Google search does), i.e., when I search for "Rattvik polska", it should retrieve both "Rattvik polska" and "Rättvik polska". Any possibility?

Why: quicker for me to search that way, plus it means if I'm unsure (or the title is incorrect) I can still find it easily.

[Zubersoft]

Just fixed this for the next update - special characters will now be ignored while typing in search terms. It doesn't seemed to have affected the speed of the filtering very much, so hopefully people won't even notice it.

[sciurius]

special characters will now be ignored while typing in search terms

Ignored? When I enter “Sinéad O'Connor” or “Duše Mé Lásky”, what will be searched?

[FiddlerJeanne]

Just fixed this for the next update - special characters will now be ignored while typing in search terms. It doesn't seemed to have affected the speed of the filtering very much, so hopefully people won't even notice it.

Thank you!

[Zubersoft]

Ignored was probably a poor choice of word. Special characters will be converted to their standard English character equivalent if possible. So Sinéad O'Connor would become Sinead O' Conner. Having said that, I just realized that I converted the special characters of the song fields before doing comparisons, but I did not convert the special characters of the text in the search field. So I would not be surprised if I now made it impossible to search using special characters.

[sciurius]

We'll see ...

[akoster]

Ignored was probably a poor choice of word. Special characters will be converted to their standard English character equivalent if possible.   So Sinéad O'Connor would become Sinead O' Conner. Having said that, I just realized that I converted the special characters of the song fields before doing comparisons, but I did not convert the special characters of the text in the search field.  So I would not be surprised if I now made it impossible to search using special characters.

According to the National Information Standards Organization, you are handling these correctly by converting to the standard English character for sorting and searching.
http://www.niso.org/publications/tr/tr03.pdf

What would be nice is if you were to also follow their recommendation for ignoring punctuation (defined as follows):

The following punctuation marks should be disregarded for arrangement purposes:
period (full stop), comma, semi-colon, colon, parentheses, square brackets, angle
brackets, braces (curved brackets), apostrophe, quotation marks (single or double), exclamation
mark, question mark. They are not to be treated as spaces.

As an example, currently these two songs sort in this order
 Jesus Shall Reign
 Jesus, Draw Me Ever Nearer

Proper Library sort order would have them in the opposite order, ignoring the comma in the title.

[Zubersoft]

Thank you for the suggestion akoster. I've updated the code, and it now ignores punctuation while sorting or filtering.

[akoster]

Thank you for the suggestion akoster. I've updated the code, and it now ignores punctuation while sorting or filtering.

Thank you!

[TCsheets]

My song titles are set up to identify a source that is embedded in the song title for my easy reference. The abbreviation for the source is offset by a dash "-" which, of course is a punctuation mark. I do the same for original key.

It appears then that I can not sort/filter on my abbreviations using the "-" dash as the demarcation of the abbreviation.

For example, filename: SongTitle-F-KS.pdf, in MS would show as "Song Title-F-KS" and if I want to find all of the songs with the "-KS" source I would search on "-KS" or find songs in the key of "F" I would search on "-F"; however, the dash is not included in the search so it finds all songs with "KS" or songs with an "F" which is not what I want.

Is there a way to have the search include actual characters in the name? For example, search on "-"+"KS" or "-"+"F" or something like that?

Thanks,

Todd

[Zubersoft]

There is no option at the moment for a literal search - that is something that is going to have to be added. It might be worthwhile to actually use dedicated metadata fields as you can filter on those fairly easily (i.e. you could put KS in one field and F in another).

Mike

[TCsheets]

Mike:

Thanks for the fast response.

I will utilize the metadata option where feasible, but I like to embed as much information in the filenames themselves so that I don't need to rely on having to do more manipulation once loaded into the program...

Thanks!
Todd