User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13)
            Gecko/20101230 Lanikai/3.1.7
MIME-Version: 1.0
References: <201101030052.p030qEUM014652@freefriends.org>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig13AFDC5608CD8F25C81D838E"
Message-ID:  <4D219F24.1030609@gmx.de>
Date:         Mon, 3 Jan 2011 11:04:20 +0100
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@listserv.uni-heidelberg.de>
Sender: Mailing list for the LaTeX3 project <LATEX-L@listserv.uni-heidelberg.de>
From: Arno Trautmann <Arno.Trautmann@GMX.DE>
Subject: Re: xparse: read arg until EOL
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <201101030052.p030qEUM014652@freefriends.org>
Precedence: list
Status: R

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig13AFDC5608CD8F25C81D838E
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Karl Berry wrote:
>     I just thought it might be good to have an argument type that reads=
 an
>     argument until the end of line. That would be a special version of =
the u
>     type, I think, but the normal user will not be able to specify it t=
hat
>     way.=20
>     Any comments?
>=20
> Based on my experience with Texinfo, my comment is that robust parsing
> of arguments delimited by end-of-line is essentially impossible.  I
> fully agree with Joseph: I wouldn't go there.=20

What about an non-robust solution? ;)
No, seriously: Would it be aceptable (generally spoken) to offer
non-robust solutions istead of no solution at all?

>     (Also I'm not sure about different line endings in *nix and Windows=
=2E)
>=20
> That isn't the problem.  The engines have always unified the various
> platform-specific line endings to \endlinechar (otherwise TeX
> portability would be a nonstarter).  The problem is distinguishing eol
> from space (gets converted very early in processing), handling the
> contexts of active eol vs. normal eol, doing all this inside other
> macros, etc. ... it's a steep and slippery slope.
>=20
> If you want to convert from TeX to OOo, my suggestion is to use an
> external program.  An eol-delimited macro will hardly be a panacea for
> that job, as you yourself pointed out.

Yes, but I wanted it just for this very special thing. I hoped that it
would be possible with some TeX-trickery or so =E2=80=A6
Maybe luaTeX could help here?
With external programs I did not succeed in converting a single
document, but that is all my fault.

Thanks for your answers,
Arno


--------------enig13AFDC5608CD8F25C81D838E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0hnyUACgkQcYXUw/rerZ40TQCgxaYdnwphGu/SMYD8uFFtOl1Z
rEsAoJphT7RTaIGXvZiXgd0yERypMEa0
=YnW7
-----END PGP SIGNATURE-----

--------------enig13AFDC5608CD8F25C81D838E--