Anonymous user
Talk:Abbreviations, simple: Difference between revisions
→Case of output: explained a task's requirement.
(→Case of output: Why to convert to uppercase?) |
(→Case of output: explained a task's requirement.) |
||
Line 5:
:: The only point to have this task in addition to the "easy" task is that using numbers to specify the length would allow preserving the case in the command table. So there is no point in converting the words to uppercase. (You could as well write the word in upper case in the command table directly.) So I think the words should not be converted to upper case. That would make this task a little bit different from the other task. --[[User:PauliKL|PauliKL]] ([[User talk:PauliKL|talk]]) 14:56, 23 February 2020 (UTC)
::: Allowing the preservation of the case of the command table was never a consideration for this Rosetta Code task. The command table is to be considered immutable, as in this case, it is "owned" by (the) editor which uses this command table. The words (commands) need to be converted to uppercase because that is what this task requires (and, as it happens, it's also what's required by the editor). It believe it would be too late to eliminate (change) this task's requirement at this late date. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 15:43, 23 February 2020 (UTC)
| |||