[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openoffice-users
Subject:    Re: Re: .doc problems
From:       rbe <rbe () flash ! net>
Date:       2004-05-26 22:55:19
Message-ID: c9378j$16i$2 () sea ! gmane ! org
[Download RAW message or body]

Marc Williams wrote:

> On Wed, 26 May 2004 17:00:08 +0100, Jim Higson wrote:
>> On Wednesday 26 May 2004 16:32, Marc Williams wrote:
>>> Ok, I've submitted bug
>>> http://www.openoffice.org/issues/show_bug.cgi?id=29535
>>>
>>> Hopefully this shows what I am seeing even though you are evidently
>>> not.
>> 
>> Having seen the doc in your MSWord screenshot (I don't have a Windows
>> computer) The problem seems to be three things:
>> 
> 
> As much as I would love to deep six Windows from my wife's machine,
> having MS Word viewer and Quicken are pretty much required until OOo
> and Gnucash can take their respective places, pretty much drop-in.

Give kmymoney2 a try.  Join their users list.  They have asked for some 
suggestions about types of reports.  In many ways it is much better 
than GnuCash and in other ways, much too limited.  They have focused on 
getting things up and running as bug-free as possilble before adding 
more bells and whistle (even delaying report options for years to make 
sure everything else is working nearly perfectly).  It's a good effort 
and faster than Gnucash.

Beyond that is Kapital from thekompany.com.  It seems to work very 
well, but is proprietary and suffering the same lack of prompt user 
response that proprietary systems have.  Still, it looks promising.  
Nothing yet replaces Qucken, but I have been using kmymoney2 for a year 
and it comes close in many ways.
 
>> 1 (maybe) the quality of the logo image is lower in OOo
>> 2 There is a ImageMap in one of the cells that pulls it to be much
>> too tall. Presumably, the user added it accidentally and MSO ignores
>> it while OOo assumes it was intentional and tries to fit it in.
>> 3 The tables in the .doc file have been incorrectly imported, so that
>> the logo's cell is shown in the wrong place.
> 
> I see your #2 as being the main issue here is I understand you
> correctly. The table is so far out of whack as to make it pretty much
> unusable.

-- 
Robert Black Eagle


[prev in list] [next in list] [prev in thread] [next in thread]