> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> http://bugzilla.lyx.org/show_bug.cgi?id=1934 not easy
Not easy indeed :(
Georg> http://bugzilla.lyx.org/show_bug.cgi?id=1973 x
I am not sure I like the patch (it is intrusive). I have to re-read
the thread to convince myself that
On Jan 9, 2006, at 10:54 AM, Jean-Marc Lasgouttes wrote:
Bennett, do you think you will be able to find somebody with acess to
OSX 10.3 to compile lyx 1.3.7? If you can, I think I am going to give
up trying to make it work with gcc3.
I think I can. (It might be easiest to put 10.3 on an
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| - it is not possible to build on OSX right now. This is related to the
| changes Lars did to the libtool files, I think. Recent libtools
| versions have code that reads -framework Foo from linker commands
| and does something with them (?).
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| I'd like to have some more information about the tar binary on OSX.
More specifically what tar formats it actually supports.
--
Lgb
On Jan 10, 2006, at 9:34 AM, Lars Gullik Bjønnes wrote:
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| I'd like to have some more information about the tar binary on OSX.
More specifically what tar formats it actually supports.
tar (GNU tar) 1.15.1
That's the version installed via fink
On Tue, 2006-01-10 at 15:14 +0100, Jean-Marc Lasgouttes wrote:
> > "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
...
> Georg> http://bugzilla.lyx.org/show_bug.cgi?id=2015 x
>
> Should have been applied long ago :)
Hear hear.
> Georg> http://bugzilla.lyx.org/show_bug.cgi?id=2019 x
>
>
Bennett Helm <[EMAIL PROTECTED]> writes:
| On Jan 10, 2006, at 9:34 AM, Lars Gullik Bjønnes wrote:
|
| > [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| >
| > | I'd like to have some more information about the tar binary on OSX.
| >
| > More specifically what tar formats it actually supports.
On Tuesday 10 January 2006 15:25, Martin Vermeer wrote:
> Ah well, some other time.
Don't worry, we will get there. ;-)
> - Martin
--
José Abílio
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
| Apple's version is: tar (GNU tar) 1.14
Lars> this might not have it
And OSX people may not have the fink version.
JMarc
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> If you can get this to work somehow, I would be happy for
Martin> 1.4.0 at least.
Not sure I can :)
Martin> Still I think we differ in our views of what the charstyle
Martin> paradigm should be (I see it as a longer term
On Jan 10, 2006, at 10:46 AM, Lars Gullik Bjønnes wrote:
Bennett Helm <[EMAIL PROTECTED]> writes:
| On Jan 10, 2006, at 9:34 AM, Lars Gullik Bjønnes wrote:
|
| > [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| >
| > | I'd like to have some more information about the tar binary
on OSX.
|
On Tue, Jan 10, 2006 at 05:36:38PM +0100, Jean-Marc Lasgouttes wrote:
> > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> Martin> If you can get this to work somehow, I would be happy for
> Martin> 1.4.0 at least.
>
> Not sure I can :)
>
> Martin> Still I think we differ in our
Am Dienstag, 10. Januar 2006 15:14 schrieb Jean-Marc Lasgouttes:
> Georg> http://bugzilla.lyx.org/show_bug.cgi?id=2192 x
>
> Can you describe what you do? I cannot guess it from the patch.
We have no format information for a file if getFormatFromContents() does
not recognize the file format.
Am Dienstag, 10. Januar 2006 15:14 schrieb Jean-Marc Lasgouttes:
> > "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
>
> Georg> http://bugzilla.lyx.org/show_bug.cgi?id=1973 x
>
> I am not sure I like the patch (it is intrusive). I have to re-read
> the thread to convince myself that there
Bennett Helm <[EMAIL PROTECTED]> writes:
| I've done a bit more digging. It turns out Firefox on Mac defaults to
| using Stuffit Expander to decompress .tar.gz files, and it's all
| Stuffit's fault. Both versions of tar (1.15 and 1.14) succeed in
| unpacking the file.
|
| We'll need to include a
Georg Baum <[EMAIL PROTECTED]> writes:
| Am Dienstag, 10. Januar 2006 15:14 schrieb Jean-Marc Lasgouttes:
| > > "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
| >
| > Georg> http://bugzilla.lyx.org/show_bug.cgi?id=1973 x
| >
| > I am not sure I like the patch (it is intrusive). I have to
Georg Baum <[EMAIL PROTECTED]> writes:
| > The src/ChageLog entry is wrong BTW.
|
| Indeed. I attach an updated patch.
IMHO this is not for 1.4.0
--
Lgb
Martin Vermeer <[EMAIL PROTECTED]> writes:
| Think about it!
_I_ will, but not for 1.4.0.
(what you say makes sense to me)
--
Lgb
Bennett == Bennett Helm [EMAIL PROTECTED] writes:
Bennett On Jan 4, 2006, at 11:08 AM, Jean-Marc Lasgouttes wrote: Note
Bennett that I still cannot compile 1.3.7 on Mac (Nor, at this
Bennett point, 1.4.0.)
Note that you can compile it, but it does not run ;)
Bennett Thbpbpthpt!
Bennett,
These are the bugs currently scheduled for 1.4.0:
bug patch comment
http://bugzilla.lyx.org/show_bug.cgi?id=1934 not easy
http://bugzilla.lyx.org/show_bug.cgi?id=1973 x
http://bugzilla.lyx.org/show_bug.cgi?id=2015 x
Georg Baum schrieb:
These are the bugs currently scheduled for 1.4.0:
I just noticed that
http://bugzilla.lyx.org/show_bug.cgi?id=2199
seems to be a crash and perhaps this should also be fixed before 1.4.
regards Uwe
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> On Jan 4, 2006, at 11:08 AM, Jean-Marc Lasgouttes wrote: Note
Bennett> that I still cannot compile 1.3.7 on Mac (Nor, at this
Bennett> point, 1.4.0.)
>> Note that you can compile it, but it does not run ;)
Bennett>
These are the bugs currently scheduled for 1.4.0:
bug patch comment
http://bugzilla.lyx.org/show_bug.cgi?id=1934 not easy
http://bugzilla.lyx.org/show_bug.cgi?id=1973 x
http://bugzilla.lyx.org/show_bug.cgi?id=2015 x
Georg Baum schrieb:
These are the bugs currently scheduled for 1.4.0:
I just noticed that
http://bugzilla.lyx.org/show_bug.cgi?id=2199
seems to be a crash and perhaps this should also be fixed before 1.4.
regards Uwe
On Mon, Jan 02, 2006 at 05:44:24PM +, Jose' Matos wrote:
On Monday 02 January 2006 17:41, Herbert Voss wrote:
uuh, this causes an error!
\tabular{lr}
Jür gen
\endtabular
You are really a magician, splitting Jürgen in half. ;-)
I thought the magic part was implementing 'undo'
On Mon, Jan 02, 2006 at 05:44:24PM +, Jose' Matos wrote:
> On Monday 02 January 2006 17:41, Herbert Voss wrote:
> > uuh, this causes an error!
> >
> > \tabular{lr}
> > Jür & gen
> > \endtabular
>
> You are really a magician, splitting Jürgen in half. ;-)
I thought the magic part was
Bo == Bo Peng [EMAIL PROTECTED] writes:
Also, if you keep the extension to .lyx, you are going to
overwrite the file. What about exporting to .lyx13?
Fine with me.
Bo But a more common approach is that the user is prompted for a new
Bo filename.
Yes, but this is more work :)
JMarc
Bennett == Bennett Helm [EMAIL PROTECTED] writes:
Note that you can compile it, but it does not run ;)
Bennett Thbpbpthpt!
I did try to do something after all!
Did I ask you to try to compile with --disable-optimization
already?
Bennett No, but it doesn't help:
So, just to make sure,
On Jan 5, 2006, at 4:51 AM, Jean-Marc Lasgouttes wrote:
Did I ask you to try to compile with --disable-optimization
already?
Bennett No, but it doesn't help:
So, just to make sure, you did a make clean and recompiled, didn't
you?
Yes.
Bennett
> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes:
>> > Also, if you keep the extension to ".lyx", you are going to
>> overwrite > the file. What about exporting to ".lyx13"?
>>
>> Fine with me.
Bo> But a more common approach is that the user is prompted for a new
Bo> filename.
Yes, but this is
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
>> Note that you can compile it, but it does not run ;)
Bennett> Thbpbpthpt!
I did try to do something after all!
>> Did I ask you to try to compile with --disable-optimization
>> already?
Bennett> No, but it doesn't help:
So, just
On Jan 5, 2006, at 4:51 AM, Jean-Marc Lasgouttes wrote:
Did I ask you to try to compile with --disable-optimization
already?
Bennett> No, but it doesn't help:
So, just to make sure, you did a "make clean" and recompiled, didn't
you?
Yes.
Bennett
On Mon, Jan 02, 2006 at 08:52:06PM +0200, Martin Vermeer wrote:
On Mon, Jan 02, 2006 at 06:17:31PM +0200, Martin Vermeer wrote:
...
Bugzilla has a fix which simply disables font attribute editing inside a
charstyle inset; see above theory. Problem solved :-)
...
See attached, tested and
Martin Vermeer wrote:
On Mon, Jan 02, 2006 at 08:52:06PM +0200, Martin Vermeer wrote:
On Mon, Jan 02, 2006 at 06:17:31PM +0200, Martin Vermeer wrote:
...
Bugzilla has a fix which simply disables font attribute editing inside a
charstyle inset; see above theory. Problem solved :-)
...
On Wed, Jan 04, 2006 at 01:48:15PM +0100, Georg Baum wrote:
Martin Vermeer wrote:
On Mon, Jan 02, 2006 at 08:52:06PM +0200, Martin Vermeer wrote:
On Mon, Jan 02, 2006 at 06:17:31PM +0200, Martin Vermeer wrote:
...
Bugzilla has a fix which simply disables font attribute editing
Martin == Martin Vermeer [EMAIL PROTECTED] writes:
Martin On Mon, Jan 02, 2006 at 09:21:09AM +0100, Juergen Spitzmueller
Martin wrote:
Martin Vermeer wrote: I believe bug 822 is fixed. Is 1561 still
major? Was partly fixed by Andre.
Are these (and 2155) the only major bugs left for
Jean-Marc Lasgouttes wrote:
Since the bug was present in 1.3.x too (wasn't it?) and we do not know
of a good fix yet, we could schedule it for later...
I was about to propose this too. The bug should definitely also apply to
1.3.x, so it's not a regression. We should try and implement a solid
Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes:
Juergen Jean-Marc Lasgouttes wrote:
Since the bug was present in 1.3.x too (wasn't it?) and we do not
know of a good fix yet, we could schedule it for later...
Juergen I was about to propose this too. The bug should definitely
Juergen
Juergen Spitzmueller wrote:
So, what's left? There are bugs 2026 and 1973, for which Georg has
announced fixes-to-come,
I don't plan anything for 2026, because I don't know what to do (reintroduce
stdletters.inc or add ObsoletedBy statements for the missing layouts).
The fix for 1973 is
Georg Baum wrote:
Then I sent a patch for 2153 (this is a regression) to the list which is
waiting for testing/comments.
I had a quick look some days ago; I have to admit that I didn't get the report
down to the ground. Do does problem only occur in LaTeX export (not view
DVI/PDF) and only if
Juergen Spitzmueller wrote:
Georg Baum wrote:
Then I sent a patch for 2153 (this is a regression) to the list which is
waiting for testing/comments.
I had a quick look some days ago; I have to admit that I didn't get the
report down to the ground. Do does problem only occur in LaTeX export
Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg I also think that 2174 would be good to have (it does not make
Georg so much sense anymore after 1.4.0 is out for some time).
Note that I'd like to release 1.3.7 as soon as possible, so that 1.3
people will actually be able to read 1.4 files.
Jean-Marc Lasgouttes wrote:
Georg == Georg Baum
[EMAIL PROTECTED]
writes:
Georg I also think that 2174 would be good to have (it does not make
Georg so much sense anymore after 1.4.0 is out for some time).
Note that I'd like to release 1.3.7 as soon as possible, so that 1.3
people will
On Wednesday 04 January 2006 15:20, Jean-Marc Lasgouttes wrote:
Isn't it possible to define a lyx13 format, so that people can export
to that?
Could you give an example?
If if find a reasonable call syntax it is easy to implement it...
JMarc
--
José Abílio
On Jan 4, 2006, at 10:20 AM, Jean-Marc Lasgouttes wrote:
Note that I'd like to release 1.3.7 as soon as possible, so that 1.3
people will actually be able to read 1.4 files.
Note that I still cannot compile 1.3.7 on Mac (Nor, at this
point, 1.4.0.)
Bennett
Georg == Georg Baum [EMAIL PROTECTED] writes:
Isn't it possible to define a lyx13 format, so that people can
export to that?
Georg That is what the patch in bugzilla does :-) See
Georg http://bugzilla.lyx.org/show_bug.cgi?id=2174, sorry that I
Georg forgot to mention that I had a patch.
I
Jean-Marc Lasgouttes wrote:
I like it, although I do not see why you add a menu entry. Doesn't it
appear in FileExport?
No, because Exporter::GetExportableFormats() only considers formats that can
be reached from the backends and not from .lyx directly.
I am not sure whether this is a bug or a
Bennett == Bennett Helm [EMAIL PROTECTED] writes:
Bennett On Jan 4, 2006, at 10:20 AM, Jean-Marc Lasgouttes wrote:
Note that I'd like to release 1.3.7 as soon as possible, so that
1.3 people will actually be able to read 1.4 files.
Bennett Note that I still cannot compile 1.3.7 on Mac
On Jan 4, 2006, at 11:08 AM, Jean-Marc Lasgouttes wrote:
Bennett Note that I still cannot compile 1.3.7 on Mac (Nor, at
Bennett this point, 1.4.0.)
Note that you can compile it, but it does not run ;)
Thbpbpthpt!
This is one of the main things that makes 1.3.7 wait, and I have run
out
Also, if you keep the extension to .lyx, you are going to overwrite
the file. What about exporting to .lyx13?
Fine with me.
But a more common approach is that the user is prompted for a new filename.
Bo
On Mon, Jan 02, 2006 at 08:52:06PM +0200, Martin Vermeer wrote:
> On Mon, Jan 02, 2006 at 06:17:31PM +0200, Martin Vermeer wrote:
>
...
> Bugzilla has a fix which simply disables font attribute editing inside a
> charstyle inset; see above theory. Problem solved :-)
...
> See attached, tested
Martin Vermeer wrote:
> On Mon, Jan 02, 2006 at 08:52:06PM +0200, Martin Vermeer wrote:
>> On Mon, Jan 02, 2006 at 06:17:31PM +0200, Martin Vermeer wrote:
>>
> ...
>
>> Bugzilla has a fix which simply disables font attribute editing inside a
>> charstyle inset; see above theory. Problem solved
On Wed, Jan 04, 2006 at 01:48:15PM +0100, Georg Baum wrote:
> Martin Vermeer wrote:
>
> > On Mon, Jan 02, 2006 at 08:52:06PM +0200, Martin Vermeer wrote:
> >> On Mon, Jan 02, 2006 at 06:17:31PM +0200, Martin Vermeer wrote:
> >>
> > ...
> >
> >> Bugzilla has a fix which simply disables font
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> On Mon, Jan 02, 2006 at 09:21:09AM +0100, Juergen Spitzmueller
Martin> wrote:
>> Martin Vermeer wrote: > I believe bug 822 is fixed. > Is 1561 still
>> major? Was partly fixed by Andre.
>> >
>> > Are these (and 2155) the only
Jean-Marc Lasgouttes wrote:
> Since the bug was present in 1.3.x too (wasn't it?) and we do not know
> of a good fix yet, we could schedule it for later...
I was about to propose this too. The bug should definitely also apply to
1.3.x, so it's not a regression. We should try and implement a
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Jean-Marc Lasgouttes wrote:
>> Since the bug was present in 1.3.x too (wasn't it?) and we do not
>> know of a good fix yet, we could schedule it for later...
Juergen> I was about to propose this too. The bug should
Juergen Spitzmueller wrote:
> So, what's left? There are bugs 2026 and 1973, for which Georg has
> announced fixes-to-come,
I don't plan anything for 2026, because I don't know what to do (reintroduce
stdletters.inc or add ObsoletedBy statements for the missing layouts).
The fix for 1973 is
Georg Baum wrote:
> Then I sent a patch for 2153 (this is a regression) to the list which is
> waiting for testing/comments.
I had a quick look some days ago; I have to admit that I didn't get the report
down to the ground. Do does problem only occur in LaTeX export (not view
DVI/PDF) and only
Juergen Spitzmueller wrote:
> Georg Baum wrote:
>> Then I sent a patch for 2153 (this is a regression) to the list which is
>> waiting for testing/comments.
>
> I had a quick look some days ago; I have to admit that I didn't get the
> report down to the ground. Do does problem only occur in
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> I also think that 2174 would be good to have (it does not make
Georg> so much sense anymore after 1.4.0 is out for some time).
Note that I'd like to release 1.3.7 as soon as possible, so that 1.3
people will actually be able to read
Jean-Marc Lasgouttes wrote:
>> "Georg" == Georg Baum
>> <[EMAIL PROTECTED]>
>> writes:
>
> Georg> I also think that 2174 would be good to have (it does not make
> Georg> so much sense anymore after 1.4.0 is out for some time).
>
> Note that I'd like to release 1.3.7 as soon as
On Wednesday 04 January 2006 15:20, Jean-Marc Lasgouttes wrote:
> Isn't it possible to define a lyx13 format, so that people can export
> to that?
Could you give an example?
If if find a reasonable call syntax it is easy to implement it...
> JMarc
--
José Abílio
On Jan 4, 2006, at 10:20 AM, Jean-Marc Lasgouttes wrote:
Note that I'd like to release 1.3.7 as soon as possible, so that 1.3
people will actually be able to read 1.4 files.
Note that I still cannot compile 1.3.7 on Mac (Nor, at this
point, 1.4.0.)
Bennett
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
>> Isn't it possible to define a lyx13 format, so that people can
>> export to that?
Georg> That is what the patch in bugzilla does :-) See
Georg> http://bugzilla.lyx.org/show_bug.cgi?id=2174, sorry that I
Georg> forgot to mention that I
Jean-Marc Lasgouttes wrote:
> I like it, although I do not see why you add a menu entry. Doesn't it
> appear in File>Export?
No, because Exporter::GetExportableFormats() only considers formats that can
be reached from the backends and not from .lyx directly.
I am not sure whether this is a bug
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> On Jan 4, 2006, at 10:20 AM, Jean-Marc Lasgouttes wrote:
>> Note that I'd like to release 1.3.7 as soon as possible, so that
>> 1.3 people will actually be able to read 1.4 files.
Bennett> Note that I still cannot compile 1.3.7
On Jan 4, 2006, at 11:08 AM, Jean-Marc Lasgouttes wrote:
Bennett> Note that I still cannot compile 1.3.7 on Mac (Nor, at
Bennett> this point, 1.4.0.)
Note that you can compile it, but it does not run ;)
Thbpbpthpt!
This is one of the main things that makes 1.3.7 wait, and I have run
> > Also, if you keep the extension to ".lyx", you are going to overwrite
> > the file. What about exporting to ".lyx13"?
>
> Fine with me.
But a more common approach is that the user is prompted for a new filename.
Bo
Martin Vermeer wrote:
I believe bug 822 is fixed.
Is 1561 still major? Was partly fixed by Andre.
Are these (and 2155) the only major bugs left for 1.4.0?
and 1656.
Cf. the list of open, non-fixedintrunk bugs targeted to 1.4.0:
http://tinyurl.com/7qacq
I think bug 2019 deserves your special
On Mon, Jan 02, 2006 at 09:21:09AM +0100, Juergen Spitzmueller wrote:
Martin Vermeer wrote:
I believe bug 822 is fixed.
Is 1561 still major? Was partly fixed by Andre.
Are these (and 2155) the only major bugs left for 1.4.0?
and 1656.
I remember that this can be fixed, but in a way
Martin Vermeer wrote:
I think bug 2019 deserves your special attendance.
Hmmm... perhaps the remark in insetcharstyle.C:draw:
// I don't understand why the above .reduce and .realize aren't
//needed, or even wanted, here. It just works. -- MV 10.04.2005
isn't quite true... could you have
On Mon, Jan 02, 2006 at 10:42:58AM +0100, Juergen Spitzmueller wrote:
Martin Vermeer wrote:
I think bug 2019 deserves your special attendance.
Hmmm... perhaps the remark in insetcharstyle.C:draw:
// I don't understand why the above .reduce and .realize aren't
//needed, or even
On Mon, Jan 02, 2006 at 10:42:58AM +0100, Juergen Spitzmueller wrote:
Martin Vermeer wrote:
I think bug 2019 deserves your special attendance.
Hmmm... perhaps the remark in insetcharstyle.C:draw:
// I don't understand why the above .reduce and .realize aren't
//needed, or even
On Monday 02 January 2006 10:15, Martin Vermeer wrote:
That having been said, obviously *some* font attributes should appear
both on-screen and in output. My understanding was that, for LaTeX use,
charstyles were for things like Emph and Noun. They should not use
any coloured representation
On Mon, Jan 02, 2006 at 10:42:58AM +0100, Juergen Spitzmueller wrote:
Martin Vermeer wrote:
I think bug 2019 deserves your special attendance.
Hmmm... perhaps the remark in insetcharstyle.C:draw:
// I don't understand why the above .reduce and .realize aren't
//needed, or even
Martin Vermeer wrote:
Actually I don't dare to touch this stuff. The whole font architecture
needs an overhaul/simplification. E.g., there are two different
getFonts, one in lyxtext (for display) and one in paragraph (for
latexing).
If it is too complicated or risky to fix this stuff now, we
On Mon, Jan 02, 2006 at 01:01:46PM +0100, Juergen Spitzmueller wrote:
Martin Vermeer wrote:
Actually I don't dare to touch this stuff. The whole font architecture
needs an overhaul/simplification. E.g., there are two different
getFonts, one in lyxtext (for display) and one in paragraph (for
On Mon, Jan 02, 2006 at 03:30:21PM +0200, Martin Vermeer wrote:
On Mon, Jan 02, 2006 at 01:01:46PM +0100, Juergen Spitzmueller wrote:
Martin Vermeer wrote:
Actually I don't dare to touch this stuff. The whole font architecture
needs an overhaul/simplification. E.g., there are two
Martin Vermeer wrote:
Actually I would put it differently: you are not supposed to mix
character styles and font attributes :-)
My idea with charstyles has always been, longer term, to become a
logical replacement for visual font attributes. In XML they represent
elements; in LaTeX my idea
On Mon, Jan 02, 2006 at 05:39:52PM +0100, Juergen Spitzmueller wrote:
Martin Vermeer wrote:
...
This sounds very reasonable to me.
Perhaps you could add this explanation to the bug report. IIRC there is also
another bug involved which will be fixed by your #2015-patch.
I propose to move
Martin Vermeer wrote:
Perhaps this should be called an enhancement request and get its own bug
number.
perhaps.
Now convince HIM to put the #2015-fix in ;-)
Which of them? ;-)
Lars or Gullik. Jean and Marc have already expressed their principal
accordance on bugzilla IIRC.
Jür gen
Juergen Spitzmueller wrote:
Martin Vermeer wrote:
Perhaps this should be called an enhancement request and get its own bug
number.
perhaps.
Now convince HIM to put the #2015-fix in ;-)
Which of them? ;-)
Lars or Gullik. Jean and Marc have already expressed their principal
On Monday 02 January 2006 17:41, Herbert Voss wrote:
uuh, this causes an error!
\tabular{lr}
Jür gen
\endtabular
You are really a magician, splitting Jürgen in half. ;-)
and don't forget \usepackage[latin9]{inputenc} ... :-)
We are very modest, in this case 1 is enough. ;-)
Herbert
On Mon, Jan 02, 2006 at 06:17:31PM +0200, Martin Vermeer wrote:
...
Actually I would put it differently: you are not supposed to mix
character styles and font attributes :-)
My idea with charstyles has always been, longer term, to become a
logical replacement for visual font attributes.
Martin Vermeer wrote:
> I believe bug 822 is fixed.
> Is 1561 still major? Was partly fixed by Andre.
>
> Are these (and 2155) the only major bugs left for 1.4.0?
and 1656.
Cf. the list of open, non-fixedintrunk bugs targeted to 1.4.0:
http://tinyurl.com/7qacq
I think bug 2019 deserves your
On Mon, Jan 02, 2006 at 09:21:09AM +0100, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
> > I believe bug 822 is fixed.
> > Is 1561 still major? Was partly fixed by Andre.
> >
> > Are these (and 2155) the only major bugs left for 1.4.0?
>
> and 1656.
I remember that this can be fixed, but
Martin Vermeer wrote:
> > I think bug 2019 deserves your special attendance.
>
> Hmmm... perhaps the remark in insetcharstyle.C:draw:
>
> // I don't understand why the above .reduce and .realize aren't
> //needed, or even wanted, here. It just works. -- MV 10.04.2005
>
> isn't quite true... could
On Mon, Jan 02, 2006 at 10:42:58AM +0100, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
> > > I think bug 2019 deserves your special attendance.
> >
> > Hmmm... perhaps the remark in insetcharstyle.C:draw:
> >
> > // I don't understand why the above .reduce and .realize aren't
> > //needed,
On Mon, Jan 02, 2006 at 10:42:58AM +0100, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
> > > I think bug 2019 deserves your special attendance.
> >
> > Hmmm... perhaps the remark in insetcharstyle.C:draw:
> >
> > // I don't understand why the above .reduce and .realize aren't
> > //needed,
On Monday 02 January 2006 10:15, Martin Vermeer wrote:
> That having been said, obviously *some* font attributes should appear
> both on-screen and in output. My understanding was that, for LaTeX use,
> charstyles were for things like Emph and Noun. They should not use
> any coloured
On Mon, Jan 02, 2006 at 10:42:58AM +0100, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
> > > I think bug 2019 deserves your special attendance.
> >
> > Hmmm... perhaps the remark in insetcharstyle.C:draw:
> >
> > // I don't understand why the above .reduce and .realize aren't
> > //needed,
Martin Vermeer wrote:
> Actually I don't dare to touch this stuff. The whole font architecture
> needs an overhaul/simplification. E.g., there are two different
> getFonts, one in lyxtext (for display) and one in paragraph (for
> latexing).
If it is too complicated or risky to fix this stuff now,
On Mon, Jan 02, 2006 at 01:01:46PM +0100, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
> > Actually I don't dare to touch this stuff. The whole font architecture
> > needs an overhaul/simplification. E.g., there are two different
> > getFonts, one in lyxtext (for display) and one in
On Mon, Jan 02, 2006 at 03:30:21PM +0200, Martin Vermeer wrote:
> On Mon, Jan 02, 2006 at 01:01:46PM +0100, Juergen Spitzmueller wrote:
> > Martin Vermeer wrote:
> > > Actually I don't dare to touch this stuff. The whole font architecture
> > > needs an overhaul/simplification. E.g., there are two
Martin Vermeer wrote:
> Actually I would put it differently: you are not supposed to mix
> character styles and font attributes :-)
>
> My idea with charstyles has always been, longer term, to become a
> logical replacement for visual font attributes. In XML they represent
> "elements"; in LaTeX
On Mon, Jan 02, 2006 at 05:39:52PM +0100, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
...
> This sounds very reasonable to me.
> Perhaps you could add this explanation to the bug report. IIRC there is also
> another bug involved which will be fixed by your #2015-patch.
>
> I propose
Martin Vermeer wrote:
> Perhaps this should be called an enhancement request and get its own bug
> number.
perhaps.
> > Now convince HIM to put the #2015-fix in ;-)
>
> Which of them? ;-)
Lars or Gullik. Jean and Marc have already expressed their principal
accordance on bugzilla IIRC.
Jür &
Juergen Spitzmueller wrote:
Martin Vermeer wrote:
Perhaps this should be called an enhancement request and get its own bug
number.
perhaps.
Now convince HIM to put the #2015-fix in ;-)
Which of them? ;-)
Lars or Gullik. Jean and Marc have already expressed their principal
On Monday 02 January 2006 17:41, Herbert Voss wrote:
> uuh, this causes an error!
>
> \tabular{lr}
> Jür & gen
> \endtabular
You are really a magician, splitting Jürgen in half. ;-)
> and don't forget \usepackage[latin9]{inputenc} ... :-)
We are very modest, in this case 1 is enough. ;-)
>
On Mon, Jan 02, 2006 at 06:17:31PM +0200, Martin Vermeer wrote:
...
> Actually I would put it differently: you are not supposed to mix
> character styles and font attributes :-)
>
> My idea with charstyles has always been, longer term, to become a
> logical replacement for visual font
101 - 200 of 202 matches
Mail list logo