7 |
8 | **Caution:** *Use of proposed or accepted characters is at implementers'
9 | own risk; the composition and allocation of the characters may change
10 | before they are finally published in the Unicode Standard. Always check
11 | the [Unicode Pipeline](http://www.unicode.org/alloc/Pipeline.html)
12 | for the latest guidance.*
13 |
14 | The relevant characters are:
15 |
16 | - U+23FB POWER SYMBOL (⏻ or )
17 | - U+23FC POWER ON-OFF SYMBOL (⏼ or )
18 | - U+23FD POWER ON SYMBOL (⏽ or )
19 | - U+23FE POWER SLEEP SYMBOL (⏾ or )
21 |
22 | As well as U+2B58 HEAVY CIRCLE (⭘ or ) for the power off symbol.
23 |
24 | - Note that POWER SLEEP SYMBOL has been moved into the "Miscellaneous
25 | Technical Symbols" block in the Basic Multilingual Plane (BMP) at position
26 | U+23FE and given its proper name at last.
27 |
28 | See the [latest news](#update20150227) here. We hope to see the new symbols
29 | in Unicode version 9.0, expected in June or July, 2016.
30 |
31 | Add IEC 60417-5009 POWER SYMBOL ⏻ to the Unicode Standard
32 | ================================================================
33 |
34 | *With sincere thanks to the Unicode Technical Committee, UTC #138, and ISO 10646 JTC1/SC2/WG2 #62!*
35 |
36 | Success!
37 | --------
38 |
39 | The U+23FB ⏻[∗](#footnote-see-the-characters),
40 | U+23FC ⏼, U+23FD ⏽, U+23FE ⏾, and
41 | U+2B58 ⭘[†](http://www.jwz.org/blog/2011/11/you-doom-us-all-to-inhuman-toil-for-the-one-whose-name-cannot-be-expressed-in-the-basic-multilingual-plane/)
42 | characters now appear in the Unicode
43 | [Pipeline Table](http://www.unicode.org/alloc/Pipeline.html) with the
44 | status of “Accepted”. They can be used now, and designed into
45 | [fonts](#fonts), and they're on their way to be in a future version of the
46 | Unicode Standard after 7.0. The symbols were approved by the ISO 10646
47 | Working Group 2 (JTC 1/SC 2/WG 2) at the WG2 #62 meeting to go into
48 | [Amendment 2 to ISO/IEC 10646:2014](http://www.unicode.org/L2/L2014/14079-n4569.pdf)
49 | for publication in 2016. Right now they are in
50 | [ISO stage 5](http://www.unicode.org/alloc/ISOStages.html). See the
51 | [latest news](#update20140729) for details.
52 |
53 |
54 |
55 | ∗ These are the symbols:
56 | ,
57 | ,
58 | ,
59 | , and
60 | ,
61 | if you don't have the [font](#fonts) and can't see them yet.
62 | [Look here](http://call-with-current-continuation.com/unicode_font_test_page.html) [*external site*]
63 | for a test of dynamic font loading in your web browser.
64 |
65 | † The suggestion has been made that this character be
66 | co-located with the others in the Basic Multilingual Plane.
67 |
68 |
69 | Feel free to use our [proposal](https://github.com/jloughry/Unicode/raw/master/proposal.pdf)
70 | and [supporting information](#font-embedding-test) as a guide to making your own proposal
71 | a success.
72 |
73 | ### Lessons learnt from a [successful proposal](https://github.com/jloughry/Unicode/raw/master/proposal.pdf):
74 |
75 | 1. **Attestations are everything.** Committee members need to see *evidence that the characters
76 | are already in common use* in running text before a proposal will be accepted. The more
77 | attestations you provide, the better. Attestations are usually photographs or scans showing the
78 | occurrence of the proposed characters in print. We managed to find attestations dating back to
79 | 1984; some proposals for scripts of historical interest have attestations going back centuries
80 | or millennia.[‡](#success-footnotes)
81 |
82 | 2. Successful proposals **cover every angle and raise every anticipated objection** before those
83 | objections can be raised in committee. Our proposal took the risk of pointing out disagreement
84 | and ambiguities around the usage of some of the characters, especially ⏻; this was
85 | probably one of the strengths of our argument.
86 |
87 | 3. It is possible to do this in a **reasonable amount of time** (around two months, from
88 | start to finish, in our case).
89 |
90 | 4. Some [**artistic drawing talent**](#update20140206) may be helpful. You'll need to make
91 | a new font.
92 |
93 | 5. Do [**provide your font**](#fonts) along with the proposal, preferably through a clickable
94 | link in the PDF of the proposal, even though the
95 | [instructions for submission](http://www.unicode.org/pending/proposals.html) don't ask
96 | for it. During the UTC meeting when your proposal is considered, it's likely that
97 | subcommittee members will need to write a quick proposal in support of your proposal
98 | (that's how it's done) and it'll help them if your font is to hand when they need it.
99 | They can't just extract the font from the PDF of your proposal, as we thought they
100 | might.[§](#success-footnotes)
101 |
102 | 6. Complete the
103 | [ISO/IEC JTC 1/SC 2/WG 2 PROPOSAL SUMMARY FORM TO ACCOMPANY SUBMISSIONS FOR ADDITIONS TO THE REPERTOIRE OF ISO/IEC 10646](http://std.dkuug.dk/JTC1/SC2/WG2/docs/summaryform.html)
104 | and attach it to your proposal.
105 |
106 | 7. The right tool for font design is surprisingly important. A custom font is needed early
107 | in the process because it's needed to write the proposal, but you should design the font
108 | from the beginning to employ arbitrary Unicode code points, because you won't know until
109 | late in the process what the actual code points will be.
110 | [**Some of our work was wasted**](#notes-on-encoding); to avoid that, choose a range in
111 | the [Unicode Private Use Area](http://en.wikipedia.org/wiki/Private_Use_Areas) (E000 to F8FF)
112 | to serve as a placeholder until the UTC suggests real code points. This ensures that
113 | you don't get wrapped up in a font design tool that doesn't support Unicode—especially code
114 | points above FFFF—which lots of programmes still don't support correctly. See
115 | [Notes on Tools for Creating Fonts](#update20140202) below for more information on free font
116 | design tools that work.
117 |
118 | 8. Choose a font file format—SVG is good—that can handle metadata
119 | so it's possible to embed the font licence and designer's contact information in the font file.
120 | *The glyphs that will be standardised, that all subsequent font designers will follow, will be
121 | defined by the final font you submit.* Official font submission happens later in the process;
122 | our proposal has been formally accepted and we haven't been asked for the official font yet,
123 | so we still have an opportunity to [fine-tune](#phase-of-the-moon) the glyphs before then.
124 |
125 | 9. **Friends on the web** are an invaluable resource; sometimes they appear out of nowhere,
126 | provide free technical reviewing services, volunteer their time, and lend a hand. We couldn't
127 | have done it without them.
128 |
129 | 10. See our [successful proposal](https://github.com/jloughry/Unicode/raw/master/proposal.pdf)
130 | here and **use it as a model for your own.**
131 |
132 |
133 |
134 | ‡⏽ and ⭘ were found in the first IBM PC operating manual
135 | on page 1-11, but are believed to have been in use in the late nineteen-seventies.
136 |
137 | § [Extracting fonts from a PDF file in the form of usable font files](http://stackoverflow.com/questions/3488042/how-can-i-extract-embedded-fonts-from-a-pdf-as-valid-font-files) can be done,
138 | but it's not very easy.
139 |
140 | Get the Fonts Here
141 | ------------------
142 |
143 | Download one of the [Unicode_IEC_symbol_font.ttf](https://github.com/jloughry/Unicode/blob/master/Unicode_IEC_symbol_font.ttf?raw=true) (TrueType),
144 | [Unicode_IEC_symbol_font.otf](https://github.com/jloughry/Unicode/blob/master/Unicode_IEC_symbol_font.otf?raw=true) (OpenType),
145 | [Unicode_IEC_symbol_font.ps](https://github.com/jloughry/Unicode/blob/master/Unicode_IEC_symbol_font.ps?raw=true)
146 | (PostScript Type 0 font—a CMap file for it will be coming soon) font files
147 | and install it on your system.
148 |
149 | If you have the font installed, the ⏻ characters ⏼ should ⏽ appear
150 | ⏾ inline ⭘ here. (This may not work in all web browsers.) See the
151 | [Web Browser Test](#update20140212) section, especially the
152 | [HTML Font Embedding Test](#font-embedding-test) page below for a more thorough test
153 | of your web browser's support for Unicode fonts.
154 |
155 | *Use of proposed or accepted characters is at implementers’ own risk; the composition and allocation
156 | of the characters may change before they are finally published in the Unicode Standard. Always check
157 | the [Unicode Pipeline](http://www.unicode.org/alloc/Pipeline.html) for the latest guidance.*
158 |
159 | Web Browser Test
160 | ----------------
161 |
162 | ### Straight Compatibility Test
163 |
164 | Here are the new characters displayed without using HTML font embedding: can you see all of them?
165 |
166 | - ⏻ POWER SYMBOL
167 | - ⏼ POWER ON-OFF SYMBOL
168 | - ⏽ POWER ON SYMBOL
169 | - ⏾ POWER SLEEP SYMBOL
170 | - ⭘ HEAVY CIRCLE (POWER OFF)
171 |
172 | ### HTML Font Embedding Test
173 |
174 | [This page](http://call-with-current-continuation.com/unicode_font_test_page.html)
175 | uses font embedding in HTML and should work on more browsers.
176 |
177 | ### Test Results
178 |
179 |
180 |
Application
Version
Platform
Results
181 |
182 |
185 |
188 |
191 |
194 |
197 |
198 |
Firefox
26.0
Windows XP Professional Service Pack 3
199 |
202 |
205 |
208 |
211 |
214 |
215 |
Firefox
26.0
Mac OS X 10.6.8 (Intel)
216 |
219 |
222 |
225 |
228 |
∗
231 |
232 |
Firefox
27.0
Mac OS X 10.6.8 (Intel)
233 |
236 |
239 |
242 |
245 |
∗
248 |
249 |
Firefox
27.0
Mac OS X 10.9.1 (Intel)
250 |
253 |
256 |
259 |
262 |
265 |
266 |
Chrome §
32.0.1700.107 m
Windows XP Professional
267 | Service Pack 3
268 |
†
271 |
†
274 |
†
277 |
†
280 |
†
283 |
284 |
(Chrome with font embedding in CSS)
285 |
288 |
291 |
294 |
297 |
300 |
301 |
Chrome
32.0.1700.107
Mac OS X 10.7.5 (Intel)
302 |
305 |
308 |
311 |
314 |
†
317 |
318 |
Safari ∥
5.1.7 (7534.57.2)
Windows XP Professional
319 | Service Pack 3
320 |
†
323 |
†
326 |
†
329 |
†
332 |
†
335 |
336 |
(Safari with font embedding in CSS)
337 |
340 |
343 |
346 |
349 |
¶
352 |
353 |
Safari
5.1.10 (6534.59.10)
Mac OX X 10.6.8 (Intel)
354 |
357 |
360 |
363 |
366 |
†
369 |
370 |
Safari
6.1.1 (7537.73.11)
Mac OS X 10.7.5 (Intel)
371 |
374 |
377 |
380 |
383 |
†
386 |
387 |
Safari
7.0.1 (9537.73.11)
Mac OS X 10.9.1 (Intel)
388 |
391 |
394 |
397 |
400 |
403 |
404 |
Safari §, **
7.0.6 (11B651)
iPad
405 |
408 |
411 |
414 |
417 |
420 |
421 |
Safari §, **
7.0.6 (11B651)
iPhone
422 |
425 |
428 |
431 |
434 |
437 |
438 |
Sea Monkey
2.24
Mac OS X 10.7.5 (Intel)
439 |
442 |
445 |
448 |
451 |
∗
454 |
455 |
IE 8
8.0.6001.18702
Windows XP Professional
456 | Service Pack 3
457 |
†
460 |
†
463 |
†
466 |
†
469 |
†
472 |
473 |
(Microsoft Internet Explorer 8 with font embedding in CSS)
474 |
†
477 |
†
480 |
†
483 |
†
486 |
†
489 |
490 |
491 |
492 | \* Displays a small box with hexadecimal numbers in it like this: .
495 |
496 | † Displays an empty box like this: .
499 |
500 | ‡ See http://gschoppe.com/blog/fixing-unicode-support-in-google-chrome/
502 | for more information on Unicode support in Chrome under Windows.
503 |
504 | § Full support on these devices (everything works correctly) using
505 | [font embedding in CSS](#font-embedding-test).
506 |
507 | ∥ Partial support (everything but BLACK WANING CRESCENT MOON
508 | POWER SLEEP SYMBOL works) using
509 | [font embedding in CSS](#font-embedding-test).
510 |
511 | ¶ Safari displays a black box for BLACK WANING CRESCENT MOON
512 | POWER SLEEP SYMBOL, like this: .
514 | alt="black box"/>
515 |
516 | \*\* iOS was the only software found to display stacked diacritics correctly.
517 |
518 | Latest News
519 | -----------
520 |
521 | *(27th February 2015)*
522 |
523 | - [Feedback](http://blog.unicode.org/2015/02/feedback-on-repertoire-for-isoiec.html)
524 | on the
525 | [draft repertoire for ISO/IEC 10646:2014 (4th Edition, Amendment 2)](http://www.unicode.org/L2/L2015/15028-n4658-pdam23-charts.pdf)
526 | is being sought by the Unicode Technical Committee (UTC) this week. The
527 | relevant characters are:
528 |
529 | - U+23FB POWER SYMBOL
530 | - U+23FC POWER ON-OFF SYMBOL
531 | - U+23FD POWER ON SYMBOL
532 | - U+23FE POWER SLEEP SYMBOL
533 |
534 | - As well as U+2B58 HEAVY CIRCLE for the power off symbol.
535 |
536 | - Note that POWER SLEEP SYMBOL has been moved into the "Miscellaneous
537 | Technical Symbols" block in the Basic Multilingual Plane (BMP) at position
538 | U+23FE and given its proper name at last.
539 |
540 | *(27th October 2014)*
541 |
542 | - For historical reasons, [this](http://hea-www.harvard.edu/~fine/OSX/unicode_apple_logo.html)
543 | was probably the original inspiration for this project (see [Reference 10](#ref10)).
544 |
545 | *(20th August 2014)*
546 |
547 | - New major revisions of Unicode are now expected to be published every year in June;
548 | look for Unicode 8.0 in June 2015, and Unicode 9.0 in June 2016.
549 |
550 | *(29th July 2014)*
551 |
552 | - Unicode 8.0 will contain Amendment 1 characters but probably not Amendment 2; these
553 | will come later in the calendar. The repertoire in which our symbols appear is
554 | [ISO/IEC 10646:2014 (4th Edition, Amendment 2)](http://www.unicode.org/L2/L2014/14142-10646-4th-pdam2.pdf).
555 |
556 | - [Feedback](http://www.unicode.org/review/pri276/) by others on Amendment 2 has suggested
557 | that POWER SLEEP SYMBOL ought to be encoded in the "Miscellaneous Technical Symbols" block
558 | in the Basic Multilingual Plane (BMP), perhaps at U+23FE. This would co-locate it "...with
559 | the other power related symbols in the same Unicode block."
560 |
561 | *(27th June 2014)*
562 |
563 | - The new symbols 23FB POWER SYMBOL, 23FC POWER ON-OFF SYMBOL, 23FD POWER ON SYMBOL,
564 | and 1F32D BLACK WANING CRESCENT MOON (use for POWER SLEEP SYMBOL)
565 | 23FE POWER SLEEP SYMBOL, together with the
566 | new cross reference on 2B58 HEAVY CIRCLE (use for POWER OFF SYMBOL) appear in the
567 | [Draft Additional Repertoire for Amendment 2 to ISO/IEC 10646:2014
568 | (4th Edition)](http://www.unicode.org/L2/L2014/14142-10646-4th-pdam2.pdf). The draft
569 | repertoire is in the Proposed Draft Amendment (PDAM) stage.
570 | [Your help is requested](http://www.unicode.org/review/pri276/) to discover any errors
571 | in character names, incorrect glyphs, or other problems.
572 |
573 | *(11th March 2014)*
574 |
575 | - I was interviewed on the
576 | [BBC Radio 5](http://downloads.bbc.co.uk/podcasts/fivelive/pods/pods_20140311-0600a.mp3)
577 | programme *Outriders* by Jamillah Knowles.
578 |
579 | *(5th March 2014)*
580 |
581 | - The [Unicode Pipeline Table](http://www.unicode.org/alloc/Pipeline.html) has been updated.
582 | Our new characters are in [ISO stage 5](http://www.unicode.org/alloc/ISOStages.html) (of 8 stages)
583 | and on track for publication in 2016 as
584 | [amendment 2 to ISO/IEC 10646:2014](http://www.unicode.org/L2/L2014/14079-n4569.pdf).
585 |
586 | *(25th February 2014)*
587 |
588 | - The symbols were approved by the ISO 10646 Working Group 2 (JTC 1/SC 2/WG 2) at the
589 | WG2 #62 meeting this week to go onto an ISO amendment; the document number of the proposal
590 | is N4567.
591 |
592 | *(14th February 2014)*
593 |
594 | - The new characters appear in the
595 | [Pipeline Table](http://www.unicode.org/alloc/Pipeline.html).
596 |
597 | - Starting a write-up for [Hacker News](https://news.ycombinator.com/) (not published yet).
598 | See [my advice to HN readers](#update20140221) in progress.
599 |
600 | *(12th February 2014)*
601 |
602 | - [Test page](#update20140212) for web browsers.
603 |
604 | *(8th February 2014)*
605 |
606 | - Working on a [CMap file](#ref9) for the Postscript Type 0 font.
607 |
608 | *(7th February 2014)*
609 |
610 | - Here is a [diagram](#update20140207) of the compass and straightedge construction.
611 |
612 | *(6th February 2014)*
613 |
614 | - [Notes on Constructing the BLACK WANING CRESCENT MOON POWER SLEEP SYMBOL](#update20140206)
615 | with compass and straightedge.
616 |
617 | - Updated [proposal](https://github.com/jloughry/Unicode/raw/master/proposal.pdf)
618 | according to revision notes from UTC #138.
619 |
620 | *(5th February 2014)*
621 |
622 | - New fonts with Unicode character code points:
623 | [Unicode_IEC_symbol_font.ttf](https://github.com/jloughry/Unicode/blob/master/Unicode_IEC_symbol_font.ttf?raw=true) (TrueType) and
624 | [Unicode_IEC_symbol_font.otf](https://github.com/jloughry/Unicode/blob/master/Unicode_IEC_symbol_font.otf?raw=true) (OpenType).
625 |
626 | - See the updated
627 | [proposal](https://github.com/jloughry/Unicode/raw/master/proposal.pdf)
628 | (in Table 6 on page 7 of the PDF file) for instructions on how to type the new characters.
629 |
630 | - The (POWER SLEEP SYMBOL) character now exhibits the
633 | [correct phase of the moon](#update20140206).
634 |
635 | - Updated [TO-DO](#TO-DO) list for wish-list items like `&power;`.
636 |
637 | *(4th February 2014)*
638 |
639 | - The UTC voted and formally accepted the following characters and code
640 | points:[7](#ref7), [8](#ref8)
641 |
642 |
664 |
665 | #### The last line above has since been changed to:
666 |
667 |
23FE;POWER SLEEP SYMBOL;So;0;ON;;;;;N;;;;;
668 |
669 |
670 | *(3rd February 2014)*
671 |
672 | - [Results of the UTC meeting](#update20140203) today.
673 |
674 | *(2nd February 2014)*
675 |
676 | - OpenType version of the
677 | [old font](https://github.com/jloughry/Unicode/blob/master/iec_symbol_font.otf?raw=true)
678 | and some more [information](#update20140202) on how the fonts were made.
679 |
680 | Get the fonts here:
681 | [TrueType](https://github.com/jloughry/Unicode/blob/master/Unicode_IEC_symbol_font.ttf?raw=true)
682 | or
683 | [OpenType](https://github.com/jloughry/Unicode/blob/master/Unicode_IEC_symbol_font.otf?raw=true)
684 | format.
685 |
686 | *(29th January 2014)*
687 |
688 | - We made it onto the [agenda](http://www.unicode.org/L2/L2014/14025.htm) for the
689 | [3–6 February 2014 meeting](http://www.unicode.org/timesens/logistics-utc138.html)
690 | of the [Unicode Technical Committee](http://www.unicode.org/consortium/utc.html)!
691 |
692 | - The proposal as submitted is
693 | [here](http://www.unicode.org/L2/L2014/14009-power-symbol.pdf)
694 | on the Unicode Consortium web site.
695 |
696 | *(Previous updates are [here](#update20140129).)
697 |
698 | Historical Section and Proposal Development
699 | ===========================================
700 |
701 | The following sections describe, in approximately chronological order, how the proposal
702 | was developed from start to finish. We began the project on 1st December 2013 and reached
703 | our goal the first week of February 2014.
704 |
705 | The IEC 60417-5009 “Stand-by” Symbol
706 | ------------------------------------------------
707 |
708 | On 1 December 2013, [Terence Eden](http://shkspr.mobi/blog/) posed a question to
709 | [Hacker News](https://news.ycombinator.com/item?id=6828102) asking why Unicode lacks
710 | the international symbol that appears on power switches. After searching for a while,
711 | I learnt he was right — in fact, Unicode lacks all of the following
712 | symbols:[1](#ref1)
713 |
714 |
715 |
716 |
IEC 60417-5007
717 |
IEC 60417-5008
718 |
IEC 60417-5009
719 |
IEC 60417-5010
720 |
IEEE 1621
721 |
722 |
723 |
727 |
731 |
735 |
739 |
743 |
744 |
745 |
“ON” (power)
746 |
“OFF” (power)
747 |
“Stand-by”
748 |
“ON”/“OFF” (push-push)
749 |
“Sleep”
750 |
751 |
Click on any image for SVG.
752 |
753 |
754 | Source of the above images: [Wikipedia](http://en.wikipedia.org/wiki/Power_symbol).
755 | The first four symbols were drawn by Wikipedia users
756 | [klork](http://commons.wikimedia.org/wiki/User:Klork) and
757 | [DarkEvil](http://commons.wikimedia.org/wiki/User:DarkEvil);
758 | the moon was made specifically for this purpose from the specifications in the
759 | [precise drawing](http://energy.lbl.gov/controls/publications/moonsymbol-brown.pdf).
760 |
761 | Clearly these would be useful to anyone writing technical or user manuals. In fact, for
762 | electronically publishing documentation, it is crucial to have symbols defined in
763 | Unicode because it makes them search-able in text.
764 |
765 | How to Add Symbols to Unicode
766 | -----------------------------
767 |
768 | [The Unicode Consortium](http://www.unicode.org/) has a procedure for
769 | [submitting character proposals](http://www.unicode.org/pending/proposals.html). None of
770 | the above symbols appear in the [pipeline](http://www.unicode.org/pending/proposals.html)
771 | of proposed new symbols, so **let's do it!**
772 |
773 | There are a few crescent moon symbols in Unicode already: the 🌙
774 | CRESCENT MOON (U+1F319), ☽ FIRST QUARTER MOON (U+263D), and
775 | ☾ LAST QUARTER MOON (U+263E) symbols, but none of them are exactly
776 | like the IEEE 1621 symbol; U+1F319 is closest, but faces the opposite direction.
777 |
778 | Getting Access to the “Official” Symbols
779 | ----------------------------------------------------
780 |
781 | [IEC](http://www.iec.ch/) charges
782 | [400 Swiss Francs](http://webstore.iec.ch/webstore/webstore.nsf/artnum/029221)
783 | (currently $440 USD) for their standard.[2](#ref2)
784 | [IEEE](http://standards.ieee.org/) charges
785 | [$58](http://www.techstreet.com/ieee/products/vendor_id/3344) for the
786 | IEEE 1621 standard.[3](#ref3)
787 |
788 | Before submitting a proposal, I would like to verify the specifications for each
789 | symbol shown above in IEEE 1621-2004 and IEC 61417, which is also
790 | [ISO 7000:2012](http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=60898),
791 | and then translate those into whatever form of description is required by Unicode.
792 |
793 | The ISO standard is free.[4](#ref4)
794 |
795 | Copyright of the Symbols
796 | ------------------------
797 |
798 | [Alex Stapleton](https://twitter.com/alexstapleton) in
799 | [this conversation](https://twitter.com/alexstapleton/status/407468582860111873)
800 | on Twitter checked the introduction of IEC 60417 for copyright information and
801 | vector drawings of the symbols.
802 |
803 | The [SVG](http://en.wikipedia.org/wiki/Svg) files for the symbols in the table
804 | are public domain.
805 |
806 | You know, it's
807 | [really hard](http://graphicdesign.stackexchange.com/questions/8586/can-i-freely-use-the-fire-exit-symbol-and-similar-iso-symbols)
808 | to find a straight answer to the question of whether ISO standard symbols are
809 | copyrighted by ISO. Evidently, they are not, but the standard *doesn't say so*.
810 |
811 | Here is what I think the law says:
812 |
813 | - Everyone is encouraged to make their things compliant with relevant and current
814 | ISO standards.
815 |
816 | - To do so, makers need a copy of the standard; they can purchase it from ISO.
817 |
818 | - Copyright of the standard document itself belongs to ISO, so pirating standards
819 | documents is a no-no.
820 |
821 | - But there is no royalty cost or anything like that on things made according to
822 | the standard.
823 |
824 | I have been unable so far to find a clear statement anywhere that **making things
825 | that are compliant with an ISO standard** is allowed. It's probably buried in the
826 | ISO by-laws.
827 |
828 | I'm not going to worry about it. The Unicode Technical Committee undoubtedly has
829 | thought about this before and probably knows the answer.
830 |
831 | Draft Proposal
832 | --------------
833 |
834 | The current draft proposal is always
835 | [here](https://github.com/jloughry/Unicode/raw/master/proposal.pdf) (PDF).
836 |
837 | #### Acknowledgements
838 |
839 | Thanks to everyone here for technical reviews, suggestions, improvements, and
840 | finding errors and omissions:
841 |
842 | - Terence Eden
843 |
844 | - Bruce Nordman
845 |
846 | - Adam De Witt
847 |
848 | - [@yuasakusa](https://twitter.com/yuasakusa)
849 |
850 | - Rick McGowan
851 |
852 | #### Late Updates to the Proposal
853 |
854 | I changed the *name* character properties of some of the proposed characters to
855 | be more descriptive, and to remove a disallowed character, in response to a
856 | [Twitter note](https://twitter.com/yuasakusa/status/424666695626530816) from
857 | [@yuasakusa](https://twitter.com/yuasakusa)—thanks!
858 |
859 | In brief, the suggested character properties are now (with names and code points from UTC #138):
860 |
861 |
862 |
863 |
Char
CP
Unicode Name
GC
CC
BC
D
NT
NV
B
1
I
U
L
T
864 |
865 |
866 |
23FB
POWER SYMBOL[*](#note-star)
So
0
ON
N
867 |
868 |
869 |
2B58
HEAVY CIRCLE[†](#note-dagger)
So
0
ON
N
870 |
871 |
872 |
1F32D 23FE
POWER SLEEP SYMBOL BLACK WANING CRESCENT MOON[‡](#note-double-dagger)
So
0
ON
N
873 |
874 |
875 |
23FD
POWER ON SYMBOL
So
0
ON
N
876 |
877 |
878 |
23FC
POWER ON-OFF SYMBOL
So
0
ON
N
879 |
880 |
881 |
882 | Notes:
883 |
884 | ∗This character is cross referenced to .
885 |
886 | †This character is aliased to POWER OFF SYMBOL and cross referenced to .
887 |
888 | ‡This character is aliased to POWER SLEEP SYMBOL and cross referenced to .
889 |
890 | *(22nd January 2014)*
891 |
892 | - [Thanks](#update20140122) to everyone who's contributed!
893 |
894 | *(21st January 2014)*
895 |
896 | - The required *ISO/IEC JTC 1/SC 2/WG 2 PROPOSAL SUMMARY FORM TO ACCOMPANY
897 | SUBMISSIONS FOR ADDITIONS TO THE REPERTOIRE OF ISO/IEC 10646* is now
898 | included in the [proposal](#update20140121).
899 |
900 | *(19th January 2014)*
901 |
902 | - [Changed the *name* character properties](#update20140119) to be more descriptive.
903 |
904 | - Removed disallowed slash from the name of the symbol in the proposal.
907 |
908 | *(16th January 2014)*
909 |
910 | - Changed name of the TrueType font to
911 | [IECsymbol](https://github.com/jloughry/Unicode/blob/master/Unicode_IEC_symbol_font.ttf?raw=true)
912 | everywhere.
913 |
914 | - TrueType font files in Windows need to have the 'execute' permission set in UNIX (0755)
915 | or they aren't recognised as a valid font file.
916 |
917 | *(15th January 2014)*
918 |
919 | - We have a document number! It is
920 | [L2/14-009](http://www.unicode.org/L2/L2014/14009-power-symbol.pdf).
921 |
922 | - New co-author.
923 |
924 | - Corrected wrong usage of the IEEE 1621 “sleep”
925 | symbol everywhere.
926 |
927 | - In response to a reviewer's question, I added evidence of the symbols' usage
928 | in running text. I was able to find evidence dating as far back as the
929 | [IBM PC/XT *Guide to Operations*](http://www.retroarchive.org/dos/docs/ibm_pc_op_guide.pdf)
930 | from 1984.
931 |
932 | - Added further notes on [copyright](#update20140115).
933 |
934 | *(14th January 2014)* The UTC agenda for the 3—6 February 2014 meeting is
935 | now being compiled.
936 |
937 | *(13th January 2014)* The proposal is [ready to send](#update20140113) to UTC
938 | in time for the February meeting.
939 |
940 | *(11th January 2014)* [Call for agenda items](#update20140111) from the Unicode
941 | Technical Committee (UTC).
942 |
943 | *(7th January 2014)* [How you can help](#update20140107).
944 |
945 | #### Schedule for submitting the proposal
946 |
947 | The [proposal](https://github.com/jloughry/Unicode/raw/master/proposal.pdf)
948 | was submitted and approved by UTC #138.
949 |
950 | #### ISO Submission Form
951 |
952 | The *ISO/IEC JTC 1/SC 2/WG 2 PROPOSAL SUMMARY FORM TO ACCOMPANY SUBMISSIONS
953 | FOR ADDITIONS TO THE REPERTOIRE OF ISO/IEC 10646* form is appended to the proposal.
954 |
955 | #### Document Submission Notes
956 |
957 | - The call for agenda items for the UTC meeting in February is out.
958 |
959 | - I joined the Unicode Consortium as a
960 | [student member](http://www.unicode.org/consortium/levels.html#student)
961 | to get on the mailing list for Unicode Technical Committee meeting announcements
962 | and to gain access to the member section of the web site.
963 |
964 | - I have the document submission details now (it's in the members section).
965 | It is encouraged that a representative for each proposal to the
966 | [UTC](http://unicode.org/consortium/utc.html) should attend the meeting
967 | and present the document. The next meeting is
968 | [February 3–6, 2014](http://www.unicode.org/timesens/calendar.html) at
969 | [IBM in San Jose, California](http://www.unicode.org/timesens/logistics-utc138.html).
970 |
971 | ### How You Can Help
972 |
973 | We need reviewers for the draft proposal. It's not ready yet, but starting in a
974 | few days, [email me](mailto:joe.loughry@stx.ox.ac.uk) for a copy. What we are
975 | looking for is not just copy-editing, but:
976 |
977 | - Was there anything you tripped over?
978 |
979 | - Anything that felt out of place or inappropriate?
980 |
981 | - Is something missing?
982 |
983 | - Technical errors...
984 |
985 | - Spelling, grammar, or other problems, of course.
986 |
987 | Any review is valuable, but the most useful of all can be things like,
988 | *I got bored half-way through this section*. The current draft proposal is always
989 | [here](https://github.com/jloughry/Unicode/raw/master/proposal.pdf) (PDF). Email
990 | the author or use a GitHub [issue](https://github.com/jloughry/Unicode/issues),
991 | however you prefer.
992 |
993 | Thanks to Adam De Witt for the idea!
994 |
995 | ### TO-DO
996 |
997 | - Get the [World Wide Web Consortium (W3C)](http://www.w3c.org) to define HTML named character
998 | entities such as `&power;` for the new symbols to make them easier to type in HTML and XML.
999 |
1000 | - Improve the metadata in the fonts to include, at minimum, licence and description
1001 | information. These get embedded in the font file if present in the SVG source code.
1002 |
1003 | - Update the [Wikipedia page](http://en.wikipedia.org/wiki/Power_symbol) as soon
1004 | as it's official; Wikipedia admins keep
1005 | [reverting](http://en.wikipedia.org/w/index.php?title=Power_symbol&action=history)
1006 | changes made to the article pointing to this project. Thanks to
1007 | [daveljonez](https://github.com/daveljonez) for pointing this out.
1008 |
1009 | - Write a follow-up article for HN.
1010 |
1011 | ### DONE
1012 |
1013 | - Determine “character properties” like name, bidirectional
1014 | class, upper and lowercase mapping, line-breaking behaviour, and collation order
1015 | for the new symbols we're proposing.
1016 |
1017 | - Check the IEC and IEEE standards to verify that the symbols in the new font
1018 | are compliant with the specifications in the standards.
1019 |
1020 | - Read [guidelines](http://www.unicode.org/pending/proposals.html) and
1021 | [FAQ](http://www.unicode.org/faq/char_proposal.html) on the Unicode Consortium
1022 | web site for required or recommended proposal format.
1023 |
1024 | - Check to make sure these symbols are not in any upcoming draft standard.
1025 |
1026 | In the [latest edition](http://www.unicode.org/Public/UCD/latest/) of the standard,
1027 | *The Unicode Standard, Version 6.3.0* [5](#ref5), released 27th September
1028 | 2013, there are 11 occurrences of the word *power* in the Unicode Character Database:
1029 |
1030 |
1031 |
1032 |
Section
Code Point
Description
1033 |
1034 |
Telugu fractions and weights
1035 |
0C78
TELUGU FRACTION DIGIT ZERO FOR ODD POWERS OF FOUR
1036 |
0C79
TELUGU FRACTION DIGIT ONE FOR ODD POWERS OF FOUR
1037 |
0C7A
TELUGU FRACTION DIGIT TWO FOR ODD POWERS OF FOUR
1038 |
0C7B
TELUGU FRACTION DIGIT THREE FOR ODD POWERS OF FOUR
1039 |
0C7C
TELUGU FRACTION DIGIT ONE FOR EVEN POWERS OF FOUR
1040 |
0C7D
TELUGU FRACTION DIGIT TWO FOR EVEN POWERS OF FOUR
1041 |
0C7E
TELUGU FRACTION DIGIT THREE FOR EVEN POWERS OF FOUR
1042 |
1043 |
Miscellaneous Symbols
1044 |
26EE
GEAR WITH HANDLES (= power plant, power substation)
1045 |
1046 |
1047 |
Kangxi Radicals
1048 |
2F12
KANGXI RADICAL POWER
1049 |
1050 |
1051 |
Yijing Hexagram Symbols
1052 |
4DE1
HEXAGRAM FOR GREAT POWER
1053 |
1054 |
Mathematical Alphanumeric Symbols
1055 |
1D4AB
MATHEMATICAL SCRIPT CAPITAL P (= power set)
1056 |
1057 |
1058 |
1059 | ...but not the IEC power symbol. There are none in [BETA](http://www.unicode.org/ucd/#Beta)
1060 | right now, nor in the [pipeline](http://www.unicode.org/pending/proposals.html) as of
1061 | 20-December-2013; therefore, it is proper to submit a proposal at this time. Hints for
1062 | [Submitting Successful Character and Script Proposals](http://www.unicode.org/faq/char_proposal.html)
1063 | for submitting good proposals are being looked at.
1064 |
1065 | - Circulate the draft proposal for review.
1066 |
1067 | - Submit proposal to the UTC.
1068 |
1069 | - Put the new [code points](#update20140204) in the font.
1070 |
1071 | - Fix the axial tilt of the crescent moon POWER SLEEP SYMBOL to match the
1072 | [precise drawing](http://energy.lbl.gov/controls/publications/moonsymbol-brown.pdf)
1073 | and [explanation](http://energy.lbl.gov/controls/publications/moonsymbol020621.pdf)
1074 | of the drawing.[6](#ref6)
1075 |
1076 | - Document the compass-and-straightedge construction of the Unicode POWER SLEEP SYMBOL.
1077 |
1078 | - Make a PostScript font and CMAP file.
1079 |
1080 | ### Deadlines
1081 |
1082 | The calendar has been updated; the next quarterly meeting of the
1083 | [Unicode Technical Committee (UTC)](http://unicode.org/consortium/utc.html) will
1084 | take place [3–6 February 2014](http://www.unicode.org/timesens/calendar.html)
1085 | in San Jose, California. The next meeting after that is 6–9 May 2014.
1086 | I want to get our proposal submitted in time to make the agenda for the February
1087 | meeting (two weeks in advance).
1088 |
1089 | ### Results of the Unicode Technical Committee meeting on 3rd February 2014
1090 |
1091 | On the first day of their quarterly meeting, the Unicode Technical Committee (UTC)
1092 | reviewed our proposal first thing. There was discussion of whether some of the symbols
1093 | (POWER ON and POWER OFF) ought to be “unified” with existing symbols such
1094 | as the ASCII vertical bar. An *ad hoc* group discussed the unification question and
1095 | came back later in the day with a short document or counter-proposal listing names and
1096 | code points. The UTC is expected to vote on it tomorrow.
1097 |
1098 | ### What To Do Next
1099 |
1100 | After the proposal is submitted, I plant to submit a “Show HN” post
1101 | on HN telling how it was done.
1102 |
1103 | Notes on Tools for Creating Fonts
1104 | ---------------------------------
1105 |
1106 | There is an excellent
1107 | [SVG font tutorial](http://www.webdesignerdepot.com/2012/01/how-to-make-your-own-icon-webfont/)
1108 | specifically aimed at generating icon fonts. It includes an SVG font starter file,
1109 | instructions for using the SVG font editor built into Inkscape 0.48, recommendations
1110 | about which on-line font converters are most reliable, and tips for editing the
1111 | metadata and distributing the new font afterwards.
1112 |
1113 | Following the above recommendation, the
1114 | [Free Online Font Converter](http://www.freefontconverter.com/) was used to generate
1115 | [TrueType](https://github.com/jloughry/Unicode/blob/master/Unicode_IEC_symbol_font.ttf?raw=true)
1116 | and
1117 | [OpenType](https://github.com/jloughry/Unicode/blob/master/Unicode_IEC_symbol_font.otf?raw=true)
1118 | fonts from the
1119 | [SVG source](https://github.com/jloughry/Unicode/blob/master/graphics/Unicode_IEC_symbol_font.svg?raw=true)
1120 | file that was made with Inkscape.
1121 |
1122 | ### LaTeX
1123 |
1124 | These instructions for
1125 | [using TrueType fonts in LaTeX](http://fachschaft.physik.uni-greifswald.de/~stitch/ttf.html)
1126 | are straightforward, but a better method is to use
1127 | [XeTeX](http://en.wikipedia.org/wiki/XeTeX)
1128 | which has built-in support for TrueType fonts already installed in the OS,
1129 | and is available in MiKTeX 2.9.
1130 |
1131 | Notes on Encoding
1132 | -----------------
1133 |
1134 | Note: This section is obsolete; the [new fonts](#update20140205) have
1135 | [Unicode code points](#code-points) and should be used now.
1136 |
1137 | When designing a new font of symbols where there is no pre-existing ordering to use, what is the
1138 | best way to define the encoding? There are practical and aesthetic reasons for doing it
1139 | thoughtfully. The practical reason is, encodings are shared across fonts, and if a string encoded
1140 | in your new symbol font is accidentally changed to or displayed in a different font, it may
1141 | coincidentally spell out a message that is
1142 | [nonsensical, confusing, or offensive](http://www.snopes.com/rumors/wingdings.asp).
1143 | (Microsoft had this problem with the Wingdings font; it was either a coincidence or a conspiracy
1144 | depending on who's telling the story.)
1145 |
1146 | Years ago at Lockheed, they had a special font containing the corporate logo in a few sizes,
1147 | for use in Microsoft Word before such graphics were common. It was not uncommon back then to
1148 | open a Word document and see a big “L” on the page where the letterhead was
1149 | supposed to be, because the font wasn't loaded. The fact suggests that the font designer
1150 | thought about the encoding and put the corporate logo in the capital-L encoding slot for
1151 | that reason, so it would fail gracefully if the font were unavailable.
1152 |
1153 | In the absence of any well-defined convention for code pages in “sparse”
1154 | symbol fonts, here is a proposed encoding for the
1155 | [old font](https://github.com/jloughry/Unicode/blob/master/iec_symbol_font.ttf?raw=true):
1156 |
267 |
268 |
269 |
--------------------------------------------------------------------------------
/old_fonts/iec-power.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
6 |
46 |
--------------------------------------------------------------------------------
/old_fonts/iec-power.ttf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/jloughry/Unicode/805536fb6f93604da985d80e0c6b099f98f8b4d9/old_fonts/iec-power.ttf
--------------------------------------------------------------------------------
/old_fonts/iec-power.woff:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/jloughry/Unicode/805536fb6f93604da985d80e0c6b099f98f8b4d9/old_fonts/iec-power.woff
--------------------------------------------------------------------------------
/power_symbol_proposal.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/jloughry/Unicode/805536fb6f93604da985d80e0c6b099f98f8b4d9/power_symbol_proposal.pdf
--------------------------------------------------------------------------------
/proposal.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/jloughry/Unicode/805536fb6f93604da985d80e0c6b099f98f8b4d9/proposal.pdf
--------------------------------------------------------------------------------
/proposal.tex:
--------------------------------------------------------------------------------
1 | %
2 | % Proposal to The Unicode Consortium to include IEC-5007, -8, -9,
3 | % -10, and IEEE 1621-2004 "sleep" symbols in Unicode.
4 | %
5 | % For information on this file please contact Joe Loughry at
6 | % Tel. +1 303 221 4380 (time zone GMT minus 7 hours) or Email:
7 | % joe.loughry@stx.ox.ac.uk
8 | %
9 |
10 | \documentclass[10pt,a4paper]{article}
11 |
12 | \usepackage[english,british]{babel}
13 |
14 | % to let me use the new TrueType font we created:
15 | \usepackage{fontspec}
16 |
17 | % for commenting out blocks of code:
18 | \usepackage{comment}
19 |
20 | % for footnotes in tables:
21 | \usepackage{threeparttable}
22 |
23 | % for formatting URLs (the `obeyspaces' option is for URLs with spaces (%20) in them):
24 | \usepackage[obeyspaces]{url}
25 |
26 | % added 20130901.2347 for putting angled brackets around URLs:
27 | \newcommand{\URL}[1]{$\langle$\url{#1}$\rangle$}
28 |
29 | % make references and footnotes into clickable links in the PDF:
30 | \usepackage{hyperref}
31 |
32 | % for XeLaTeX logo
33 | \usepackage{hologo}
34 |
35 | % for multiple authors with different affiliations
36 | \usepackage{authblk}
37 |
38 | % for including pages from a separate PDF in the output (\includepdf command).
39 | \usepackage{pdfpages}
40 |
41 | % Use \UnicodeIEC{x} to display a symbol in the new font.
42 | \newcommand{\UnicodeIEC}[1]{{\fontspec{UnicodeIECsymbol}#1}}
43 |
44 | % Define a few shortcuts to make the new symbols easier to type.
45 | \newcommand{\IECpower}{\UnicodeIEC{\symbol{"23FB}}}
46 | \newcommand{\IEConoff}{\UnicodeIEC{\symbol{"23FC}}}
47 | \newcommand{\IECon}{\UnicodeIEC{\symbol{"23FD}}}
48 | \newcommand{\IECoff}{\UnicodeIEC{\symbol{"2B58}}}
49 | \newcommand{\IECsleep}{\UnicodeIEC{\symbol{"1F32D}}}
50 |
51 | % Tell Adobe Acrobat Reader not to display the bookmarks pane.
52 | \hypersetup{pdfpagemode=UseNone}
53 |
54 | % Tell it to start in my preferred size.
55 | \hypersetup{pdfstartview=FitH}
56 |
57 | % Fill in some other information in the PDF header.
58 | \hypersetup{pdftitle=Proposal to Include IEC Power Symbols}
59 | \hypersetup{pdfauthor=Terence Eden and Joe Loughry and Bruce Nordman}
60 | \hypersetup{pdfsubject=Unicode Character Proposal}
61 | \hypersetup{pdfkeywords={IEC power symbols Unicode font}}
62 |
63 | \begin{document}
64 |
65 | \title{Proposal to Include IEC Power Symbols}
66 |
67 | \author{Terence Eden%
68 | \thanks{Electronic address: \texttt{terence.eden@shkspr.mobi}} \and
69 | Joe Loughry%
70 | \thanks{Corresponding author's address (University of Oxford):
71 | \texttt{joe.loughry@stx.ox.ac.uk}}
72 | \and
73 | Bruce Nordman%
74 | \thanks{Lawrence Berkeley National Laboratory: \texttt{BNordman@LBL.gov}}}
75 |
76 | \maketitle
77 |
78 | % put a header on the page; the \pagestyle command must come after \maketitle
79 | \pagestyle{myheadings}
80 | \markright{\hfill Loughry\ }
81 |
82 | \begin{abstract}
83 | The international symbol IEC 60417-5009 \IECpower\ meaning `power'
84 | is not in Unicode. Clearly it would be useful to anyone writing technical or
85 | user manuals. Furthermore, for electronically published documentation, it is
86 | crucial for this and a few other symbols to be defined because it makes them
87 | searchable in plain text. In this proposal we provide TrueType and OpenType fonts
88 | named `UnicodeIECsymbol' containing the glyphs as specified in three international
89 | standards together with the needed character properties for Unicode specification
90 | as well as evidence that these characters have been used in running text
91 | for thirty years.
92 | \end{abstract}
93 |
94 | \section{Introduction}
95 |
96 | The \IECpower, \IEConoff, \IECoff, and \IECon\ symbols are defined in IEC 60417
97 | \cite{IEC60417}, which is also ISO 7000:2012 \cite{ISO7000}. IEEE 1621-2004
98 | defines \IECsleep\ and refines the definition of \IECpower, notably by saying:
99 |
100 | \begin{quote}
101 | IEC 60417 defines \IECpower\ for use with a power switch that does not do a total
102 | mains disconnect, and hence the device consumes standby power. \IECpower\ is
103 | generally used and understood to mean ``power,'' as on power buttons,
104 | indicators, and elsewhere. \IECpower, therefore, means ``power'' with a nonzero
105 | power level in the \emph{off} state. Electronic devices shall use \IECpower\ to
106 | be a synonym for ``power'' on power controls.
107 | \end{quote}
108 |
109 | \noindent \cite[\S 4.3, emphasis in original]{IEEE1621}. IEEE 1621-2004
110 | standardises current practice for devices with regard to the \IECpower\ symbol
111 | and introduces \IECsleep\ for sleep \cite{Nordman2003,Nordman2002a}.
112 |
113 | These characters, particularly \IECpower, are needed for
114 | technical writing and are not in Unicode. Adding these standardised symbols to
115 | Unicode will allow for their semantic identification and use. For the first
116 | time they would be searchable in plain text, something not possible with
117 | embedded graphics, which is the way the symbols have been displayed to date.
118 |
119 | \section{Suitability for Inclusion}
120 |
121 | These symbols are characters according to the definition in the Glossary,
122 | and do not appear in the Archive of Notices of Non-Approval. As of this writing,
123 | they are not included in the Unicode Pipeline Table or BETA. These symbols are
124 | widely used on electronic equipment and thus their technical documentation
125 | (Figures \ref{figure:example-of-use-Agilent}--\ref{figure:example-of-use-Ugolini}).
126 | Semantically identifying the symbols allows for textual search and programmatic
127 | decision making, as well as reducing the use of binary images and single purpose
128 | symbol fonts in technical writing. It would benefit technical writers and readers
129 | if they were available in Unicode because it would make user manuals and other
130 | technical documentation searchable in plain text.
131 |
132 | We provide along with our proposal TrueType and OpenType fonts, with no
133 | restrictions on their use.
134 |
135 | \section{Evidence of Use in Running Text}
136 |
137 | Figures \ref{figure:example-of-use-Agilent}--\ref{figure:example-of-use-Ugolini}
138 | show evidence of the use of each of these symbols in running text during the past
139 | thirty years.
140 |
141 | \begin{figure}[h!]
142 | \includegraphics[width=\textwidth]{graphics/Agilent2011.png}
143 | \caption{Example of \IECpower\ usage in running text from 2011,
144 | in the installation guide for a network analyser.
145 | From \cite[Chapter 2, p.~24]{Agilent2011}.}
146 | \label{figure:example-of-use-Agilent} % label must come after caption
147 | \end{figure}
148 |
149 | \begin{figure}[h!]
150 | \includegraphics[width=\textwidth]{graphics/Apple2007.png}
151 | \caption{Example of \IECpower\ usage in running text from 2007,
152 | in the user's guide for a computer. From \cite[Chapter 1, p.~12]{Apple2007}.}
153 | \label{figure:example-of-use-Apple} % label must come after caption
154 | \end{figure}
155 |
156 | \begin{figure}[h!]
157 | \includegraphics[width=\textwidth]{graphics/HP2009.png}
158 | \caption{Example of \IECpower\ usage in running text from 2009,
159 | in the setup guide for a printer. From \cite[p.~2]{HP2009}.}
160 | \label{figure:example-of-use-HP} % label must come after caption
161 | \end{figure}
162 |
163 | \begin{figure}[ht]
164 | \includegraphics[width=\textwidth]{graphics/IEEE1621.png}
165 | \caption{Example of \IECon, \IECsleep, and \IECoff\ usage in running
166 | text from 2004, in a standards document. From \cite[\S 4.5.2, p.~7]{IEEE1621}.}
167 | \label{figure:example-of-use-IEEE} % label must come after caption
168 | \end{figure}
169 |
170 | \begin{figure}[ht]
171 | \centering
172 | \includegraphics[width=0.5\textwidth]{graphics/IBM1984.png}
173 | \caption{Example of \IECon\ and \IECoff\ usage in running text from
174 | 1984, in the user manual for a computer. From \cite[p.~1-11]{IBM1984}.}
175 | \label{figure:example-of-use-IBM} % label must come after caption
176 | \end{figure}
177 |
178 | \begin{figure}[ht]
179 | \includegraphics[width=\textwidth]{graphics/Motorola2010.png}
180 | \caption{Example of \IECpower\ usage in running text from 2010,
181 | in the installation guide for a cable modem. From \cite[p.~7]{Motorola2010}.}
182 | \label{figure:example-of-use-Motorola} % label must come after caption
183 | \end{figure}
184 |
185 | \begin{figure}[ht]
186 | \includegraphics[width=\textwidth]{graphics/Nordman2002-0T.png}
187 | \caption{Example of \IECoff\ and \IEConoff\ used in running text, in a
188 | monograph from 2002. From \cite[p.~4]{Nordman2002} (used by permission).}
189 | \label{figure:example-of-use-Nordman-0T} % label must come after caption
190 | \end{figure}
191 |
192 | \begin{figure}[ht]
193 | \centering
194 | \includegraphics[width=0.8\textwidth]{graphics/Nordman2002-01TP.png}
195 | \caption{Example of \IECon, \IECoff, \IEConoff, and \IECpower\ usage in
196 | running text, in a monograph from 2002. From \cite[p.~2]{Nordman2002}
197 | (used by permission).}
198 | \label{figure:example-of-use-Nordman-01TP} % label must come after caption
199 | \end{figure}
200 |
201 | \begin{figure}[ht]
202 | \includegraphics[width=\textwidth]{graphics/Nordman2002-S.png}
203 | \caption{Example of \IECsleep\ used in running text, in a
204 | monograph from 2002. From \cite[p.~2]{Nordman2002} (used by permission).}
205 | \label{figure:example-of-use-Nordman-S} % label must come after caption
206 | \end{figure}
207 |
208 | \begin{figure}[ht]
209 | \centering
210 | \includegraphics[width=0.8\textwidth]{graphics/Ugolini2013.png}
211 | \caption{Example of \IECoff\ and \IECon\ used in running text from 2013,
212 | in the operator's manual for a coffee maker. From \cite[p.~18]{Ugolini2013}.}
213 | \label{figure:example-of-use-Ugolini} % label must come after caption
214 | \end{figure}
215 |
216 | \section{Character Properties}
217 |
218 | Suggested character properties for the proposed symbols are given in Tables
219 | \ref{table:character-properties-P}--\ref{table:character-properties-T} and
220 | here in Unicode Character Database (UCD) format. The names are generally
221 | similar to the names in IEEE 1621-2004. None of the proposed names appear
222 | already in the Character Name Index.
223 |
224 | \begin{quote}
225 | \begin{verbatim}
226 | 23FB;POWER SYMBOL;So;0;ON;;;;;N;;;;;
227 | 23FC;POWER ON-OFF SYMBOL;So;0;ON;;;;;N;;;;;
228 | 23FD;POWER ON SYMBOL;So;0;ON;;;;;N;;;;;
229 | 1F32D;BLACK WANING CRESCENT MOON;So;0;ON;;;;;N;;;;;
230 | \end{verbatim}
231 | \end{quote}
232 |
233 | \begin{table}[htbp]
234 | \centering
235 | \begin{tabular}{ll}
236 | \textbf{Property} & \textbf{Suggested Value} \\
237 | \hline \\
238 | Code point & 23FB \\
239 | Name & POWER SYMBOL \\
240 | General Category & So \\
241 | Canonical Combining Class & 0 \\
242 | Bidirectional Class & ON \\
243 | Decomposition Type/Decomposition Mapping \\
244 | Numeric Type \\
245 | Numeric Value \\
246 | Bidi Mirrored & N \\
247 | Unicode 1 Name \\
248 | ISO Comment \\
249 | Simple Uppercase Mapping \\
250 | Simple Lowercase Mapping \\
251 | Simple Titlecase Mapping \\
252 | \end{tabular}
253 | \caption{Suggested character properties for \IECpower. This
254 | symbol is cross referenced to \IECoff.}
255 | \label{table:character-properties-P} % label must come after caption!
256 | \end{table}
257 |
258 | \begin{table}[htbp]
259 | \centering
260 | \begin{tabular}{ll}
261 | \textbf{Property} & \textbf{Suggested Value} \\
262 | \hline \\
263 | Code point & 2B58 \\
264 | Name & HEAVY CIRCLE \\
265 | General Category & So \\
266 | Canonical Combining Class & 0 \\
267 | Bidirectional Class & ON \\
268 | Decomposition Type/Decomposition Mapping \\
269 | Numeric Type \\
270 | Numeric Value \\
271 | Bidi Mirrored & N \\
272 | Unicode 1 Name \\
273 | ISO Comment \\
274 | Simple Uppercase Mapping \\
275 | Simple Lowercase Mapping \\
276 | Simple Titlecase Mapping \\
277 | \end{tabular}
278 | \caption{Suggested character properties for \IECoff. This symbol was
279 | unified in UTC \#138 with the alias POWER OFF SYMBOL and cross
280 | referenced to \IECpower.}
281 | \label{table:character-properties-0} % label must come after caption!
282 | \end{table}
283 |
284 | \begin{table}[htbp]
285 | \centering
286 | \begin{tabular}{ll}
287 | \textbf{Property} & \textbf{Suggested Value} \\
288 | \hline \\
289 | Code point & 1F32D \\
290 | Name & BLACK WANING \\
291 | & CRESCENT MOON \\
292 | General Category & So \\
293 | Canonical Combining Class & 0 \\
294 | Bidirectional Class & ON \\
295 | Decomposition Type/Decomposition Mapping \\
296 | Numeric Type \\
297 | Numeric Value \\
298 | Bidi Mirrored & N \\
299 | Unicode 1 Name \\
300 | ISO Comment \\
301 | Simple Uppercase Mapping \\
302 | Simple Lowercase Mapping \\
303 | Simple Titlecase Mapping \\
304 | \end{tabular}
305 | \caption{Suggested character properties for \IECsleep. This symbol is
306 | cross referenced to \IECpower\ and has the alias POWER SLEEP SYMBOL.}
307 | \label{table:character-properties-S} % label must come after caption!
308 | \end{table}
309 |
310 | \begin{table}[htbp]
311 | \centering
312 | \begin{tabular}{ll}
313 | \textbf{Property} & \textbf{Suggested Value} \\
314 | \hline \\
315 | Code point & 23FD \\
316 | Name & POWER ON SYMBOL \\
317 | General Category & So \\
318 | Canonical Combining Class & 0 \\
319 | Bidirectional Class & ON \\
320 | Decomposition Type/Decomposition Mapping \\
321 | Numeric Type \\
322 | Numeric Value \\
323 | Bidi Mirrored & N \\
324 | Unicode 1 Name \\
325 | ISO Comment \\
326 | Simple Uppercase Mapping \\
327 | Simple Lowercase Mapping \\
328 | Simple Titlecase Mapping \\
329 | \end{tabular}
330 | \caption{Suggested character properties for \IECon.}
331 | \label{table:character-properties-1} % label must come after caption!
332 | \end{table}
333 |
334 | \begin{table}[htbp]
335 | \centering
336 | \begin{tabular}{ll}
337 | \textbf{Property} & \textbf{Suggested Value} \\
338 | \hline \\
339 | Code point & 23FC \\
340 | Name & POWER ON-OFF \\
341 | & SYMBOL \\
342 | General Category & So \\
343 | Canonical Combining Class & 0 \\
344 | Bidirectional Class & ON \\
345 | Decomposition Type/Decomposition Mapping \\
346 | Numeric Type \\
347 | Numeric Value \\
348 | Bidi Mirrored & N \\
349 | Unicode 1 Name \\
350 | ISO Comment \\
351 | Simple Uppercase Mapping \\
352 | Simple Lowercase Mapping \\
353 | Simple Titlecase Mapping \\
354 | \end{tabular}
355 | \caption{Suggested character properties for \IEConoff.}
356 | \label{table:character-properties-T} % label must come after caption!
357 | \end{table}
358 |
359 | \begin{samepage}
360 |
361 | \subsection{Collation Order}\label{section:collation-order}
362 |
363 | There is no required collation order, although there is an implied state transition
364 | ordering:
365 |
366 | \begin{quote}
367 | Power states shall be understood to have physical relationships to each other.
368 | Specifically, \emph{on} is taken to be above \emph{sleep}, and \emph{sleep}
369 | above \emph{off}.
370 | \end{quote}
371 |
372 | \noindent \cite[\S 4.4, emphasis in original]{IEEE1621}. We suggest \IECpower,
373 | \IECoff, \IECsleep, \IECon, \IEConoff. They exhibit no shaping behaviour and
374 | have no particular required sorting order (except see the quoted paragraph
375 | above). The characters are uncased. There is no special line-breaking
376 | behaviour required. These characters are not meant for use in identifiers,
377 | although they have been used for such.\footnote{This web site has a collection
378 | of more than thirty examples of IEC 60417-5009 used in logo design:
379 | \URL{http://www.logodesignlove.com/logos-using-the-standby-symbol}.} They are
380 | stand-alone symbols. They are not white-space characters and have no numeric
381 | values. They are neither combining characters nor punctuation.
382 |
383 | \end{samepage}
384 |
385 | \section{The \emph{UnicodeIECsymbol} Font}
386 |
387 | The five symbols included in the \emph{UnicodeIECsymbol} TrueType or OpenType font
388 | are shown in Table~\ref{table:symbols}. Only these symbols exist in the font; if
389 | an undefined character, for example `A' is called for in the font, the result is
390 | implementation-defined.\footnote{In \hologo{XeTeX}, for example, the result of
391 | `A' in \emph{UnicodeIECsymbol} is \UnicodeIEC{A}. In OpenOffice Writer, the
392 | result is the letter `A' but in a san-serif typeface.}
393 |
394 | \begin{table}[htbp]
395 | \centering
396 | \begin{threeparttable}
397 | \begin{tabular}{clll}
398 | \textbf{Character} & \textbf{Applicable} & \textbf{How to} & \textbf{Unicode Name} \\
399 | & \textbf{Standard(s)} & \textbf{Type It} \\
400 | \hline \\
401 | \IECpower & IEC 60417-5009 & \verb,⏻, & POWER SYMBOL \\
402 | \IEConoff & IEC 60417-5010 & \verb,⏼, & POWER ON-OFF SYMBOL \\
403 | \IECon & IEC 60417-5007 & \verb,⏽, & POWER ON SYMBOL \\
404 | \IECoff & IEC 60417-5008 & \verb,⭘, & HEAVY CIRCLE\tnote{*} \\
405 | \IECsleep & IEEE 1621-2004 & \verb,🌭, & BLACK WANING \\
406 | & & & CRESCENT MOON\tnote{$\dagger$} \\
407 | \end{tabular}
408 | \begin{tablenotes}
409 | \item[*] {\footnotesize This character is aliased to POWER OFF SYMBOL.}
410 | \item[$\dagger$] {\footnotesize This character is aliased to POWER SLEEP SYMBOL.}
411 | \end{tablenotes}
412 | \end{threeparttable}
413 | \caption{All of the available glyphs in the \emph{UnicodeIECsymbol} font.}
414 | \label{table:symbols} % label must come after caption!
415 | \end{table}
416 |
417 | \begin{comment}
418 | Placement of symbols in the \emph{UnicodeIECsymbol} TrueType font was chosen
419 | thoughtfully so as to be mnemonic: `P' for power, `S' for sleep,
420 | `T' for toggling power on or off, and `1' and `0' for power-on and power-off,
421 | respectively; these mnemonics `fail gracefully' in text should the
422 | \emph{UnicodeIECsymbol} font happen to be unavailable.
423 | \end{comment}
424 |
425 | In text with normal spacing, the \IECpower\ characters \IECoff\ look \IECsleep\ like
426 | \IECon\ this \IEConoff.\footnote{The spacing around \IECon\ in the font appears wider
427 | because the glyphs are fixed-width.}
428 |
429 | \section{Anticipated Objections}
430 |
431 | It might be argued that the meaning of \IECpower\ is disputed between IEC 60417 and
432 | IEEE 1621-2004, {\it i.e.}, that IEC 60417 (as well as ISO 7000:2012) defined
433 | \IECpower\ to mean `stand-by' and IEEE 1621-2004 changed it to mean `power'. We
434 | counter that the issue is irrelevant to the Unicode Consortium for two reasons:
435 | firstly, because the symbol itself is needed by writers, regardless of the fact
436 | that `stand-by' has no consistent definition;\footnote{The term is routinely used
437 | to mean \emph{off}, \emph{sleep}, \emph{on}, and other meanings that do not map
438 | to a consistent power state at all.} and secondly, because IEEE 1621-2004 specifically
439 | codifies existing practice; the number of devices using \IECpower\ to mean `power'
440 | dwarfs the number of devices that use it to mean `stand-by'.
441 | Furthermore,
442 |
443 | \begin{quote}
444 | No safety issue is introduced by the use of the symbol on a switch that causes
445 | the device to go to a \emph{hard-off} state.
446 | \end{quote}
447 |
448 | \noindent \cite[\S 4.3, emphasis in original]{IEEE1621}.
449 |
450 | There are, of course, many characters in Unicode already resembling circles
451 | (\IECoff), or lines (\IECon), or the crescent moon (\IECsleep). None of the existing
452 | characters, however, has anything semantically to do with the concepts of `power',
453 | `switch', `toggle', or `interrupter'. There are several occurrences of the crescent
454 | moon, but none showing the \IECsleep\ phase; IEEE 1621-2004 intended
455 | the symbol to be different from other Unicode instances of a crescent moon. There
456 | are eleven occurrences of the word `power' in Version 6.3.0 of the Unicode standard
457 | (Table \ref{table:power}) but none has anything to do with device control
458 | \cite{Unicode2013}. We caution against unifying \IECon\ with the ASCII vertical bar
459 | `\verb,|,' because of the high probability that both symbols will appear technical
460 | documents, inviting confusion. Likewise, we strongly recommend not unifying
461 | \IECoff\ with either capital `O' or the numeral zero because of the probability of
462 | confusion in technical documents.
463 |
464 | \section{Drawing the Symbols}
465 |
466 | The proposed characters are not part of any script and the precise form of
467 | their drawing is not critical. As IEEE 1621-2004 says:
468 |
469 | \begin{quote}
470 | In accordance with IEC 80416-3, symbols can be filled, be rotated, have their lines
471 | thickened, or be used on digital displays, as long as an ordinary user can recognize
472 | the symbol correctly.
473 | \end{quote}
474 |
475 | \noindent \cite[\S 4.3]{IEEE1621}. There is no need to mirror any of the symbols for
476 | right-to-left scripts.
477 |
478 | \begin{table}[htbp]
479 | \centering
480 | \begin{tabular}{lcl}
481 | \textbf{Section} & \textbf{Code Point} & \textbf{Description} \\
482 | \hline \\
483 | Telugu fractions \
484 | & 0C78 & TELUGU FRACTION DIGIT \\
485 | and weights & & ZERO FOR ODD POWERS \\
486 | & & OF FOUR \\
487 | & 0C79 & TELUGU FRACTION DIGIT \\
488 | & & ONE FOR ODD POWERS \\
489 | & & OF FOUR \\
490 | & 0C7A & TELUGU FRACTION DIGIT \\
491 | & & TWO FOR ODD POWERS \\
492 | & & OF FOUR \\
493 | & 0C7B & TELUGU FRACTION DIGIT \\
494 | & & THREE FOR ODD POWERS \\
495 | & & OF FOUR \\
496 | & 0C7C & TELUGU FRACTION DIGIT \\
497 | & & ONE FOR EVEN POWERS \\
498 | & & OF FOUR \\
499 | & 0C7D & TELUGU FRACTION DIGIT \\
500 | & & TWO FOR EVEN POWERS \\
501 | & & OF FOUR \\
502 | & 0C7E & TELUGU FRACTION DIGIT \\
503 | & & THREE FOR EVEN \\
504 | & & POWERS OF FOUR \\
505 | \hline
506 | Miscellaneous \
507 | & 26EE & GEAR WITH HANDLES \\
508 | Symbols & & (= power plant, power \\
509 | & & substation) \\
510 | \hline
511 | Kangxi Radicals \
512 | & 2F12 & KANGXI RADICAL POWER \\
513 | \hline
514 | Yijing Hexagram Symbols \
515 | & 4DE1 & HEXAGRAM FOR GREAT \\
516 | & & POWER \\
517 | \hline
518 | Mathematical \
519 | & 1D4AB & MATHEMATICAL SCRIPT \\
520 | Alphanumeric Symbols & & CAPITAL P (= power set) \\
521 | \end{tabular}
522 | \caption{All occurrences of `power' in the Unicode Standard, Version 6.3.0.}
523 | \label{table:power} % label must come after caption!
524 | \end{table}
525 |
526 | \subsection{Severability}
527 |
528 | Of all the characters in Table \ref{table:symbols}, the most needed is \IECpower.
529 | We included the others in this proposal because they form a logical group. If,
530 | however, there is any objection to inclusion of \IECon, \IECoff, \IEConoff, or
531 | \IECsleep, the one we most need is \IECpower.
532 |
533 | \section{Sponsors}
534 |
535 | The address for correspondence is:
536 |
537 | \begin{quote}
538 | Joe Loughry \\
539 | 6214 South Krameria Street \\
540 | Centennial, CO 80111-4243 \\
541 | USA
542 |
543 | \medskip Tel.\ +1 303 221 4380
544 |
545 | \medskip Email:~\texttt{joe.loughry@stx.ox.ac.uk}
546 | \end{quote}
547 |
548 | \noindent The other sponsors' postal addresses are:
549 |
550 | \begin{quote}
551 | Terence Eden \\
552 | 24 Thames View Road \\
553 | Oxford, OX4 4TG \\
554 | ENGLAND
555 |
556 | \medskip Email: \texttt{terence.eden@shkspr.mobi}
557 | \end{quote}
558 |
559 | \noindent and
560 |
561 | \begin{quote}
562 | Bruce Nordman \\
563 | 90-2000 \\
564 | 1 Cyclotron Road \\
565 | Lawrence Berkeley National Laboratory \\
566 | Berkeley, CA 94720-8130 \\
567 | USA
568 |
569 | \medskip Tel.\ 510-486-7089
570 |
571 | \medskip Email: \texttt{BNordman@LBL.gov}
572 | \end{quote}
573 |
574 | \section{Summary and Conclusion}
575 |
576 | The \IECpower, \IECoff, \IECsleep, \IECon, and \IEConoff\ symbols are needed
577 | by technical writers to produce manuals in which these important symbols are
578 | searchable in plain text. Because they were invented by the standards body to
579 | be distinctive, new, and unambiguous, there is no confusion with existing
580 | scripts. They have been in use in running text for at least thirty years. The
581 | suggested character properties are straightforward. We provide along with this
582 | proposal TrueType and OpenType fonts called \emph{UnicodeIECsymbol}
583 | containing the new symbols; the fonts are made available with no restrictions.
584 |
585 | \bibliographystyle{plain}
586 | \bibliography{consolidated_bibtex_file}
587 |
588 | \vfill
589 | \noindent{\tiny This document was made with \hologo{XeTeX}. Build \input{build_counter.txt}}
590 |
591 | \newpage
592 | \includepdf[pages={1-2}]{ISO_submission_form/n4102-form-completed.pdf}
593 |
594 | \end{document}
595 |
596 |
--------------------------------------------------------------------------------
/submitted_20140114.1430/power_symbol_proposal.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/jloughry/Unicode/805536fb6f93604da985d80e0c6b099f98f8b4d9/submitted_20140114.1430/power_symbol_proposal.pdf
--------------------------------------------------------------------------------
/submitted_20140115.1204/power_symbol_proposal_revised.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/jloughry/Unicode/805536fb6f93604da985d80e0c6b099f98f8b4d9/submitted_20140115.1204/power_symbol_proposal_revised.pdf
--------------------------------------------------------------------------------
/unicode_font_test_page.html:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/jloughry/Unicode/805536fb6f93604da985d80e0c6b099f98f8b4d9/unicode_font_test_page.html
--------------------------------------------------------------------------------
/working_group/14059-power.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/jloughry/Unicode/805536fb6f93604da985d80e0c6b099f98f8b4d9/working_group/14059-power.pdf
--------------------------------------------------------------------------------