measure

As per angularsen/UnitsNet#328 (comment)

Having a set of tests to validate that the correct abbreviation notations and symbols are used would be helpful, as we have seen from before that discrepancies tend to creep in over time.

See #328 for the (currently work in progress) guideline, go through the comments and identify what tests to write for the guid

Bug description

Scaphandre doesn't provide selinux module to be granted, so scaphandre is not supposed able to reach /proc files

To Reproduce

Run podman scaphandre on a CentOS node with Selinux permissive or enforced.

Expected behavior

```type=PROCTITLE` msg=audit(1620219205.083:466054): proctitle=2F7573722F6C6F63616C2F62696E2F7363617068616E6472650070726F6D657468657573
typ

👋 Hello. We have a component that’s using this hook with in it’s default form (no custom callback) and have been getting a lot of ResizeObserver loop limit exceeded errors thrown during usage.

From my brief search around the internet it seems as though this is harmless but it does add a lot of noise in common usage and that that noise could be avoided

This project is always looking for help with translation to non-English languages. If the translation to your language is missing, incomplete or has errors, you're very welcome to contribute!

Where are the files to translate?

This project uses [Microsoft's .resx file format](https://docs.microsoft.com/en-us/dotnet/framework/resources/creating-resource-files-for-desktop-apps#resources-in-

No Unit found is not descriptive at all.

We should at least make that error message more clear for cases like:

• "75kg" instead of "75 kg"

Our assumption for parsing a compound quantity is that there will be a space character between the value and the unit