Content deleted Content added
→Decimal input (Windows) Part 2: I do not understand what Spitzak is trying to say. |
|||
Line 212:
:::[[User:Peter M. Brown|Peter Brown]] ([[User talk:Peter M. Brown|talk]]) 21:05, 20 September 2020 (UTC)
::I am having a very hard time trying to figure out what you are thinking. The words "turns into" means: the user types the number 960, and the software eventually inserts a Unicode character with a certain code point, lets assume that for some reason this code point is 192. The input to this operation is the number 960, and the output is the number 192. I think it is extremely common to say "960 ''turns into'' 192" and am really curious why this term confuses you and how you would state it.
::Using "turns into" your statement is "960 is equivalent to 448 modulus 256, and 448 turns into 448, not 192, therefore modulus has nothing to do with it". What you have shown is that modulus is not applied to 448. And the number 960 is completely irrelevant to this conclusion.
::The other question is why you think using 448 instead of 960 somehow increases "brevity". My best guess is that you think the system might turn 960 into 448 and that you are avoiding difference between ANSI and OEM code pages? But then you correctly indicate that 448 turns into 448, not involving 960 at all, and even correctly identify the code point 448 would turn into if modulus 256 was applied (192, using the character from the ANSI code page). I am really trying to figure out your logic here. Perhaps you could write the "less brevity" version using 960 so I could get some idea of what in the world you are thinking?[[User:Spitzak|Spitzak]] ([[User talk:Spitzak|talk]]) 18:53, 21 September 2020 (UTC)
| |||