Making a translation: po-file testing
Hi, LyXers I have an improved version of es.po ready for testing. I have downloaded, configured, compiled and installed lyx-1.1.6cvs. As I don't have the slightest clue on how to incorporate my corrections, I have overwritten the previous es.po in the po directory with my own. I have recompiled and reinstalled. No trace of my po file when starting LyX: it seems to be using the old one. Please note that I have been configuring with the flags --with-lyxname=lyx-1.1.6cvs --prefix=/usr/local Anybody knows what to do? I would like to start committing my translation files asap, but I need to do some testing, thanks to all, -- Álvaro Tejero Cantero p42.org
Unintended feature in Math-mode (RFF!!)
Hi, LyXers I have been using LyX now for more than a year and a half on an everyday basis. I feel that some little subtle things could be improved in math mode, and today (after some reflections) I have decided to share my views with you regarding one particular aspect. When you are writing in math mode you use attributes such as bold to convey information. Many people, as it is my case, use bold letters to mean that the particular mathematical object has a vectorial nature. There is no relationship between the vectorial nature of the letter a and it's subscript. BUT when one continues writing in subscript-level, it maintains the bold attribute given to the "parent" character. In a vast majority of cases this is absolutely unintended, and slows down mathematical writing a lot (i.e. going back to make the subscript again "normal"). I wish this behavior (appearing up to LyX 1.1.6cvs) was eliminated or, if someone has something in favor of it, at least user-selectable. Greets, -- Álvaro Tejero Cantero p42.org
New tabular inset in 1.1.6cvs
Hello, The new tabular inset format produces tables that cannot be read with =1.1.4. (I didn't test with 1.1.5). Is that going to be fixed? -- Álvaro Tejero Cantero p42.org
Re: New tabular inset in 1.1.6cvs
On Sun, 22 Oct 2000, Alvaro Tejero Cantero wrote: Hello, The new tabular inset format produces tables that cannot be read with =1.1.4. (I didn't test with 1.1.5). Is that going to be fixed? No. You have to break some eggs to make an omelette. And a very yummy omelette it is too. We don't guarantee upward-compatibility only backward-compatibility. Or vice versa depending on your perspective. Anyway. It's not broken. The format has changed that's all. This is deliberate. We have never guaranteed that the LyX format will never change. We have however guaranteed that your old files will be read by a newer version (up to a point -- then you need an intermediate version to convert really old files to a newer format). Allan. (ARRae)
Fwd: Re: New tabular inset in 1.1.6cvs
The new tabular inset format produces tables that cannot be read with =1.1.4. (I didn't test with 1.1.5). Is that going to be fixed? | No. | We don't guarantee upward-compatibility only backward-compatibility. | Or vice versa depending on your perspective. Yes. Perhaps I was too concise. I simply wanted to know, I was not criticizing the policy (to which indeed I agree!). So excuse me if my message sounded harsh. Best, -- Álvaro Tejero Cantero p42.org
Re: Fwd: Re: New tabular inset in 1.1.6cvs
On Sun, 22 Oct 2000, Alvaro Tejero Cantero wrote: The new tabular inset format produces tables that cannot be read with =1.1.4. (I didn't test with 1.1.5). Is that going to be fixed? | No. | We don't guarantee upward-compatibility only backward-compatibility. | Or vice versa depending on your perspective. Yes. Perhaps I was too concise. I simply wanted to know, I was not criticizing the policy (to which indeed I agree!). So excuse me if my message sounded harsh. It's 3:32am here and I'm just a little tired so please excuse my long winded reply. Allan. (ARRae)
Making a translation: po-file testing
Hi, LyXers I have an improved version of es.po ready for testing. I have downloaded, configured, compiled and installed lyx-1.1.6cvs. As I don't have the slightest clue on how to incorporate my corrections, I have overwritten the previous es.po in the po directory with my own. I have recompiled and reinstalled. No trace of my po file when starting LyX: it seems to be using the old one. Please note that I have been configuring with the flags --with-lyxname=lyx-1.1.6cvs --prefix=/usr/local Anybody knows what to do? I would like to start committing my translation files asap, but I need to do some testing, thanks to all, -- Álvaro Tejero Cantero p42.org
Unintended feature in Math-mode (RFF!!)
Hi, LyXers I have been using LyX now for more than a year and a half on an everyday basis. I feel that some little subtle things could be improved in math mode, and today (after some reflections) I have decided to share my views with you regarding one particular aspect. When you are writing in math mode you use attributes such as bold to convey information. Many people, as it is my case, use bold letters to mean that the particular mathematical object has a vectorial nature. There is no relationship between the vectorial nature of the letter a and it's subscript. BUT when one continues writing in subscript-level, it maintains the bold attribute given to the "parent" character. In a vast majority of cases this is absolutely unintended, and slows down mathematical writing a lot (i.e. going back to make the subscript again "normal"). I wish this behavior (appearing up to LyX 1.1.6cvs) was eliminated or, if someone has something in favor of it, at least user-selectable. Greets, -- Álvaro Tejero Cantero p42.org
New tabular inset in 1.1.6cvs
Hello, The new tabular inset format produces tables that cannot be read with =1.1.4. (I didn't test with 1.1.5). Is that going to be fixed? -- Álvaro Tejero Cantero p42.org
Re: New tabular inset in 1.1.6cvs
On Sun, 22 Oct 2000, Alvaro Tejero Cantero wrote: Hello, The new tabular inset format produces tables that cannot be read with =1.1.4. (I didn't test with 1.1.5). Is that going to be fixed? No. You have to break some eggs to make an omelette. And a very yummy omelette it is too. We don't guarantee upward-compatibility only backward-compatibility. Or vice versa depending on your perspective. Anyway. It's not broken. The format has changed that's all. This is deliberate. We have never guaranteed that the LyX format will never change. We have however guaranteed that your old files will be read by a newer version (up to a point -- then you need an intermediate version to convert really old files to a newer format). Allan. (ARRae)
Fwd: Re: New tabular inset in 1.1.6cvs
The new tabular inset format produces tables that cannot be read with =1.1.4. (I didn't test with 1.1.5). Is that going to be fixed? | No. | We don't guarantee upward-compatibility only backward-compatibility. | Or vice versa depending on your perspective. Yes. Perhaps I was too concise. I simply wanted to know, I was not criticizing the policy (to which indeed I agree!). So excuse me if my message sounded harsh. Best, -- Álvaro Tejero Cantero p42.org
Re: Fwd: Re: New tabular inset in 1.1.6cvs
On Sun, 22 Oct 2000, Alvaro Tejero Cantero wrote: The new tabular inset format produces tables that cannot be read with =1.1.4. (I didn't test with 1.1.5). Is that going to be fixed? | No. | We don't guarantee upward-compatibility only backward-compatibility. | Or vice versa depending on your perspective. Yes. Perhaps I was too concise. I simply wanted to know, I was not criticizing the policy (to which indeed I agree!). So excuse me if my message sounded harsh. It's 3:32am here and I'm just a little tired so please excuse my long winded reply. Allan. (ARRae)
Making a translation: po-file testing
Hi, LyXers I have an improved version of es.po ready for testing. I have downloaded, configured, compiled and installed lyx-1.1.6cvs. As I don't have the slightest clue on how to incorporate my corrections, I have overwritten the previous es.po in the po directory with my own. I have recompiled and reinstalled. No trace of my po file when starting LyX: it seems to be using the old one. Please note that I have been configuring with the flags --with-lyxname=lyx-1.1.6cvs --prefix=/usr/local Anybody knows what to do? I would like to start committing my translation files asap, but I need to do some testing, thanks to all, -- Álvaro Tejero Cantero p42.org
Unintended feature in Math-mode (RFF!!)
Hi, LyXers I have been using LyX now for more than a year and a half on an everyday basis. I feel that some little subtle things could be improved in math mode, and today (after some reflections) I have decided to share my views with you regarding one particular aspect. When you are writing in math mode you use attributes such as bold to convey information. Many people, as it is my case, use bold letters to mean that the particular mathematical object has a vectorial nature. There is no relationship between the vectorial nature of the letter a and it's subscript. BUT when one continues writing in subscript-level, it maintains the bold attribute given to the "parent" character. In a vast majority of cases this is absolutely unintended, and slows down mathematical writing a lot (i.e. going back to make the subscript again "normal"). I wish this behavior (appearing up to LyX 1.1.6cvs) was eliminated or, if someone has something in favor of it, at least user-selectable. Greets, -- Álvaro Tejero Cantero p42.org
New tabular inset in 1.1.6cvs
Hello, The new tabular inset format produces tables that cannot be read with <=1.1.4. (I didn't test with 1.1.5). Is that going to be fixed? -- Álvaro Tejero Cantero p42.org
Re: New tabular inset in 1.1.6cvs
On Sun, 22 Oct 2000, Alvaro Tejero Cantero wrote: > Hello, > > The new tabular inset format produces tables that cannot be read with > <=1.1.4. (I didn't test with 1.1.5). Is that going to be fixed? No. You have to break some eggs to make an omelette. And a very yummy omelette it is too. We don't guarantee upward-compatibility only backward-compatibility. Or vice versa depending on your perspective. Anyway. It's not broken. The format has changed that's all. This is deliberate. We have never guaranteed that the LyX format will never change. We have however guaranteed that your old files will be read by a newer version (up to a point -- then you need an intermediate version to convert really old files to a newer format). Allan. (ARRae)
Fwd: Re: New tabular inset in 1.1.6cvs
> > The new tabular inset format produces tables that cannot be read > with <=1.1.4. (I didn't test with 1.1.5). Is that going to be > fixed? | No. | We don't guarantee upward-compatibility only backward-compatibility. | Or vice versa depending on your perspective. Yes. Perhaps I was too concise. I simply wanted to know, I was not criticizing the policy (to which indeed I agree!). So excuse me if my message sounded harsh. Best, -- Álvaro Tejero Cantero p42.org
Re: Fwd: Re: New tabular inset in 1.1.6cvs
On Sun, 22 Oct 2000, Alvaro Tejero Cantero wrote: > > > > > The new tabular inset format produces tables that cannot be read > > with <=1.1.4. (I didn't test with 1.1.5). Is that going to be > > fixed? > > | No. > > | We don't guarantee upward-compatibility only backward-compatibility. > | Or vice versa depending on your perspective. > > Yes. Perhaps I was too concise. I simply wanted to know, I was not > criticizing the policy (to which indeed I agree!). So excuse me if my > message sounded harsh. It's 3:32am here and I'm just a little tired so please excuse my long winded reply. Allan. (ARRae)
