This will be the successor of PlistJsonConverter. SerializedDataConverter will convert plists, yaml and json to each other.

I have added a built-in yaml highlighter because sublime's yaml highlighter isn't even that usable. You can override the one I provided with Sublime's, or you can override with others such as AAAPackageDev's yaml. I personally am not using AAAPackageDev at this time its rules were a bit too sublime settings specific with keys and some other minor things. With that said, mine has flaws as well. I am working on yet another yaml highlighter to replace the current one which uses a different approach, to hopefully improve highlighting overall with yaml, and I also plan to look into AAAPackageDev's version as well to see if its flaws can be improved and even replace mine. Overall, I feel that PackageDev's and mine will allow you to edit languages and Sublime settings much better than Sublime's built-in one. If you want to use them to edit general yaml files outside of sublime settings, you can evaluate which one works better for you, or use something else entirely.

I also added a little extra feature as well. When working with sublime settings, you can use !!regex (which is mapped to !!str for conversion), and it will highlight your data with regex highlighting. This way it isn't too sublime-specific, but you can still use it to edit tmLanguage files.

If you have old json languages, you can convert them to yaml as well. You can convert yaml, json, and plist between each other (at least for basic stuff, I am still not sure about all of the yaml features and if they all translate, but as far as sublime languages, themes, settings, they should all translate back and forth to any of the supported formats.

Includes fixes for better output, and fixes to the built-in tmLanguage. Remember, if you don't like the yaml tmLanguage I provided, just override it in the settings file. I realize that most yaml tmLanguages have issues, and mine is no exception, so use the one that is best for you. I am working on yet another one to replace the current one I include (hopefully), I realized I would need a different approach to handle different formats of yaml to make this work as a decent general yaml language file, but again, this can always be overridden if you prefer other great yaml tmLanguages such as AAAPackageDev (one I am still looking into as a possible permanent replacement).

Edit: That reminds me: I actually worked on a syntax definition for generic YAML before the one I made for AAAPackageDev but eventually considered it to be too much of a hassle because YAML is not really a regex language and then didn't look back at it again. I didn't make much progress though so it's not worth looking at.

Yeah, I know what you mean. I had to take a break. It is so labor intensive to come up with a general YAMl language. The language is a bit too flexible when it comes to trying to highlight it. And everything can take on so many varying forms.

SerializedDataConverter has now replaced JsonPlistConverter in Package Control (though it does not right now include the discussed YAML tmLanguage file which is a separate side project that I will make available).