Dear Michael,
> In the future, please do not "svn update" while changing your local po
> file. I will remerge the po files from time to time such that such
> conflicts may arise.
>
> For simplicity, download the po file, change it, and send it back to me.
> Before I commit it to the repository, I
Georg Baum schrieb:
> Am Sonntag, 5. November 2006 19:22 schrieb Herbert Voss:
>> I am interested in seeing how someone will parse a tex source, where
>> _every_ macro or environment can be hide after several other macros
>> or catcode changes ...
>
> Impossible IMHO. It is possible to create a te
Am Sonntag, 5. November 2006 19:11 schrieb José Matos:
> On Sunday 05 November 2006 4:36 pm, Georg Baum wrote:
> > Tex2lyx is currently several file format versions behind LyX, but I
don't
> > know if it makes sense to work on that. If José is really serious with
> > reimplementing it in python th
Am Sonntag, 5. November 2006 19:22 schrieb Herbert Voss:
> I am interested in seeing how someone will parse a tex source, where
> _every_ macro or environment can be hide after several other macros
> or catcode changes ...
Impossible IMHO. It is possible to create a tex2lyx that works perfectly
f
Georg Baum schrieb:
> Am Sonntag, 5. November 2006 17:25 schrieb Enrico Forestieri:
>
>> Maybe tex2lyx should be updated to take into account the fact that
>> the latex file could be utf8 encoded?
>
> Yes, as I wrote: tex2lyx almost completely ignores encodings.
>
>> If I am not wrong, now LyX c
On Sunday 05 November 2006 4:36 pm, Georg Baum wrote:
> Tex2lyx is currently several file format versions behind LyX, but I don't
> know if it makes sense to work on that. If José is really serious with
> reimplementing it in python then it does not make sense to do anything
> else than simple bugf
On Sun, Nov 05, 2006 at 06:17:12PM +0100, Asger Ottar Alstrup wrote:
> Enrico Forestieri wrote:
> > The point is that I am not able to link with debug info (-g) as the
> > final link stage fails with a "Memory exhausted" error.
>
> You could try to compile most of the code without debug info, exc
On Sun, Nov 05, 2006 at 05:25:37PM +0100, Abdelrazak Younes wrote:
> Alex wrote:
> >Dear Sirs,
> >
> >I can reproduce any time:
> >1. start lyx1.5.0svn
> >2. create 1 section
> >3. Insert TOC
> >4. click on TOC inset
> >
> >I have attached a small backtrace and some info about the compile.
> >
> >I
On Sun, Nov 05, 2006 at 05:09:15PM -, [EMAIL PROTECTED] wrote:
> Author: schmitt
> Date: Sun Nov 5 18:09:14 2006
> New Revision: 15751
>
> URL: http://www.lyx.org/trac/changeset/15751
> Log:
> * Status.15x: all button and label texts are not translated
>
> Modified:
> lyx-devel/tr
Am Sonntag, 5. November 2006 18:11 schrieb Enrico Forestieri:
> Thanks, I'll try to digest that. At a first glance it seems really
> irksome...
Yes. Some stuff is really powerful, but sometimes also horribly
complicated. Fortunately one does not need to touch these things often.
> > I guess tha
On Sun, Nov 05, 2006 at 06:07:20PM +0100, Herbert Voss wrote:
> Enrico Forestieri schrieb:
> > On Sun, Nov 05, 2006 at 04:21:47PM +0100, Herbert Voss wrote:
> >
> >> Enrico Forestieri schrieb:
> >>
> > I think that we should leave the 256, but if you and others don't agree,
> > then pleas
On Sun, Nov 05, 2006 at 09:34:08AM +0100, Asger Ottar Alstrup wrote:
> My take on which of the known bugs are showstoppers for the test release:
>
> * The title bar does not contain the document name when a new window is
> opened (Joost 4/11/06). Should be a simple fix for those in the know.
>
>
Enrico Forestieri wrote:
The point is that I am not able to link with debug info (-g) as the
final link stage fails with a "Memory exhausted" error.
You could try to compile most of the code without debug info, except for
the files you are interested in debugging. Just pass -g to the files you
On Sun, Nov 05, 2006 at 05:45:35PM +0100, Georg Baum wrote:
> Am Sonntag, 5. November 2006 17:19 schrieb Enrico Forestieri:
> > where os is an odocstream. If I change these lines to:
> >
> > if (par_begin + 1 == par_end)
> > os << "% Preview source code for current paragraph\n\n";
> >
Enrico Forestieri schrieb:
> On Sun, Nov 05, 2006 at 04:21:47PM +0100, Herbert Voss wrote:
>
>> Enrico Forestieri schrieb:
>>
> I think that we should leave the 256, but if you and others don't agree,
> then please also make the corresponding changes to texparser.C
only the characters
Enrico Forestieri wrote:
> > This is current svn with no patches and qt 4.2.1.
>
> This must be a bug in qt 4.2.1 as I don't see it with qt 4.1.4
Me neither. Qt 4.1.2.
Jürgen
Am Sonntag, 5. November 2006 17:26 schrieb Georg Baum:
> Am Sonntag, 5. November 2006 17:12 schrieb Michael Gerz:
> > Why is biggg/Biggg not used in the frontend?
>
> Because it is only defined in one special font (I forgot which one, but
> IIRC there should be a comment somehere).
Yep, it is in
Am Sonntag, 5. November 2006 17:51 schrieb Enrico Forestieri:
> On Sun, Nov 05, 2006 at 05:36:56PM +0100, Georg Baum wrote:
>
> > Am Sonntag, 5. November 2006 17:25 schrieb Enrico Forestieri:
> >
> > > Maybe tex2lyx should be updated to take into account the fact that
> > > the latex file could b
On Sun, Nov 05, 2006 at 05:36:56PM +0100, Georg Baum wrote:
> Am Sonntag, 5. November 2006 17:25 schrieb Enrico Forestieri:
>
> > Maybe tex2lyx should be updated to take into account the fact that
> > the latex file could be utf8 encoded?
>
> Yes, as I wrote: tex2lyx almost completely ignores en
Am Sonntag, 5. November 2006 17:19 schrieb Enrico Forestieri:
> where os is an odocstream. If I change these lines to:
>
> if (par_begin + 1 == par_end)
> os << "% Preview source code for current paragraph\n\n";
> else
> os << "% Preview source code for selected paragra
Am Sonntag, 5. November 2006 17:25 schrieb Enrico Forestieri:
> Maybe tex2lyx should be updated to take into account the fact that
> the latex file could be utf8 encoded?
Yes, as I wrote: tex2lyx almost completely ignores encodings.
> If I am not wrong, now LyX could output such encoding.
Yes,
On Sun, Nov 05, 2006 at 05:23:37PM +0100, Georg Baum wrote:
> Am Sonntag, 5. November 2006 17:03 schrieb Juergen Spitzmueller:
> > Georg Baum wrote:
> > > This is not fixed.
> >
> > Could you describe this bug more precisely?
>
> Start LyX. Open the preferences dialog: It looks like prefs1.png.
Am Sonntag, 5. November 2006 17:12 schrieb Michael Gerz:
> Hi,
>
> I am going to commit the following patch:
>
> Index: frontends/qt4/QDelimiterDialog.C
> ===
> --- frontends/qt4/QDelimiterDialog.C(Revision 15750)
> +++ frontends
On Sun, Nov 05, 2006 at 05:12:24PM +0100, Michael Gerz wrote:
> Hi,
>
> I am going to commit the following patch:
>
> Index: frontends/qt4/QDelimiterDialog.C
> ===
> --- frontends/qt4/QDelimiterDialog.C(Revision 15750)
> +++ fro
Alex wrote:
Dear Sirs,
I can reproduce any time:
1. start lyx1.5.0svn
2. create 1 section
3. Insert TOC
4. click on TOC inset
I have attached a small backtrace and some info about the compile.
Is it enough? What to do more?
You report is perfect. Even though I cannot reproduce the crash on
On Sun, Nov 05, 2006 at 04:58:28PM +0100, Georg Baum wrote:
> Am Sonntag, 5. November 2006 16:51 schrieb Enrico Forestieri:
>
> > Then I'll shut up. However, I think that the same change from 256 to 128
> > should also be done in texparser.C, for consistency.
>
> That would introduce an extra if
I feel a bit stupid with this, but I think I am a sorcerer apprentice
with not enough experience to solve it.
The problem is that on cygwin (and I think it is the same with mingw)
the "View source" feature does not work when the source of a single
paragraph (or a group of paragraphs) is to be disp
Hi,
I am going to commit the following patch:
Index: frontends/qt4/QDelimiterDialog.C
===
--- frontends/qt4/QDelimiterDialog.C(Revision 15750)
+++ frontends/qt4/QDelimiterDialog.C(Arbeitskopie)
@@ -45,8 +45,8 @@
char const *
Georg Baum wrote:
> This is not fixed.
Could you describe this bug more precisely?
Jürgen
Alex wrote:
I have successfully resolved the problem with svn.
There was a conflict with my modification and the one coming from the
repository.
In the future, please do not "svn update" while changing your local po
file. I will remerge the po files from time to time such that such
conflict
Am Sonntag, 5. November 2006 16:51 schrieb Enrico Forestieri:
> Then I'll shut up. However, I think that the same change from 256 to 128
> should also be done in texparser.C, for consistency.
That would introduce an extra if clause.
Georg
Am Sonntag, 5. November 2006 13:30 schrieb Juergen Spitzmueller:
> Juergen Spitzmueller wrote:
> > I don't know if this is the "dialog is much too small" bug mentioned in
> > Status.15 (I don't see any other size problem, though).
>
> I left the entry untouched. The people who reported that bug sh
On Sun, Nov 05, 2006 at 04:34:53PM +0100, Georg Baum wrote:
> Am Sonntag, 5. November 2006 15:46 schrieb Enrico Forestieri:
> > I am trying to say that, currently, LyX is not correctly tracking
> > catcodes
> > and if we want to improve on that, then we should maintain the 256.
>
> Yes, I unders
Dear Sirs,
I can reproduce any time:
1. start lyx1.5.0svn
2. create 1 section
3. Insert TOC
4. click on TOC inset
I have attached a small backtrace and some info about the compile.
Is it enough? What to do more?
Alex
uname -m = x86_64
uname -r = 2.6.13-15.12-default
uname -s = Linux
uname -v =
Am Sonntag, 5. November 2006 15:46 schrieb Enrico Forestieri:
> I am trying to say that, currently, LyX is not correctly tracking
catcodes
> and if we want to improve on that, then we should maintain the 256.
Yes, I understood that, but I don't think that this will be improved in the
near future
Asger Ottar Alstrup wrote:
My take on which of the known bugs are showstoppers for the test release:
* The title bar does not contain the document name when a new window is
opened (Joost 4/11/06). Should be a simple fix for those in the know.
Fixed:
Author: younes
Date: Sun Nov 5 16:34:18 2
On Sun, Nov 05, 2006 at 04:21:47PM +0100, Herbert Voss wrote:
> Enrico Forestieri schrieb:
>
> >>> I think that we should leave the 256, but if you and others don't agree,
> >>> then please also make the corresponding changes to texparser.C
> >> only the characters 0,13,32,35-38,65-90,92,94,95,97
Enrico Forestieri schrieb:
> On Sun, Nov 05, 2006 at 04:00:39PM +0100, Abdelrazak Younes wrote:
>
>> Enrico Forestieri wrote:
>>> On Sun, Nov 05, 2006 at 09:58:28AM +0100, Georg Baum wrote:
> I think that we should leave the 256, but if you and others don't agree,
> then please also make t
On Sun, Nov 05, 2006 at 04:00:39PM +0100, Abdelrazak Younes wrote:
> Enrico Forestieri wrote:
> > On Sun, Nov 05, 2006 at 09:58:28AM +0100, Georg Baum wrote:
> >>> I think that we should leave the 256, but if you and others don't agree,
> >>> then please also make the corresponding changes to texp
Am Sonntag, 5. November 2006 16:00 schrieb Abdelrazak Younes:
> Are you saying that it is allowed to create new catcodes in a latex file?
No. You can not create new catcodes, but you can change the catcode of
characters. That is what Enrico did.
Georg
Enrico Forestieri schrieb:
>>> I think that we should leave the 256, but if you and others don't agree,
>>> then please also make the corresponding changes to texparser.C
>> only the characters 0,13,32,35-38,65-90,92,94,95,97-123,125-127
>> have a catcode other than 12. All others from the 256 pos
Enrico Forestieri wrote:
On Sun, Nov 05, 2006 at 09:58:28AM +0100, Georg Baum wrote:
I think that we should leave the 256, but if you and others don't agree,
then please also make the corresponding changes to texparser.C
Abdel is right that a table of 256 is not needed, since we never set the
c
On Sun, Nov 05, 2006 at 11:09:18AM +0100, Herbert Voss wrote:
> Enrico Forestieri schrieb:
>
> >> If you are sure that there is at least one catcode greater than 128 is
> >> classified as something other than catOther, I'll do the change. But
> >> from what I read about TeX catcode since then,
On Sun, Nov 05, 2006 at 09:58:28AM +0100, Georg Baum wrote:
> Am Sonntag, 5. November 2006 00:19 schrieb Enrico Forestieri:
> > On Sat, Nov 04, 2006 at 11:27:49PM +0100, Abdelrazak Younes wrote:
> >
> > > Enrico Forestieri wrote:
> > > > This is wrong because \catcode works on 8-bit numbers. Plea
> I suggest that you send him a private email. Lars has some problem
> with memory :-)
That's what I did but never got a reply.
Uwe
Juergen Spitzmueller wrote:
> The attached patch fixes the width of the treeview in the document and
> prefs dialog (which is way too small in the German localization). Qt is
> still too dumb to resize it properly itself, so we have to do the
> calculation.
It's in.
> I don't know if this is the
Abdelrazak Younes wrote:
> I meant: I am going to call _you_ the Polisher from now on ;-)
I think I understood. Feel free to do so (*and* call me when there's something
to polish; I'm not going to wash your dishes, though) ;-)
> That is "the guy who do the polishing", I am not very good at Engli
Asger Ottar Alstrup wrote:
* Spell checking cannot be invoked a second time. I can not reproduce
because I do not have aspell. I guess cmake does not support aspell yet?
It does. The library and include is installed in my GnuWin32 directory
and CMake correctly detect and use that. I can send t
Juergen Spitzmueller wrote:
Abdelrazak Younes wrote:
I am going to call the Polisher from now on ;-)
Feel free to do so.
I meant: I am going to call _you_ the Polisher from now on ;-)
That is "the guy who do the polishing", I am not very good at English
joking.
Abdel.
Abdelrazak Younes wrote:
> I am going to call the Polisher from now on ;-)
Feel free to do so.
Jürgen
Hello,
This patch optimizes the redraw problem pointed out by Edwin. There's
still too much redraw inside insets but this is fixable.
One of the difficult problem that this patch solves is the recursive
descending inside Insets within LyXText::editXY(). The problem was that,
when clicking on
[EMAIL PROTECTED] wrote:
+Prizes (donated by Michael):
+
+ #1: LyX-labeled Tick Tock Wall Clock
+ #2: LyX-labeled Coffee and Tea Mug
+ #3: LyX-labeled Mousepad
Watch this ^^
Michael
Asger Ottar Alstrup wrote:
My take on which of the known bugs are showstoppers for the test release:
[...]
* TOC crashes (simply make a few sections, subsections, sections; then
add TOC before all sections and click on the left button)
I cannot reproduce that one. Backtrace please.
* Cursor
Peter Kümmel wrote:
I've fixed it:
Index: QPrefsDialog.C
===
--- QPrefsDialog.C (revision 15726)
+++ QPrefsDialog.C (working copy)
@@ -938,10 +938,13 @@
void PrefConverters::switch_converter(int nr)
{
- if (nr<0)
+
Enrico Forestieri schrieb:
>> If you are sure that there is at least one catcode greater than 128 is
>> classified as something other than catOther, I'll do the change. But
>> from what I read about TeX catcode since then, I doubt it.
>
> Maybe you are right as, from what I can see, only the ca
Am Samstag, 4. November 2006 21:31 schrieb Abdelrazak Younes:
> Are you aware that you sent this twice?
Yes. If you look at the headers of the first one you will see that it spent
several hours in a black hole until it appeared on the list.
Therefore I thought that something went wrong and sent
Am Sonntag, 5. November 2006 00:19 schrieb Enrico Forestieri:
> On Sat, Nov 04, 2006 at 11:27:49PM +0100, Abdelrazak Younes wrote:
>
> > Enrico Forestieri wrote:
> > > This is wrong because \catcode works on 8-bit numbers. Please, change
> > > the 128 to 256.
It was from memory. Obviously I am be
My take on which of the known bugs are showstoppers for the test release:
* The title bar does not contain the document name when a new window is
opened (Joost 4/11/06). Should be a simple fix for those in the know.
* Spell checking cannot be invoked a second time. I can not reproduce
because
58 matches
Mail list logo
