If more people *did* fall in step with standards (Microsoft included),
things would be a lot easier for everyone because everything would always be
in the same place. There would be no need to hunt and search to discover how
THIS or THAT software package decided to implement it.
That's what standards are *for*. s
Dan
mtnpastor wrote:
Thank you for the prompt reply, Suzanne. That is very interesting
and I understand more now about why the symbols are arranged the way
they are. However, it still does not seem to me that it is very
intuitive or user friendly. This has been a frustration of mine for
a long time and I would be interested to know if others have
expressed the same frustration. Just because some intenational board
dictates that something should be a certain way, does that mean that
everybody has to fall into step?
"Suzanne S. Barnhill" wrote:
The symbols are listed in their ANSI or Unicode order (depending on
the display). The arrangement of character sets dates back to the
Stone Age of computing and, as the names imply (ANSI = American
National Standards Institute; for Unicode, see http://unicode.org/)
the layout has been determined by national/international standards
organizations; it is not something Microsoft can change any more
than it can change the arrangement of keys on a QWERTY keyboard.
But you don't need to go to Insert | Symbol just to insert the ¢
symbol. The keyboard shortcut is Ctrl+/, c. Find more at
http://word.mvps.org/FAQs/General/InsertSpecChars.htm
--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
"mtnpastor" wrote in message
...
This is one of the least intuitive aspects of MS Word. I have Word
2003 with
all the updates and to find the ¢ symbol, I have to go to insert,
symbol, then cursor down seven lines to get to the ¢ symbol. What
I find odd about
this is the $ is on the first line of the symbol listing. Why is
the ¢ symbol not right next to it!!! I find this odd and not
typical of the way most people think when they are searching for
monetary symbols. Does anyone
out there agree? How do we go about communicating this to the MS
Word/Office
staff to get an update that corrects this situation?