Talk:String case: Difference between revisions

From Rosetta Code
Content added Content deleted
(It must be ASCII / Latin-1)
 
No edit summary
Line 1: Line 1:
I think the task must explicitly refer to an encoding to use. I guess it is should be ASCII or else 8-bit Latin-1. If not, as in the case of a more or less full Unicode, changing the case would require some further definitions, see [http://unicode.org/reports/tr21/tr21-5.html Unicode case mappings]. --[[User:Dmitry-kazakov|Dmitry-kazakov]] 10:18, 11 June 2009 (UTC)
I think the task must explicitly refer to an encoding to use. I guess it is should be ASCII or else 8-bit Latin-1. If not, as in the case of a more or less full Unicode, changing the case would require some further definitions, see [http://unicode.org/reports/tr21/tr21-5.html Unicode case mappings]. --[[User:Dmitry-kazakov|Dmitry-kazakov]] 10:18, 11 June 2009 (UTC)
:I think the idea was to use the default encoding for a string variable. The hope was probably to show string functions built in to languages. Maybe we could specify to use the encoding of a string literal? --[[User:Mwn3d|Mwn3d]] 12:03, 11 June 2009 (UTC)

Revision as of 12:03, 11 June 2009

I think the task must explicitly refer to an encoding to use. I guess it is should be ASCII or else 8-bit Latin-1. If not, as in the case of a more or less full Unicode, changing the case would require some further definitions, see Unicode case mappings. --Dmitry-kazakov 10:18, 11 June 2009 (UTC)

I think the idea was to use the default encoding for a string variable. The hope was probably to show string functions built in to languages. Maybe we could specify to use the encoding of a string literal? --Mwn3d 12:03, 11 June 2009 (UTC)