[sugar] Activity sharing broken
Whenever I try to share an activity, I get an error about get_id() not being defined on an Activity (and if you add it just for the heck of it, it complains about get_service_name missing). For example: DEBUG - root: ActivityService.set_active: 1. DEBUG - root: Requesting share of activity 70ffd154d3b749edde51c3800ce9f581bd7d4032. STDERR - Traceback (most recent call last): File "/Development/sugar-jhbuild/build/lib/python2.4/site-packages/sugar/activity/activity.py", line 79, in _share_clicked_cb self._activity.share() File "/Development/sugar-jhbuild/build/lib/python2.4/site-packages/sugar/activity/activity.py", line 313, in share self._pservice.share_activity(self) File "/Development/sugar-jhbuild/build/lib/python2.4/site-packages/sugar/presence/presenceservice.py", line 377, in share_activity actid = activity.get_id() AttributeError: 'AbiWordActivity' object has no attribute 'get_id' Does anyone know what should be done to get this up and running again? Thanks, Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Tubes message dropping
To the Tube guys: Do you drop messages on your XMPP server? An AbiCollab packet that contains an image never gets sent over, resulting in documents getting out of sync (in fact, the PS seems to disconnect the buddy altogether from the Write session). As AbiCollab assumes packets are never dropped (and are in-order), this results in issues like http://dev.laptop.org/ticket/2253 What would be the proper way to solve this? I can implement full checking of message ordering/dropping in AbiCollab ofcourse, but that seems like a solution at the wrong level. Cheers, Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Tubes message dropping
> We could modify our IBB implementation to fragment big stanzas but that > would make the code sensibly more complicated. Furthermore I'm not sure > the server will allow us to send N MAX_SIZE stanzas consecutively. IBB > is really not designed to send big datas (XEP suggests 4096 bytes as max > payload size). > A quick workaround could be to raise the allowed stanza max size in the > server config. Could we try this for now as a workaround? I think this is the sole cause of people 'bugging' me with "my documents are getting out of sync" reports. I'd like to make sure that it really is though :) Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] First impressions of a B4 machine
> Next is AbiWord. Why was it not stripped of support for most file > formats? Microsoft Word .doc is proprietary and should be removed, > not to mention it's useless for children using XO -- none of their > classmates or teachers will be using Microsoft Word. > AbiWord's own format should be removed because its useless for > interoperability It is _required_ for collaboration, so it can't even technically be removed. > and ODT does a fine job by itself. ... that's why has been the default for 2 months now. > RTF? Who uses RTF these days? The whole web is filled with it. > This is all bloat and has no point for the children. I tend disagree. > OpenDocument should be the default format for saving new documents and > open older ones. It already is > HTML support makes sense if children will put stuff on the Web, and if > so, HTML should be kept in its simple form, no Multipart HTML crap, > which doesn't even work on XULRunner, anyway. Plain text support is > always a good idea, after all, Linux is all about editing text files > :) However, I have no idea what "Encoded Text" is. That's why encoded text is not in the UI. > Other character sets besides ANSI? Useless. It only confuses the children. Agreed, see above. > Appropriate handling of character encodings should not force seperate > text formats. Actually it's not even a problem anymore with Unicode > around. > > If it could export PDF as OpenOffice does then Abi would become quite > useful. That's not the case, right now. I heard there's an > unofficial plugin to do this. Maybe worth looking at? No need fo unofficial plugin: AbiWord core can already save PDF's, but currently printing support is disabled altogether. We require libgnomeprint for PDF output. I'm willing to enable this if the need arises. Regards, Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] How to try TamTam - noob questions (sorry!)
> - When I run sugar-jhbuild build, I get errors flagged at build (and > install) of libabiword-plugins, and errors flagged installing chat- > activity - is this normal? I assume it is because the master tree is > in constant flux and I just caught it at a bad time? Speaking for libabiword-plugins: yes, get you just caught a bad time. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] telepathy-gabble Tubes wire protocol change
On Mon, 2007-09-03 at 15:43 +0100, Simon McVittie wrote: > FYI to all developers using Tubes: > > The version of Gabble I hope to upload to sugar-jhbuild soon (we're waiting > for go-ahead from Jim Gettys) changes the wire protocol to something we're > able to support longer term. Once it arrives in sugar-jhbuild it'll also > be in the next image build. > > The new protocol is incompatible - if old and new clients join the same > activity, old clients will not see messages that were sent by new > clients and vice versa - so once this change goes in, everyone who cares > about collaborative activities and Tubes should upgrade to the new version > of Gabble. > > The new protocol also adds message fragmentation, which should fix large > messages getting dropped by the server (they'll be slow, due to server > rate-limiting, but better than nothing). Yay, I love whoever implemented this :) Make sure to demand your free beer whenever I meet you. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Write collaboration recording in jhbuild
Hi all, Whenever you do a collaboration session now in Write using jhbuild (not using the actual images!), the complete session of events will be recorded. This will allow us to debug collaboration errors after they have occurred. A binary log will be written to $HOME/.AbiSuite/Session-. If you ever see something weird happening during collaboration, such as documents going out of sync, it would be really helpful if the recorded session log was attached to a bugreport. The recorded information from all participating people would be even more helpful. Cheers, Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] libabiword stable branch
Hola, I just switched libabiword and related modules to track the AbiWord 2.6 branch in sugar-jhbuild (instead of trunk); you might want to do a clean rebuild. Cheers, Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] How to handle application protocols
While fixing some bugs in AbiCollab, I found a bug that I can only fix by breaking the existing protocol. I can also imagine that this will happen more in the future (caused by new features, or other unknown bugs that might need fixing). Do we have any policy on application level protocol changes? At the moment, a "new" AbiCollab will simple refuse to communicate with an "old" AbiCollab. Cheers, Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] How to handle application protocols
On Tue, 2007-10-09 at 16:05 -0400, Noah Kantrowitz wrote: > Change your application version number in the .activity file? Well ofcourse. But consider this: 3 kids update their Write activity (including the underlying libabiword), which will also upgrade their AbiCollab protocol. 7 others don't upgrade yet, and continue to use their old version of Write/libabiword. Now kids from both groups will will see each other on the mesh view, see shared documents, but when they try to collaborate, it will 'silently fail'. That doesn't look user-friendly to me. Marc > --Noah > > On Oct 9, 2007, at 3:53 PM, J.M. Maurer wrote: > > > While fixing some bugs in AbiCollab, I found a bug that I can only fix > > by breaking the existing protocol. I can also imagine that this will > > happen more in the future (caused by new features, or other unknown > > bugs > > that might need fixing). > > > > Do we have any policy on application level protocol changes? At the > > moment, a "new" AbiCollab will simple refuse to communicate with an > > "old" AbiCollab. > > > > Cheers, > > Marc > > > > ___ > > Sugar mailing list > > Sugar@lists.laptop.org > > http://lists.laptop.org/listinfo/sugar > > > ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] How to handle application protocols
On Tue, 2007-10-09 at 16:24 -0400, Noah Kantrowitz wrote: > In theory (not sure how implemented this is), when one activity has a > higher version, its code should be automatically pushed to the other > machines. I can see that happening for python code. However, Write is part Python, part C++. The Python part depends on a specific version of the C++ part, so you can't just send over the python part and expect it to work. Now we don't track the non-python dependencies for an activity anywhere as far as I know, so I don't see this working in practice. Cheers! Marc > --Noah > > On Oct 9, 2007, at 4:17 PM, J.M. Maurer wrote: > > > On Tue, 2007-10-09 at 16:05 -0400, Noah Kantrowitz wrote: > >> Change your application version number in the .activity file? > > > > Well ofcourse. > > > > But consider this: 3 kids update their Write activity (including the > > underlying libabiword), which will also upgrade their AbiCollab > > protocol. 7 others don't upgrade yet, and continue to use their old > > version of Write/libabiword. > > Now kids from both groups will will see each other on the mesh > > view, see > > shared documents, but when they try to collaborate, it will 'silently > > fail'. > > > > That doesn't look user-friendly to me. > > > > Marc > > > > > > > >> --Noah > >> > >> On Oct 9, 2007, at 3:53 PM, J.M. Maurer wrote: > >> > >>> While fixing some bugs in AbiCollab, I found a bug that I can > >>> only fix > >>> by breaking the existing protocol. I can also imagine that this will > >>> happen more in the future (caused by new features, or other unknown > >>> bugs > >>> that might need fixing). > >>> > >>> Do we have any policy on application level protocol changes? At the > >>> moment, a "new" AbiCollab will simple refuse to communicate with an > >>> "old" AbiCollab. > >>> > >>> Cheers, > >>> Marc > >>> > >>> ___ > >>> Sugar mailing list > >>> Sugar@lists.laptop.org > >>> http://lists.laptop.org/listinfo/sugar > >>> > >> > > > > > ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] How to handle application protocols
On Tue, 2007-10-09 at 23:52 +0200, Marco Pesenti Gritti wrote: > On 10/9/07, Eben Eliason <[EMAIL PROTECTED]> wrote: > > > I can see that happening for python code. However, Write is part Python, > > > part C++. The Python part depends on a specific version of the C++ part, > > > so you can't just send over the python part and expect it to work. > > > > > > Now we don't track the non-python dependencies for an activity anywhere > > > as far as I know, so I don't see this working in practice. > > > > This is really just an extension of the bundle transfer idea, by which > > anyone should be able to join an activity on the mesh they don't yet > > have. There is overhead involved, but bundles are self-contained > > largely for reasons like this. If the bundle has a newer version, > > then it should be simple enough to transfer the entire bundle from A > > to B. Assuming the bundle contains the C++ component, what's the > > complication? > > I think the c++ component (libabiword) is currently installed in the system. Exactly; libabiword is not part of the Write bundle. We could do that ofcourse, but then other applications can't benefit from the libabiword code (such as a Develop activity for example). I suspect more activities depend on code not in the bundle (browse, etoys?) Cheer, Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] How to handle application protocols
On Tue, 2007-10-09 at 18:30 -0400, Eben Eliason wrote: > On 10/9/07, J.M. Maurer <[EMAIL PROTECTED]> wrote: > > On Tue, 2007-10-09 at 23:52 +0200, Marco Pesenti Gritti wrote: > > > On 10/9/07, Eben Eliason <[EMAIL PROTECTED]> wrote: [] > > > I think the c++ component (libabiword) is currently installed in the > > > system. > > > > Exactly; libabiword is not part of the Write bundle. We could do that > > ofcourse, but then other applications can't benefit from the libabiword > > code (such as a Develop activity for example). > > No, I see the complication. That code definitely belongs separate > from Write. I think the thread is just titled wrong, as this is a > policy concern for "system software" and not for individual > activities. The title reflects the initial problem I was facing. Given the current solution direction, the title is indeed wrong. Feel free to open a new thread :) Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] How to handle application protocols
> Alternatively, things could work as today (rpms for libabiword and > libabiword-plugins), but bundles can provide their own plugins that can > override the system-wide plugins? > > Is this feasible? The only thing needed is to be able to specify a plugin search path. Right now we look only in ~/.AbiSuite/plugins and [libdir]/abiword-2.6/plugins. That way we could ship plugins in the bundle as well, overriding the system-wide plugins. We would need to be really careful though, as plugins are C++ plugins at the moment. There is no stable api at the moment. However, we do try really hard not to break plugins during a stable series; this is not set in stone though. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Notes on joyride-258 and 630
> > First, Write and all the MaMaMedia activities appear to be broken by a > > failing attempt to 'import abiword' that kills all these activities as > > they start. Whoever is supposed to be supplying that 'abiword' python > > package needs to fix his or her RPM. > > > > Abiword has been completely removed in 257. Looks like uwog ChangeLog > is missing the footers, maybe that's the issue. Can we publish the > joyride logs so that these problems are more easily catched? Nice catch. I was already wondering why my packages were removed, and cscott didn't reply to my mails. Would be nice if there was a mail alias that was read by a couple of people that have a clue about the build process. Or do we have mailing list for build issues? Cheers, Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] doc import export
On Wed, 2007-11-21 at 17:17 -0500, Erik Blankinship wrote: > Perhaps a naive question, but could Write come bundled with importers and > exporters for the .doc file format? It already ships with that support. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Where is Walter?
On Wed, 2008-04-23 at 14:05 +0200, Bobby Powers wrote: > I'm new around here, but it seems like this whole conversation is > based on a bunch of what-ifs surrounding that AP article. People > generally seem on the same page that switching to Windows and non-free > software would be a Bad Thing. Maybe we could take a break from > talking about the sky falling until we hear something from Negroponte > or someone else at 1CC regarding Windows? A clear statement on the direction of the project would be a first in the 1.5 years I'm involved with OLPC. I don't count on it anymore. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Where is Walter?
On Wed, 2008-04-23 at 08:05 -0700, Joshua N Pritikin wrote: > On Wed, Apr 23, 2008 at 04:31:30PM +0200, J.M. Maurer wrote: > > On Wed, 2008-04-23 at 14:05 +0200, Bobby Powers wrote: > > > Maybe we could take a break from > > > talking about the sky falling until we hear something from Negroponte > > > or someone else at 1CC regarding Windows? > > > > A clear statement on the direction of the project would be a first in > > the 1.5 years I'm involved with OLPC. I don't count on it anymore. > > If you can't see the obvious, that OLPC has invested and continues to > invest engineering talent in Sugar and related technologies, then I > can't imagine what kind of statement would reassure you. > > Until there is clear evidence to the contrary (not just rumors and wild > speculation), I think we can and should assume that OLPC continues to > march towards free software constructivist learning. Assuming/hoping that OLPC is following the aforementioned direction does not really help motivating unpaid volunteers (on which OLPC depends heavily!). If the recent media attention about a possible focus change (and for some the speculation around Ivan's and Walter's leave) did not happen, then I'd agree with you. But it did happen, so now people want to be reassured that their *very precious spare time* will not be wasted. Cheers, Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Error when building libabiword-plugins
On Thu, 2008-04-24 at 16:34 +0200, Marco Pesenti Gritti wrote: > Hello, > > I'm building libabiword-plugins on Fedora (soon to be) 9 and I get the > following error. libstdc++ version is 4.3.0. > > Btw, can we update sugar-jhbuild to use 2.6.2? if someone can upload > tarballs on sugar.abisource.com I'll be happy to take care of jhbuild > modulesets update... Will do later tonight (I hope it works out of the box, because pyabiword is a bit behind; i think everything sugar uses is up2date though). Marc > Marco > > > g++ -DPACKAGE_NAME=\"abiword-plugins\" > -DPACKAGE_TARNAME=\"abiword-plugins\" -DPACKAGE_VERSION=\"2.6.0\" > "-DPACKAGE_STRING=\"abiword-plugins 2.6.0\"" > -DPACKAGE_BUGREPORT=\"http://bugzilla.abisource.com/\"; > -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 > -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 > -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 > -DHAVE_UNISTD_H=1 -DHAVE_STRINGS_H=1 -DPACKAGE=\"abiword-plugins\" > -DVERSION=\"2.6.0\" -DHAVE_DLFCN_H=1 -DHAVE_BOOST= > -DHAVE_BOOST_THREAD= -I. -I. -I./../../.. -I./../../../core/packet > -DDEBUG -DUT_DEBUG > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/util/xp > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/util/unix > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/xap/xp > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/ev/xp > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/gr/xp > -I../../../../../../libabiword-2.6.0.svn20071127/src/text/fmt/xp > -I../../../../../../libabiword-2.6.0.svn20071127/src/text/ptbl/xp > -I../../../../../../libabiword-2.6.0.svn20071127/src/wp/impexp/xp > -I../../../../../../libabiword-2.6.0.svn20071127/src/wp/ap/xp > -I../../../../../../libabiword-2.6.0.svn20071127/src/other/spell/xp > -I../../../../../../libabiword-2.6.0.svn20071127/src/other/fribidi/xp > -I../../../../../../libabiword-2.6.0.svn20071127/src/other/ttftool/unix > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/xap/unix > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/ev/unix > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/gr/unix > -I../../../../../../libabiword-2.6.0.svn20071127/src/text/fmt/unix > -I../../../../../../libabiword-2.6.0.svn20071127/src/wp/ap/unix > -DABI_PLUGIN_VERSION=\"2.6.0\" -DABI_PLUGIN_MAJOR=2 > -DABI_PLUGIN_MINOR=6 -DABI_PLUGIN_MICRO=0 -DABI_PLUGIN_SOURCE=1 > -DABICOLLAB_RECORD_ALWAYS -I/usr/include/loudmouth-1.0 > -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > -DABICOLLAB_HANDLER_XMPP -I/usr/include/freetype2 > -I/usr/include/fribidi -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -I/usr/include/libgsf-1 > -I/usr/include/libxml2 -I/usr/include/gtk-2.0 > -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo > -I/usr/include/pango-1.0 -I/usr/include/libglade-2.0 -g -O2 -MT > XMPPUnixAccountHandler.lo -MD -MP -MF .deps/XMPPUnixAccountHandler.Tpo > -c XMPPUnixAccountHandler.cpp -fPIC -DPIC -o > .libs/XMPPUnixAccountHandler.o > In file included from XMPPUnixAccountHandler.h:24, > from XMPPUnixAccountHandler.cpp:20: > ./../../../backends/xmpp/xp/XMPPAccountHandler.h:27: error: > 'std::string' has not been declared > make[5]: *** [XMPPUnixAccountHandler.lo] Error 1 ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Error when building libabiword-plugins
On Thu, 2008-04-24 at 20:00 +0200, J.M. Maurer wrote: > On Thu, 2008-04-24 at 16:34 +0200, Marco Pesenti Gritti wrote: > > Hello, > > > > I'm building libabiword-plugins on Fedora (soon to be) 9 and I get the > > following error. libstdc++ version is 4.3.0. > > > > Btw, can we update sugar-jhbuild to use 2.6.2? if someone can upload > > tarballs on sugar.abisource.com I'll be happy to take care of jhbuild > > modulesets update... > > Will do later tonight (I hope it works out of the box, because pyabiword > is a bit behind; i think everything sugar uses is up2date though). AbiWord 2.6.2 and pyabiword 0.6.1 pushed to jhbuild, 100% untested ofcourse (well, it compiles :) Marc > Marc > > > > Marco > > > > > > g++ -DPACKAGE_NAME=\"abiword-plugins\" > > -DPACKAGE_TARNAME=\"abiword-plugins\" -DPACKAGE_VERSION=\"2.6.0\" > > "-DPACKAGE_STRING=\"abiword-plugins 2.6.0\"" > > -DPACKAGE_BUGREPORT=\"http://bugzilla.abisource.com/\"; > > -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 > > -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 > > -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 > > -DHAVE_UNISTD_H=1 -DHAVE_STRINGS_H=1 -DPACKAGE=\"abiword-plugins\" > > -DVERSION=\"2.6.0\" -DHAVE_DLFCN_H=1 -DHAVE_BOOST= > > -DHAVE_BOOST_THREAD= -I. -I. -I./../../.. -I./../../../core/packet > > -DDEBUG -DUT_DEBUG > > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/util/xp > > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/util/unix > > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/xap/xp > > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/ev/xp > > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/gr/xp > > -I../../../../../../libabiword-2.6.0.svn20071127/src/text/fmt/xp > > -I../../../../../../libabiword-2.6.0.svn20071127/src/text/ptbl/xp > > -I../../../../../../libabiword-2.6.0.svn20071127/src/wp/impexp/xp > > -I../../../../../../libabiword-2.6.0.svn20071127/src/wp/ap/xp > > -I../../../../../../libabiword-2.6.0.svn20071127/src/other/spell/xp > > -I../../../../../../libabiword-2.6.0.svn20071127/src/other/fribidi/xp > > -I../../../../../../libabiword-2.6.0.svn20071127/src/other/ttftool/unix > > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/xap/unix > > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/ev/unix > > -I../../../../../../libabiword-2.6.0.svn20071127/src/af/gr/unix > > -I../../../../../../libabiword-2.6.0.svn20071127/src/text/fmt/unix > > -I../../../../../../libabiword-2.6.0.svn20071127/src/wp/ap/unix > > -DABI_PLUGIN_VERSION=\"2.6.0\" -DABI_PLUGIN_MAJOR=2 > > -DABI_PLUGIN_MINOR=6 -DABI_PLUGIN_MICRO=0 -DABI_PLUGIN_SOURCE=1 > > -DABICOLLAB_RECORD_ALWAYS -I/usr/include/loudmouth-1.0 > > -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > > -DABICOLLAB_HANDLER_XMPP -I/usr/include/freetype2 > > -I/usr/include/fribidi -I/usr/include/glib-2.0 > > -I/usr/lib/glib-2.0/include -I/usr/include/libgsf-1 > > -I/usr/include/libxml2 -I/usr/include/gtk-2.0 > > -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo > > -I/usr/include/pango-1.0 -I/usr/include/libglade-2.0 -g -O2 -MT > > XMPPUnixAccountHandler.lo -MD -MP -MF .deps/XMPPUnixAccountHandler.Tpo > > -c XMPPUnixAccountHandler.cpp -fPIC -DPIC -o > > .libs/XMPPUnixAccountHandler.o > > In file included from XMPPUnixAccountHandler.h:24, > > from XMPPUnixAccountHandler.cpp:20: > > ./../../../backends/xmpp/xp/XMPPAccountHandler.h:27: error: > > 'std::string' has not been declared > > make[5]: *** [XMPPUnixAccountHandler.lo] Error 1 > > ___ > Sugar mailing list > Sugar@lists.laptop.org > http://lists.laptop.org/listinfo/sugar ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Sugar Digest, Vol 22, Issue 98
On Mon, 2008-04-28 at 09:26 -0700, ValS wrote: > Thanks for this wonderful program! Speaking as an XO user, I am > requesting a feature that I imagine would benefit any users that have > internet access. I would like to be able to use the Write function, > and then send what I have written in an email as an attachment. That > way, I can send it to others, send it to a computer with a printer, > and use the written material in various ways, even as a book. So is > there a chance of compatibility between the Write (and other) > functions and the Browse (where we can access email)? If there is any service on the XO that can send email, then this would be trivial to add to Write. Isn't there a Google SoC application this year to create an an email thing based on tinymail for the XO ? Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] xomail
On Tue, 2008-04-29 at 00:19 +0200, Shikhar wrote: > J.M. Maurer wrote: > > On Mon, 2008-04-28 at 09:26 -0700, ValS wrote: > > > >> Thanks for this wonderful program! Speaking as an XO user, I am > >> requesting a feature that I imagine would benefit any users that have > >> internet access. I would like to be able to use the Write function, > >> and then send what I have written in an email as an attachment. That > >> way, I can send it to others, send it to a computer with a printer, > >> and use the written material in various ways, even as a book. So is > >> there a chance of compatibility between the Write (and other) > >> functions and the Browse (where we can access email)? > >> > > > > If there is any service on the XO that can send email, then this would > > be trivial to add to Write. Isn't there a Google SoC application this > > year to create an an email thing based on tinymail for the XO ? > > > > Marc > > > While not an accepted application, I will be working on an email client > for the XO during June-August regardless. Support for attachments and > mailto: URI's is planned. The wiki page > http://wiki.laptop.org/go/Email_Activity details my ideas and I would > appreciate any suggestions. Thanks, I'll keep an eye on it! :) Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Collaboration in an activity
On Wed, 2008-04-30 at 18:55 +0200, Urko Fernandez wrote: > Hi, > > For sending files I've seen that stream tubes are used in Read activity, > and many examples use D-Bus tubes (Write, Web, Connect...) for sending > python objects. Can I send binary files using D-Bus tubes? Fyi: This is what Write does. It sends binary data over D-Bus tubes, which sometimes (on the initial join, just like in your situation) happens to be an entire word processing file. We never send Python objects over the D-Bus tube. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Missing 0.81.1 tarballs
On Thu, 2008-05-22 at 13:37 +0200, Marco Pesenti Gritti wrote: > See: > > http://wiki.sugarlabs.org/go/Release#Module_release > > Please release your modules as soon as possible. We are missing: > > write-activity Working on it. I hope to have it ready before this weekend. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Write needs your help (was Re: Programming environments on the XO)
> For Firefox, that means (for example) that we can use upstreams > Awesome Bar instead of reimplementing our own url completion. For > abiword, it means acknowledging that a lot of our initial Tubes port > was/is simply unnecessary now that we have a stream-based > collaboration mechanism, and we can/should be able to strip down Write > as a consequence. Iirc, the collaboration code in Write itself is already tiny these days. Or did I miss something spectacular that changes the way collaboration on the XO works? Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Programming environments on the XO
On Thu, 2008-07-17 at 21:41 -0400, Benjamin M. Schwartz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Martin Sevior wrote: > | Hi Folks, > | Just so you know. The only reason for #7447 is because we > | haven't put the UI in to enable it. > > I would like an additional control for background color. Eben, what do > you think? > > | I'm not sure different colors for different users is such a good idea > | though. The document will quickly become a mess. Though if the kids > | want to do this they can. > > Have you used Gobby? It's the shared editor that people at OLPC > _actually_ use, and having per-user background colors is among its key > features. Not sure if I read this correctly, but are you implying that Write's collaboration is not used, but Gobby's is? If so, is there any particular collaboration issue/bug that needs my attention? Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Write needs your help (was Re: Programming environments on the XO)
On Thu, 2008-07-17 at 10:16 +0200, Tomeu Vizoso wrote: > On Thu, Jul 17, 2008 at 8:01 AM, Bobby Powers <[EMAIL PROTECTED]> wrote: > > > >> Marc is a bit of a perfectionist so I'm not sure how usable "95%" of the > >> work is and whether it could be finished by simply using it and > >> providing bug reports as needed would be. > > > > Is this something the community could help with? I know myself and > > maybe another person or two who would be willing to help if it was > > clear what else needed to be done. There is 1 issue in abiword's layout engine that prevents this from being finished. Martin and I discussed it on IRC, and we might have a way to do it. It needs some more explicit designing before we should implement it though. As for me being a perfectionist: I don't want to allow hacks in the code that fix a particular problem now, but will haunt us in the future :) > Martin and Marc will know better about the syntax highlighting stuff, > but if you can help with the very important activity that Write is, > please consider properly packaging pyabiword for fedora (and other > distros): > > http://fedoraproject.org/wiki/PackageMaintainers/WishList#OLPC_Wishlist > > We are using a _really_ old prerelease tarball of abiword: > 2.6.0.svn20071127 . The Abi guys have already released 2.6.4 :/ I'm working on pushing proper packages in Fedora as we speak. It could take a few days before it's finished as this is all spare time work. AbiSource Corporation employees (read: me) can be hired though *hint* :-) Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Programming environments on the XO
On Sat, 2008-07-19 at 18:02 -0400, Benjamin M. Schwartz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > J.M. Maurer wrote: > |> Have you used Gobby? It's the shared editor that people at OLPC > |> _actually_ use, and having per-user background colors is among its key > |> features. > | > | Not sure if I read this correctly, but are you implying that Write's > | collaboration is not used, but Gobby's is? > > Yes. OLPC developers may have been using Write for collaborative document > authoring, but I am not aware of it. I am aware of several occasions on > which Gobby has been used for this purpose, for example for preparing > minutes for a meeting on IRC. But does this hold for kids as well? After all, they are the primary audience for Write. > | If so, is there any > | particular collaboration issue/bug that needs my attention? > > Not a bug. There are two issues: > 1. To the best of my knowledge, Write's collaboration system does not > interoperate with any application that is available on non-Sugar desktops. Well, the AbiCollab plugin existed before Write did, so making Write 'interoperate' with AbiWord would be trivial (in fact, they are exactly the same). > ~ Thus, in order to make use of Write, all participants must have an XO, > emulator, or sugar-jhbuild running. I do not see this as a significant > obstacle in a Rwandan elementary school, but in the diverse environments > of OLPC volunteers, we cannot assume that everyone has easy access to a > Sugar instance. > > In my view, the ultimate solution to this is to push our Telepathy-based > collaboration stack upstream into the standard Linux desktop environments. > ~ Until then, we should come up with a streamlined Sugar emulator that > makes it easy to run an Activity like Write under any standard Linux desktop. There is no technical reason at all that Write could not be made to collaborate with normal AbiWord's. Technically, it already works. There is just no UI that currently exposes it. One could for example add a UI that would allow Write to use abicollab.net's service. This way normal AbiWord users could interoperate trivially with Write, on a global scale. This already works *now*, and has been built from the ground up to scale. Millions of users should be no problem at all for the service. What I'm trying to say: Write's collaboration protocol is *exactly* the same as AbiWord's protocol. > 2. Sugar collaboration over the internet requires a specialized Jabber > server. It has proven difficult to set up such a server at all, and > impossible to set up a server that can be made public without collapsing > under the load. Hopefully, after the Gadget work is complete, we will > begin to see reliable public collaboration servers appear. I've always been of the opinion that using Jabber for this sort of thing was a bad choice. That's why we don't depend on it anymore. Marc > - --Ben > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkiCZHkACgkQUJT6e6HFtqSjfQCfaoF+5IbBo6aFsRFwX5LV6jOb > vmoAoIZ/VhpLCcygbI1eHQa2jjzLo99k > =DkVL > -END PGP SIGNATURE- ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Silver medal
On Tue, 2008-07-22 at 01:17 +0200, Marco Pesenti Gritti wrote: > http://www.idsa.org/IDEA_Awards/gallery/2008/award_details.asp?ID=772 > > Not bad! And gold: http://www.idsa.org/IDEA_Awards/gallery/2008/award_winners.asp?Categories_ID=2#gold Even better! Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Remarks on the Work of Sugar
On Wed, 2008-07-23 at 09:36 +0200, Simon Schampijer wrote: > > Write, Read, TamTam, Paint, Record, Memorize to name a few have been > really struggling lately. There are probably various reasons for that > - one might be I that the activities have been taken out from the base > system another one that the overall development has been really fast > and no entry points/good documentation could be found. And well, the > windows news were not helpful either. You are missing 'funding': Most of Write's development was funded by OLPC, which gave us what we have today. Expecting volunteers to hack on Write is unrealistic at this point. Let me clarify: Write is written in Python and uses the pyabiword bindings around AbiWord's GTK canvas widget extensively. The GTK widget and pyabiword bindings were extended as I went along, to expose the functionality Write needed. Currently almost 100% of pyabiword's functionality is used by Write. What this means is that if Write needs new feature X, it will almost always require new functionality to be exposed through pyabiword *and* AbiWord's GTK canvas widget. This will generally be too hard for volunteers who just want to spend a few hours hacking on something fun. Cheers, Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] libabiword, libabiword-plugins, pyabiword and abiword merged
Hi all, I've merged libabiword, libabiword-plugins and pyabiword from OLPC with the official Fedora AbiWord package. libabiword-plugins only existed in OLPC-land, and has been retired. Everything is built through koji now and joyride should build again. If there are any problems (for example, dragging in too many deps on OLPC), please let me know. Sorry for all the build breakages in the process. It wasn't exactly a trivial merge. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] libabiword, libabiword-plugins, pyabiword and abiword merged
On Wed, 2008-07-23 at 22:24 +0200, J.M. Maurer wrote: > Hi all, > > I've merged libabiword, libabiword-plugins and pyabiword from OLPC with > the official Fedora AbiWord package. libabiword-plugins only existed in > OLPC-land, and has been retired. > > Everything is built through koji now and joyride should build again. If > there are any problems (for example, dragging in too many deps on OLPC), > please let me know. > > Sorry for all the build breakages in the process. It wasn't exactly a > trivial merge. Oh, this also means that libabiword in joyride is the latest upstream version again, instead of some random SVN snapshot from Nov. 2007. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] libabiword, libabiword-plugins, pyabiword and abiword merged
On Thu, 2008-07-24 at 13:10 +0300, Jani Monoses wrote: > Tomeu Vizoso wrote: > > On Wed, Jul 23, 2008 at 10:34 PM, J.M. Maurer <[EMAIL PROTECTED]> wrote: > >> On Wed, 2008-07-23 at 22:24 +0200, J.M. Maurer wrote: > >>> Hi all, > >>> > >>> I've merged libabiword, libabiword-plugins and pyabiword from OLPC with > >>> the official Fedora AbiWord package. libabiword-plugins only existed in > >>> OLPC-land, and has been retired. > >>> > >>> Everything is built through koji now and joyride should build again. If > >>> there are any problems (for example, dragging in too many deps on OLPC), > >>> please let me know. > >>> > >>> Sorry for all the build breakages in the process. It wasn't exactly a > >>> trivial merge. > >> Oh, this also means that libabiword in joyride is the latest upstream > >> version again, instead of some random SVN snapshot from Nov. 2007. > > Is everything needed for Sugar in upstream AbiWord, meaning other > distributions packaging it get all the functionality as well? Yes, as long as they compile AbiWord and plugins with --enable-libabiword (this will be default in 2.8.x). Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Performance
On Thu, 2008-07-24 at 06:16 -0400, Greg Smith wrote: > Hi All, > > I just got word from a decision maker in Uruguay that they are very > concerned about "performance". They say that Sugar is slow. The sugar & activity developers have been for 2.5 years as well :) [snip] > - Activity or main GUI responsiveness to cursor > It seems to me that the activities are a little slow. e.g. when I try to > draw a line in paint, it takes a little while (maybe 100s of ms but > noticeable) for the line to show on the screen. Similar with cursor > placement in write or in the journal/home. Has anyone else noticed that? > Is that due to CPU cycles or screen refresh or something else? > > - Hardware > Can anyone evaluate how much faster it would be with twice the RAM? Is > the NAND slowing us down? > > This may cost us significantly if we don't show improvement. Send me > ideas. Any quick wins would be considered, even if they have a downside > in another metric. Quick wins are ofcourse fine, but *please finally* also invest in a fundamental solution to the problem. Hire/contract someone to properly investigate all the performance issues down from the kernel all the way up to the sugar/activity level. As long as I've been around (2.5 years or so), I've been hearing from developers that they are really eager to work on the performance issues, but have 'always' being held back by being forced to go for the quick wins/hacks. Cheers! Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Programming environments on the XO
On Thu, 2008-07-31 at 21:37 +1000, Martin Edmund Sevior wrote: > > Thanks Tomeu and Eben. Yes, we'll need to expand the abiwidget api. > I'll look to do this if I can can get sugar-jhbuild to work again. That, or we could just add an 'EditMethod', so we can invoke it using a 'well known' function name. Not sure what the nicest approach is. I'm inclined to expand the api though. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [RELEASE] Write 56
On Sat, 2008-08-02 at 02:08 +1000, Martin Edmund Sevior wrote: > > Hi Simon, > Which version of libabiword does this release use? > > Thanks! Write has no dependency on a specific release of libabiword. Any 2.6.x will do. The question should be: which version of libabiword is on the images these days? Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Programming environments on the XO
On Sat, 2008-08-02 at 13:10 +1000, Martin Sevior wrote: > > Hi everyone, >I'm perfectly willing to do this work but how I can be sure > it will actually be used? > > What do we need to do to get libabiword updated? > > sugar-jhbuild uses an ancient patched tree dating from November last > year. We've released 2.6.4 3 weeks ago with *tons* of bug fixes on > that. Afaik, 2.6.4 is on the images > What version is actually being shipped with sucrose? What do we need > to > do to get it updated? Someone should just update jhbuild... i could do that when i find some spare time and motivaten; feel free to beat me to it. > I'd just like to know what I need to do to get the required libabiword > into the tree so that this feature can be implemented. We'll need to backport the featured to 2.6.x first. Will do that soonish as well. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Programming environments on the XO
On Sat, 2008-08-02 at 16:47 +0200, J.M. Maurer wrote: > > > What version is actually being shipped with sucrose? What do we > > need to do to get it updated? > > Someone should just update jhbuild... i could do that when i find some > spare time and motivaten; feel free to beat me to it. Updated jhbuild to abiword 2.6.4. Let's hope we can get the coloring per collaborator in 2.6.5, or at least 2.6.6. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Fwd: [Localization] Arabic Open Bugs in 8.2.0
> To make it short, here is a list of the issues that I think are a must > for an Arabic (and RTL in general) friendly build: > > #3108 The intro screen need to be RTL (there is a patch) > #6562 Mirroring of arrow icons ((there is a patch) > #6800 Journal window RTL (a new complementary patch needs to be applied > since the already applied patch wasn't complete) > #7800 Untranslated time strings in Journal and activity list (there is a > patch, but some issues remain unfixed) Does this mean Arabic works as intended in Write? I seem to recall this was a 'major' issue a year ago. Maybe we fixed it in the meantime :) Marc > So, generally the it is almost done, these patches need to be reviewed > and committed. > > Regards, > Khaled > > > -- > Khaled Hosny > Arabic localizer and member of Arabeyes.org team > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAkiXmKcACgkQRoqITGOuyPKcxACfRLA1THTvFzvHyxHkW6aX3f5+ > BgQAniM8M0rRu1de128oa70KCV3NDu1c > =752b > -END PGP SIGNATURE- > > ___ > Localization mailing list > [EMAIL PROTECTED] > http://lists.laptop.org/listinfo/localization > ___ > Sugar mailing list > Sugar@lists.laptop.org > http://lists.laptop.org/listinfo/sugar ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Question about write from Niue -OLPC training
On Thu, 2008-08-07 at 12:22 +1000, Martin Sevior wrote: > > There is a good chance this is fixed in the current joyride > 8.20 builds. Clearly we need to get these out to you. I can't seem to remember any backport in AbiWord I did that would be related to this. Perhaps your memory is better than mine? Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] abiword difficult for me to understand
On Sun, 2008-08-17 at 23:20 -0400, Mikus Grinbergs wrote: > Went to the location given by the wiki Activities page to download > Write-57.xo. [I've applied the bypass to rename 'keybindings.xml' > in that activity's directory.] Launched Write, entered . CTRL-N should be disabled. How did you build libabiword? > That gave me "real" Abiword -- but the top-of-screen menu items > (plus all the drop-down palette entries) were in Portuguese. I > don't know Portuguese, so I've had to *guess* what all those items > were. This is all not supported for the OLPC, so this is moot really. > Is there an __English language__ Write-57.xo available ? AbiWord uses the LANG environment setting. Set it to en_US, and it will just work. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [RELEASE] Write 58
On Thu, 2008-09-18 at 15:23 +0200, Simon Schampijer wrote: > Simon Schampijer wrote: > > J.M. Maurer wrote: > >> On Sun, 2008-09-14 at 13:20 +0200, J.M. Maurer wrote: > >>> Changelog: > >>> * Fix 6021: Write crash on buddy left > >>> * Add license field to activity.info > >>> > >>> Bundle: http://dev.laptop.org/~uwog/Write-58.xo > >> Source: http://dev.laptop.org/~uwog/Write-58.tar.bz2 > >> > >> Marc > > > > Hi Marc, > > > > thanks for the release! > > > > The tarballs need to go to this repository > > http://dev.laptop.org/pub/sugar/sources/write-activity/ > > > > Actually there has been a sucrose-0.82 branch created ( > > http://dev.laptop.org/git?p=projects/write;a=shortlog;h=sucrose-0.82 > > ) where the localizations have been committed to. Would be cool to > > cherry-pick the commits from master > > ( http://wiki.laptop.org/go/Git_Tips ) and do a new release. > > > > Extra bonus if you add a COPYING file for the fedora packaging and > > http://bugzilla.redhat.com/show_bug.cgi?id=460960 create a new MANIFEST :) > > > > - get the latest sugar-toolkit (there are some bundlebuilder fixes) > > - rm the current MANIFEST in the calculate activity > > - do ./setup.py fix_manifest > > - release and create the new tarball > > > > Thanks, > > Simon > > Done it to speed up the rawhide process. > > source: > http://dev.laptop.org/pub/sugar/sources/write-activity/Write-59.tar.bz2 > > bundled: > http://dev.laptop.org/~erikos/bundles/0.82.1/Write-59.xo Thanks, I still had it marked TODO. I'm in a very busy week, sorry. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] XO evaluation paper
On Mon, 2008-10-20 at 01:27 +0200, Marco Pesenti Gritti wrote: > Am I the only to have missed this paper? > > http://www.teachingmatters.org/evaluations/olpc_kappa.pdf > > The bits about the Journal makes me think that it's really the right idea, > and it will rock as soon as we have a decent implementation of it. Also see > the section about what they disliked... our roadmap is very much on target! > >From page 23: "(5) The computer-to-computer sharing function was not reliable enough for the teacher to be able to build on its functionality—for instance, by having students read and edit each other’s work—presumably because there were too many conflicting signals. Where possible, it would be advisable to set up a school server to act as a switchboard for all the XOs in the school." Does anyone have a clue if this was 1) an hardware/wireless issue 2) a telepathy issue 3) a Write/other application issue, 4) .. something else? It would be a bit annoying if one of the fancy features of the XO was only usable in the lab, and not in practice :) Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Translation into Amharic updates
Hi all, Could any Amharic speaker please have a look a the AbiWord translation update attached in the original message[1]? All strings are marked 'fuzzy', which makes me hesitant to commit it. Any help is very much appreciated, Marc [1] http://www.abisource.com/mailinglists/abiword-dev/2008/Aug/.html On Wed, 2008-08-27 at 11:28 +0200, J.M. Maurer wrote: > To add: all strings are all of a sudden 'fuzzy'. That looks like an > error to me. > > Cheers! >Marc > > > On Fri, 2008-08-01 at 11:56 +0200, Marc "Foddex" Oude Kotte wrote: > > Hi Alex, > > > > For what version of Abiword is this translation file? Trunk? Or 2.6.x? > > > > Cheers, > > Marc > > > > > > On Fri, 2008-08-01 at 12:06 +0300, Alexander Menk wrote: > > > Hi! > > > > > > my colleague, Milka Abay, updated the translation for abiword. > > > > > > Can somebody integrate this into the project ? > > > > > > Do you know if the translation is automatically importet to the Ubuntu > > > project? > > > > > > Thanks, > > >Alex > > > ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] AbiWord 2.6.5 pushed, please test!
Hi all, I've just updated AbiWord to 2.6.5 in sugar-jhbuild as well as fedora's OLPC-3 branch. A public release on abisource.com will follow soonish, but we don't want to keep the kids waiting now, do we? The most important change in this release for OLPC is "improved complex script rendering". To be precise: before 2.6.5, AbiWord did not always shape composite glyphs correctly. This made AbiWord unusable for languages like Arabic. So, I'd like to ask everyone familiar with such languages to test AbiWord 2.6.5. If you use the Write activity that uses libabiword 2.6.5 to test Arabic for example, then make sure to use a font that includes Arabic glyphs. DejaVu Sans does if I remember correctly[1]. We improved our rendering based on community feedback only, as none of the AbiWord developers have any knowledge of complex scripts themselves. Ergo: * We depend on your feedback! * Thanks to all who helped in the process so far. If you find any bugs, the please file a bug report at http://bugzilla.abisource.com. Extra kudos if you can reproduce it reliably :) Cheers! Marc [1] Write should default to a proper font based on the locale. It's a known 'bug'. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] AbiWord 2.6.5 pushed, please test!
On Sun, 2008-11-23 at 23:28 +, Daniel Drake wrote: > Hi Marco, > > Thanks for your efforts. > > On Sun, Nov 23, 2008 at 10:14 PM, J.M. Maurer <[EMAIL PROTECTED]> wrote: > > I've just updated AbiWord to 2.6.5 in sugar-jhbuild as well as fedora's > > OLPC-3 branch. A public release on abisource.com will follow soonish, > > but we don't want to keep the kids waiting now, do we? > > You'll have to push to OLPC-4 now, since we moved to F10. And as we > only just did this, there are some problems launching activities right > now, but that will hopefully be fixed within the next few days. Thanks for the pointer Daniel! I will file a branch request, and report when the build is available. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] AbiWord 2.6.5 pushed, please test!
Hi Greg, > Can you make a .xo file that people can download and install via the > browser on the XO? You don't need an .xo update for this (the current Write version will work just fine), but an libabiword RPM update. I'm not sure how people with an XO would retrieve this, as I was out of the loop for a lil' while and stuff has been changing fast ;) Anyone? Marc > If you can post that, I think I can get a few Arabic speakers with > Arabic XOs to try it out. That would be very much appreciated! Marc > Thanks, > > Greg S > > > > Date: Sun, 23 Nov 2008 23:14:44 +0100 > From: "J.M. Maurer" <[EMAIL PROTECTED]> > Subject: [sugar] AbiWord 2.6.5 pushed, please test! > To: sugar@lists.laptop.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain > > Hi all, > > I've just updated AbiWord to 2.6.5 in sugar-jhbuild as well as fedora's > OLPC-3 branch. A public release on abisource.com will follow soonish, > but we don't want to keep the kids waiting now, do we? > > The most important change in this release for OLPC is "improved complex > script rendering". To be precise: before 2.6.5, AbiWord did not always > shape composite glyphs correctly. This made AbiWord unusable for > languages like Arabic. > > So, I'd like to ask everyone familiar with such languages to test > AbiWord 2.6.5. If you use the Write activity that uses libabiword 2.6.5 > to test Arabic for example, then make sure to use a font that includes > Arabic glyphs. DejaVu Sans does if I remember correctly[1]. > > We improved our rendering based on community feedback only, as none of > the AbiWord developers have any knowledge of complex scripts themselves. > Ergo: > >* We depend on your feedback! * > > Thanks to all who helped in the process so far. > > If you find any bugs, the please file a bug report at > http://bugzilla.abisource.com. Extra kudos if you can reproduce it > reliably :) > > Cheers! >Marc > > [1] Write should default to a proper font based on the locale. It's a > known 'bug'. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] AbiWord 2.6.5 pushed, please test!
On Wed, 2008-11-26 at 10:31 +0100, Tomeu Vizoso wrote: > On Tue, Nov 25, 2008 at 9:17 PM, J.M. Maurer <[EMAIL PROTECTED]> wrote: > > Hi Greg, > > > >> Can you make a .xo file that people can download and install via the > >> browser on the XO? > > > > You don't need an .xo update for this (the current Write version will > > work just fine), but an libabiword RPM update. I'm not sure how people > > with an XO would retrieve this, as I was out of the loop for a lil' > > while and stuff has been changing fast ;) > > Well, this is still pretty much the same, people would need to install > a rpm via the traditional methods and would need root for that. So "yum -y update libabiword" it is. Marc > There's some chance of bundling the libraries inside the .xo, > overriding the ones in the system, though haven't tried that myself > and I'm not sure what it would take. > > Regards, > > Tomeu > > > Anyone? > > > > Marc > > > >> If you can post that, I think I can get a few Arabic speakers with > >> Arabic XOs to try it out. > > > > That would be very much appreciated! > > > > Marc > > > >> Thanks, > >> > >> Greg S > >> > >> > >> > >> Date: Sun, 23 Nov 2008 23:14:44 +0100 > >> From: "J.M. Maurer" <[EMAIL PROTECTED]> > >> Subject: [sugar] AbiWord 2.6.5 pushed, please test! > >> To: sugar@lists.laptop.org > >> Message-ID: <[EMAIL PROTECTED]> > >> Content-Type: text/plain > >> > >> Hi all, > >> > >> I've just updated AbiWord to 2.6.5 in sugar-jhbuild as well as fedora's > >> OLPC-3 branch. A public release on abisource.com will follow soonish, > >> but we don't want to keep the kids waiting now, do we? > >> > >> The most important change in this release for OLPC is "improved complex > >> script rendering". To be precise: before 2.6.5, AbiWord did not always > >> shape composite glyphs correctly. This made AbiWord unusable for > >> languages like Arabic. > >> > >> So, I'd like to ask everyone familiar with such languages to test > >> AbiWord 2.6.5. If you use the Write activity that uses libabiword 2.6.5 > >> to test Arabic for example, then make sure to use a font that includes > >> Arabic glyphs. DejaVu Sans does if I remember correctly[1]. > >> > >> We improved our rendering based on community feedback only, as none of > >> the AbiWord developers have any knowledge of complex scripts themselves. > >> Ergo: > >> > >>* We depend on your feedback! * > >> > >> Thanks to all who helped in the process so far. > >> > >> If you find any bugs, the please file a bug report at > >> http://bugzilla.abisource.com. Extra kudos if you can reproduce it > >> reliably :) > >> > >> Cheers! > >>Marc > >> > >> [1] Write should default to a proper font based on the locale. It's a > >> known 'bug'. > > > > ___ > > Sugar mailing list > > Sugar@lists.laptop.org > > http://lists.laptop.org/listinfo/sugar > > ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
