If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#181
|
|||
|
|||
Technical & legal background using copyrighted fonts in custom road signs in PowerPoint
On Fri, 15 Sep 2017 14:02:14 +0100, Tim Streater
wrote: Why do single and double quotes in PowerPoint always show up as funny characters in Usenet? Why are you using PowerPoint as a Usenet client? My mistake for not being clear. The original document is a PowerPoint document which contained the summaries on where to get fonts. In that original PowerPoint 2007 document, I had typed doublequotes (") and single quotes "'" which I then cut and pasted into the Usenet summary in my Usenet client. When I pasted from PowerPoint to my Usenet client, the doublequotes and single quotes looked "fine" but when I sent it, "something" in that process of sending the text to the Usenet changed the doublequotes and single quotes to a cent sign. Why? I don't know why. Do you? |
#182
|
|||
|
|||
Technical & legal background using copyrighted fonts in custom road signs in PowerPoint
On 2017-09-15 11:14:48 +0000, Chaya Eve said:
On Fri, 15 Sep 2017 11:11:31 +0000 (UTC), Chaya Eve wrote: The latest Win10 ships with a DIN-look-alike font named ¡Bahnschrift¢ Why do single and double quotes in PowerPoint always show up as funny characters in Usenet? Because Usenet (and email) is *meant* to be plain text. "Curly quotes" (and "curly apostrophes") are not part of plain text, so some usenet newsreader applications do not work with them, which is the correct approach. Same goes for other non-plain text typographical characters, such as long dashes and ellipsis. Some badly made Usenet newsreader applications do work with "curly quotes", etc., but they're a pain in the backside in proper Usenet reader applications since the characters come through as strange characters. |
#183
|
|||
|
|||
Technical & legal background using copyrighted fonts in custom road signs in PowerPoint
On Sat, 16 Sep 2017 10:29:05 +1200, Your Name wrote:
Because Usenet (and email) is *meant* to be plain text. "Curly quotes" (and "curly apostrophes") are not part of plain text, so some usenet newsreader applications do not work with them, which is the correct approach. Same goes for other non-plain text typographical characters, such as long dashes and ellipsis. Some badly made Usenet newsreader applications do work with "curly quotes", etc., but they're a pain in the backside in proper Usenet reader applications since the characters come through as strange characters. I didn't know that a "curly quote" is different from a "regular" quote until Paul's note about PowerPoint automatically substituting "curly quotes" for regular quotes. What the heck is the difference between regular and curly to us anyway? It's a quote for heaven's sake. What's so horrible about not-curly quotes that PowerPoint has to change them to "curly" quotes? |
#184
|
|||
|
|||
Technical & legal background using copyrighted fonts in customroad signs in PowerPoint
Your Name wrote:
On 2017-09-15 11:14:48 +0000, Chaya Eve said: On Fri, 15 Sep 2017 11:11:31 +0000 (UTC), Chaya Eve wrote: The latest Win10 ships with a DIN-look-alike font named ¡Bahnschrift¢ Why do single and double quotes in PowerPoint always show up as funny characters in Usenet? Because Usenet (and email) is *meant* to be plain text. "Curly quotes" (and "curly apostrophes") are not part of plain text, so some usenet newsreader applications do not work with them, which is the correct approach. Same goes for other non-plain text typographical characters, such as long dashes and ellipsis. Some badly made Usenet newsreader applications do work with "curly quotes", etc., but they're a pain in the backside in proper Usenet reader applications since the characters come through as strange characters. I don't know if I'd call them badly made. Supporting a curly quote, is no harder than supporting this. ソーラン渡り鳥 (島津亜矢 +ã€€ç”°å ·å¯¿ç¾Žï¼‰.aac If your newsreader supports internationalization, you should be able to see that the way it was intended. Before I added the font file to my OS, I was seeing squares. Now, I see Chinese characters followed by four "regular" characters. https://s2.postimg.org/hax9prms9/no_squares.gif If I'd done that in xvnews 25 years ago, it would have "looked like ****". Because all that supported was plain ASCII. At one time, some comm trunks used for data, only supported 7 bit transmission. (The eighth bit was robbed for OOB signalling.) And email and news worked within those limits. Using 7-bit ASCII was a natural fit for the misshapen network. Now, however, the assumption is all the pipes are 8 bit transparent, and multi-byte characters can be sent, to support symbol sets that have thousands of characters. If you're using a really old newsreader, good luck dealing with the above string. Modern newsreaders even support character code escapes in things like the Subject or From line. You can declare UTF-8 long enough, to put special punctuation in there. The header in each message, has a directive for character coding and the like. Many things I've not tested, are supported. Paul |
#185
|
|||
|
|||
Technical & legal background using copyrighted fonts in custom road signs in PowerPoint
In article , Paul
wrote: Your Name wrote: Because Usenet (and email) is *meant* to be plain text. "Curly quotes" (and "curly apostrophes") are not part of plain text, so some usenet newsreader applications do not work with them, which is the correct approach. Same goes for other non-plain text typographical characters, such as long dashes and ellipsis. Some badly made Usenet newsreader applications do work with "curly quotes", etc., but they're a pain in the backside in proper Usenet reader applications since the characters come through as strange characters. I don't know if I'd call them badly made. newsreaders that handle text encodings are actually well made. what he wrote is bull****. |
#186
|
|||
|
|||
Technical & legal background using copyrighted fonts in custom road signs in PowerPoint
In article , Chaya Eve
wrote: What's so horrible about not-curly quotes that PowerPoint has to change them to "curly" quotes? go learn something about typography. |
#187
|
|||
|
|||
Technical & legal background using copyrighted fonts in customroad signs in PowerPoint
On 09/15/2017 07:53 PM, Chaya Eve wrote:
On Sat, 16 Sep 2017 10:29:05 +1200, Your Name wrote: Because Usenet (and email) is *meant* to be plain text. "Curly quotes" (and "curly apostrophes") are not part of plain text, so some usenet newsreader applications do not work with them, which is the correct approach. Same goes for other non-plain text typographical characters, such as long dashes and ellipsis. Some badly made Usenet newsreader applications do work with "curly quotes", etc., but they're a pain in the backside in proper Usenet reader applications since the characters come through as strange characters. I didn't know that a "curly quote" is different from a "regular" quote until Paul's note about PowerPoint automatically substituting "curly quotes" for regular quotes. What the heck is the difference between regular and curly to us anyway? It's a quote for heaven's sake. What's so horrible about not-curly quotes that PowerPoint has to change them to "curly" quotes? Pick up a quality book from your book shelf, and look for a quote. (I just happened to pick up Rick Meyerowitz's "Drunk Stoned Brilliant Dead") At the beginning of the quote, the the double quotes have the dot at the bottom and the curly going up. At the end of the quote, the dot is at the top, and the curly goes down. I don't know that this is a constant, but I picked up a second book (Maroon & Wicker's "The Nixon Years"), and it was the same in that book. A sample of two in this case is sufficient for me. -- Ken Hart |
#188
|
|||
|
|||
Technical & legal background using copyrighted fonts in custom road signs in PowerPoint
On 2017-09-16 00:04:12 +0000, Paul said:
Your Name wrote: On 2017-09-15 11:14:48 +0000, Chaya Eve said: On Fri, 15 Sep 2017 11:11:31 +0000 (UTC), Chaya Eve wrote: The latest Win10 ships with a DIN-look-alike font named ¡Bahnschrift¢ Why do single and double quotes in PowerPoint always show up as funny characters in Usenet? Because Usenet (and email) is *meant* to be plain text. "Curly quotes" (and "curly apostrophes") are not part of plain text, so some usenet newsreader applications do not work with them, which is the correct approach. Same goes for other non-plain text typographical characters, such as long dashes and ellipsis. Some badly made Usenet newsreader applications do work with "curly quotes", etc., but they're a pain in the backside in proper Usenet reader applications since the characters come through as strange characters. I don't know if I'd call them badly made. snip Usenet and email are meant to be plain text. Any app that ignores that standard is badly made because it isn't sticking to the established rules. It's teh same issue that madea complete mess of website creatiojn wehn Microsloth decided to ignore the established ruels and do things their own way in Internt Exploiter (another badly made app). :-( |
#189
|
|||
|
|||
Technical & legal background using copyrighted fonts in custom road signs in PowerPoint
On 2017-09-16 01:24:39 +0000, Ken Hart said:
On 09/15/2017 07:53 PM, Chaya Eve wrote: On Sat, 16 Sep 2017 10:29:05 +1200, Your Name wrote: Because Usenet (and email) is *meant* to be plain text. "Curly quotes" (and "curly apostrophes") are not part of plain text, so some usenet newsreader applications do not work with them, which is the correct approach. Same goes for other non-plain text typographical characters, such as long dashes and ellipsis. Some badly made Usenet newsreader applications do work with "curly quotes", etc., but they're a pain in the backside in proper Usenet reader applications since the characters come through as strange characters. I didn't know that a "curly quote" is different from a "regular" quote until Paul's note about PowerPoint automatically substituting "curly quotes" for regular quotes. What the heck is the difference between regular and curly to us anyway? It's a quote for heaven's sake. What's so horrible about not-curly quotes that PowerPoint has to change them to "curly" quotes? Pick up a quality book from your book shelf, and look for a quote. (I just happened to pick up Rick Meyerowitz's "Drunk Stoned Brilliant Dead") At the beginning of the quote, the the double quotes have the dot at the bottom and the curly going up. At the end of the quote, the dot is at the top, and the curly goes down. I don't know that this is a constant, but I picked up a second book (Maroon & Wicker's "The Nixon Years"), and it was the same in that book. A sample of two in this case is sufficient for me. Yep, the "curly quote" is the proper way of doing it in publishing and should be in handwriting. The rule that used to be taught in schools was something like "66 and 99" around the quote because the start quote curls up and looks (sort-of) like tyhe number 66 while the end quote curls down and looks (sort-of) like the number 99. The straight quote was most likely brought in with the typewriter to save an extra key and the laziness / speed of the typist only needing to use one key. That followed through to early computers. These days most writing and desktop publishing apps will convert straight quotes to curly quotes (based on whether there's a space before or after them), although there's usually an option to turn that off if you want. The apostrophe in words like it's should also be curly (curling downwards) in proper publishing and there's a corressponding updward curly apostrophe for when using them as single quote marks. There are other typographical characters too. The ellipsis, for example, is usually typed as three fullstops (...) because that's what the typewriter and computer keyboard has, but in reality it's meant to be three dots that are closer together and apps like Word will automaticaly replace three consequetive fullstops with the correct character. It will also replace a hypen / minus sign used in the middle of a sentence - like this for example - with a longer hyphen (called either em dash or en dash, depending on its length). There are also some character combinations that often replaced by a single character because it looks better. the word "flood", for example" may have the f and l characters replaced by a single "fl" character. |
#190
|
|||
|
|||
Technical & legal background using copyrighted fonts in custom road signs in PowerPoint
In article , Your Name
wrote: Some badly made Usenet newsreader applications do work with "curly quotes", etc., but they're a pain in the backside in proper Usenet reader applications since the characters come through as strange characters. I don't know if I'd call them badly made. snip Usenet and email are meant to be plain text. Any app that ignores that standard is badly made because it isn't sticking to the established rules. curly quotes are plain text. It's teh same issue that madea complete mess of website creatiojn wehn Microsloth decided to ignore the established ruels and do things their own way in Internt Exploiter (another badly made app). :-( no it's not the same issue. not even close to the same issue. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
70+ Free Pixel Fonts | [email protected] | Digital Photography | 0 | May 6th 06 04:08 PM |
FS: ART Graphics Plug ins Backgrounds Fonts & More CD-ROM | Seals4Deals | Digital Photo Equipment For Sale | 0 | April 18th 06 03:20 PM |
FS: ART Graphics Plug ins Backgrounds Fonts & More CD-ROM | Seals4Deals | Digital Photo Equipment For Sale | 0 | March 9th 06 09:53 PM |
FS: ART Graphics Plug ins Backgrounds Fonts & More CD-ROM | Seals4Deals | Digital Photo Equipment For Sale | 0 | February 23rd 06 10:31 PM |
Wal-Mart won't print my digital photo..Said looked copyrighted. Help | Barry Fritz | Digital Photography | 108 | November 2nd 04 02:30 PM |