Talk:Number names

Long vs. short scale

Please choose between long and short scale, and amend the task description. --Michael Mol 04:02, 22 March 2010 (UTC)

Why not both? Split it into "Number names/Short scale" and "Number names/Long scale" with this page holding the description of the task, and definition of short scale vs. long scale, with links to the subpages. -- Eriksiers 13:51, 22 March 2010 (UTC)

Either? (So no present code is invalidated) --Paddy3118 16:57, 22 March 2010 (UTC)

Either is fine, but give a brief explanation of long form vs short form in the task description, then require the choice to be documented in the example. --Michael Mol 19:58, 22 March 2010 (UTC)

I'd recommend sticking to the short scale, since it's standard among English-speaking countries and Rosetta Code is in English. —Underscore (Talk) 21:12, 22 March 2010 (UTC)

Do you think the U.K. (who, most whould say, are English-speaking) may disagree with the last recommendation? Gerard Schildberger 23:22, 15 December 2010 (UTC)

No. From the WP: "In 1974, the government of the UK switched to the short scale" --Mwn3d 02:28, 16 December 2010 (UTC)

I'd recommend supporting both scales. That's what programs do, offer choices, formats, options, different parameters... Gerard Schildberger 23:24, 15 December 2010 (UTC)

I suggest to rw-word the original task: Show how to spell out a number in (English) words. You can use ... Gerard Schildberger 23:36, 15 December 2010 (UTC)

Do as English does

Since the task deals with a natural language, a program's output should follow the normal language usage. How do you pronounce 1,001? "one thousand and one", not "one thousand, one". Currently Java, Ruby, Basic and Python solutions, probably among others, should be considered inadequate. --Ledrug 21:51, 22 June 2011 (UTC)