You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pint ships with some "specialized" US area units like square_foot. When I discovered that there was an alias for this of sq_ft I thought that maybe sq might be a recognised prefix representing "square".
I was sad to find that sqm or sq_m doesn't exist. Given that sq_ftdoes exist in pint this seems like an anomaly.
We often use Pint to parse user-submitted data and our users think of "square metres" as "sqm".
Would it be possible for Pint to understand sqX to mean X ** 2? So, for example, sqcm or sq_cm would also be supported.
The text was updated successfully, but these errors were encountered:
you can add sqm and others as definitions and aliases to default_en.txt. A PR adding these is welcomed.
I can see some difficulty in getting the parser to understand that the prefix changes the dimensionality (atm prefixes are only numerical multipliers), and with the formatting code. Therefore I don't think it's worth writing something to handle sq as an extra prefix
Pint ships with some "specialized" US area units like
square_foot
. When I discovered that there was an alias for this ofsq_ft
I thought that maybesq
might be a recognised prefix representing "square".I was sad to find that
sqm
orsq_m
doesn't exist. Given thatsq_ft
does exist in pint this seems like an anomaly.We often use Pint to parse user-submitted data and our users think of "square metres" as "sqm".
Would it be possible for Pint to understand
sqX
to meanX ** 2
? So, for example,sqcm
orsq_cm
would also be supported.The text was updated successfully, but these errors were encountered: