Editing Talk:2109: Invisible Formatting
Please sign your posts with ~~~~ |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 4: | Line 4: | ||
:Some programming puzzles are often solved with stuff like this: AΑ [[User:Fabian42|Fabian42]] ([[User talk:Fabian42|talk]]) 15:19, 8 February 2019 (UTC) | :Some programming puzzles are often solved with stuff like this: AΑ [[User:Fabian42|Fabian42]] ([[User talk:Fabian42|talk]]) 15:19, 8 February 2019 (UTC) | ||
:"l" (lower-case "L") is a valid suffix to integer literals in C and derived languages. It indicates the number is of the "long int" type as opposed to a plain "int". Because C automatically upconverts the "int" type into "long int" when needed, the "l" suffix is rarely used. The result: "long int a = 1;" and "long int a = 1l;" mean exactly the same thing, and both statements are perfectly standard and won't raise any warning from compilers. "ll" (double el) is also a valid suffix, this time for the "long long int" type. [[User:GuB|GuB]] ([[User talk:GuB|talk]]) 15:39, 8 February 2019 (UTC) | :"l" (lower-case "L") is a valid suffix to integer literals in C and derived languages. It indicates the number is of the "long int" type as opposed to a plain "int". Because C automatically upconverts the "int" type into "long int" when needed, the "l" suffix is rarely used. The result: "long int a = 1;" and "long int a = 1l;" mean exactly the same thing, and both statements are perfectly standard and won't raise any warning from compilers. "ll" (double el) is also a valid suffix, this time for the "long long int" type. [[User:GuB|GuB]] ([[User talk:GuB|talk]]) 15:39, 8 February 2019 (UTC) | ||
− | :Typing lowercase ''L'' instead of ''1'' is a common thing for people of a certain age. Old manual typewriters usually don't have a "1" key, so people learned to use lowercase ''L'' instead -- and sometimes slip back into that habit on newer technology. --[[User:Aaron of Mpls|Aaron of Mpls]] ([[User talk:Aaron of Mpls|talk]]) 02:03, 9 February 2019 (UTC) | + | :Typing lowercase ''L'' instead of ''1'' is a common thing for people of a certain age. Old manual typewriters usually don't have a "1" key, so people learned to use lowercase ''L'' instead -- and sometimes slip back into that habit on newer technology. --[[User:Aaron of Mpls|Aaron of Mpls]] ([[User talk:Aaron of Mpls|talk]]) 02:03, 9 February 2019 (UTC) Tha's exactly what happened in my example. I blame the programmer, though, for allowing a letter where a numeral was required or possibly converting the l to a 1 if the programmer knew such a thing ever happened. In either case, it shouldn't have allowed the l to just sit there like a bomb waiting to blow apart the post-tax-year processing. [[Special:Contributions/172.68.58.83|172.68.58.83]] 15:22, 9 February 2019 (UTC) |
− | |||
I went to this page, expecting it to be self-referential. Was not disappointed. [[User:Fabian42|Fabian42]] ([[User talk:Fabian42|talk]]) 15:19, 8 February 2019 (UTC) | I went to this page, expecting it to be self-referential. Was not disappointed. [[User:Fabian42|Fabian42]] ([[User talk:Fabian42|talk]]) 15:19, 8 February 2019 (UTC) | ||
Line 35: | Line 34: | ||
I frequently see a similar, related problem. In preparing a weekly newsletter (consisting mostly of links to articles from various news sources), people submitting articles to me usually send me Microsoft Word files into which they have used copy/paste to insert the headline, URL and a few lines of text for context. On far too many articles, I find that the resulting text has embedded UNICODE {{w|Left-to-right mark}} characters (U+200E) in it. These don't affect display and printing at all (since all of the text is already left-to-right), but it creates broken links if one appears in a URL and I copy/paste it into a web browser's location bar. There doesn't seem to be any way to make these characters visible in Word. If manually cursoring over the text (with left/right keys), you will see the cursor change shape without moving when stepping over the left-to-right mark, but that's the only indication. It's quite annoying to have to work around. (If anyone knows of a good workaround, please let me know.) [[User:Shamino|Shamino]] ([[User talk:Shamino|talk]]) 19:32, 10 February 2019 (UTC) | I frequently see a similar, related problem. In preparing a weekly newsletter (consisting mostly of links to articles from various news sources), people submitting articles to me usually send me Microsoft Word files into which they have used copy/paste to insert the headline, URL and a few lines of text for context. On far too many articles, I find that the resulting text has embedded UNICODE {{w|Left-to-right mark}} characters (U+200E) in it. These don't affect display and printing at all (since all of the text is already left-to-right), but it creates broken links if one appears in a URL and I copy/paste it into a web browser's location bar. There doesn't seem to be any way to make these characters visible in Word. If manually cursoring over the text (with left/right keys), you will see the cursor change shape without moving when stepping over the left-to-right mark, but that's the only indication. It's quite annoying to have to work around. (If anyone knows of a good workaround, please let me know.) [[User:Shamino|Shamino]] ([[User talk:Shamino|talk]]) 19:32, 10 February 2019 (UTC) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |