Re: [cssed-devel] Problems with encoding changes

[<mic...@ea...>]

Le 25 sept. 2004, =E0 19:34, Iago Rubio a =E9crit :

>> Maybe, but better force encoding :-)
> Upsh ! Sure :)
>
> Do you think we must change the name ?
Yes, because it is very confusing. The user should be aware he may=20
spoil his file if he uses this without thinking first about it.
With Force encoding, or something like that, it is clear that it is not=20=

a "normal" way of doing it.
Maybe a tooltip on the menu items to tell the user that he should use=20
it before writing anithing in the document or something like that would=20=

be useful too.

Mich=E8le
<http://micmacfr.homeunix.org>