Apache OpenOffice (AOO) Bugzilla – Issue 3702
SPELLOUT() number spell out function (multi-lingual)
Last modified: 2013-08-07 15:12:27 UTC
Number spell out, is "words" that represent a given numeric value. for examples, "ten" for 10, "one hundred and twenty" for 120. This functionality is very important for financial related spreadsheet. (cheque writing, for example) ---- may be it will works like this (just for an idea), SPELLOUT( value [, language [, currency] ]) SPELLOUT(120) = "one hundred and twenty" ** get default language from locale (in this case English) SPELLOUT(120, "en") = "one hundred and twenty" SPELLOUT(120, "th") = "˹Öè§ÃéÃÂÂÕèÊÔº" SPELLOUT(120, "en", "JP") = "one hundred and twenty yen" SPELLOUT(120, "en", "FR") = "one hundred and twenty euro" SPELLOUT(120, "th", "JP") = "˹Öè§ÃéÃÂÂÕèÊÔºà ¹" ** pass country code to tell currency name additional parameters may added to tell it - add "only" to string if input is integer (for cheque printing) ICU has mentioned about the rule-based number spell out at http://www-124.ibm.com/icu/docs/papers/a_rule_based_approach_to_number_spellout/
Hi Falko, this one is for you.
Yepp, good function but that's exactly our Calc-API is for! This is one of those jobs for third-party. That's why I use "wontfix".
so just open the api/interface, to allow the third-party implements it :)
my idea is, every language/locale should have a common way to do this thing. because this function is a very common task frequently used. third-parties' BAHTTEXT(), YENSPELLOUT(), PRINTEUROTEXT(), DOLLAR(), etc ...i think that is not a good idea. considers two templates for invoice. 1st uses SPELLOUT(). 2nd uses third-party's (function name differs for each lang/locale) 1st template can be instantly used in any lang/locale, without modification. (since SPELLOUT() can use the user default/current lang/locale) 2nd template, needs to find the third-party add-on function for current lang/locale, and then manually replace all old add-on functions to new add-on functions.
As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified.
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified.
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.
re-opened
Hi Eike, sounds interesting. Maybe something for our friends. Frank
*** Issue 83789 has been marked as a duplicate of this issue. ***
Closing this in favor of issue 103746 that has more details and already an implementation of an extension offering the functionality. *** This issue has been marked as a duplicate of 103746 ***
duplicate -< closed