Re: [cssed-devel] Problems with encoding changes

[Iago R. <iag...@hi...>]

On Fri, 2004-09-24 at 19:04, Mich=C3=A8le Garoche wrote:
> Le 24 sept. 2004, =C3=A0 18:47, Iago Rubio a =C3=A9crit :
>=20
> > On Fri, 2004-09-24 at 10:14, Mich=C3=A8le Garoche wrote:
> >> Say I write down a file with no special encoding.
> >
> > ok.
> >
> >> I put Mich=C3=A8le in it: (e grave on the first e).
> >> Then I save the file.
> >>
> >> Then I change the encoding to utf8, with Document->Encoding,
> >
> > Nope, you forze the buffer to be treated as UTF-8, it does not change
> > the encoding, nor convert between encodings.
> >
> > All text in the buffer will be in the file's encoding, and all new text
> > in the  selected encoding.
> >
> >> it leads
> >> to the loss of all characters after Mich (on the display at least).
> >> That's annoying.
[snip]
> > So the encoding is treated trasparently, but can not convert between
> > encodings yet.
> >
> > So ... what the hell is needed the anoying "Encoding" stuff ?
> No, I find it perfect. That's not annoying at all. Just people should=20
> know how it works.

Yes, you're right.

> > It's needed because cssed will treat all documents as UTF-8. If you=20
> > need
> > to write a document to anyone that can not read UTF-8, you can forze=20
> > the
> > encoding - before to write any text - and save in you preferred
> > encoding.
> >
> > I think that will be better to rename it as "Forze encoding" or
> > something like that.
> Maybe, but better force encoding :-)
Upsh ! Sure :)

Do you think we must change the name ?
--=20
Iago Rubio  =20
- Home page    * http://www.iagorubio.com=20
- Last project * http://cssed.sourceforge.net        =20
- GPG Keyserv  * pgp.rediris.es id=3D0x909BD4DD