Re: Bugs of yesteryear

On Tue, 31 May 2011, Morten Juhl-Johansen [ISO-8859-1] Zölde-Fejér wrote:

> Date: Tue, 31 May 2011 00:25:54 +0200
> From: "Morten Juhl-Johansen [ISO-8859-1] Zölde-Fejér"
> <mjjzf@syntaktisk.dk>
> To: abiword-dev@abisource.com
> Subject: Bugs of yesteryear
>
>
> I would like to nominate the following to be closed:

The way you presented this email means to reply readers will need to
go through the slow process of looking-up each report and reading it,
sometimes having to read a whole lot to get the sense of it.

A short summary or bug title would have gotten better responses. For the
bugs I've looked up I've included a summary with my reply to help others.

(By virtue of having taken on the task of bug traige you could probably
have closed any and all reports you liked and waited to see if anyone
cared enough to reopen them. Thankfully abiword has usually been a much
more civilised project than that so thanks for bringing these to the
list. I should check bugzilla for reports I threatened to close if no one
reponded, they're probably still there from years ago.)

> * http://bugzilla.abisource.com/show_bug.cgi?id=1016 - Fixed

bug 1016 Printing PDF

If all platforms are using Cairo (not just GTK) then yes this is truly
fixed, as mentioned in the report.

> * http://bugzilla.abisource.com/show_bug.cgi?id=1022 - if anything,
> this behavior should merely be documented.

If you are on the last line of a column in a multi-colum layout down arrow
will bring you to the next page rather than the next column.

According to the bug report OpenOffice/LibreOffice does not behave this
way.
Microsoft Office 2000 behaves as abiword does.
This behaviour seems okay to me.

> * http://bugzilla.abisource.com/show_bug.cgi?id=1467 - comments? It
> seems like a pointless effort, and a major one at that. One would
> assume that there is a likely loss in all exports?

I've close it as WONTFIX

... many other requests some of which I might look up later ...

> Also, requests have been made for import filters for various
> applications. Quite a few of these requests have not been touched for
> 10 years.

If the file format is proprietary and undocumented politely close the
request.
If the file format is undocumented but code is open you should probably
close the request too but maybe best to just add a comment stating how
unlikely it is to be implmented but that patches would be welcome.

Sometimes people jump on those import export filters as smaller projects
to familiarise themselves with the codebase. Are there any that look
particularly promising they might be worth mentioning in the next release
notes or a news item?

-- 
Alan H