Hi,
in the course of vcard and the encoding issue I ask herewith for help to
solve another annoying utf8 encoding issue.
Problem:
Attached images show that My_Documents when language set to bg gets mangled.
Unfortunately looking into this I found out it is mangled in
/opt/trinity/share/apps/kdesktop/Desktop/My_Documents
I tested in fresh install of TDE, but after first logout/login it changed
I workaround it by fixing the file and removing the write permissions.
I don't know where to look for the system:/ entry.
regards
Hi,
after few months of testing, I do not see any issues in the TDE
backends/plugins.
I want to finalize this work and upload the code in some way. I asked
SyncEvolution about it [1,2] while trying to build 1.5.1 against synthesis.
This required version which is provided in debian sid. Unfortunately I hit
a bug [3] and I think I'll try against syncevolution from git as the patch
for [3] is still to be uploaded for 1.5.1.
What I want to discuss with you based on [1] is if you think it is wise to
provide syncevolution-whatever-trinity package(s), which for the moment I
think is the best and fast (but not optimal) solution. I will call this
short term solution - STS.
I think it would be more complex to push each distro to include support for
tdepim in syncevolution, but in long term it is the best solution. I will
call this long term solution - LTS. However I think there are still few
places to improve in the code (the calendar part mostly) and there are some
issues in the underlaying libkcal or whatever handles the todo's
subject/description when utf-8 and/or quoted content. In fact I dropped
support for cal v1 in the plugins as it looks broken and I did not have
time to deal with it. SyncEvolution does convert internally a v1 cal into
v2 just excellent.
So the plan for the STS would be to modify the vendors build scripts (I know
only debian ... so debian/*) to produce the syncevolution packages with
trinity extention, which will be build with the tdepim/wallet support on
top of the vendors configure options. Those packages should replace the
vendors own packages and thus provide the tdepim support.
The LTS would easy the way that we'll have tdepim/wallet in the mainline,
but perhaps we should still provide packages to overwrite the distros
shipped package.
Based on this what are you thinking?
Thanks in advance
[1] http://comments.gmane.org/gmane.comp.mobile.syncevolution/5396
[2] http://comments.gmane.org/gmane.comp.mobile.syncevolution/5393
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824426
Hi
another question that popped up when working on syncevolution plugins was
the future of dbus.
https://www.mail-archive.com/syncevolution%40syncevolution.org/msg05071.html
It looks like it is getting replaced by gdbus and I found that libraries
are linked to dbus-1 for some reason I do not understand.
Example
ldd /opt/trinity/lib/libkaddressbook.so | grep dbus
libdbus-1-tqt.so.0 => /usr/lib/libdbus-1-tqt.so.0
(0x00007fb69ebb2000)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3
(0x00007fb69d452000)
ldd /opt/trinity/lib/trinity/libkaddressbookpart.so | grep dbus
libdbus-1-tqt.so.0 => /usr/lib/libdbus-1-tqt.so.0
(0x00007f61da129000)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3
(0x00007f61d89c9000)
What are the plans and what can we do in future?
thanks and regards
Hi again,
I'm sorry to bother you again with this, but I asked once how I can add a
testing target.
I started then working on this tdepim libkcal testing stuff again. I still
have some issues when my "SUMMARY" or "DESCRIPTION" of event or todo are in
cyrillic. Unfortunately I was/am busy at work and I lost all threads ....
perhaps you know this feeling ... getting older.
I also found the key to building testing targets
DEB_MAKE_CHECK_TARGET=testing fakeroot debian/rules build
so I think the next exercise (may be long term one) would be to revive the
check/testing code laying around.
I think I have a good plan
1. fix the libkcal issue "SUMMARY" - "DESCRIPTION"
2. build syncevolution deb packages for TDE
3. fix the libkcal test cases (now a lot of them fail on some date issue -
perhaps because originally there was a local zoneinfo data included in the
code and now it is not there)
4. start migrating testing to CMake (first in the packages I already have
worked with)
what do you think?
regards
Hi,
I would like to see Trinity on FreeBSD, so I subscribed to see what I
can do. Please let me know how I can help. I run FreeBSD and can
code, although I don't have a lot of experience with kernel level
programming.
Thanks
Mark Moellering
