Improve the target stats display on the in-flight map

[Henrik Heimbuerger]

1. "type/speed/range" should be capitalized consistently with the rest of the UI -- either make everything lowercase, like the personal stats on the left of the map or capitalize these correctly.
2. "range" should be renamed to "distance", as it is always relative to you.
3. The distance should be postfixed with 'm' like all other distances.
4. Fix the range shown when in base, see comment:1.
5. Fix long ship types overlapping with ETA/speed numbers, see comment:2.

[girlyboy]

Additional points on range:

When docked and viewing the F3 command view, the "range" readout will behave oddly.

• If you go to F3 after start of a game, before you've launched from the base, and right-click on any object, its range will be displayed from the exact centre of the sector (regardless of anything else, like garrison location, etc).
• Once you've launched and re-docked, range on F3 will always be displayed from the last base you -docked at- (transferring with F8 has no effect on this).
• Viewing other sectors in F3 and checking range for objects there will give a range from the same spot on the command map, even though you're viewing a different sector. I.e. if you've last docked at a base at a particular point in sector A, then view sector B through F3, all ranges will be shown from the equivalent point in sector B.

I personally would suggest either removing range altogether if you're viewing F3 from within base, or always giving it from the centre of the sector being viewed, since there might be some specific situations where this might be useful (e.g. quickly guesstimating distances between alephs, bases, other points of interest, etc).

[girlyboy]

Additional point:

If the "type" of the target shown in the target window is long enough, sometimes the "target type" text will overlap with the ETA/Speed numbers. For example, if your target has type "Enh Sm Constructor", this text will take up two lines, and the second line will take up the same space as the ETA/Speed readout, making both hard to read.

I don't know if this would be affected by resolution; I play at 1280x800.