Now that the Accounting format has been resolved (see 45780), add the following accounting code format to the list of per-defined formats under Currency:
[$$-409]* #,##0.00_);[RED][$$-409]* (#,##0.00);[$$-409]* -_)
Hi Phil, please explain the purpose of this report. What is the difference with Bug 45780?
A fair question. The original bug report (Bug 45780) was to address a fundamental technical deficiency that prevented the basic ability to even create an accounting format, and the implied (though not explicitly stated) addition of an "Accounting" format to the list of pre-defined number formats. That technical issue has now been solved but not the addition of the Accounting format entry. That is left to the user to 1) build the format, 2) create a new template 3) make the new template the default. Hardly an adopter friendly process. As I have bellowed from my soap-box before, we must make this "work" for the adopters and leaving this other piece undone creates a barrier to them.
This bug report is an effort to drop the other shoe and bring that remaining piece to the fore to be addressed. (And does not get lost in the "completion" of the primary bug.)
It's not a very challenging fix unlike the technical underpinnings. The biggest issue would be what the formatting code should be (I would defer to a professional accountant for that). But I would amend my original suggestion to correct the right-indent of the negative value:
[$$-409]* #,##0.00_);[RED][$$-409]* (#,##0.00)_);[$$-409]* -_)
Separately, I feel LO should add the ability of a user to define number formats and then have [Add] and [Delete] buttons to manage their User Defined formats in the default template
(In reply to comment #2)
> ...As I have bellowed from my soap-box
> before, we must make this "work" for the adopters and leaving this other
> piece undone creates a barrier to them.
Smells like an enhancement.
> This bug report is an effort to drop the other shoe and bring that remaining
> piece to the fore to be addressed. (And does not get lost in the
> "completion" of the primary bug.)
> It's not a very challenging fix unlike the technical underpinnings. The
> biggest issue would be what the formatting code should be (I would defer to
> a professional accountant for that). But I would amend my original
> suggestion to correct the right-indent of the negative value:
> [$$-409]* #,##0.00_);[RED][$$-409]* (#,##0.00)_);[$$-409]* -_)
Feel free to submit a patch for this.
> Separately, I feel LO should add the ability of a user to define number
> formats and then have [Add] and [Delete] buttons to manage their User
> Defined formats in the default template
Feel free to submit this as a separate enhancement request.
*** Bug 92121 has been marked as a duplicate of this bug. ***
*** Bug 78542 has been marked as a duplicate of this bug. ***
In en_US, three last currency formats have currency symbol left aligned. If that not fit your needs, you may suggest new format with some reference.
waiting in silence.. maybe relatively easy, Jani/dev x ?
There seems to be missing consensus about what should be added (like having an accounting look at it), I would suspect too that this would be country or at least region specific.
So first we need to have 1 (or more) fixed definitions, then we can add them.
LibO, with en-US and en_GB locales, already contains two currency formats with left justify currency symbol and right justify decimal number:
[$$-409]* #,##0;-[$$-409]* #,##0
[$$-409]* #,##0.00;-[$$-409]* #,##0.00
These formats are defined in
<FormatElement msgid="CurrencyFormatskey7" default="false" type="short"
<FormatCode>[CURRENCY]* #,##0;-[CURRENCY]* #,##0</FormatCode>
<FormatElement msgid="CurrencyFormatskey8" default="false" type="medium" usage="CURRENCY" formatindex="83">
<FormatCode>[CURRENCY]* #,##0.00;-[CURRENCY]* #,##0.00</FormatCode>
This was added 4 years ago:
We may add some more formats but we need some references: currency unit can be on left or right, negative numbers can be in red or not, with a minus sign or with parentheses, zeros can be displayed as --, etc. There are many possibilities depending on locales acceptance rules.
As I have no accounting capacities, I looked to other spreadsheet for fr-FR:
_(0,00* [$€-1]_);_((0,00)* [$€-1];_("-"??* [$€-1]_);_(@_)
_-* # ##0,00 €_-;-* # ##0,00 €_-;_-* "-"?? €_-;_-@_-
I would prefer Excel proposition as there is thousand separator and decimal are aligned.
According to help
Accounting format for en-US in Excel may look like:
[$$-409]* #,##0.00_);[$$-409]* (#,##0.00);[$$-409]* -_);_(@_)
This has to be defined for each locale which needs an accounting format. There are 198 XML files in http://opengrok.libreoffice.org/xref/core/i18npool/source/localedata/data to be modified. But they can be modified one after one, when localization teams decide what is the best format for each.
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker
(In reply to jani from comment #8)
> There seems to be missing consensus about what should be added (like having
> an accounting look at it), I would suspect too that this would be country or
> at least region specific.
IMO comment #0 and comment #2 are clear enough > NEW