On Saturday 01 September 2007 15:30:47 Jean-Marc Lasgouttes wrote:
> José Matos <[EMAIL PROTECTED]> writes:
> >> Because this feature more or less duplicates with embedding, and if we
> >> decide to go with .lyz for lyx bundle format, .lyx will always be a
> >> plain text file.
> >
> > I think that the dos time is gone long ago and a lyx suffix should
> > stand for lyx files no matter what the internal format used.
>
> You are forcing for no good reason people to use a complicated python
> binding (you know, the-one-that-nobody-ever-saw) to make the simplest
> modification on a LyX file, but you are not telling what the reason
> is.
No I am not. If people do not use compress that will not show up.
I think that we can distribute a set of tools to work outline with zip and
compressed files. It would be nice, for example, that I could extract all the
files of the embedded package into a directory. Do the changes I want to and
then ask to the same script to wrap up the directory. Do you think this would
be useful?
> Unix is about simple and predictable things, and I think that LyX
> should keep that. I do not know of _any_ format that may or may not be
> compressed.
> Telling users "you are not supposed to understand how it works, use
> our sort-of-proprietary bindings instead" is not the correct message.
> I often read people praising the "simple, text only" format of LyX,
> and we seem to try to use any possible mean to make .lyx file
> impossible to handle with the usual swiss army knife tools.
>
> > The question is that anyone that changes the lyx file directly knows
> > enough to know what to do. If (s)he does not know how to use file or any
> > other mean to determine the file type then it is better not to do it.
>
> At lot of people who do not understand the .lyx format, appreciate to
> be able to change \alpha to \beta throughout the file.
That is orthogonal to our discussion. If people do not use compress or
embedded they will still be able to do that as they did before.
If they use one of those features what I am saying is that they should know
enough to know what those options implies. And with the set of tools that I
am proposing above they would still be able to use in a normal way.
> JMarc
--
José Abílio
