rgheck schrieb:
What do you mean, update the other docs?
I usually copy new stuff to the other language versions. Then either the translators automatically
translate it when they contribute the next time thing to LyX or I inform them when there are enough
changes.
regards Uwe
Uwe Stöhr wrote:
Hello Pavel,
I requested that Georg used change tracking in his commit so that the
other language versions of Customization can be updated accordingly.
When you accept changes, please also update the other doc files
accordingly. (Customization is currently only for German and
David Mertens wrote:
0) LyX is written in C++. That much is clear from the website, and the
Developer Resources seem to have lots of guidance for learning good C++
style.
See the files in development/coding/...once you get the source.
1) In what toolkit is LyX written? It appears to be Q
Hello Pavel,
I requested that Georg used change tracking in his commit so that the other language versions of
Customization can be updated accordingly. When you accept changes, please also update the other doc
files accordingly. (Customization is currently only for German and Spanish under acti
Greetings All -
I'd say I write some pretty solid C++ code, but I haven't the first clue
where to start if I wanted to play with the LyX code, let alone contribute
to the project. I looked around the website but I couldn't find what I was
looking for. Links to any of the following information wo
Georg Baum writes:
> Jean-Marc Lasgouttes wrote:
>
>> It looks pretty good. Only question: why is readWithoutConv needed?
>
> It prevents an endless loop if layout2layout does not produce the desired
> format. In my case this happened because I forgot to update the
> layout2layout version number,
Jean-Marc Lasgouttes wrote:
> It looks pretty good. Only question: why is readWithoutConv needed?
It prevents an endless loop if layout2layout does not produce the desired
format. In my case this happened because I forgot to update the
layout2layout version number, but it could also happen if lay
Hi developers,
My documents have a large number of labels and I find myself
scrolling often to try to locate items to cross-reference. I thought a
feature that short-lists the labels based on the string entered into the
reference line edit (referenceED widget) would be useful.
I now hav
Georg Baum writes:
> The former was the solution (I just passed a boolean function argument). I
> did not think of this before because LaTeXFeatures::useBabel() led me on a
> side track.
>
> Is the attached patch OK? It basically implements your suggestions, but uses
> different names for the two
Vincent van Ravesteijn writes:
> - Labels of Insets with a background color defined get this color as
> their label (like Note is now, this can be easily recognized),
> - Labels of Insets with no background color get the default value.
In the case of Notes, I find the yellow-on-grey quite unreada
10 matches
Mail list logo
