[oz1]

What you are asking for doesn't fit cleanly into the current design, because the user can order the fields in any way they want, and include any fields they want. Being able to specify different font properties only for specific fields being referenced means either needing a verbose complex syntax such as  %COLLECTIONS: Font(arial, 15pt)%, or having a font override for any field other than the title. This makes the rendering of the text significantly more complex and costly too. I then can't use a single TextView element to render the text - I either have to split it up into multiple elements stacked horizontally (which then introduces wrapping issues with long text across multiple lines) or I have to switch to using something that supports spans with rich text, which will be much slower, potentially impacting scrolling performance. I can't also easily handle it one way for users that want a custom font and another way for users that don't - it would become a nightmare, so it needs to be the same implementation regardless of the selected settings.

The second request is possible if I add a new "Group Song Title Formatting" setting and then use that instead of the standard song title formatting only when viewing songs under a group. I'd like to hear from more users as to whether this would be useful/desired though.

Mike

yes I understand the complexity, that makes total sense.
If you did thew second request that would totally work for me (I'm not sure what "group" refers to, but I assume it distinguishes between the song list and the setlist).

BTW I found the advanced formatting: very complex but awesome!   Although: the song title formatting is not copied to the sync'ed client when using the "sync library" even if all the options are checked in the server's "device sync activity"