Re: Parser error of readme.xds in conglomerate 0.9.1

On Wed, 2005-06-22 at 20:39 +0200, Mich=C3=A8le Garoche wrote:
> Le 22 juin 2005 =C3=A0 16:53, David Malcolm a =C3=A9crit :
>=20
> > On Wed, 2005-06-22 at 15:02 +0200, Mich=C3=A8le Garoche wrote:
> >
> >> Le 22 juin 2005 =C3=A0 14:16, Geert Stappers a =C3=A9crit :
> >>
> >>
> >>> On Wed, Jun 22, 2005 at 01:56:14PM +0200, Mich=C3=A8le Garoche wrot=
e:
> >>>    <snip/>
> >>>
> >>>
> >>>> 3 - Cure
> >>>>
> >>>> Remove the xml:lang=3D"en" part of <_description> on line 5 in
> >>>> dispspecs/readme.xds.in
> >>>>
> >>>>
> >>>
> >>>
> >>> Do you mean
> >>>
> >>> --- dispspecs/readme.xds.in     29 Dec 2004 17:30:24 -0000      1.1
> >>> +++ dispspecs/readme.xds.in     22 Jun 2005 12:10:04 -0000
> >>> @@ -2,7 +2,7 @@
> >>>  <dispspec>
> >>>         <metadata>
> >>>                 <_name>Experimental "readme" format</_name>
> >>> -               <_description xml:lang=3D"en">This is a document ty=
pe
> >>> associated with the "readme" file distributed with the
> >>> initial prototype of Conglomerate.</_description>
> >>> +               <_description>This is a document type associated
> >>> with the "readme" file distributed with the initial prototype of
> >>> Conglomerate.</_description>
> >>>         </metadata>
> >>>         <document-models>
> >>>         </document-models>
> >>>
> >>>
> >>> ?
> >>>
> >>>
> >> Yes, exactly, Geerts.
> >>
> >
> > Thanks.  Do you have CVS access yet?
> Yes, I had it yesterday, thanks. But I need to get in touch with the =20
> coordinator of gnome French translation and with Geerts also, to know =20
> how I should use it. I have not succeeded today in doing this, That's =20
> why I send just a mail so that you know there is a little problem here.
>=20
> > Feel free to fix this in CVS (with
> > a ChangeLog entry)
> Can it be delayed a bit or not. If it can be delayed, I'll do it =20
> within the week. Because it has also incidence on the po files =20
> (namely only fr.po and en-ca.po files), and that I should learn how =20
> to do it properly with CVS access.
>=20
> > Note that a patch together with a justification is probably the =20
> > best way
> > to discuss this.
> Sure, as soon as I put my cvs tree in order, I'll do it this way.

Sounds good.