> On 06.01.2010 14:20, Mike Williams wrote:
>
>> Not a trivial problem to solve at the time. When discussed with Bram it
>> was decided this was not wanted. Dunno if time has changed the argument
>> at all.
>
> I'm complaining about this issue for the last ten years. This is just
> unbelievable: such a mighty text editor as gVim just does not allow
> Windows international users to print their texts when gVim is set to use
> UTF-8 as it's internal encoding... :(
Indeed. Windows supports encoding conversion so it should be possible
to do it as part of gvim without having to find a copy of iconv. It
just hasn't been an issue for any of the Windows VIM developers. There
is not a lot I can do about that.
> Note, please: you are _forced_ to use the UTF-8 as gVim internal
> encoding if you want to be able to perform encoding conversions...
>
> I just don't remember any other text editor with such restriction (not
> counting the crippleware ones)...
>
> For many of us printing is as important as saving your edits.
> Can you imagine a full-featured text editor in a year 2010 which does
> not allow users to save or print the text files? :(
>
I hear you. New features seem to be all the rage, I doubt this would be
a candidate for GSoC which would be a nice way to sort this all out.
TTFN
Mike
--
Education is what you get from reading the small print; experience is
what you get from not reading it.
No comments:
Post a Comment