Ralph Shumaker wrote:
> I've tried to find the check mark symbol in Linux (rh - various versions
> now) and have had no success.  I can't even find approximations of it
> (including the square root sign).  Is there some extra font I would have
> to download to get this?  Or are the check marks in Linux just really
> well hidden?

Relevant Unicode character names are

U+2713  check mark
 UTF-8: 0xE2 0x9C 0x93

U+2714  heavy check mark
 UTF-8: 0xE2 0x9C 0x94

U+221A  square root sign (aka radical sign)
 UTF-8: 0xE2 0x88 0x9A


Getting them recorded (encoded) or displayed somewhere depends on
various things.

Assuming

- you are running Xwindows, and your system has /etc/sysconfig/i18n
containing something like
-------------------------------------------
LANG="en_US.UTF-8"
SYSFONT="latarcyrheb-sun16"
SUPPORTED="en_US.UTF-8:en_US:en"
--------------------------------
(verified by typing
  locale
and seeing
  LC_CTYPE="en_US.UTF-8"
  ..and so on..

-and you have a recent Linux distribution with iso10646 fonts,

then you can get your shell terminal to display by cutting and pasting
from the Accessories > Character Map application on the menu, or by (say)
  echo -e '\xE2\x9C\x93'
  echo -e '\xe2\x9c\x94'
  echo -e '\xe2\x88\x9a'

That completes the proof-of-concept <heh>.

  You can also demo the concept by hexediting into a file or,
  by echo -ne '\xE2\x9C\x93' >checkmark-utf8, and then something
  like cat checkmark-utf8.

I don't do this too much except for html, ..but.. if you are composing a
document, then the document presumably has a way to specify the
character encoding. And you can cut-n-paste as above.

  Now, I'm sure there are other ways to get input into a document
  (perhaps: IIIMF/XIM/successor, just now coming-out) -- but we're
  going to need to appeal to someone with more expertise than I have.

Wherever the document gets displayed and/or printed must, of course, be
configured to expect the document to be encoded in UTF-8.

==> Alternatively <==
I'm sure you can do this in other unicode encodings (eg, UTF-16), as
well as non-unicode choices such as one of the 8859 sets or one of the
windows codesets.

Perhaps someone else can pick up on follow-up questions.

..jim


-- 
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie

Reply via email to