3003: Sandwich Helix - Revision history

NiceGuy1: I changed this, I checked the wrong comic, 3002, which also has an apostrophe, Randall DID enter it this way.

2025-06-14T04:38:23Z

I changed this, I checked the wrong comic, 3002, which also has an apostrophe, Randall DID enter it this way.

NiceGuy1: Fixing the smart quote in the title text. Last time I thought Randall had put the messed up replacement characters, but he didn't, I think he put a straight quote!

2025-06-14T04:33:57Z

Fixing the smart quote in the title text. Last time I thought Randall had put the messed up replacement characters, but he didn't, I think he put a straight quote!

172.70.163.35: /* Explanation */ More detail added. Got away with me (still could have much more said about it!) so I moved things a bit to help the flow not get too diverted mid-sentence.

2025-03-23T20:19:13Z

‎Explanation: More detail added. Got away with me (still could have much more said about it!) so I moved things a bit to help the flow not get too diverted mid-sentence.

NiceGuy1: /* Explanation */

2025-03-22T06:42:58Z

‎Explanation

172.71.218.122 at 01:31, 22 February 2025

2025-02-22T01:31:03Z

Firestar233: removed Category:Unicode using HotCat this isn't really about unicode

2025-02-06T21:42:36Z

removed Category:Unicode using HotCat this isn't really about unicode

172.68.164.155: /* Transcript */ -incomplete

2024-12-22T16:05:10Z

‎Transcript: -incomplete

The-Ergster at 02:41, 2 December 2024

2024-12-02T02:41:55Z

172.71.195.112: /* Explanation */

2024-11-15T00:30:55Z

‎Explanation

HARRISWON2024! at 23:36, 14 November 2024

2024-11-14T23:36:20Z

@@ Line 6: / Line 6: @@
 | imagesize = 257x376px
 | noexpand  = true
-| titletext = The number one rule of string manipulation is that you've got to specify your encodings.
+| titletext = The number one rule of string manipulation is that youâ€™ve got to specify your encodings.
 }}

@@ Line 6: / Line 6: @@
 | imagesize = 257x376px
 | noexpand  = true
-| titletext = The number one rule of string manipulation is that youâ€™ve got to specify your encodings.
+| titletext = The number one rule of string manipulation is that you've got to specify your encodings.
 }}

@@ Line 20: / Line 20: @@
 The fictitious "Sandwich Helix" plays on another concept in communication, the "{{w|Compliment sandwich|Compliment Sandwich}}" (a.k.a. "Shit Sandwich"), wherein a statement of criticism is sandwiched between two complimentary statements in order to make the negative statement easier to accept.  The difference is that the Compliment Sandwich is a communication technique which is well known and whose meaning has not been lost (though it is currently disputed whether the technique is effective or whether it even might accomplish the inverse of its goals). A possible inspiration for the "helix" part is the {{w|Models of communication#Dance|Helical Model of Communication}}. The creator of the model, Frank Dance, emphasised the role of communication problems. He shows communication as a dynamic and non-linear process.
-The title text contains several odd-looking characters that seem random (but are actually meaningful, to those familiar with them) where an apostrophe should be, as an example of a string that did NOT have its encoding handled properly. It is an example of {{w|Mojibake}}. Some special characters and symbols require a special {{w|Character encoding|encoding}} (such as UTF-8, Windows-1252, Shift-JIS, etc) in order to be stored and displayed properly, and are encoded using the equivalent of multiple characters. If the code to display the text doesn't understand what encoding was used and assumes a different/lesser level of encoding, you can get "garbage" similar to what is in the title text. In this case, the original character was <code>’</code>, a "smart apostrophe", (being an apostrophe angled to the right as opposed to the straight apostrophe available to type on standard keyboards), which when encoded in UTF-8 and decoded in Windows-1252 becomes <code>â€™</code>. Similar garbage is seen in the title text of [[1683: Digital Data]].
+The title text contains several odd-looking characters that seem random (but are actually meaningful, to those familiar with them) where an apostrophe should be, as an example of a string that did NOT have its encoding handled properly. It is an example of {{w|Mojibake}}. Some special characters and symbols require a special {{w|Character encoding|encoding}} (such as UTF-8, Windows-1252, Shift-JIS, etc) in order to be stored and displayed properly, and are encoded using the equivalent of multiple characters. If the code to display the text doesn't understand what encoding was used and assumes a different/lesser level of encoding, you can get "garbage" similar to what is in the title text. In this case, the original character was <code>’</code>, a "smart apostrophe" which, when encoded in UTF-8 and decoded in Windows-1252, becomes <code>â€™</code>. Similar garbage is seen in the title text of [[1683: Digital Data]]. The apostrophe angled to the right, as opposed to the straight apostrophe normally typed on standard keyboards, is ''often'' intended to pair with a leftwards-angled one as marks at either end of some quoted text, `smartly´ applied by some word processing software by way of an autocorrection of what was typed - though not always when actually wanted, or correctly applied even when it might be.
 ==Transcript==

@@ Line 20: / Line 20: @@
 The fictitious "Sandwich Helix" plays on another concept in communication, the "{{w|Compliment sandwich|Compliment Sandwich}}" (a.k.a. "Shit Sandwich"), wherein a statement of criticism is sandwiched between two complimentary statements in order to make the negative statement easier to accept.  The difference is that the Compliment Sandwich is a communication technique which is well known and whose meaning has not been lost (though it is currently disputed whether the technique is effective or whether it even might accomplish the inverse of its goals). A possible inspiration for the "helix" part is the {{w|Models of communication#Dance|Helical Model of Communication}}. The creator of the model, Frank Dance, emphasised the role of communication problems. He shows communication as a dynamic and non-linear process.
-The title text contains several odd-looking characters that seem random (but are actually meaningful, to those familiar with them) where an apostrophe should be, as an example of a string that did NOT have its encoding handled properly. It is an example of {{w|Mojibake}}. Some special characters and symbols require a special {{w|Character encoding|encoding}} (such as UTF-8, Windows-1252, Shift-JIS, etc) in order to be stored and displayed properly, and are encoded using the equivalent of multiple characters. If the code to display the text doesn't understand what encoding was used and assumes a different/lesser level of encoding, you can get "garbage" similar to what is in the title text. In this case, the original character was probably <code>’</code>, which when encoded in UTF-8 and decoded in Windows-1252 becomes <code>â€™</code>. Similar garbage is seen in the title text of [[1683: Digital Data]].
+The title text contains several odd-looking characters that seem random (but are actually meaningful, to those familiar with them) where an apostrophe should be, as an example of a string that did NOT have its encoding handled properly. It is an example of {{w|Mojibake}}. Some special characters and symbols require a special {{w|Character encoding|encoding}} (such as UTF-8, Windows-1252, Shift-JIS, etc) in order to be stored and displayed properly, and are encoded using the equivalent of multiple characters. If the code to display the text doesn't understand what encoding was used and assumes a different/lesser level of encoding, you can get "garbage" similar to what is in the title text. In this case, the original character was <code>’</code>, a "smart apostrophe", (being an apostrophe angled to the right as opposed to the straight apostrophe available to type on standard keyboards), which when encoded in UTF-8 and decoded in Windows-1252 becomes <code>â€™</code>. Similar garbage is seen in the title text of [[1683: Digital Data]].
 ==Transcript==

← Older revision		Revision as of 01:31, 22 February 2025
Line 37:		Line 37:
	[[Category:Comics featuring Hairy]]		[[Category:Comics featuring Hairy]]
	[[Category:Language]]		[[Category:Language]]
		+	[[Category:Unicode]]

@@ Line 36: / Line 36: @@
 [[Category:Comics featuring Ponytail]]
 [[Category:Comics featuring Hairy]]
 [[Category:Language]]

@@ Line 23: / Line 23: @@
 ==Transcript==
 :[Cueball, with his palm out, is standing in front of a class and facing Ponytail and Hairy, who are sitting at their classroom desks.]
 :Cueball: Always remember the #1 rule of communication:
-:Cueball: ''Sandwich Helix.''
+:Cueball: '''''Sandwich Helix.'''''
 :Ponytail: What does that mean?
 :Cueball: Unfortunately, the context has been lost.

@@ Line 10: / Line 10: @@
 ==Explanation==
-{{incomplete|Created by a BOTWICH HELIX - Please
 This comic details an important issue in communication: even if the content of your message goes through, there might be important context that is necessary to correctly interpret it.