Hi Liviu,
I agree with all your suggestions, except for the proposition. We use
"Propozitie'' for proposition in mathematics. Feel free to make these
changes. I think it is a good idea to apply your patch to replace the
characters you mentioned in a different email using the correct encoding.
Mar
Liviu Andronic wrote:
> I'm not sure how to do this, and I can no longer find the localization
> test. Additionally,
its still there if you have svn checkout (lib/examples/localization_test.lyx)
attached is layouttranslation file generated from your file to be put in your
tree.
>it was complain
On 26/04/2011 7:28 PM, Vincent van Ravesteijn wrote:
On 26-4-2011 20:14, Julien Rioux wrote:
On 26/04/2011 4:59 AM, Vincent van Ravesteijn wrote:
It would be possible to use svn/git together for one release cycle. I've
been maintaining a git repo parallel to the svn repo for the last few months
On 26-4-2011 20:14, Julien Rioux wrote:
> On 26/04/2011 4:59 AM, Vincent van Ravesteijn wrote:
>> It would be possible to use svn/git together for one release cycle. I've
>> been maintaining a git repo parallel to the svn repo for the last few months.
>> However, everyone needs to become used to us
Liviu Andronic wrote:
> Pavel
> A bit off-topic but localization-related, I propose a monstrous patch
> that replaces all occurrences of incorrect (for Romanian) chars with
> cedilla below, with correct chars with comma below. Cf [1] and #7348.
> It's a big change, so it would be best if someone co
Hey Marius
On Tue, Apr 26, 2011 at 10:03 PM, Pavel Sanda wrote:
> we still miss review of math layout strings for many languages
> which were updated not so long ago - in particular:
>
I'm playing with the Romanian strings for [1] and I'd like your input
on some changes I propose:
"Acknowledgemen
Diego Queiroz wrote:
> Yeah. I would love to.
ok, i'll write you privately.
> Since I joined the mailling list I am receiving some mails of portuguese
> speakers asking about things I've done (as the ABNT layout, for example).
> I think a portuguese mailing list and a site would bring more people
On Wed, Apr 27, 2011 at 12:11 AM, Julien Rioux
wrote:
> On 26/04/2011 5:57 PM, Liviu Andronic wrote:
>>
>> On Tue, Apr 26, 2011 at 11:53 PM, Pavel Sanda wrote:
>>>
>>> anyway letting this untranslated in english version is not
>>> big deal. maybe the specific translation even don't exists
>>> in
Richard Heck wrote:
> On 04/26/2011 06:03 PM, Pavel Sanda wrote:
>> Richard Heck wrote:
>>> By the way, should we be setting x_target_ here once we have calculated
>>> it?
>>> I do not understand this code very well.
>> i can't comment on the code either, but is there some estimate how
>> risky is
Liviu Andronic wrote:
> russian,
> I double-checked the translations for ru and they're mostly OK. I have
> a slight doubt on
> "Acknowledgement" "??"
>
> which is similar to the French:
> "Acknowledgement" "Remerciements"
>
> I have a feeling that it should be in plural:
On 26/04/2011 5:57 PM, Liviu Andronic wrote:
On Tue, Apr 26, 2011 at 11:53 PM, Pavel Sanda wrote:
anyway letting this untranslated in english version is not
big deal. maybe the specific translation even don't exists
in many languages.
Can I assume that in the absence of an obvious translation
> Probably best to use the default icon set.
Sure.
I'm taking screenshots of LyX defaults, I mean, without any kind of
customization (menu position, toolbars, etc).
The main difference is that I am using Windows 7 and the PDF Viewer is
TeXworks. But that's not a big deal...
Pavel,
I already did
On Tue, Apr 26, 2011 at 10:03 PM, Pavel Sanda wrote:
> we still miss review of math layout strings for many languages
> which were updated not so long ago - in particular:
>
>
> arabic, chinese, russian,
>
I double-checked the translations for ru and they're mostly OK. I have
a slight doubt on
"Ac
Yeah. I would love to.
Since I joined the mailling list I am receiving some mails of portuguese
speakers asking about things I've done (as the ABNT layout, for example).
I think a portuguese mailing list and a site would bring more people to the
LyX community, and of course, more volunteers.
So i
On 04/26/2011 06:03 PM, Pavel Sanda wrote:
Richard Heck wrote:
By the way, should we be setting x_target_ here once we have calculated it?
I do not understand this code very well.
i can't comment on the code either, but is there some estimate how
risky is this patch wrt to new regressions?
I t
Richard Heck wrote:
> By the way, should we be setting x_target_ here once we have calculated it?
> I do not understand this code very well.
i can't comment on the code either, but is there some estimate how
risky is this patch wrt to new regressions?
if yes then it might be better to postpone t
On Tue, Apr 26, 2011 at 11:53 PM, Pavel Sanda wrote:
> anyway letting this untranslated in english version is not
> big deal. maybe the specific translation even don't exists
> in many languages.
>
Can I assume that in the absence of an obvious translation, that the
translation for 'table' is the
Liviu Andronic wrote:
> Hello
> Is
> "List of Tableaux" "Liste des tableaux (TO)"
>
> and
> "Tableau" "Tableau"
>
> in the sense of "table" [1], you know, the thingy with rows and cols?
> Are you absolutely sure that "Tableau" is the right term for the
> context? I ask because my dictionary does
Hello
Is
"List of Tableaux" "Liste des tableaux (TO)"
and
"Tableau" "Tableau"
in the sense of "table" [1], you know, the thingy with rows and cols?
Are you absolutely sure that "Tableau" is the right term for the
context? I ask because my dictionary doesn't give me a very
mathematical descriptio
On 26/04/2011 11:23 AM, Diego Queiroz wrote:
Isn't interesting to update the Graphical Tour of LyX?
http://www.lyx.org/Walkthrough
It is mentioned in splash.lyx document but there is a long time it isn't
updated...
I think it should be updated with the final release of LyX 2.0.0.
---
Diego Q
On 26/04/2011 1:51 PM, venom00 wrote:
Shouldn't we start with 2.1 first?
Yes.
This thread is growing fast and I don't know if this is the right place for
features, but I've been thinking of some features it would be nice to have in
LyX:
- scripting: it would be great to allow community to con
On 26.04.2011 22:36, venom00 wrote:
- scripting: it would be great to allow community to
contribute with plugins,
maybe for some specific LaTeX packages using a simple
language as Python
I propose Lua, currently I write a easy-to-use and maintain
C++ binding.
Don't know, Python has a lot of
On 26/04/2011 3:15 PM, Liviu Andronic wrote:
I don't think that the average user is one bit aware of this. And if
there is no file format change to care about, the better.
Liviu
It's described here
http://www.lyx.org/VersioningSystem
Anyway, separating file-format development and non-file-f
> > - scripting: it would be great to allow community to
> contribute with plugins,
> > maybe for some specific LaTeX packages using a simple
> language as Python
>
> I propose Lua, currently I write a easy-to-use and maintain
> C++ binding.
Don't know, Python has a lot of libraries (also for
Abdelrazak Younes wrote:
> On 04/26/2011 06:48 PM, Pavel Sanda wrote:
>> Abdelrazak Younes wrote:
>>> we are always seeing new
>>> developers around new releases; 2.0 is no exception.
>> this looks as interesting insight, the more that i do not recognize that
>> ;)
>> isn't it just illusion made b
Pavel Sanda wrote:
> i'm waiting for a few last localization contributions but apart
> from it we are done. either wed or thu evening i'll prepare tarballs.
due to the unexpected number of unannounced last-minute .po updates and math
layout fixes (thanks!) i decided to set down deadline for .po &
I hereby grant permission to license my contributions to LyX under the
Gnu General Public License, version 2 or later.
Marcus Kriele
To date I have only fixed some sv* layout files (Bug 7301) which is targeted
for 2.0.1.
To all whom it may concern,
When installing LyX on a Windows machine with a python 3 distribution already
in place, LyX may fail to initialize since the python scripts are incompatible.
To resolve this I'm using the following batch file (LyX.bat) to set the
appropriate environment variable:
@
On Tue, Apr 26, 2011 at 7:06 PM, Pavel Sanda wrote:
>> It will be ok if I use LyX 2.0.0 RC3, right?
>
> sure
>
Probably best to use the default icon set.
Liviu
On 2011-4-26 14:58 , Richard Heck wrote:
On 04/26/2011 02:09 PM, Marcus Kriele wrote:
I have found that LyXHTML chokes on the table of contents. If the
table of contents is removed in my example files then LyXHTML
produces valid HTML files that can be read by Firefox 4.
Hmm. Well, I should
On Tue, Apr 26, 2011 at 6:08 PM, Vincent van Ravesteijn wrote:
>> I'd drop the stunning releases and increment the major version
>> at each format change, in this case. Too many numbers.
>
> Wouldn't this be confusing for the user that suddenly 2.0/2.1/2.2
> have the same file format. So he can ea
On 26/04/2011 2:42 PM, Peter Kümmel wrote:
Opinions ?
My opinion is that the best way to use git would be very short-lived
branches. I wouldn't mind doing it this way: "Hey guys, here's a pull
request that fixes bug #1234, can you try it out and push it in?"
In other words, the same as "Hey
On 04/26/2011 02:09 PM, Marcus Kriele wrote:
I have produced a new version of the layout files, the test files, and
the templates. It has been posted to the bug tracker.
This new version is now fully backward compatible. However, the style
abstract now behaves differently as the current impl
Peter Kümmel wrote:
> And one additional advantage of working on one branch is the ability to
> "communicate" over this channel, everyone could jump in without switching
> the branch.
yep, if there is something unusable about git branches its online switching
between them.
single change in some h
On 26.04.2011 20:14, Julien Rioux wrote:
On 26/04/2011 4:59 AM, Vincent van Ravesteijn wrote:
It would be possible to use svn/git together for one release cycle. I've
been maintaining a git repo parallel to the svn repo for the last few months.
However, everyone needs to become used to using git
On 26.04.2011 19:51, venom00 wrote:
Shouldn't we start with 2.1 first?
Yes.
This thread is growing fast and I don't know if this is the right place for
features, but I've been thinking of some features it would be nice to have in
LyX:
- scripting: it would be great to allow community to contr
Vincent van Ravesteijn wrote:
> I agree. It is stupid to have new and exciting features to be stalled
> for two years before being released.
acting as the devils advocate, one good thing about the current release
model is that we have stable (i mean _STABLE_) 1.6.10 product for people
who look for
On 26/04/2011 4:59 AM, Vincent van Ravesteijn wrote:
It would be possible to use svn/git together for one release cycle. I've
been maintaining a git repo parallel to the svn repo for the last few months.
However, everyone needs to become used to using git, we need to decide on
a place to host the
I have produced a new version of the layout files, the test files, and
the templates. It has been posted to the bug tracker.
This new version is now fully backward compatible. However, the style
abstract now behaves differently as the current implementation is broken.
The following price ha
On 26.04.2011 14:37, Vincent van Ravesteijn wrote:
I'm not opposed to moving to git, but I do not use it, and never have, so it
would mean some learning here.
Well, we'll guide you through. When doing svn-like development,
there is not much to learn. If you want to use all git features,
you mi
On 26/04/2011 11:40 AM, Vincent van Ravesteijn wrote:
new feature releases
I would keep the numbering as it is and allow new feature releases once
a year. As long as we are careful about the format conversion (and I
have seen that this is very serious), then it's not a problem for users
to j
> > Shouldn't we start with 2.1 first?
>
> Yes.
This thread is growing fast and I don't know if this is the right place for
features, but I've been thinking of some features it would be nice to have in
LyX:
- scripting: it would be great to allow community to contribute with plugins,
maybe for so
On 25.04.2011 14:37, nbubis wrote:
Here's an attempt with a small 'y' :)
Thanks again to all the "real" developers for an awesome piece of software -
somewhere around the world a future Nobel prize winner is writing his thesis
with LyX.
Thanks, also looks good. But I was wrong, it's indeed a
On 04/26/2011 12:18 PM, Vincent van Ravesteijn wrote:
On 26-4-2011 18:12, Johannes Wilm wrote:
Will this mean that we will not be allowed to put bib-information into the
header until 2013?
At the earliest point in time, this will be released in the end of 2012 indeed.
This seems long, but in
Diego Queiroz wrote:
> And how about the lyx.org site?
> How to proceed to start a translation of it in Portuguese?
do you intend to create and maintain portuguese version of lyx site?
pavel
Diego Queiroz wrote:
> LOL
>
> That was not exactly what I was thinking of (lazyness), but I can handle
> that.
>
> I'll work on it this afternoon. :-)
> BTW I think it won't take a long time to just update the images.
>
> It will be ok if I use LyX 2.0.0 RC3, right?
sure
pavel
On 26-4-2011 18:55, Abdelrazak Younes wrote:
> On 04/26/2011 06:48 PM, Pavel Sanda wrote:
>> Abdelrazak Younes wrote:
>>> we are always seeing new
>>> developers around new releases; 2.0 is no exception.
>> this looks as interesting insight, the more that i do not recognize that ;)
>> isn't it just
On 04/26/2011 06:48 PM, Pavel Sanda wrote:
Abdelrazak Younes wrote:
we are always seeing new
developers around new releases; 2.0 is no exception.
this looks as interesting insight, the more that i do not recognize that ;)
isn't it just illusion made by the fact the we are in freeze, rejecting n
On 26-4-2011 18:48, Pavel Sanda wrote:
> Abdelrazak Younes wrote:
>> we are always seeing new
>> developers around new releases; 2.0 is no exception.
>
> this looks as interesting insight, the more that i do not recognize that ;)
> isn't it just illusion made by the fact the we are in freeze, rej
Abdelrazak Younes wrote:
> we are always seeing new
> developers around new releases; 2.0 is no exception.
this looks as interesting insight, the more that i do not recognize that ;)
isn't it just illusion made by the fact the we are in freeze, rejecting new
stuff
and (hopefully) nicely expalini
On Tue, Apr 26, 2011 at 9:35 AM, Vincent van Ravesteijn wrote:
...
> I know there are different opinions about what a file format change is.
> Some people say that every change in LaTeX output is basically a file
> format change. That is, the same file gives a different output, and
> thus the for
Vincent van Ravesteijn wrote:
> Wouldn't this be confusing for the user that suddenly 2.0/2.1/2.2
> have the same file format.
that was my concern as well... p
> ok, I can understand that. I just wondered whether there is some
> differentiation
> in file format changes. For example, adding bibliography-info there, like I
> did
> with a little test patch, does not mean that the file no longer can be opened
> from an earlier version of LyX.
I don't know
On Tue, Apr 26, 2011 at 9:18 AM, Vincent van Ravesteijn wrote:
> On 26-4-2011 18:12, Johannes Wilm wrote:
> > Will this mean that we will not be allowed to put bib-information into
> the header until 2013?
> >
>
> At the earliest point in time, this will be released in the end of 2012
> indeed.
>
On 04/26/2011 06:08 PM, Vincent van Ravesteijn wrote:
I'd drop the stunning releases and increment the major version
at each format change, in this case. Too many numbers.
Wouldn't this be confusing for the user that suddenly 2.0/2.1/2.2
have the same file format. So he can easily upgrade. He is
On 26-4-2011 18:12, Johannes Wilm wrote:
> Will this mean that we will not be allowed to put bib-information into the
> header until 2013?
>
At the earliest point in time, this will be released in the end of 2012 indeed.
This seems long, but in practice we need the time. Fixing all little bugs
Will this mean that we will not be allowed to put bib-information into the
header until 2013?
On Tue, Apr 26, 2011 at 9:08 AM, Vincent van Ravesteijn wrote:
> > I'd drop the stunning releases and increment the major version
> > at each format change, in this case. Too many numbers.
>
> Wouldn't
LOL
That was not exactly what I was thinking of (lazyness), but I can handle
that.
I'll work on it this afternoon. :-)
BTW I think it won't take a long time to just update the images.
It will be ok if I use LyX 2.0.0 RC3, right?
---
Diego Queiroz
2011/4/26 Pavel Sanda
> Diego Queiroz wrote
> I'd drop the stunning releases and increment the major version
> at each format change, in this case. Too many numbers.
Wouldn't this be confusing for the user that suddenly 2.0/2.1/2.2
have the same file format. So he can easily upgrade. He is used to
having a stable file format only during the
> I'd drop the stunning releases and increment the major version
> at each format change, in this case. Too many numbers.
I mean LyX-10.0 in 2028 of course ;)
>
> JMarc
Vincent
> I'd drop the stunning releases and increment the major version
> at each format change, in this case. Too many numbers.
Raising the first number every 2 years leads to 10.0 in 2032.
That doesn't seem like a reason not to do it.
Anyone objects to this ?
>
> JMarc
Vincent
> 2.1.0.0 could happen sooner of course if we think we have reached
> something worth releasing (like the bib stuff or the epub export).
Yes of course. Given that there are only non-file-format changes,
there is no reason not to do that more often.
>
> Another important argument in favor of freq
On 04/26/2011 05:52 PM, Jean-Marc Lasgouttes wrote:
Le 26/04/2011 17:40, Vincent van Ravesteijn a écrit :
So we will have
(maintenance releases)
2.0.0.0 end of april 2011
2.0.0.1 end of may 2011
2.0.0.2 end of july 2011
2.0.0.3 end of september 2011
(new feature releases)
2.0.1.0 end of octobe
Le 26/04/2011 17:40, Vincent van Ravesteijn a écrit :
So we will have
(maintenance releases)
2.0.0.0 end of april 2011
2.0.0.1 end of may 2011
2.0.0.2 end of july 2011
2.0.0.3 end of september 2011
(new feature releases)
2.0.1.0 end of october 2011
2.0.2.0 end of april 2012
2.0.3.0 end of octob
On 04/26/2011 05:40 PM, Vincent van Ravesteijn wrote:
On 26-4-2011 17:34, Abdelrazak Younes wrote:
On 04/26/2011 05:29 PM, Pavel Sanda wrote:
Vincent van Ravesteijn wrote:
file-format changes releases.
i must admit that being lately forced to cooperate with people
not having full control over
On 26-4-2011 17:34, Abdelrazak Younes wrote:
> On 04/26/2011 05:29 PM, Pavel Sanda wrote:
>> Vincent van Ravesteijn wrote:
>>> file-format changes releases.
>> i must admit that being lately forced to cooperate with people
>> not having full control over the version of LyX installed
>> release cycl
On 04/26/2011 05:30 PM, Pavel Sanda wrote:
Diego Queiroz wrote:
Isn't interesting to update the Graphical Tour of LyX?
http://www.lyx.org/Walkthrough
It is mentioned in splash.lyx document but there is a long time it isn't
updated...
I think it should be updated with the final release of LyX
On 04/26/2011 05:00 PM, Richard Heck wrote:
I am still wondering if there is not some way to proceed here that
would allow more new features that do not touch file format into the
stable branch. It seems to me that the main concern is that some new
features that could have been included in 1.6.
On 04/26/2011 05:29 PM, Pavel Sanda wrote:
Vincent van Ravesteijn wrote:
file-format changes releases.
i must admit that being lately forced to cooperate with people
not having full control over the version of LyX installed
release cycle of 2 years does not sound so bad to me ;-p
Which is exa
Le 26/04/2011 17:23, Diego Queiroz a écrit :
Isn't interesting to update the Graphical Tour of LyX?
http://www.lyx.org/Walkthrough
Of course, it would be very interesting (and to add some of the most
important new features).
JMarc
Diego Queiroz wrote:
> Isn't interesting to update the Graphical Tour of LyX?
>
> http://www.lyx.org/Walkthrough
>
> It is mentioned in splash.lyx document but there is a long time it isn't
> updated...
>
>
> I think it should be updated with the final release of LyX 2.0.0.
the question is: wi
Vincent van Ravesteijn wrote:
> file-format changes releases.
i must admit that being lately forced to cooperate with people
not having full control over the version of LyX installed
release cycle of 2 years does not sound so bad to me ;-p
1.5->1.6 took 1,5 years and i dont remember such preasur
And how about the lyx.org site?
How to proceed to start a translation of it in Portuguese?
And how about a portuguese mailing list?
Regards,
---
Diego Queiroz
2011/4/25 Diego Queiroz
> Thanks Pavel. :-)
>
> ---
> Diego Queiroz
>
>
>
>
> 2011/4/25 Pavel Sanda
>
>> Diego Queiroz wrote:
>> >
Isn't interesting to update the Graphical Tour of LyX?
http://www.lyx.org/Walkthrough
It is mentioned in splash.lyx document but there is a long time it isn't
updated...
I think it should be updated with the final release of LyX 2.0.0.
---
Diego Queiroz
On 26-4-2011 17:00, Richard Heck wrote:
> On 04/26/2011 10:46 AM, Pavel Sanda wrote:
>> Vincent van Ravesteijn wrote:
>>> I'm not advocating to have 3 layers in general.
>> ok, Abdel is :)
>>
>> if i understand correctly there are 3 proposals:
>>
>> 1) 3 trees:
>> - agile (gui things)
>> - trunk (f
Though it's completely arbitrary, a six month release schedule might make
sense. Once a year for format changes, once a year for file formats? It seems
to have worked well for Ubuntu, KDE and Gnome ...
Cheers,
Rob
On 26-4-2011 16:46, Pavel Sanda wrote:
> Vincent van Ravesteijn wrote:
>> I'm not advocating to have 3 layers in general.
>
> ok, Abdel is :)
>
> if i understand correctly there are 3 proposals:
>
> 1) 3 trees:
> - agile (gui things)
> - trunk (fileformat)
> - stable
>
> 2) 2 trees, 3 trees in
On 04/26/2011 10:46 AM, Pavel Sanda wrote:
Vincent van Ravesteijn wrote:
I'm not advocating to have 3 layers in general.
ok, Abdel is :)
if i understand correctly there are 3 proposals:
1) 3 trees:
- agile (gui things)
- trunk (fileformat)
- stable
2) 2 trees, 3 trees in freze transitions
3
Sure, the user can put it manually under "LaTeX options" but I think it
would be helpful to have a text box. This way, LyX could also display that
page instead of the first page.
Would this be difficult? My guess is that the text box would not be
difficult, but displaying the correct page would be
On 04/26/2011 10:34 AM, Rob Oakes wrote:
I'm also worried about what effect it might have on the release schedule.
Fragmenting the code might also fragment developers. Would all GUI related
changes be automatically merged with the non-GUI branch (meaning that all GUI
related bugs also end up i
Vincent van Ravesteijn wrote:
> I'm not advocating to have 3 layers in general.
ok, Abdel is :)
if i understand correctly there are 3 proposals:
1) 3 trees:
- agile (gui things)
- trunk (fileformat)
- stable
2) 2 trees, 3 trees in freze transitions
3) current scheme with sooner alpha.
1 is mo
On Apr 26, 2011, at 8:33 AM, Liviu Andronic wrote:
> One possibility is to use the Xfce numbering scheme: odd for
> development releases and even for stable releases. For example, 2.0.0
> is the major stable release, 2.0.2 is the minor stable release, 2.0.3
> is the minor development release.
Th
I know that I don't really have a vote in this things, but I can't help but
jump in on the conversation.
> So the idea is to have two parallel development trees, basically: One that is
> devoted to changes that do not touch the file format, like GUI improvements,
> and one where we can make for
On Tue, Apr 26, 2011 at 2:57 PM, Abdelrazak Younes wrote:
> I would be glad if we could be more liberal indeed. But then we would also
> need bug fixing only releases. If you allow some new big features at one
> point, say 2.0.2 and then declare that 2.0.3 will only be about bug fixing
> because
On 04/26/2011 08:57 AM, Abdelrazak Younes wrote:
On 04/26/2011 02:40 PM, Richard Heck wrote:
The file format change is _the_ reason why people are kept back with
older version of LyX. 2 or 3 years time is OK for a file format
change but 6 months is obviously not.
The problem here is that so
I did some investigation of this, and maybe we can fix it before we
land. It is pretty nasty.
Here's the backtrace:
0 raise raise.c 64 0x3726c330c5
1 abort abort.c 92 0x3726c34a76
2 lyx::lyx_exit LyX.cpp 236 0x510568
3 boost::assertion_failed boost.cpp 47 0x460e5d
4 lyx::doAssert lassert.cpp
On 04/26/2011 02:45 PM, Richard Heck wrote:
On 04/26/2011 05:57 AM, Pavel Sanda wrote:
Abdelrazak Younes wrote:
That's also why time between releases are sooo long... 2 or 3 releases
every six without file format changes sounds very appealing to the user
that I am. To the developer, this means
On 04/26/2011 02:40 PM, Richard Heck wrote:
On 04/26/2011 05:04 AM, Abdelrazak Younes wrote:
On 04/26/2011 10:48 AM, Pavel Sanda wrote:
Abdelrazak Younes wrote:
I'd like to propose that 2.x release are only about GUI
improvements and
code cleanup. IOW 2.x should keep the file format unchanged
On 04/26/2011 07:17 AM, Vincent van Ravesteijn wrote:
Two notes about the bugs in the bug tracker:
- Please do not blindly retarget all bugs with a 1.6.x milestone
to 2.0.x. Let's only target bugs for 2.0.x which we think should
be fixed in this cycle. Bugs that haven't been touched or loo
On 04/26/2011 05:57 AM, Pavel Sanda wrote:
Abdelrazak Younes wrote:
That's also why time between releases are sooo long... 2 or 3 releases
every six without file format changes sounds very appealing to the user
that I am. To the developer, this means that his pet feature will arrive
sooner to th
On 04/26/2011 05:04 AM, Abdelrazak Younes wrote:
On 04/26/2011 10:48 AM, Pavel Sanda wrote:
Abdelrazak Younes wrote:
I'd like to propose that 2.x release are only about GUI
improvements and
code cleanup. IOW 2.x should keep the file format unchanged.
How are you going to do that? No format ch
> I'm not opposed to moving to git, but I do not use it, and never have, so it
> would mean some learning here.
Well, we'll guide you through. When doing svn-like development,
there is not much to learn. If you want to use all git features,
you might want to learn, but that's just fun.
As said
On 04/26/2011 04:48 AM, Pavel Sanda wrote:
Abdelrazak Younes wrote:
Most "active" developers (I am not) are already using git AFAIK...
i dont think you are right (highly depends on Richard) if we count it on the
number of commits. i use git personally but i'm not so excited about the change
be
On 04/26/2011 04:48 AM, Tommaso Cucinotta wrote:
Il 25/04/2011 14:56, rgh...@lyx.org ha scritto:
Author: rgheck
Date: Mon Apr 25 14:56:09 2011
New Revision: 38496
URL: http://www.lyx.org/trac/changeset/38496
Log:
Fix crash when there are text insets in a table cell with decimal
alignment. This
Am 26.04.2011 um 13:21 schrieb Pavel Sanda:
> Stephan Witt wrote:
>>> if you added some feature which is not in our manuals yet (or outdated)
>>> please
>>> consider to contribute documentation to it as well. (please remember to
>>> switch
>>> on the change tracking so our translators see whats
>>>
>>> - We can think of having several branches: e.g., LyX3.0 (or experimental)
>>> /LyX2.1 (or development)/LyX2.0.1(or maintenance)
>>
>> There are certainly benefits.
>
> these were all true. i wouldn't divide development on 3 layers though.
> just keeping experimental branch in a working
Stephan Witt wrote:
> > if you added some feature which is not in our manuals yet (or outdated)
> > please
> > consider to contribute documentation to it as well. (please remember to
> > switch
> > on the change tracking so our translators see whats happening).
>
> I feel some responsibility her
> unless the branch is merged into some kind of trunk that means they will have
> incongruent version of file format. if they are just users, thats showstopper
> with dataloss possibility due to some lyx2lyx chaos later.
I assume a user wants to use/try the new feature not before it is stable
and
Vincent van Ravesteijn wrote:
> Two notes about the bugs in the bug tracker:
>
> - Please do not blindly retarget all bugs with a 1.6.x milestone
> to 2.0.x. Let's only target bugs for 2.0.x which we think should
> be fixed in this cycle. Bugs that haven't been touched or looked
> upon in th
Two notes about the bugs in the bug tracker:
- Please do not blindly retarget all bugs with a 1.6.x milestone
to 2.0.x. Let's only target bugs for 2.0.x which we think should
be fixed in this cycle. Bugs that haven't been touched or looked
upon in the last two years, surely don't deserve thi
1 - 100 of 133 matches
Mail list logo
