Confirmed. 

Marking as:
New (confirmed)
Enhancement (leave it as is)
Priority (low, won't be useful for most users but for a limited group will be useful)

Whiteboard status: ProposedEasyHack

Thanks for the suggestion and for helping us make LibO a better office suite for everyone

for "Version:" field, we should set 3.6 or next?

Version is always the version that the bug was originally found in OR the version that the enhancement was first thought of. If this was 3.5 go ahead and leave it. There is always confusion about what version means but it does mean the oldest, not the newest or latest, version, where the request was made against

anyway thank you for considering this enhancement useful for electronics

Created attachment 71444 [details]
Basic macro which has needed functionality

I have written formula on Basic Macro. It produces text that looks like correct hex and bin numbers. But because of it is text, no further calculations with such numbers are possible. Intended only for final output.
Only 31 bit numbers allowed. Alas. No 64 bit.

(In reply to comment #0)
> Menu Format, Cells, tab Numbers, Category list: Binary and Hex
 
> Binary should postpend a small 'b', hex should prepend a '0x'.

IMHO the "binary" and "hexadecimal" format characters should not prepend anything by themselves; any constant string can be added in the format as such.

E.g., if we make the "binary digit" format character "b" and the "hex digit" format character "x", then the effect you want to achieve can be had by:

"b"b
"0x"x

But if one wants Ruby-compatible formatting, one can use:

"0b"b
"0x"x

And if one wants "like Fortran", one can use:

\B\"b\"
\Z\"x\"

Like ADA? Easy peasy:

"2#"b\#
"16#"x\#

etc, etc.

If we implement that, we could as well add octal (base 8) to the mix.

Actually, we could take inspiration from Ada and just allow an arbitrary base in number formats...

> Both should have "digit grouping" that is similar to decimal thousand
> separator, but happen every 4 digit.

Hmm... That's more difficult to achieve with my "arbitrary base" idea, but maybe this should also be arbitrarily configurable? <shrug>

a general base solution is best but maybe hard, while hex and binary are very useful in engineering and not too hard to implement, many could settle for those

Keep in mind that if this was implemented we'd also need to define how to store it in ODF. Does Excel have such thing in its number formats?

Indeed - we may need to close this and recommend Valerio get in touch with the ODF committee to see if they want to implement his.

Eike - agree with this? Really we can't do anything until ODF supports it.

In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval.

Thank you and apologies for the noise