From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] package_deb.bbclass: Handle exception when encoding non-ASCII characters
Date: Thu, 13 Aug 2015 14:31:52 -0500 [thread overview]
Message-ID: <55CCF0A8.4010409@windriver.com> (raw)
In-Reply-To: <CAMKF1sqHK5q-Xq9Gv4wae4MZdSw57e_OVyc_kdFkWgeAKd8v+g@mail.gmail.com>
On 8/13/15 2:21 PM, Khem Raj wrote:
> On Thu, Aug 13, 2015 at 12:05 PM, Burton, Ross <ross.burton@intel.com> wrote:
>> Debian control files are defined to be UTF-8, so the use of an ASCII
>> encoding method is wrong
>> (https://www.debian.org/doc/debian-policy/ch-controlfields.html).
>>
>> (RPM appears to assume UTF-8 too)
>
> but check it still fine isnt it.
>
RPM isn't really utf-8.. it's more single 8-bit characters... UTF-8 (1 byte
characters) work fine.. multibyte are not promised to work.
If you need special encoding (more then 8-bit characters) then you should be
using 'po' style files to translate the 8-bit chars to localized versions...
So checking (and fixing) the strings for various things is a good idea for RPM
at least.
--Mark
next prev parent reply other threads:[~2015-08-13 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 8:58 [PATCH 0/2] Check non-ASCII characters on recipe metadata leonardo.sandoval.gonzalez
2015-08-13 8:58 ` [PATCH 1/2] insane.bbclass: Check non-ASCII characters on metadata leonardo.sandoval.gonzalez
2015-08-13 8:58 ` [PATCH 2/2] package_deb.bbclass: Handle exception when encoding non-ASCII characters leonardo.sandoval.gonzalez
2015-08-13 19:05 ` Burton, Ross
2015-08-13 19:21 ` Khem Raj
2015-08-13 19:31 ` Mark Hatle [this message]
2015-08-13 19:33 ` Burton, Ross
2015-08-13 19:34 ` Burton, Ross
2015-08-17 14:43 ` Leonardo Sandoval
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=55CCF0A8.4010409@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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.