May 25, 2018 updates: Privacy Policy

Ticket #37666

Metapost/fontbase numeric problems with botip

Open Date: 2017-11-16 07:53 Last Update: 2017-11-19 14:54

Reporter:
Owner:
Type:
Status:
Open [Owner assigned]
Component:
MileStone:
Priority:
7
Severity:
5 - Medium
Resolution:
None

Details

The tip() macro of the font-base macros we inherited, as accessed through our set_botip() interface, has trouble making sharp corners in the case where control points are close together. We would want to set "tip" to a large number in order to extend the edges significantly further than the distance between successive control points, but setting it any larger than 1 is likely to trigger a numeric overflow in Metapost's fixed-point arithmetic. Ideally, when set to 1 it should be effectively infinite (extend the edges as far as necessary to make them intersect). We very rarely use any values other than 1 and 0. But at the very least, we should be able to extend edges further than the amount that the current 1.0 means.

Maybe the current font-base macros can be changed to allow longer, and even unlimited, extension without overflow. Maybe now is the time to switch to using one of the fancier numeric formats permitted by current versions of Metapost.

Attachment File List

No attachments

Ticket History (2/2 Histories)

2017-11-16 07:53 Updated by: mskala
  • New Ticket "Metapost/fontbase numeric problems with botip" created
2017-11-19 14:54 Updated by: mskala
  • Priority Update from 6 to 7
  • Details Updated

Edit

You are not logged in. I you are not logged in, your comment will be treated as an anonymous post. » Login