Re: AbiWord Fork or Replacement that does not require libgnome*

John R. Culleton wrote:

>On Tuesday 21 February 2006 18:05, Hubert Figuiere wrote:
>
>
>>John R. Culleton wrote:
>>
>>
>>>On Tuesday 21 February 2006 16:14, Ryan Pavlik wrote:
>>>
>>>
>>>>John R. Culleton wrote:
>>>>
>>>>This is not a matter of "insisting on GNOME" and non-libgnomeprint unix
>>>>printing, was, indeed, "broke." Libgnomeprint is a small and poorly
>>>>named (as it doesn't require GNOME) library that provides immensive
>>>>improvements to printing, improving the functionality for the users of
>>>>AbiWord. Libgnomeprint is so useful, in fact, that it's being
>>>>considered to be integrated into new releases of GTK+ (I believe). As a
>>>>slackware user myself, I am aware of the removal of GNOME. A suggestion
>>>>to include libgnomeprint and the related libraries, I feel, would not be
>>>>an overwhelming request, because they do not bring in the entire GNOME
>>>>tree. Furthermore, if you want to use the fully GNOME version of
>>>>AbiWord, there are several distributions of GNOME for Slackware that
>>>>will allow you to use the fully-GNOME version or the GTK+-only version
>>>>equally well.
>>>>
>>>>Thanks for using AbiWord!
>>>>
>>>>
>>>Well now I am confused. Lots of other programs have printing
>>>functions, implemented by interfacing with either cups or
>>>lprng, depending on which package is in use at the particular
>>>site. I have no idea what you mean about printing being poorly
>>>implemented on Unix. It always worked for me.
>>>
>>>
>>because you don't understand. cups or lprng are transport layers for
>>printing. You still need to generated something the printer will
>>understand, ie PostScript. libgnomeprint offers this generation to then
>>send it to the printer. It is that Postscript code generation that cause
>>LOT OF PROBLEMS. Now we can:
>>1/ spend time working on cool feature or important bugfixes
>>2/ spend time satisfying users that have decided that the Linux desktop
>>should still stay the way it was 10 years ago.
>>
>>I pick 1/
>>
>>
>
>Well I agree on that. And I would even be willing to contribute
>within the limits of my skills. Some time back I pointed up the
>fact that the LaTeX export was in need of a few simple fixes. I
>asked what code module that function was located in. The silence
>was deafening.
>
>Sorry if I was a bit testy. I just wasted some time with an
>unsuccessful install of a neat program that put me in the
>"first you need A, but before A works you need B, but before B
>works...." etc. It sounded like gnomeprint was an unnecessary
>complication. Now I see that it is included with Gimp. But Gimp
>isn't great in the PostScript area either, perhaps due to benign
>neglect.
>
>
>
Looks like you already found it, but the location in the source of the
LaTeX exporter is /abiword-plugins/wp/impexp/latex

Development-related questions such as how to contribute code would
probably do better on the dev list, since most users and people
subscribed to this list probably wouldn't know the answers to that kind
of question. Some devs are subscribed, but it's still not quite the
right place.

Thanks for using AbiWord!

-- 
Ryan Pavlik
AbiWord Win32 Platform Maintainer
www.abisource.com
"Optimism is the father that leads to achievement." - Helen Keller
-----------------------------------------------
To unsubscribe from this list, send a message to
abiword-user-request@abisource.com with the word
unsubscribe in the message body.