From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Satya Swaroop Damarla <swaroop.damarla@gmail.com>,
yocto@yoctoproject.org
Subject: Re: Installing foreign fonts into the yocto build
Date: Fri, 05 Apr 2013 08:26:57 +0100 [thread overview]
Message-ID: <3486181.3zQ0PC9o8U@helios> (raw)
In-Reply-To: <CAFMfyzKMBXx+j6Wx2e=xdaTU2gHsvTqiEsKAmmCm7AKde_5THw@mail.gmail.com>
On Friday 05 April 2013 09:05:34 Satya Swaroop Damarla wrote:
> Thank you Paul.. This was very helpful... From your reply. I understood
> that poky build doesnot support unicode characters set because the german
> special characters are not displayed ... Am I right?
There's nothing inherent about Poky / OpenEmbedded that means it doesn't
support Unicode. Individual pieces of software might have difficulties however.
I just copied over a text file containing "Schrödinger's 😻" (i.e. one German
character and one special one) in UTF-8 to a core-image-sato image. The file
doesn't display properly in the matchbox-terminal application (displaying
garbage, indicating the encoding is incorrect), however in Notes (leafpad) it
displays the ö but not the 😻 (displaying a single box with hex code instead,
indicating that the font is missing that special character).
FYI I read this article recently and found it very useful - you may already
know some or all of this, but just in case:
http://www.joelonsoftware.com/articles/Unicode.html
Cheers,
Paul
PS please keep the discussion on the mailing list, thanks.
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-04-05 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 8:47 Installing foreign fonts into the yocto build Satya Swaroop Damarla
2013-04-04 23:14 ` Paul Eggleton
[not found] ` <CAFMfyzKMBXx+j6Wx2e=xdaTU2gHsvTqiEsKAmmCm7AKde_5THw@mail.gmail.com>
2013-04-05 7:26 ` Paul Eggleton [this message]
2013-04-05 9:35 ` Burton, Ross
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3486181.3zQ0PC9o8U@helios \
--to=paul.eggleton@linux.intel.com \
--cc=swaroop.damarla@gmail.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.