On Mon, 7 May 2007, Bo Peng wrote:
Ok. I thought it was only one other person that would need to open/edit
the .lyx-file.
A few people will edit the file but the file will be released to public.
I do not expect many (any?) people to open the file with lyx because the
PDF version will also
Ok. I thought it was only one other person that would need to open/edit
the .lyx-file.
A few people will edit the file but the file will be released to
public. I do not expect many (any?) people to open the file with lyx
because the PDF version will also be released. It does not make sense
to re
On Mon, 7 May 2007, Bo Peng wrote:
> The file format problem would not be solved by a branch.
Why not? (I don't understand)
Because the reference manual I produce can not be opened by others
except for a few people in my own group GUI, validations stuff are
superficial, file format is
> The file format problem would not be solved by a branch.
Why not? (I don't understand)
Because the reference manual I produce can not be opened by others
except for a few people in my own group GUI, validations stuff are
superficial, file format is the key of this debate.
Bo
On Mon, 7 May 2007, Bo Peng wrote:
Could Bo and his colleague work using a LyX that's compiled from a branch,
where the split from trunk is done just after 1.5.0 has been released?
The file format problem would not be solved by a branch.
Why not? (I don't understand) The way I envision it
Could Bo and his colleague work using a LyX that's compiled from a branch,
where the split from trunk is done just after 1.5.0 has been released?
The file format problem would not be solved by a branch. All I need is
a placeholder in 1.5.0 to read \inset listings, \lstinputlisting and
\lstparam
On Mon, 7 May 2007, Jean-Marc Lasgouttes wrote:
Jürgen> But apart from that (and independent from the specific patch and
Jürgen> feature), I just think it's long overdue to stop putting things
Jürgen> in 1.5 that are not strictly fixing bugs.
+10
Could Bo and his colleague work using a LyX
> "Jürgen" == Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
Jürgen> The risk it that we implement it in a way that is not
Jürgen> thoroughly pondered (because of lacking time). Georg already
Jürgen> pointed out that he sees several things that have to be
Jürgen> thought about carefully with t
On technical grounds I think that another option is to have:
language=Python
float
I will explain what I have done in another thread.
Bo
On Saturday 05 May 2007 16:43:47 Bo Peng wrote:
> The only solution I can think of is the HTML way, where special
> characters are encoded in &1023; etc for storage and transportation.
> Does anyone know how to implement this?
On technical grounds I think that another option is to have:
language=
The only problem I can see with file format is that listings can have
a large number of parameters and lexer may not be able to read the
whole string. Right now, I save/load/transport parameter strings like
language=Python,float
in the form of
language=Python!float
but ! may (I am not sure) be
> The risk it that we implement it in a way that is not thoroughly pondered
> (because of lacking time). Georg already pointed out that he sees several
> things that have to be thought about carefully with the listings
> implementation.
It would be much easier to 'ponder' with this patch. Please
Jürgen Spitzmüller wrote:
> Peter Kümmel wrote:
>> If you are not a developer and you need listings you throw away LyX,
>
Ah, I forgot, one could use ERTs.
> How do you substantiate that statement? What data do you have about users
> that
> have thrown away LyX for exactly that reason?
>
Ha
Peter Kümmel wrote:
> If you are not a developer and you need listings you throw away LyX,
How do you substantiate that statement? What data do you have about users that
have thrown away LyX for exactly that reason?
> and when you are developer but you don't need it then you are not interested
Jürgen Spitzmüller wrote:
> Peter Kümmel wrote:
>> I agree with Bo that we shouldn't wait until 1.6
>> with the support of listings, it's so essential
>> when writing documents with code listings.
>>
>> Especially many of the LyX users are familiarly with
>> a programming language and will maybe us
Peter Kümmel wrote:
> I agree with Bo that we shouldn't wait until 1.6
> with the support of listings, it's so essential
> when writing documents with code listings.
>
> Especially many of the LyX users are familiarly with
> a programming language and will maybe use listings
> for their documents.
I agree with Bo that we shouldn't wait until 1.6
with the support of listings, it's so essential
when writing documents with code listings.
Especially many of the LyX users are familiarly with
a programming language and will maybe use listings
for their documents.
When we put in Bo's patch now we
17 matches
Mail list logo
