Georgia looks and functions best when you tag your files liberally with lots of metadata. I have very strict standards in my library about tag field names, but I understand that no one else will follow the same standards, so this page will document some best practices and also discuss how to adjust the theme to use your own personal field names.
I personally recommend the foo_musicbrainz tagger component as it is integrated with foobar2000, and the default tag field names are the same ones this theme has configured by default. Also, I’m the maintainer of foo_musicbrainz, and future updates to that component will be reflected in Georgia as well. Synergy!
There are plenty of other great taggers out there, but all of them will differ from the field names used in Georgia in minor/major ways. Fortunately you don’t need to give up your favorite tagger or alter your workflow as you can easily edit the fields used throughout Georgia in the config file. As of version 2.0.2, Georgia also has limited support for some default fields populated by foo_discogs.
No problem! Don’t update all your tags (unless you really want to)! Because of the amount of information and metadata displayed, Georgia was designed to make it easy for users to be able to change the field names that it looks up. You’ll need to open up the config file, and go to the
title_format_strings section. Find the property you want to update, and just change the value.
Let’s say you tag your vinyl files using
%vinyltrack% and so Georgia never displays vinyl-style track notations. In the config file find this section:
…and then edit those strings to reflect the fields tagged in your files:
georgia-config.jsonc and then reload the theme (right-click on the panel background). You should now see your corrected fields showing up. Georgia only reads the config file once at startup, so any changes made in the file are not reflected until a reload occurs.
See the Title-Formatting fields page for a detailed list of every Title-formatting string property that Georgia uses, what that property is used for or means, and when and where in the UI that property can be seen.