Tree geometry is too sensitive to long strings

[refob]

My gedcom files contain large locations strings which produce huge node boxes like this:

It would help to shorten long strings for nodes and show the full string only in the right detail window.

[PeWu]

I agree it would be nice to make the boxes smaller. Do you have a suggestion how to shorten the long strings?

[endolith]

For United States locations, shorten to just the state abbreviation

In fact, I can imagine it dynamically showing more or less information as you zoom in and out horizontally, to make the tree wider or narrower, with rules defined that increasingly shorten the text so that it is still maximally useful:

• Cyclone, Keating Township, McKean, Pennsylvania, United States
• Cyclone, Keating Township, McKean, Pennsylvania, US
• Cyclone, Keating Township, McKean, PA, US
• Cyclone, Keating, McKean, PA, US
• Cyclone, McKean, PA, US
• Cyclone, PA, US
• Cyclone, PA
• PA

The totally unrelated https://sigrok.org/wiki/PulseView application has this function, where you can zoom in to a decoded signal and it will show different abbreviations of the content depending on zoom level and what fits:

with the shortening rules defined like:

c1 = 'Left channel' if not self.oldws else 'Right channel'
c2 = 'Left' if not self.oldws else 'Right'
c3 = 'L' if not self.oldws else 'R'