[Development] Heads-up: glibc 2.28 will break matching of [a-z], [0-9] and other ranges
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, inclusively. It is expressed as the starting point and the ending point separated by a hyphen (-). Range expressions must not be used in portable applications [...] This turns out to break globs (and other patterns) using ranges; if you want to match lower-case letters, you need to say [[:lower:]], and similarly for [[:digit:]], etc. For example, [a-z] shall now match all the upper-case letters except A and Z, which you probably didn't intend. More background: https://sourceware.org/bugzilla/show_bug.cgi?id=23393 http://pubs.opengroup.org/onlinepubs/7908799/xbd/re.html#tag_007_003_005 I don't know how that may affect us, but my guess is we probably have to change some shell scripts and potentially also some regexes. I've created QTBUG-69518 to track this, Eddy. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt Linguist should tell how many strings are in a file
> -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 provisional translations. So did you use localise.co in the end? If so, how did you organize the data Import and export? For Qt Linguist itself: Nobody has been working on it lately. It does what it does, but extending it is not in the current development focus. Anyhow, if anybody fancies spending some time on it, be welcome to do so đ However, for more complicated setups I'd expect that people would use other tools, probably using lconvert to convert .ts files back and forth between standard formats like XLIFF. But we haven't been advertising this much. Regards Kai ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] [Announce] Qt Creator 4.7.0 released
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, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B ___ Announce mailing list annou...@qt-project.org http://lists.qt-project.org/mailman/listinfo/announce ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt Linguist should tell how many strings are in a file
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 scripts. We used lokalize to get the translations from the translators and all that entails (user management, scope, etc) I would expect that Qt would adopt/focus on GNU gettext/PO files in the future? > Sent: Wednesday, July 18, 2018 at 5:20 AM > From: "Kai Koehne" > To: "Jason H" , scootergrisen > Cc: "development@qt-project.org" > Subject: RE: [Development] Qt Linguist should tell how many strings are in a > file > > > -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 provisional translations. > > So did you use localise.co in the end? If so, how did you organize the data > Import and export? > > For Qt Linguist itself: Nobody has been working on it lately. It does what it > does, > but extending it is not in the current development focus. Anyhow, > if anybody fancies spending some time on it, be welcome to do so đ > > However, for more complicated setups I'd expect that people would use > other tools, probably using lconvert to convert .ts files back and forth > between standard formats like XLIFF. But we haven't been advertising > this much. > > Regards > > Kai > > ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt Linguist should tell how many strings are in a file
> -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 later also experienced when writing my merge scripts. > We used lokalize to get the translations from the translators and all that > entails > (user management, scope, etc) Would be good to know exactly what the issues are. > I would expect that Qt would adopt/focus on GNU gettext/PO files in the > future? Well, you can use gettext already right now, for your own translations. Anyhow, I doubt that we can change the existing tooling in Qt to gettext without breaking user code. And given our focus on compatibility, I don't see this happen any time soon. Regards Kai ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt Linguist should tell how many strings are in a file
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 the XML, which I later also experienced > when writing my merge scripts. We used lokalize to get the > translations from the translators and all that entails (user > management, scope, etc) > > I would expect that Qt would adopt/focus on GNU gettext/PO files in > the future? I would not expect that. The use of Linguist and the Qt translation system in general is completely optional for a Qt application, you can use any other system for your own translations already now.I Apart from that, Qt translations and gettext are not equivalent featurewise, neither is a super nor a subset of the other, so *dropping* the Qt translation system will hurt someone. Andre' ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
