Re: MSWrite plugin default codepage issue

From: Ingo Brückl <ib_at_wupperonline.de>
Date: Tue Aug 02 2011 - 11:55:10 CEST

Urmas wrote on Mon, 1 Aug 2011 23:25:51 +0700:

> The inability of users of marginal OS's with ~1% popularity to set it
> correctly definitely is not a reason to negatively affect users of other
> OS's, which can be easily set up accordingly to user-preferred language
> setting, including codepage for legacy documents.

I didn't speak of inability, but of a deliberate use. Not all users stay with
the codepage and/or the OS they used in Write times.

Common benefit (i.e. general usage) takes precedence over personal benefit.

>>> Importer parameters can be specified only in batch conversions, not when
>>> opening a document in a standard way.
>>
>> Hmmm, then I'm doing something wrong, because this patch works just fine as a
>> command line argument to AbiWord, translating all Write documents into the
>> given codepage when opening.
>>

> Because you're setting importer properties from global variable, parsed
> from arguments, instead of using preset properties from IE_Imp. It's a
> hack.

Well, I'd be delighted to see a "non-hack" solution that does the job then.

Ingo
Received on Tue Aug 2 13:31:03 2011

This archive was generated by hypermail 2.1.8 : Tue Aug 02 2011 - 13:31:03 CEST