Hi Jan,
Windows has a built-in facility to do just that: C:\WINDOWS\system32\charmap.exe (works a bit faster).
Cheers,
E.
Windows has a built-in facility to do just that: C:\WINDOWS\system32\charmap.exe (works a bit faster).
Cheers,
E.
Spice is a special case. In order to maintain case insensitivity, they needed to have something unique for milli and mega, since both use a single 'm' in a different case. So they chose to keep m for milli and use meg for mega. Also, since everything is based on plain ascii text input and output (and there is no "mu" character in ascii code), they chose to use 'u' for micro.
so Does Mac, by opening Apple menu/System preferences/Keyboard and enabling 'show keyboard and character viewers in menu bar' then in top right of the screen 'show character viewer' you can then select all sorts of currency, Math, latin etc and make your own containing all the characters you want.
Hi,
Windows 7 the easy way: Win-key type "character map", only "char" may be enough (depending on other installed programs) and hit [enter].
Windows 7 the easy way: Win-key type "character map", only "char" may be enough (depending on other installed programs) and hit [enter].
on mac, at least on Lion anyway; once youve enabled it, its in the menu at all times. I should have made that clear
I'd use a space between V and RMS, writing
Japanese mains voltage is 100 V RMS.,
because RMS isn't really part of the unit but part of the sentence, where it describes the quantity being measured.
Wikipedia tells me both lower case and upper case abbreviations are used for RMS, so it seems both rms and RMS are acceptable:
Root mean square - Wikipedia, the free encyclopedia
I disagree with "100 V RMS"
I would prefer to read, in this order: VRMS, Vrms, VRMS, V RMS.
Back to the microfarad discussion, while "uF" is clearly non-standard and technically incorrect, it is also clear that uF is completely unambiguous. When you see "2.2 uF", you might think it is ugly, but you know instantly without benefit of context that it means "2.2 microfarad" and not anything else. I would try to never publish anything with "uF" in it, I would definitely get the right units on it (if possible), but for conversation it is OK. When you see "2.2 mfd" or "2.2 mf" or "2.2 mF", then you need to stop and figure out what the author probably meant, and ambiguity in a quantity is unforgivable. For that reason, I think that expressing a capacitance in millifarads should always be avoided. It is also extremely rarely used, making it unexpected, which substantially increases risk of misinterpretation. You can't change the past, and in the past, 'm' was sometimes used for micro, so don't use m to express milli specifically for capacitance! You can argue all day that "mF" really does mean millifarads (and you would be correct), but you can't make it unambiguous. That isn't up to any of us. Get over it.
Just reading along to some hard copy, when the author writes, "a useful rule to remember is that no space is used for a single-letter qualifier like “5V,” but spaces are used for multi-letter qualifiers like “5 Hz”, so it appears there is a rule for every combination.
These what i know, 5Vrms = 5V = 5 volts, its means rms value except write as 5Vpp = 5 volts peak to peak,
- Status
- Not open for further replies.