Comment 1 for bug 1827503

In lieu of having the particular annotation scheme I wanted within eeschema itself, I ended up writing a standalone program in Python that read the .sch files and applied my annotation scheme to them. I did that out of personal necessity, but it occurs to me that it might be a more-appropriate approach than trying to implement a bunch of different annotation schemes directly within eeschema that were each of use to only a few people.

The way it could work is that the program itself would be completely generic except that there would be a single function in it that supplied an annotation for a given component, on the basis of inputs like a sheet number, a base reference designator, and so on, and that the user could replace the contents of this function to create whatever annotation rule he/she happened to like.

Just a thought.