unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Oleksandr Gavenko <gavenko@bifit.com.ua>
Cc: help-gnu-emacs@gnu.org
Subject: Re: UTF8_STRING vs. COMPOUND_TEXT
Date: Tue, 11 Jan 2011 18:08:50 +0100	[thread overview]
Message-ID: <20ADA01D-CA22-4C8B-8834-E82AED8ACA81@Web.DE> (raw)
In-Reply-To: <ighlvf$i6c$1@dough.gmane.org>


Am 11.01.2011 um 14:29 schrieb Oleksandr Gavenko:

> How I can know which encoding used by X Window?
> On which this depend?


Age, version number, objects in the X server, the window manager, the  
X clients. When libiconv, libXft, Pango are used, it's likely a modern  
system. Fvwm is from last millennium.

OTOH, a simple copy&paste check would show.

--
Greetings

   Pete
You can never know too little of what is not worth knowing at all.
			– Anon.




      reply	other threads:[~2011-01-11 17:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 13:29 UTF8_STRING vs. COMPOUND_TEXT Oleksandr Gavenko
2011-01-11 17:08 ` Peter Dyballa [this message]

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=20ADA01D-CA22-4C8B-8834-E82AED8ACA81@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=gavenko@bifit.com.ua \
    --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).