[Zubersoft]

Unfortunately, annotations are just anchored to a specific point on the page - there is no correlation between their positioning and rendered content in the file. In order to support what you are describing where annotations could move as the font sizes increase or decrease, the entire implementation would have to be changed so that each annotation is anchored to something on the page (i.e. the nearest word). This still isn't guaranteed to provide exactly the results you would want either, as the things on the page can shift a great deal as the font sizes increase, and annotations could very quickly be moved off the page. There is also the issue where the file could be edited and the anchored word could be removed and so there would have to be a great deal of code to ensure annotations always have a valid anchor point after a file is edited (which would be complex to implement). These kinds of changes also means that the annotation implementation would have to be significantly different for chord pro files versus other file types, increasing the likelihood of bugs. It also would increase the workload as any change to annotations would have to be tested independently on chord pro files to ensure it wouldn't break things. 

If someone else has an idea about how this could be implemented, I'm all ears, but chord pro files are just text files so nothing complex can be stored in them. I don't really want to introduce any changes to the files themselves that would cause them to be incompatible with any other chord pro application. The pango syntax support might eliminate the need for some annotations in chord pro files, so perhaps when that is implemented, this won't be as an issue for some.

Mike