Overbars

[epmoyer]

William,

I'm not going to drag over-bars into the scope of the already broad PR we're working on, but it turns out that there is a "COMBINING_OVERLINE" Unicode character (\u0305) that places an overline over the character it follows. One would have to deal with Python2 vs. 3 Unicode issues, and it wouldn't be useful to people unless the output device their data was headed for supported it (so it would have to be a unique mode option), but at least it is possible.

>>> print("130\u03050")
130̅0
>>>

Food for thought :)

[epmoyer]

William,

I have an overbar implementation which is coming along nicely. It's over here if you'd like to take a peek:
https://github.com/epmoyer/to-precision/tree/overbar

I've added Travis CI integration and am currently testing against Python 2.7, & 3.3 -> 3.6
It's nearly finished. Remaining on my todo list is:

• Run demonstration.py as part of tests.py, just to check that it doesn't crash (i.e. not to validate the output). That will ensure, over time, that Travis catches any incompatibilities across Python versions.
• Step away for a day :) I need a little distance before I go back and review.

It turns out that GitHub's markdown engine does not properly handle the Unicode overbar when it occurs within a code block. For example, the value in the post above actually ends in two zeros (the first of which has an overbar), but the second zero does not render (though it is visible in "edit" mode"). To circumvent the rendering issue I embedded an image in the README.md to show the behavior of the new convention option.

Cheers!

[BebeSparkelSparkel]

This is a good option.

What do you think about converting these values back integers or floats for people because that starts to become a problem if being stored for later use?