tde-devels

devels@trinitydesktop.org

4 participants
3805 discussions

i18n locale packages
by Darrell Anderson 07 Feb '14

07 Feb '14

All, We have an inconsistent mixed delivery of i18n files. Many locales are packaged with tde-i18n; some are packaged in a smaller i18n package, such as gwenview, k3b, and koffice; while others are packages as part of the parent app. That last group includes the following: amarok digikam filelight kbiff kdbg kdiff3 kile kipi-plugins kmplayer knights knutclient konversation krecipes krusader kshowmail kshutdown ksquirrel kvpnc rosegarden showfoto tdepowersave tdesvn tellico Of this latter group, only a few locales are supported in each of the packages. With the three packages that include all i18n files: gwenview, k3b, and koffice, a challenge is gwenview and k3b is an all or nothing installation. Conversely, like tde-18n, koffice-i18n can be compiled as separate locale packages. tde-i18n has become a monster module, just too large to deal with. That module should be split into smaller locale modules. Then the packages listed above, as well as gwenview, k3b, and koffice, could be merged into each respective locale module. Comments appreciated. Darrell

2 1

Re: [trinity-devel] Commit 83f044c5 [tdebase]
by Darrell Anderson 07 Feb '14

07 Feb '14

>Please try attached patch. As far as I can tell from the build log and actual usage, the patch works fine at my end. Darrell

2 1

Re: [trinity-devel] Add attached to tdebase /opt/trinity/share/apps/kicker/wallpapers
by Darrell Anderson 07 Feb '14

07 Feb '14

> I created a fantastic kicker wallpaper that I would like to have >added to the >tdebase install. (343 bytes total) It goes with the default theme >and makes >kicker look pretty slick. I'm not saying make it the default >kicker background, >but just provide it in the directory. I would probably rename it >'blueglass.png' >instead of the attached filename. Take a look. Nobody complained and I built the new image without incident. Pushed to git in commit 1a452134. Nice artwork. :) Darrell

1 0

Re: [trinity-devel] python-tqt FTBFS - ImportError: No module named sip4_tqt
by Darrell Anderson 07 Feb '14

07 Feb '14

>I assume that both patches (1912, 1913) from bug 1790 can be >considered as tested => suitable for pushing to Git. No build problems here. Push. Darrell

1 0

cannot open shared object file: No such file or directory
by Darrell Anderson 07 Feb '14

07 Feb '14

All, I don't know what happened within the past several weeks, but of late, anytime I delete only the tdelibs package from my build environment and rebuild to test patches, the build log is filled with this kind of spew: libtdeabc.so.1: cannot open shared object file: No such file or directory libtdeparts.so.2: cannot open shared object file: No such file or directory When I delete all other packages other than the tdelibs dependencies, then tdelibs builds as expected without the spew. Any ideas? Darrell

1 0

Warning: patch updates
by Darrell Anderson 06 Feb '14

06 Feb '14

All, For several days I have been working on several items with the help handbook system. I've been thorough and have been testing intensely with the hope of avoiding new bugs after the patches are pushed to git. Much of the work revolves around fixing tdeioslaves and protocol handbooks, but there are other patches such as fixing missing icons, fixing DocPath keys, updated handbooks, etc. The patches include tde-i18n fixes to match as much as possible the changes made in the parent packages. I ran a final full build set last night with all of the upcoming patches, including tde-i18n. There were no build failures and my usage tests today went as expected. As the patch set includes the tdelibs module, which include entity changes, your best approach is to run a full build set. Any time we update the entities in tdelibs that means help handbooks using the previous entities will fail to build. After many rounds of package rebuilding and usability testing I'm not expecting problems, but as always I'm only one person and don't conceive of or anticipate all use cases. Please report potentially related bugs to the list and I'll look into them. Please don't report bugs unless you performed a full package set rebuild because that will be my first reply. :) I plan to soon start pushing those patches. I plan to run another full build set tonight after I finish pushing all patches to ensure no new problems. Darrell

1 0

Re: [trinity-devel] python-tqt FTBFS - ImportError: No module named sip4_tqt
by Darrell Anderson 06 Feb '14

06 Feb '14

>> I've read through it until I'm blue in the face and I can't >figure out what it >> means to my build script. How are you building it? Obviously my >build for >> python-sip and python2-sip build but are now completely broken. >I'm building with: >> >> CFLAGS="${CFLAGS} -I/usr/include/tqt -I${TDEDIR}/include - >I${QTDIR}/include" Grab a copy of my build scripts. There are some nominal changes in the sip4-tqt and python-tqt scripts. Notice the changes in the configuration section. Rebuild both packages. Darrell

2 1

tdeutils FTBFS (cmake) - error: 'PyString_CheckExact' was not declared in this scope
by David C. Rankin 05 Feb '14

05 Feb '14

Darrell, Slavek, With a complete build (tqt3 -> tdeutils), tdeutils fails at 96% with the following: [ 96%] Building CXX object superkaramba/src/CMakeFiles/superkaramba.dir/meter_python.cpp.o cd /build/tde-tdeutils/src/build/superkaramba/src && /usr/bin/c++ -DHAVE_CONFIG_H -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -I/opt/tqt3/include -I/usr/include/tqt -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -I/build/tde-tdeutils/src/build -I/build/tde-tdeutils/src/build/superkaramba/src -I/build/tde-tdeutils/src/tdeutils/superkaramba/src -I/usr/include/python3.3m -I/opt/trinity/include -I/opt/tqt3/include -I/usr/include/tqt -o CMakeFiles/superkaramba.dir/meter_python.cpp.o -c /build/tde-tdeutils/src/tdeutils/superkaramba/src/meter_python.cpp In file included from /build/tde-tdeutils/src/tdeutils/superkaramba/src/karamba.h:73:0, from /build/tde-tdeutils/src/tdeutils/superkaramba/src/meter_python.cpp:17: /build/tde-tdeutils/src/tdeutils/superkaramba/src/imagelabel.h:41:14: warning: declaration 'class TDEIO::CopyJob' does not declare anything [enabled by default] class TDEIO::CopyJob; ^ /build/tde-tdeutils/src/tdeutils/superkaramba/src/meter_python.cpp: In function 'TQString PyString2TQString(PyObject*)': /build/tde-tdeutils/src/tdeutils/superkaramba/src/meter_python.cpp:96:33: error: 'PyString_CheckExact' was not declared in this scope if (PyString_CheckExact(text)) ^ /build/tde-tdeutils/src/tdeutils/superkaramba/src/meter_python.cpp:98:41: error: 'PyString_AsString' was not declared in this scope char* t = PyString_AsString(text); ^ /build/tde-tdeutils/src/tdeutils/superkaramba/src/meter_python.cpp: In function 'PyObject* TQString2PyString(TQString)': /build/tde-tdeutils/src/tdeutils/superkaramba/src/meter_python.cpp:151:38: error: 'PyString_FromString' was not declared in this scope pyString = PyString_FromString(""); ^ superkaramba/src/CMakeFiles/superkaramba.dir/build.make:973: recipe for target 'superkaramba/src/CMakeFiles/superkaramba.dir/meter_python.cpp.o' failed make[2]: *** [superkaramba/src/CMakeFiles/superkaramba.dir/meter_python.cpp.o] Error 1 make[2]: Leaving directory '/build/tde-tdeutils/src/build' CMakeFiles/Makefile2:5060: recipe for target 'superkaramba/src/CMakeFiles/superkaramba.dir/all' failed make[1]: *** [superkaramba/src/CMakeFiles/superkaramba.dir/all] Error 2 make[1]: Leaving directory '/build/tde-tdeutils/src/build' Makefile:119: recipe for target 'all' failed How to solve? -- David C. Rankin, J.D.,P.E.

1 0

Screen captures for i18n packages
by Darrell Anderson 05 Feb '14

05 Feb '14

All, As we continue to update the help handbooks, a significant challenge is updating not only the text but the screen captures. I would like to automate part of this process as much as possible. The basic screen capture process: * Save a new screen capture in English. * Note the image size properties. * Toggle to a different language. * Verify the respective tde-i18n module is using that same image. (Not all i18n modules support everything.) * Save a new screen capture in the respective language with the same image size properties. * Repeat through all i18n languages. I'm thinking we need a way to update all i18n po file references to the original source file and code lines, as well as update the po file English reference to what is now actually in the source code. We've made many changes the past few years and the po file English references are not current. Many code line references are incorrect. We lack the project size needed to keep all of the i18n files updated, but at least we can update the English references and source code lines as well as the screen captures. I am asking that you let this challenge fester for a while in your subconcious and hopefully a solution emerges. These are not R14.0.0 priorities, but as Slavek mentioned previously, probably marked for R14.0.2. As always, thank you. :) Darrell

1 0

Re: [trinity-devel] Default video player (Formerly UUGH! Desktop Icons open in DOLPHIN -- really?)
by Darrell Anderson 05 Feb '14

05 Feb '14

>maybe tmplayer? I don't think the name matters all that much. >there >already exists smplayer, gnome-mplayer, kplayer and kmplayer >according >to my debian package list. I meant a name change consistent with our previous name changes. Not a priority. Darrell

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels