Comments on: AbiWord team interview http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/ Red Hat Magazine Fri, 10 Oct 2008 20:20:19 +0000 http://lyceum.ibiblio.org/?v=1.0.2 by: Степаныч http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-110138 Wed, 30 Jul 2008 22:57:58 +0000 http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-110138 Да уж. В этом блоге хоть комментаторы нормальные А то пишут в комментарии чушь всякую. Да уж. В этом блоге хоть комментаторы нормальные А то пишут в комментарии чушь всякую.

]]> by: Jayne Brooks http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-101104 Thu, 26 Jun 2008 21:27:13 +0000 http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-101104 My computer tech son is traveling and can't help me until he returns. I cannot figure out why my resume created in Abiword does not hold its format. The bullet points and bolded fonts are totally lost, plus there are huge gaps of information that don't even show up when printed out. Can anybody give me an advice? I would appreciate your comments. Thanks! Jayne My computer tech son is traveling and can’t help me until he returns. I cannot figure out why my resume created in Abiword does not hold its format. The bullet points and bolded fonts are totally lost, plus there are huge gaps of information that don’t even show up when printed out. Can anybody give me an advice? I would appreciate your comments.

Thanks!
Jayne

]]> by: linuzine.net » AbiWord http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-94024 Thu, 05 Jun 2008 19:35:39 +0000 http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-94024 [...] In una recente intervista su Red Hat Magazine e dal suo blog, Marc Mauner, spiega le motivazioni che hanno orientato gli sviluppatori al supporto del formato Office Open XML in Abiword. [...] […] In una recente intervista su Red Hat Magazine e dal suo blog, Marc Mauner, spiega le motivazioni che hanno orientato gli sviluppatori al supporto del formato Office Open XML in Abiword. […]

]]> by: Kim Dammers http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-92257 Sun, 01 Jun 2008 01:02:24 +0000 http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-92257 I have to say that I am disappointed in AbiWord. It seems to mimic MSW too much (with many of the same problems) and yet doesn't appear to have some of good features of MSW. Also, the support system is opaque to me. I guess it's designed for geeks, so making it usable by others is of no interest to you folks. That's too bad. I have to say that I am disappointed in AbiWord. It seems to mimic MSW too much (with many of the same problems) and yet doesn’t appear to have some of good features of MSW. Also, the support system is opaque to me. I guess it’s designed for geeks, so making it usable by others is of no interest to you folks. That’s too bad.

]]> by: Alban’s blog » Collaborative editing of source code http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-85899 Thu, 15 May 2008 14:34:26 +0000 http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-85899 [...] The editors landscape use very different languages: Emacs Lisp for GNU Emacs, the Vim script language for vim (although Python can be used, see this presentation from PyCon), C and Python for gedit. Whatever the way we choose to resolve conflicts that happens in real-time editing, it seems complex: it took some years to the Abiword team to build the Collab plugin. I would prefer to avoid writing complex things in all theses differents editors and languages. [...] […] The editors landscape use very different languages: Emacs Lisp for GNU Emacs, the Vim script language for vim (although Python can be used, see this presentation from PyCon), C and Python for gedit. Whatever the way we choose to resolve conflicts that happens in real-time editing, it seems complex: it took some years to the Abiword team to build the Collab plugin. I would prefer to avoid writing complex things in all theses differents editors and languages. […]

]]> by: Συνέντευξη του Abiword Team στο Red Hat Magazine « Altervedo’s Weblog http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-85297 Wed, 14 May 2008 08:31:42 +0000 http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-85297 [...] Μάιος 14, 2008 στο 12:45 μ.μ · Κατηγορία Software, Δωρεάν, Δωρεάν Software and επιτυχής ετικέτα: AbiCollab, Abiword, ODT, OLPC, OpenOffice To abiword είναι ο επεξεργαστής κειμένου που χρησιμοποιώ για τις καθημερινές μου ανάγκες. Πολύ καλό και χρήσιμο software. Το Red Hat Magazine δημοσίευσε μια συνέντευξη με τους developers του Abiword. Καλύπτει μεγάλο αριθμό θεμάτων ( AbiWord, AbiCollab, OLPC, OOXML, ODT και άλλα ) που δυστυχώς δεν έχω το χρόνο να αναλύσω εδώ. Πολύ ενδιαφέρουσα συνέντευξη..αξίζει την ανάγνωση. [...] […] Μάιος 14, 2008 στο 12:45 μ.μ · Κατηγορία Software, Δωρεάν, Δωρεάν Software and επιτυχής ετικέτα: AbiCollab, Abiword, ODT, OLPC, OpenOffice To abiword είναι ο επεξεργαστής κειμένου που χρησιμοποιώ για τις καθημερινές μου ανάγκες. Πολύ καλό και χρήσιμο software. Το Red Hat Magazine δημοσίευσε μια συνέντευξη με τους developers του Abiword. Καλύπτει μεγάλο αριθμό θεμάτων ( AbiWord, AbiCollab, OLPC, OOXML, ODT και άλλα ) που δυστυχώς δεν έχω το χρόνο να αναλύσω εδώ. Πολύ ενδιαφέρουσα συνέντευξη..αξίζει την ανάγνωση. […]

]]> by: J David Eisenberg http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-84921 Tue, 13 May 2008 15:39:03 +0000 http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-84921 "basically because ODT is nothing more than a dump of OpenOffice.org’s internal format" This is incorrect. OpenDocument is designed as an idealized structure for office documents. From the spec: "The schema provides for high-level information suitable for editing documents." In other words, it's not a low-level dump of an internal format. As to ODF being controlled by IBM, Sun, etc: they are members, but that doesn't mean that outside contributors aren't welcomed. Look at the spec for version 1.0 and the list of editors and contributors. Of the 18 names, only 3 are from Sun, and none from IBM. (One co-chair of the committee is now from IBM.) Individual memberships to OASIS are also possible; US$300 per year. Full disclosure: I am a member of the ODF Adoption Technical Committee. “basically because ODT is nothing more than a dump of OpenOffice.org’s internal format”

This is incorrect. OpenDocument is designed as an idealized structure for office documents. From the spec: “The schema provides for high-level information suitable for editing documents.” In other words, it’s not a low-level dump of an internal format.

As to ODF being controlled by IBM, Sun, etc: they are members, but that doesn’t mean that outside contributors aren’t welcomed. Look at the spec for version 1.0 and the list of editors and contributors. Of the 18 names, only 3 are from Sun, and none from IBM. (One co-chair of the committee is now from IBM.) Individual memberships to OASIS are also possible; US$300 per year. Full disclosure: I am a member of the ODF Adoption Technical Committee.

]]> by: Jakob Petsovits http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-84802 Tue, 13 May 2008 10:21:00 +0000 http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-84802 Very nice interview. The only part that I didn't like were the biased statements against ODF - the KOffice people proved it's not necessary to have large company backing in order to participate in the process, and they also proved that it's possible to use ODF as default format even if you're not OpenOffice. Also mind that ODF is still evolving and you can still fix the mentioned shortcomings - if you still have no intention to join the process itself, I would guess that talking to David Faure (who represents KOffice and is generally a very nice guy) could also help a lot. Very nice interview.

The only part that I didn’t like were the biased statements against ODF - the KOffice people proved it’s not necessary to have large company backing in order to participate in the process, and they also proved that it’s possible to use ODF as default format even if you’re not OpenOffice.

Also mind that ODF is still evolving and you can still fix the mentioned shortcomings - if you still have no intention to join the process itself, I would guess that talking to David Faure (who represents KOffice and is generally a very nice guy) could also help a lot.

]]> by: MarcMaurer http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-82915 Sat, 10 May 2008 19:57:50 +0000 http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-82915 @Janne: Thanks a lot for doing that work! A developer will hopefully fix your issue soon then. This is a 100% volunteer effort, so some things might take (too much) time from time to time. Even though we might be slow to respond, your input is highly appreciated. @Janne: Thanks a lot for doing that work! A developer will hopefully fix your issue soon then. This is a 100% volunteer effort, so some things might take (too much) time from time to time. Even though we might be slow to respond, your input is highly appreciated.

]]> by: Janne http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-82372 Sat, 10 May 2008 04:16:00 +0000 http://www.redhatmagazine.com/2008/05/08/abiword-team-interview/#comment-82372 Marc, I am not able to help with coding (time as well as programmatic knowledge of input method handling prevents it). What I can do is show how it goes wrong, and what should actually happen. But this I have already done - I've left four bug reports on this so far, about one per major release. The last one with illustrations attached showing exactly what the problem is and how other GTK applications behave correctly. And as you have the problem described in detail a number of times already I just don't see a point in filling a fifth bug report with the same information. Marc, I am not able to help with coding (time as well as programmatic knowledge of input method handling prevents it). What I can do is show how it goes wrong, and what should actually happen. But this I have already done - I’ve left four bug reports on this so far, about one per major release. The last one with illustrations attached showing exactly what the problem is and how other GTK applications behave correctly. And as you have the problem described in detail a number of times already I just don’t see a point in filling a fifth bug report with the same information.

]]>