Dom Lachowicz wrote:
>
> > Bummer. I've already got it working. I cloned the Language dialog
> > and loaded English, Japanese, and Unicode this afternoon. I've been
> > working on adding all the major encodings which libiconv supports
> > and thinking about problems such as which order to list them under
> > different OSes, selecting the language and having code to guess the
> > encoding, and building in only the encodings the machine's iconv
> > can handle. I'll look into extending the FileOpenSaveAs dialog but
> > I'm not sure I'll have time since I'm also planning a major overseas
> > trip...
>
> Don't get too down on yourself ;-) I try to do tree control every once in a
> while! Your dialog will be fine. Your other code I'm sure is fine. The only
> thing that I'm contesting is where you should activate your dialog and how its
> information gets propegated to the importer/exporter.
>
> > Would it be acceptable to submit it the current way so that others
> > can bend it into shape?
>
> Yes, please do submit this and someone will integrate this into the tree
> appropriately (i.e. after those few mods are made).
>
> This is something that I'm *really* glad that someone did and i *really really
> really* want to see go into the tree ASAP. I won't have any time to do this in
> the next week or so but chances are that I'll have time next week.
>
> > I'll see what I can do though I'd hate to think my efforts might
> > be wasted. Especially in the greatly overlooked area of
> > multilanguage support.
>
> Fear not, your efforts aren't wasted. They're *greatly* appreciated. This is
> functionality that we dearly need and will put us ahead of our competition in
> this regard.
>
> Thank you very much Andrew for all of your hard work. Keep it up dude!
Hi Dom and thanks very much for your kinds words and encouragement.
I've spent some time thinking about these dialogs and I'm certain I
understand why you want it this way - it would seem technically more
polished - and I did think the same initially. I'll do my best to
go with what you guys decide is best but here are a few reasons why
I think the way I've already got is a good thing:
1. There won't be a useless and confusing encoding checkbox when you're
not saving/loading a text file.
2. There won't be a confusing encoding checkbox when church secretaries
and 7-bit ASCII only people are saving/loading a text file.
3. Since importers and exporters can now be optional modules, people
who choose not to install the Encoded Text import and export modules
will never see this mysterious extra widget on the Open/Save dialog.
4. We won't have to do tricky code to add/remove or show/hide this
checkbox to alleviate points 1 to 3.
5. The Encoded Text import/export modules will be fully self-contained
and the Open/Save dialog will be fully self-contained.
And this isn't a real point since I hate MS too... (:
6. Word 2000 already does it this way and some people are used to it.
Thanks for listening to my hopefully well thought out rant.
Does anybody else have a viewpoint on this? Again, I'm the newbie
here so whatever you guys say goes (:
Andrew.
--
http://linguaphile.sourceforge.net
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
