To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=87665


User er changed the following:

                What    |Old value                 |New value
================================================================================
          Ever confirmed|                          |1
--------------------------------------------------------------------------------
                  Status|UNCONFIRMED               |NEW
--------------------------------------------------------------------------------
        Target milestone|---                       |OOo 3.0
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Wed Apr  2 11:13:08 +0000 
2008 -------
> "din." (short for dinars), not "Din", in unofficial currency symbol,
> wich is no longer used in official documents. If you want to write
> Invoice or something, you can only use RSD, not "din.".

If RSD is the official currency symbol we do need that. However,
http://en.wikipedia.org/wiki/Serbian_dinar does not say so, it has
'din.' in Latin and Cyrillic script, and I didn't find anything related
at http://www.nbs.yu/internet/english/35/index.html

> Some people still want to use "din." for their ***personal*** documents,
> so we have to keep that one too, that is why duplication. I can change
> code to Din ("din." as symbol), for compatibility reasons, but note that
> there was never bank code DIN.

We can not have two currencies with the same BankSymbol listed. As said,
we can add a duplicate with a different CurrencySymbol if the
legacyOnly="true" attribute is added to be able to display already
existing documents that used the old symbol, but the entry wouldn't be
listed as available number formats if a document doesn't use it. This is
on purpose. Note that in a stored document only the ISO 4217 code is
stored, taken from BankSymbol. When loading we do a match against the
symbol of the display string to determine the number format used, if it
is BankSymbol or CurrencySymbol. If there is no match with the current
definition we match against legacyOnly entries.


> Default currency symbol should be RSD (РСД in Cyrillic), bank code RSD.
> Legacy code is CSD (used during state union Serbia & Montenegro) but
> sometime there is a need to use this in new documents too.

Having one CSD and one RSD entry at the same time is no problem.

> Even older
> code is YUD (1993-2000), same about usage apply here too.

We can add that as well if it is needed, no problem. Altogether it just
makes the list of available currency formats in the dialog quite long.


Regarding the change of  replaceTo="[$Din-881A]"  to  replaceTo="[$RSD-881A]"
The symbol used there has to match the CurrencySymbol of the Currency
element that has the usedInCompatibleFormatCodes="true" attribute. Note
that to display the number formats in the dialog and to derive the
default currency format for a locale the symbol is exchanged with the
one from the default="true" Currency element, so it doesn't matter if
there is an old symbol listed in format codes, it just has to match the
element flagged as usedInCompatibleFormatCodes.


> What about sr_YU and sh_YU locales, do we need those for compatibility
> or not?

Yes, we do, to be able to properly load documents that used those
locales in the past. See also
http://l10n.openoffice.org/servlets/ReadMsg?list=features&msgNo=122


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to