From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: squares in buffer instead of utf-8 characters
Date: Sat, 14 Apr 2007 19:27:58 +1000 [thread overview]
Message-ID: <87k5wfwbj5.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: mailman.2033.1176464083.7795.help-gnu-emacs@gnu.org
rahed <raherh@gmail.com> writes:
> Hi,
>
> I created a file using input method and saved as utf-8. The file is
> rendered ok in a browser but in an emacs buffer all unicode characters
> are mere boxes.
>
> Unicode characters have typically this property:
>
> character: ? (331835, #o1210073, #x5103b, U+011B)
> charset: mule-unicode-0100-24ff (Unicode characters of the range U+0100..U+24FF.)
> code point: #x20 #x3B
> syntax: w which means: word
> category: l:Latin
> buffer code: #x9C #xF4 #xA0 #xBB
> file code: #xC4 #x9B (encoded by coding system mule-utf-8-unix)
> display: no font available
>
> Don't know how to remedy unavailability of the font. OS is Solaris and
> emacs version 22.0.91.1.
>
At a guess, I suspect you are running under X. This means you have either a
fontpath setting that points to directories containing the fonts your X server
is able to provide or you have a font server configured. The boxes indicate
that emacs wants to display the characters with a specific font, but it cannot
find that font (either in your font path or from the font server).
There are a couple of points to keep in mind here. If your connecting to the
solaris box from a remote system, such as a workstation, then the fonts need to
be available to your local workstation X server, not on the solaris X server.
In this case, the issue is with your local X configuration or the fonts it has
available.
You can use a program like xfontsel, which will allow you to select fonts from
those which are available to the X server. Use this program and try to identify
a suitable font. Set the font for emacs to this font and things should work.
This can be done in a number of ways, but to begin with and for
experimentation, set it on the command line using the -fn option (I think its
-fn, check the manual). Don't forget that since the font names contain *, you
will need to quote the font string to prevent the shell from trying to expand
the *. Once you have a font that works, set it in either your .Xresources file,
your .emacs file or via customize.
HTH
Tim
--
tcross (at) rapttech dot com dot au
next parent reply other threads:[~2007-04-14 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2033.1176464083.7795.help-gnu-emacs@gnu.org>
2007-04-14 9:27 ` Tim X [this message]
2007-04-24 11:18 ` squares in buffer instead of utf-8 characters rahed
2007-04-24 14:54 ` Peter Dyballa
2007-04-24 18:34 ` rahed
2007-04-25 8:46 ` Peter Dyballa
2007-04-26 15:29 ` rahed
2007-04-26 15:47 ` Peter Dyballa
2007-04-26 3:46 ` Karl Hegbloom
2007-04-13 10:24 rahed
2007-04-13 14:15 ` Peter Dyballa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k5wfwbj5.fsf@lion.rapttech.com.au \
--to=timx@nospam.dev.null \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).