On Wed, Jul 18, 2018 at 03:30:14PM +0200, Jason H wrote:
> It was unfortunately a combination of lokalise.co and my scripts. The
> owner/opertator/developer of lokalise was very helpful in adjusting
> his service which apparently supported Qt 3 to Qt4's format. He
> complained about issues with
> -Original Message-
> [...]
> It was unfortunately a combination of lokalise.co and my scripts. The
> owner/opertator/developer of lokalise was very helpful in adjusting his
> service
> which apparently supported Qt 3 to Qt4's format. He complained about issues
> with the XML, which I
It was unfortunately a combination of lokalise.co and my scripts. The
owner/opertator/developer of lokalise was very helpful in adjusting his service
which apparently supported Qt 3 to Qt4's format. He complained about issues
with the XML, which I later also experienced when writing my merge
We are happy to announce the release of Qt Creator 4.7.0!
http://blog.qt.io/blog/2018/07/18/qt-creator-4-7-0-released/
--
Eike Ziller
Principal Software Engineer
The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
eike.zil...@qt.io
http://qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius,
> -Original Message-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> [...]
> The closest I got was using some web service that we were able to export from
> (https://lokalise.co/ ?). Also having a built-in google translate button
> would be
> very helpful for the
Hi all,
A discussion on the GNU make mailing list brought this to my attention.
Apparently glibc 2.28 is going to implement the POSIX spec on ranges,
which says
A range expression represents the set of collating elements that fall
between two elements in the current collation sequence,
