Martin Sevior wrote:
>
> On Tue, 29 May 2001, Andrew Dunbar wrote:
>
> > Martin Sevior wrote:
> > >
> > > Hi Andrew,
> > > Are you sure the dialog should be called from within ie_*? Why
> > > not from within the "open" or "save as" dialogs? These are called from the
> > > the file:
> >
> > I thought of this too and calling a dialog from a dialog seems
> > undesirable. Also for importing it's nice to run the function that
> > tries to guess the encoding first and making it the default option.
> >
>
> This will always be run from within a dialog anyway right? I mean you
> select "save file as" and up pops a dialog asking for the file name. Would
> it make sense to have an extra button or two on that dialog rather than a
> second dialog that pops up after you've selected the filename?
It seems simpler to have the one dialog appear after the other.
At least on Windows the file open and save dialogs are unmodified
system dialogs. They may be extendable but this seems like much
unnecessary complication and may be beyond my Windows skills anyway.
It would also be painful for the to port to the other OSes.
I know it's sinful to do things just because MS Word does them a
certain way but in this case it seems simpler and more logical all
around.
> > > src/wp/ap/xp/ap_EditMethods.cpp. > >
> > > I think that ie_imp_* and ie_exp* should report back to their calling
> > > dialogs (open) and "save" or "save as" or "export" the state of the
> > > encoding.
> >
> > I'll look down that path, thanks.
> >
> > > However as a plain old ascii user I certainly wouldn't want to know about
> > > what encoding to set my file to. How do you plan on hiding this info from
> > > this large target market?
> >
> > Well you'd probably be surprised how many characters above 127 you
> > actually do use unless you consciously avoid them. On almost all
> > OSes the default charset is 8 bit: ISO-8859-1 for *nix, code page
> > 1252 for Windows, and Mac Roman of course on a Mac. And even then
> > English is almost alone in being fully expressable in 7-bit ASCII.
> >
>
> I really don't want to know about how my file is
> encoded. I just want it to work and I want to be able to type
> "more fred.abw" and see sensible text.
This will never affect .abw files. It's for people who need to
import and export plain text documents from a different platform
or in countries that regularly use more than one encoding. For
these people this is something they know and understand. Even
"church secretaries" already have to do this in Asia for example.
This is also a way to use annoying Windows text files with smart
quotes and such.
> Maybe users in other locales are used to encoding issues but English
> speakers aren't and really don't want to know.
They'll never use it. Even in England, the pound sign "�" is
essential - and it's not ASCII!
> > Still, I intend to supplement the current "Text" option with an
> > "Encoded Text" option in the Open and Save dialogs. Note that
> > this will only work properly once Bug 1471 is fixed:
> > http://bugzilla.abisource.com/show_bug.cgi?id=1471
>
> That can be fixed pretty easily. It's just a bug.
Cool (:
--
http://linguaphile.sourceforge.net
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
