It could be useful to check the localization in a release build. But, currently, we can have key ID provided by the qtz pseudo-language only in a dev. build like beta versions (the ones which are installed under the name LibreOfficeDev). I suggest that the build of the qtz pseudo-language could be decided the same way than for all other languages by adding its code in the option --with-lang in the autogen.input file. Best regards. JBF
Forgot to set it as enhancement. Best regards. JBF
What would be the advantages of doing that? It would not be enabled for official builds, so one would have to build libreoffice oneself. But in that case one can just do a non-release build... IMHO the key "translations" are testing/debugging aid, therefore they do not belong to release builds.
(In reply to comment #2) > What would be the advantages of doing that? It would not be enabled for > official builds, so one would have to build libreoffice oneself. But in that > case one can just do a non-release build... I think that if qtz pseudo-language was available in official builds too, that would make debugging translations in x.y.z (z > 0) versions easier. > IMHO the key "translations" are testing/debugging aid, therefore they do not > belong to release builds. In fact we are always in testing period. When translations bugs are found in the integrated help by advanced users in x.y.0 or x.y.1 versions, it would be easier to find their exact locations with the keyID. It would be sufficient to say her: please install qtz language and give me the keyID. Actually it may be very complicated to explain how to go to a particular help page. On the other hand, it seems that dev builds with keyID are available only for betas which concerns only x.y.0 versions. Best regards. JBF
Since JBF has already provided the needed info, this should be set back to UNCONFIRMED. I agree that this enhancement request is reasonable, So I set it to NEW. There are always UI/help translation errors in release builds. KeyID is really helpful to locate strings quickly and help to speed-up localization. In fact, if you look at 4.3.0.1, many languages are not 100% translated. For 4.2.5.2 release, there are still many strings need translation improvements.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.