Re: [cssed-devel] Test packages 0.3.0

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

On Fri, 2004-09-24 at 10:01, Mich=C3=A8le Garoche wrote:
> Le 24 sept. 2004, =C3=A0 9:51, Iago Rubio a =C3=A9crit :
> > On Fri, 2004-09-24 at 04:23, Mich=C3=A8le Garoche wrote:
> >> Do you mean you have changed the build scripts versus cvs?
> > No, I've no changed them and will not change until the release. Right
> > now they're frozen.
> OK, perfect, when completely done, could you load somewwhere the=20
> definitive packages (but not on the web site, otherwise, people as=20
> likely to download them), so that I test them as if I dowload them (not=20
> from cvs).

I will upload it to your box and mail you.

> >>> The source tree is the CVS one.
> >>> I'm working now in the BSD port and Debian packages,
> >>> I hope we'll release this week-end :)
> >> Hope the doc is finished by this time :-) Deadline? Sunday 23 hours?
> > If it's a big workload for you, or you need more time for the doc, we
> > can wait.
> I'll think it will be ok, but well, I discover some glitches while=20
> making the doc, so that's may delay a bit.

Don't worry about the delay.=20

> Some questions:
>=20
> Encoding->Default: what is it? (utf-8, defined by the user, picked from=20
> the file extension, or other?)

Usually an ISO-##### encoding.

> Encoding->others (utf8, dbcs): does it change the encoding of the file=20
> or just the display in cssed?

It will not change the current buffer but will set this encoding for all
incoming text.

How it's work is simple:

- Any blank document will be set as UTF-8 and saved as UTF-8.

- If you don't want it to be UTF-8, select another encoding before to
write any text.

- When a given document is opened, if it's in UTF-8 it will be
recognized and set as UTF-8.

- If it's not valid UTF-8 it will be set to the best match ISO-####
code.

- If you want to write JIS (japanese) or Hangul you must forze to DBCS
on each document you'll open and on each new document.

This entry should be called "Forze encoding".

Right now cssed will handle UTF-8/ISO text transparently and DBCS
forzed.

The default file encoding is UTF-8.

To forze ISO code as UTF-8 will result in bad rendering in the display,
and the same if is forzed UTF-8 code to ISO.

Just try it:
1.- Create a blank document, use accenter characters and save it. The
use "file" to know the encoding on disk, it should tell you UTF-8 as
it's the default.=20

Something like:
$file test
test: UTF-8 Unicode text

2.-  Create a blank document,forze to default, use accenter characters
and save it. Then use file again and it should tell you the encoding is
ISO-bhla_bhla.=20

Something like:
$ file test
test: ISO-8859 text

3.- Open an UTF-8 file, change the text and save it again.=20
It should be in UTF-8.

4.- Open an ISO-#### file, change the text and save it again.
It should be ISO-######.

Take into account that if you take out all accented characters in the
text, it will be recogniced always as ASCII by file.

It will not convert between encodings. If you opens UTF-8 and forzes
ISO, It will end in bad rendering.

Does it helped or still confused ??
--=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