From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10836] New: Missing Qt5 component : translations
Date: Mon, 05 Mar 2018 21:31:27 +0000 [thread overview]
Message-ID: <bug-10836-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10836
Bug ID: 10836
Summary: Missing Qt5 component : translations
Product: buildroot
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: pinaraf at pinaraf.info
CC: buildroot at uclibc.org
Target Milestone: ---
Hi
The translations for the Qt5 user interface is split from the Qt5 code in a
qt5translations submodule, for instance
http://download.qt.io/official_releases/qt/5.9/5.9.3/submodules/qttranslations-opensource-src-5.9.3.tar.xz
It is a simple package, depending on the linguist host tools (already
packages).
The only trick would be to be able to choose the required languages from the
configuration menu. It is of great importance for people building embedded Qt
applications targeting non-english users.
I am willing to work on this package if you can not work on it (I'm not 100%
familiar with buildroot packaging rules, even less with a complex multi-version
package like Qt5, so I can not guarantee the quality of my work there).
Regards
Pierre
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-03-05 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 21:31 bugzilla at busybox.net [this message]
2018-03-05 21:47 ` [Buildroot] [Bug 10836] Missing Qt5 component : translations bugzilla at busybox.net
2018-03-05 21:51 ` bugzilla at busybox.net
2018-03-05 21:52 ` bugzilla at busybox.net
2018-03-05 21:57 ` bugzilla at busybox.net
2024-06-15 14:47 ` bugzilla
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-10836-163@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox