Talk:Unicode input: Difference between revisions

Revision as of 16:23, 22 September 2020

Revision as of 18:53, 22 September 2020

Line 240:

Yes, I absolutely agree there is just misunderstanding here, not an argument. I believe Peter Brown has some fundemental error and I really am trying to be helpful in correcting it, though it is very hard to tell exactly what his error is. The basic question is why he started talking about 448, either implying that mod-256 can turn 980 into 448, or that for some reason 448 has fewer possible results of mod-256 than 980, when in fact both of them turn into the exact same number, 192.

I think your math expression is possibly messed up as you use letters in the last one that don't appear in any others, thus it's unrelated. But yes y=f(gf'(f''(x))) defines a function thethat doesapplies the translation gf'' ofto x, andf' thento thethat translationresult, and f ofto that result, and could be written as a new function h such that y=h(x).

You are wrong about what happens when a file is sent to Japan. All the software under consideration is storing the resulting unicode code points in the file, not the numbers the user typed, and the file will display the same there.