Re: [cssed-devel] New release

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

On Wed, 2005-02-09 at 17:51, Mich=C3=A8le Garoche wrote:
> Le 9 f=C3=A9vr. 2005, =C3=A0 17:41, Iago Rubio a =C3=A9crit :
>=20
> >>>> Severe problems when a document is not utf-8 encoded.
> > Could you please elaborate it a little and/or send me the file ?
> >
> > The UTF conversion/detection code have not changed from last release.
> Maybe not the detection, but the handling probably since I've never=20
> seen this behaviour before.

I was not even touched a single line of code.

> It's hard to explain because I should make a movie to explain what=20
> happens:
>=20
> This message repeats constantly in console=3D
> ** (cssed:19170): WARNING **: Invalid UTF8 string passed to=20
> pango_layout_set_text()
> The line is cut and cssed tries constantly to redraw it.
> If I move the cursor, some characters of the line are inserted in a new=20
> line below the given line, or removed, well cssed is kind of movie=20
> player.

I've seen this in some bogus files with characters that did not match
any encoding but never in "normal" files.

With normal I mean, written with a keyboard, as the weird behaviour on
the files I mentioned, was caused by characters completly out of
keyboard's range.

Have you tried to forze other encoding ?

> Here's the file:

Will take a look at this, but at first sight it seems ISO-8859, if it's
not well rendered with "Default" encoding, then we've got a problem.

ITOH it's passes g_utf8_validate checks, not being utf8.
--=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