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 |
#21
|
|||
|
|||
Short on my metal case (ouch)
Loren Pechtel wrote:
On Sun, 28 Jun 2015 01:18:00 -0400, Paul wrote: Loren Pechtel wrote: On Wed, 24 Jun 2015 00:49:59 +0000 (UTC), "JT" wrote: The ohm symbol O That came through here as a plain O. That's why I described it rather than trying to actually embed it--no knowing exactly what font support there will be on the other end. What happens if you just find the symbol in some text and just paste it ? 1000 ? Let's see how that comes out. Paul It doesn't look quite the same but it's still showing as a circle, not an Ohm symbol. When I sent my message, I sent it UTF-8. The transfer encoding in the header says: Content-Transfer-Encoding: 8bit I found my message on this server... http://al.howardknight.net/msgid.cgi...nt-email.me%3E and what was transmitted from my end was (in hex) 0xCE 0xA9 --- the ohm symbol The page here, describes the UTF-8 scheme, and (near the bottom) it shows that exotic characters use two bytes, while regular characters use one byte. And in their table, 0xCE 0xB8 maps to theta, suggesting 0xCE is for some Greek letters. http://gedcom-parse.sourceforge.net/doc/encoding.html The question then is, whether your newsreader handles stuff like that or not. If you go back far enough (like some of the USENET readers I used eons ago), they were really only good for vanilla ASCII, and didn't understand anything else. I used a newsreader back in the beginning, which wasn't even threaded. And that was the era, where quoting style was *very* important :-) It was pure luxury, when I got my first threaded reader operating. Back then, we compiled them from source (Unix box). Paul |
#22
|
|||
|
|||
Short on my metal case (ouch)
Paul wrote:
Loren Pechtel wrote: On Wed, 24 Jun 2015 00:49:59 +0000 (UTC), "JT" wrote: The ohm symbol O That came through here as a plain O. That's why I described it rather than trying to actually embed it--no knowing exactly what font support there will be on the other end. What happens if you just find the symbol in some text and just paste it ? 1000 Ω Let's see how that comes out. Paul Looks good to me Paul! JT |
#23
|
|||
|
|||
Short on my metal case (ouch)
JT wrote:
Paul wrote: Loren Pechtel wrote: On Wed, 24 Jun 2015 00:49:59 +0000 (UTC), "JT" wrote: The ohm symbol O That came through here as a plain O. That's why I described it rather than trying to actually embed it--no knowing exactly what font support there will be on the other end. What happens if you just find the symbol in some text and just paste it ? 1000 Ω Let's see how that comes out. Paul Looks good to me Paul! JT Write it as \Omega and it will appear the same on everyone's browser (that's one of the "right" solutions) |
#24
|
|||
|
|||
Short on my metal case (ouch)
Bill wrote:
JT wrote: Paul wrote: Loren Pechtel wrote: On Wed, 24 Jun 2015 00:49:59 +0000 (UTC), "JT" wrote: The ohm symbol O That came through here as a plain O. That's why I described it rather than trying to actually embed it--no knowing exactly what font support there will be on the other end. What happens if you just find the symbol in some text and just paste it ? 1000 Ω Let's see how that comes out. Paul Looks good to me Paul! JT Write it as \Omega and it will appear the same on everyone's browser (that's one of the "right" solutions) That string isn't rendering here. What option would I need to turn on ? The HTML capability on my USENET client is turned off. OK, this article says your construct is for Tex :-) https://en.wikipedia.org/wiki/Omega_(letter) Paul |
#25
|
|||
|
|||
Short on my metal case (ouch)
Paul wrote:
Bill wrote: JT wrote: Paul wrote: Loren Pechtel wrote: On Wed, 24 Jun 2015 00:49:59 +0000 (UTC), "JT" wrote: The ohm symbol O That came through here as a plain O. That's why I described it rather than trying to actually embed it--no knowing exactly what font support there will be on the other end. What happens if you just find the symbol in some text and just paste it ? 1000 Ω Let's see how that comes out. Paul Looks good to me Paul! JT Write it as \Omega and it will appear the same on everyone's browser (that's one of the "right" solutions) That string isn't rendering here. What option would I need to turn on ? It may look like Latex or Tex, but I intend it just as text. The point is that it is machine independent (like newsgroups were intended to be). Cheers, Bill The HTML capability on my USENET client is turned off. OK, this article says your construct is for Tex :-) https://en.wikipedia.org/wiki/Omega_(letter) Paul |
#26
|
|||
|
|||
Short on my metal case (ouch)
Bill wrote:
Paul wrote: Bill wrote: JT wrote: Paul wrote: Loren Pechtel wrote: On Wed, 24 Jun 2015 00:49:59 +0000 (UTC), "JT" wrote: The ohm symbol O That came through here as a plain O. That's why I described it rather than trying to actually embed it--no knowing exactly what font support there will be on the other end. What happens if you just find the symbol in some text and just paste it ? 1000 Ω Let's see how that comes out. Paul Looks good to me Paul! JT Write it as \Omega and it will appear the same on everyone's browser (that's one of the "right" solutions) That string isn't rendering here. What option would I need to turn on ? It may look like Latex or Tex, but I intend it just as text. The point is that it is machine independent (like newsgroups were intended to be). Cheers, Bill Note: This gives you a way to insert characters like \Alpha or \alpha into your text in an effective way that won't get lost in the translation. You can even refer to the \' or \tab characters if you like. I'm not sure about a \space character. I don't think \space is defined in Tex, but you know what I mean, I think. The HTML capability on my USENET client is turned off. OK, this article says your construct is for Tex :-) https://en.wikipedia.org/wiki/Omega_(letter) Paul |
#27
|
|||
|
|||
Short on my metal case (ouch)
On Mon, 29 Jun 2015 20:41:27 -0400, Paul wrote:
It doesn't look quite the same but it's still showing as a circle, not an Ohm symbol. When I sent my message, I sent it UTF-8. The transfer encoding in the header says: Content-Transfer-Encoding: 8bit I found my message on this server... http://al.howardknight.net/msgid.cgi...nt-email.me%3E and what was transmitted from my end was (in hex) 0xCE 0xA9 --- the ohm symbol The page here, describes the UTF-8 scheme, and (near the bottom) it shows that exotic characters use two bytes, while regular characters use one byte. And in their table, 0xCE 0xB8 maps to theta, suggesting 0xCE is for some Greek letters. http://gedcom-parse.sourceforge.net/doc/encoding.html The question then is, whether your newsreader handles stuff like that or not. If you go back far enough (like some of the USENET readers I used eons ago), they were really only good for vanilla ASCII, and didn't understand anything else. I used a newsreader back in the beginning, which wasn't even threaded. And that was the era, where quoting style was *very* important :-) It was pure luxury, when I got my first threaded reader operating. Back then, we compiled them from source (Unix box). I'm using Agent 4.2 (I haven't seen anything in the newer versions that is worth upgrading over.) I believe it supports Unicode. |
#28
|
|||
|
|||
Short on my metal case (ouch)
Loren Pechtel wrote:
On Mon, 29 Jun 2015 20:41:27 -0400, Paul wrote: It doesn't look quite the same but it's still showing as a circle, not an Ohm symbol. When I sent my message, I sent it UTF-8. The transfer encoding in the header says: Content-Transfer-Encoding: 8bit I found my message on this server... http://al.howardknight.net/msgid.cgi...nt-email.me%3E and what was transmitted from my end was (in hex) 0xCE 0xA9 --- the ohm symbol Hence my argument to use \Omega instead. It doesn't get any easier. The page here, describes the UTF-8 scheme, and (near the bottom) it shows that exotic characters use two bytes, while regular characters use one byte. And in their table, 0xCE 0xB8 maps to theta, suggesting 0xCE is for some Greek letters. http://gedcom-parse.sourceforge.net/doc/encoding.html The question then is, whether your newsreader handles stuff like that or not. If you go back far enough (like some of the USENET readers I used eons ago), they were really only good for vanilla ASCII, and didn't understand anything else. I used a newsreader back in the beginning, which wasn't even threaded. And that was the era, where quoting style was *very* important :-) It was pure luxury, when I got my first threaded reader operating. Back then, we compiled them from source (Unix box). I'm using Agent 4.2 (I haven't seen anything in the newer versions that is worth upgrading over.) I believe it supports Unicode. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Anti-corrosion paint for old metal case | Man-wai Chang to The Door (+MS=32B) | Homebuilt PC's | 7 | November 5th 09 07:12 AM |
Case Short | Hardline | General | 7 | January 11th 07 07:24 PM |
need switches and LEDs that snap into the metal case | Bill Schaible | Homebuilt PC's | 2 | November 30th 05 03:59 PM |
Can the case short out? | bendy | Homebuilt PC's | 2 | September 10th 04 05:03 AM |
Short case fan wire - is there another way? | N/A | Asus Motherboards | 3 | June 20th 04 08:23 PM |