# Picard 2.0.3 released: Crash-fixes and scripting improvements **URL:** https://community.metabrainz.org/t/picard-2-0-3-released-crash-fixes-and-scripting-improvements/393584 **Category:** MusicBrainz Picard **Created:** [August 10, 2018, 3:37pm UTC](https://community.metabrainz.org/t/picard-2-0-3-released-crash-fixes-and-scripting-improvements/393584 "2018-08-10T15:37:34Z") **Posts on this page:** 1 **Showing post:** 3
### Author: ![hiccup](https://community.metabrainz.org/user_avatar/community.metabrainz.org/hiccup/32/5512_2.png) [@hiccup](https://community.metabrainz.org/u/hiccup) #### Post date: [August 10, 2018, 5:55pm UTC](https://community.metabrainz.org/t/picard-2-0-3-released-crash-fixes-and-scripting-improvements/393584/3 "2018-08-10T17:55:25Z")
Great, thanks @samj1912 I was wondering, could you comment on this observation I have made earlier? : > [@Picard 2.0.2 released! Signed macOS releases!](https://community.metabrainz.org/t/picard-2-0-2-released-signed-macos-releases/390756/34): > > Suppose you have a simple script like this: $set(DISPLAY ARTIST,%artist%) (note the use of capitals) Using that, on a first run Picard will show ‘DISPLAY ARTIST’ in the first column of the bottom pane. But when you save the result, and then scan the release again, it will display a populated ‘display artist’ (lower case), and add a second line with a blank ‘DISPLAY ARTIST’ that it offers to populate. So you now have two display artists in the left column. Is this expected behaviour? edit: … . And another thing I noticed: The input for the ‘preserve these tags’ option seems to be case-sensitive. I myself can not think of any useful reason that it is. On the contrary, it makes it more troublesome to get it working, since you’ll have to worry about idiosyncrasies of other software and the different codecs you might be using. Do you agree? Could it be made case-insensitive? --- _[View the full topic](https://community.metabrainz.org/t/picard-2-0-3-released-crash-fixes-and-scripting-improvements/393584)._