From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13551] 2021.02.rc2: Unicode not work on qt 5.15.2
Date: Mon, 22 Feb 2021 19:06:20 +0000 [thread overview]
Message-ID: <bug-13551-163-CNHicZHUon@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13551-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13551
--- Comment #1 from Peter Seiderer <ps.report@gmx.net> ---
A very brief description...., please describe exactly what (and how) did you
test, which result did you expect and which result did you get?
I suspect you did test something like the following:
#include <QDebug>
int main(int argc, char* argv[]) {
qInfo() << "\u25C0";
return 0;
}
Please compile and run on the target and provide the output of the following
call:
$ ./test 2>&1 | hexdump -C
On my desktop system I get:
00000000 e2 97 80 0a |....|
00000004
Which is the expected UTF-8 output for the Unicode/UTF-16
Black-Left-Pointing-Triangle ([1])...
[1] https://codepoints.net/U+25C0?lang=en
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-22 19:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 7:37 [Buildroot] [Bug 13551] New: 2021.02.rc2: Unicode not work on qt 5.15.2 bugzilla at busybox.net
2021-02-22 19:06 ` bugzilla at busybox.net [this message]
2021-02-23 6:24 ` [Buildroot] [Bug 13551] " bugzilla at busybox.net
2021-02-23 6:25 ` bugzilla at busybox.net
2021-02-23 19:29 ` bugzilla at busybox.net
2021-02-28 16:12 ` bugzilla at busybox.net
2021-03-17 16:01 ` bugzilla at busybox.net
2021-03-17 16:02 ` bugzilla at busybox.net
2021-03-17 18:54 ` bugzilla at busybox.net
2021-03-17 18:56 ` bugzilla at busybox.net
2021-03-17 18:57 ` bugzilla at busybox.net
2021-03-17 23:00 ` bugzilla at busybox.net
2021-03-18 7:35 ` bugzilla at busybox.net
2021-03-18 19:28 ` bugzilla at busybox.net
2021-05-07 13:07 ` bugzilla at busybox.net
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=bug-13551-163-CNHicZHUon@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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.