On Mon, Sep 11, 2006 at 11:50:31AM +0100, Ozgur Ugras BARAN wrote:
> It is so rare that, It is fantastic not to be wrong. :))
>
> then it should work well for the case \command[][]{}
>
> any comments on backporting this feature to lyx 1.4.x ?? it shouldn't
> take too much time for me..
Have it
On Mon, Sep 11, 2006 at 09:19:14AM +0100, Ozgur Ugras BARAN wrote:
> Therefore the command and its parameters are isolated from anything else,
> including another {}. Am I wrong?? (probably I am :) )
Erm. No. I was probably thinking about tex2lyx or such.
Should be pretty safe given this explan
OK.. I'll start next week, but I am not sure when I can finish. It can take
time depending on my free time.
I am very glad that you will handle lyx2lyx conversion :)
he necessary lyx2lyx conversion methods, and we put it in.
> Then we put the nomencl support in.
> This order has the advantage that the lyx2lyx changes will be a bit easier.
FWIW I agree with Georg on all points above.
> Georg
--
José Abílio
ceed like this:
You change InsetCommandParams to support a name,value pair interface for
parameters and send it to the list for review. When it is OK you can change
the existing insets to use the new interface. After that Jose or I create
the necessary lyx2lyx conversion methods, and we put it i
Well, I didn't like the way to store LaTeX commands, either. I am not
sure that I am brave enough to (or capable of) develop that part, but
I can give it a try.
However, in my incredibly humble opinion, the syntax should be based
on a markup language (preferably XML), which is planned for lyx-1.6
Ozgur Ugras BARAN wrote:
> It is so rare that, It is fantastic not to be wrong. :))
>
> then it should work well for the case \command[][]{}
The fact that InsetCommand stores its parameters in LaTeX-like syntax in LyX
files is a historical mistake, so I would rather avoid to extend this even
fu
It is so rare that, It is fantastic not to be wrong. :))
then it should work well for the case \command[][]{}
any comments on backporting this feature to lyx 1.4.x ?? it shouldn't
take too much time for me..
On 9/11/06, Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> "Ozgur" == Ozgur Ug
> "Ozgur" == Ozgur Ugras BARAN <[EMAIL PROTECTED]> writes:
Ozgur> \begin_inset LatexCommand \command[]{}{} \end_inset
Ozgur> Therefore the command and its parameters are isolated from
Ozgur> anything else, including another {}. Am I wrong?? (probably I
Ozgur> am :) )
No you are not!
JMarc
On 9/8/06, Andre Poenitz <[EMAIL PROTECTED]> wrote:
On Fri, Sep 08, 2006 at 03:24:56PM +0100, Ozgur Ugras BARAN wrote:
> and last of all, I developed this against the lyx 1.5.x. However, (if
> insetCommandParams mod. is correct) there is no reason not to add this
> functionality in lyx 1.4.x
>
On Fri, Sep 08, 2006 at 03:24:56PM +0100, Ozgur Ugras BARAN wrote:
> and last of all, I developed this against the lyx 1.5.x. However, (if
> insetCommandParams mod. is correct) there is no reason not to add this
> functionality in lyx 1.4.x
>
> with my kindest regards,
As usual: Things about whic
Dear all,
You can find an implementation of nomencl support in the attachments.
there are two diffs and the tgz file for the new files.
I basically developed everything deriving from the index counterpart.
Files in the directory frontend should be OK ( except the silly
constructors), since they
12 matches
Mail list logo