Re: MSWrite plugin default codepage issue

From: "Ingo Brückl" <ib@wupperonline.de>
Sent: Sunday, July 24, 2011 7:29 PM
To: <abiword-dev@abisource.com>
Subject: MSWrite plugin default codepage issue

> This is the patch I propose to deal with the default codepage issue.
>
> It follows a non-working version committed earlier and allows the user to
> select his/her favorite default codepage by passing an importer argument,
> namely '-i mswrite-codepage:CP1250' (CP1250 in this example, but every other
> supported encoding allowed).
>

'Non-working version' of what? Would you stop to buffoon? Also, why is the parameter 'mswrite-codepage' and not 'encoding' like in other similar plugins? Why the most common case when documents are in user's local codepage is not fixed? Importer parameters can be specified only in batch conversions, not when opening a document in a standard way.

Unless you provide some test cases when the using of user settings to select default codepage, I will be consider your actions as intentional sabotaging of a program functionality in interests of Western countries users minority.
Received on Mon Jul 25 00:17:59 2011