On Fri, Nov 01, 2002 at 01:40:10PM +0800, Rod Pinna wrote:
In the qt version of 130, the pulldown list for included text shows the
text as verbatim, even though in 122, the doc was saved with the
included text as included.
Thanks, fixed in my tree.
wanting a rock to wind a piece of string
John Levon [EMAIL PROTECTED] writes:
| wanting a rock to wind a piece of string around,
That is a reference I do not get...
--
Lgb
On Fri, Nov 01, 2002 at 01:40:10PM +0800, Rod Pinna wrote:
> In the qt version of 130, the pulldown list for included text shows the
> text as "verbatim", even though in 122, the doc was saved with the
> included text as "included".
Thanks, fixed in my tree.
wanting a rock to wind a piece of
John Levon <[EMAIL PROTECTED]> writes:
| wanting a rock to wind a piece of string around,
That is a reference I do not get...
--
Lgb
In the qt version of 130, the pulldown list for included text shows the
text as verbatim, even though in 122, the doc was saved with the
included text as included.
It seems to format OK for latex though.
Rod
_
rod | Beneath the
In the qt version of 130, the pulldown list for included text shows the
text as "verbatim", even though in 122, the doc was saved with the
included text as "included".
It seems to format OK for latex though.
Rod
_
rod | "Beneath
On Thu, Oct 17, 2002 at 10:52:15AM +0800, John Summerfield wrote:
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting instructions
in Help-Introduction and send us a bug report, if necessary. Thanks !
Bye.
Aborted
It would be helpful to get the
On Thu, Oct 17, 2002 at 10:52:15AM +0800, John Summerfield wrote:
> lyx: SIGSEGV signal caught
> Sorry, you have found a bug in LyX. Please read the bug-reporting instructions
> in Help->Introduction and send us a bug report, if necessary. Thanks !
> Bye.
> Aborted
It would be helpful to get
I don't have web access ATM.
Here's the version:
[summer@numbat summer]$ rpm -qif /usr/bin/lyx
Name: lyx Relocations: /usr
Version : 1.2.0 Vendor: (none)
Release : 1 Build Date: Sat 17 Aug 2002
05:30
I don't have web access ATM.
Here's the version:
[summer@numbat summer]$ rpm -qif /usr/bin/lyx
Name: lyx Relocations: /usr
Version : 1.2.0 Vendor: (none)
Release : 1 Build Date: Sat 17 Aug 2002
05:30
Garst R. Reese [EMAIL PROTECTED] writes:
| Upgrading A's box to xforms-1.0RC4 cured the problem.
Ok, then I'll consider this case closed.
--
Lgb
"Garst R. Reese" <[EMAIL PROTECTED]> writes:
| Upgrading A's box to xforms-1.0RC4 cured the problem.
Ok, then I'll consider this case closed.
--
Lgb
A. A. Reese [EMAIL PROTECTED] writes:
| This is a reproducable crash that Alice found. The file has a number of
| minipages, some with graphics. It is a newsletter using multicol. Open
| it up, use PgDn key to end of file, then PgUp until it crashes. Below is
| a partial listing of lyx -dbg key.
"A. A. Reese" <[EMAIL PROTECTED]> writes:
| This is a reproducable crash that Alice found. The file has a number of
| minipages, some with graphics. It is a newsletter using multicol. Open
| it up, use PgDn key to end of file, then PgUp until it crashes. Below is
| a partial listing of lyx -dbg
This is a reproducable crash that Alice found. The file has a number of
minipages, some with graphics. It is a newsletter using multicol. Open
it up, use PgDn key to end of file, then PgUp until it crashes. Below is
a partial listing of lyx -dbg key.
Please don't cc this address, I'll get the
This is a reproducable crash that Alice found. The file has a number of
minipages, some with graphics. It is a newsletter using multicol. Open
it up, use PgDn key to end of file, then PgUp until it crashes. Below is
a partial listing of lyx -dbg key.
Please don't cc this address, I'll get the
Anyone build LyX 1.2.x successfully on HP-UX 11i with GCC 3.1.1 or
3.2? With 3.2, I get errors like:
typeinfo name for MathStackrelInset(first referenced in
mathed/.libs/libmathed.a(formulabase.o)) (data)
ControlInsetInsetGraphics, InsetGraphicsParams::updateSlot(bool)
(first referenced in
Anyone build LyX 1.2.x successfully on HP-UX 11i with GCC 3.1.1 or
3.2? With 3.2, I get errors like:
typeinfo name for MathStackrelInset(first referenced in
mathed/.libs/libmathed.a(formulabase.o)) (data)
ControlInset::updateSlot(bool)
(first referenced
Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes:
Juergen Jean-Marc Lasgouttes wrote:
If there is something you really want in 1.2.1, send a (well
tested) patch.
Juergen I've just discovered that you cleaned up the bindings for
Juergen starred sectioning commands. Well, I want that
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Jean-Marc Lasgouttes wrote:
>> If there is something you really want in 1.2.1, send a (well
>> tested) patch.
Juergen> I've just discovered that you cleaned up the bindings for
Juergen> starred sectioning commands.
Herbert == Herbert Voss [EMAIL PROTECTED] writes:
Herbert Jean-Marc Lasgouttes wrote:
If somebody does it for me, I will consider to apply the patch. I
do not have much time to do it myself. Anyway, I already would like
to release 1.2.1 pretty soon, so some features have to be
postponed. If
Jean-Marc Lasgouttes wrote:
If there is something you really want in 1.2.1, send a (well tested)
patch.
I've just discovered that you cleaned up the bindings for starred sectioning
commands. Well, I want that for german too ;-)
Here's a patch (against 1.2.1cvs). It's not really important, but
On Thu, Aug 15, 2002 at 06:14:30PM +0200, Juergen Spitzmueller wrote:
I've just discovered that you cleaned up the bindings for starred sectioning
commands. Well, I want that for german too ;-)
I wonder who's got the idea of localized key bindings. That's crazy to use
if you often switch
Andre Poenitz [EMAIL PROTECTED] writes:
| On Thu, Aug 15, 2002 at 06:14:30PM +0200, Juergen Spitzmueller wrote:
I've just discovered that you cleaned up the bindings for starred sectioning
commands. Well, I want that for german too ;-)
| I wonder who's got the idea of localized key bindings.
On Thu, Aug 15, 2002 at 06:30:25PM +0200, Andre Poenitz wrote:
I wonder who's got the idea of localized key bindings. That's crazy to use
if you often switch languanges. IMO formating paragraphs it should be M-p
for German too, even if 'Absatz' does not has a 'p'
You're on thin ice here.
On Thu, Aug 15, 2002 at 05:38:28PM +0100, John Levon wrote:
You're on thin ice here. Being pathetically mono-lingual I often imagine
if Atari hadn't screwed themselves and somehow most software was
primarily German. I can tell you one thing: M-b for Paragraph would
infuriate me, and it would
On Thu, Aug 15, 2002 at 06:49:03PM +0200, Andre Poenitz wrote:
Reminds me of some (English) guy who didn't like foreign movies (even those
translated to English) because he was (unconciously) used to reading lips.
There's nothing worse than dubbed films anyway. Subtitles !
Believe me, you
John Levon [EMAIL PROTECTED] writes:
| On Thu, Aug 15, 2002 at 06:49:03PM +0200, Andre Poenitz wrote:
Reminds me of some (English) guy who didn't like foreign movies (even those
translated to English) because he was (unconciously) used to reading lips.
| There's nothing worse than dubbed
Andre Poenitz wrote:
I wonder who's got the idea of localized key bindings. That's crazy to use
if you often switch languanges. IMO formating paragraphs it should be M-p
for German too, even if 'Absatz' does not has a 'p'
I don't care, as long as they are memorizable and not too
> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
Herbert> Jean-Marc Lasgouttes wrote:
>> If somebody does it for me, I will consider to apply the patch. I
>> do not have much time to do it myself. Anyway, I already would like
>> to release 1.2.1 pretty soon, so some features have to
Jean-Marc Lasgouttes wrote:
> If there is something you really want in 1.2.1, send a (well tested)
> patch.
I've just discovered that you cleaned up the bindings for starred sectioning
commands. Well, I want that for german too ;-)
Here's a patch (against 1.2.1cvs). It's not really important,
On Thu, Aug 15, 2002 at 06:14:30PM +0200, Juergen Spitzmueller wrote:
> I've just discovered that you cleaned up the bindings for starred sectioning
> commands. Well, I want that for german too ;-)
I wonder who's got the idea of localized key bindings. That's crazy to use
if you often switch
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Thu, Aug 15, 2002 at 06:14:30PM +0200, Juergen Spitzmueller wrote:
>> I've just discovered that you cleaned up the bindings for starred sectioning
>> commands. Well, I want that for german too ;-)
>
| I wonder who's got the idea of localized key
On Thu, Aug 15, 2002 at 06:30:25PM +0200, Andre Poenitz wrote:
> I wonder who's got the idea of localized key bindings. That's crazy to use
> if you often switch languanges. IMO formating paragraphs it should be M-p
> for German too, even if 'Absatz' does not has a 'p'
You're on thin ice
On Thu, Aug 15, 2002 at 05:38:28PM +0100, John Levon wrote:
> You're on thin ice here. Being pathetically mono-lingual I often imagine
> if Atari hadn't screwed themselves and somehow most software was
> primarily German. I can tell you one thing: M-b for "Paragraph" would
> infuriate me, and it
On Thu, Aug 15, 2002 at 06:49:03PM +0200, Andre Poenitz wrote:
> Reminds me of some (English) guy who didn't like foreign movies (even those
> translated to English) because he was (unconciously) used to reading lips.
There's nothing worse than dubbed films anyway. Subtitles !
> Believe me,
John Levon <[EMAIL PROTECTED]> writes:
| On Thu, Aug 15, 2002 at 06:49:03PM +0200, Andre Poenitz wrote:
>
>> Reminds me of some (English) guy who didn't like foreign movies (even those
>> translated to English) because he was (unconciously) used to reading lips.
>
| There's nothing worse than
Andre Poenitz wrote:
> I wonder who's got the idea of localized key bindings. That's crazy to use
> if you often switch languanges. IMO formating paragraphs it should be M-p
> for German too, even if 'Absatz' does not has a 'p'
I don't care, as long as they are memorizable and not too
Lars Gullik Bjønnes wrote:
John Levon [EMAIL PROTECTED] writes:
| On Mon, Aug 12, 2002 at 05:42:19PM +0200, Lars Gullik Bjønnes wrote:
For the manual fontchanges we automatically create a unnamed
CharacterStyle for it. (some magic internal name)
| I'd rather not allow such manual
Dekel == Dekel Tsur [EMAIL PROTECTED] writes:
4) Bookmarks do not work inside an inset.
What is a bookmark?
Dekel It allows you to save a position in the document and return to
Dekel it later.
Note that this is a bug entered in bugzilla (bug 384). Could you have
a quick look at it? It is
fdesign it couldn't find the X libraries. I patched the
Peter fdesign/Makefile with a -L/usr/X11R6/lib and then it worked
Peter fine.
Peter I untarred the lyx-1.2.0 source again and ran configure ala`:
Sorry, xforms 1.0 is not supported by lyx 1.2.0. It should work when
1.2.1 is released.
JMarc
Mike == Mike Fabian [EMAIL PROTECTED] writes:
Mike But this patch is really only a hack and certainly should not
Mike applied like that to the upstream version of LyX. I only
Mike attached it to show what the problem is. There must be a better
Mike solution.
Yes, but I really do not know which
Philipp == Philipp Sasse [EMAIL PROTECTED] writes:
Philipp Hello, (sorry I didn't find where this is documented ...)
It is not.
Philipp I'm used to applying lots of changes to my po/xx.po file
Philipp before building lyx. But as with 1.2.0 the changes are
Philipp ignored. It seems, the xx.gmo
Lars Gullik Bjønnes wrote:
>
> John Levon <[EMAIL PROTECTED]> writes:
>
> | On Mon, Aug 12, 2002 at 05:42:19PM +0200, Lars Gullik Bjønnes wrote:
> >
> >> For the manual fontchanges we automatically create a unnamed
> >> CharacterStyle for it. (some magic internal name)
> >
> | I'd rather not
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
>> > 4) Bookmarks do not work inside an inset.
>>
>> What is a bookmark?
Dekel> It allows you to save a position in the document and return to
Dekel> it later.
Note that this is a bug entered in bugzilla (bug 384). Could you have
a quick
> Mostly this went well except when the make tried to link
Peter> fdesign it couldn't find the X libraries. I patched the
Peter> fdesign/Makefile with a "-L/usr/X11R6/lib" and then it worked
Peter> fine.
Peter> I untarred the lyx-1.2.0 source again and ran configure ala`:
> "Mike" == Mike Fabian <[EMAIL PROTECTED]> writes:
Mike> But this patch is really only a hack and certainly should not
Mike> applied like that to the upstream version of LyX. I only
Mike> attached it to show what the problem is. There must be a better
Mike> solution.
Yes, but I really do
>>>>> "Philipp" == Philipp Sasse <[EMAIL PROTECTED]> writes:
Philipp> Hello, (sorry I didn't find where this is documented ...)
It is not.
Philipp> I'm used to applying lots of changes to my po/xx.po file
Philipp> before building lyx. But as wit
On Sun, Aug 11, 2002 at 08:15:04PM +0300, Dekel Tsur wrote:
On Thu, Aug 08, 2002 at 08:35:30AM +0200, Andre Poenitz wrote:
But using insets have other problems.
The most important one is that an inset cannot be broken across lines
(e.g.
+---
foo foo foo |bar bar
---+
On Sun, Aug 11, 2002 at 11:52:09PM +0300, Dekel Tsur wrote:
The cleanest way is perhaps with insets, but this will require a much
improved handling of insets: For example, allowing an inset to break over
two lines. It will be a long time before we can have this, if at all.
Could people
On Mon, Aug 12, 2002 at 12:59:30AM +0100, John Levon wrote:
| A SimpleInset would only contain plain characters _or_ (as in
| exclusive) insets.
|
| what about space and accent insets ?
a space could be regarded as a regular character... an accent inset
would be regarded as a
On Sun, Aug 11, 2002 at 10:23:09PM +0200, Lars Gullik Bjønnes wrote:
I think we should first of all have a discussion on how to implement
character styles as cleanly as possible.
Discussion opened?
Ok: Character styles should be done by using something similar to
MathFontInsets.
John == John Levon [EMAIL PROTECTED] writes:
John I'm not sure if it's still valid though. And in fact, I'm
John surprised that fixincludes in gcc doesn't fix this problem. It
John may be old cruft.
fixincludes does not touch the x11 headers, AFAIK. And I would think
that things like solaris
On Mon, Aug 12, 2002 at 09:50:55AM +0200, Andre Poenitz wrote:
Ok: Character styles should be done by using something similar to
MathFontInsets.
Regular font (i.e. commands like \textbf) should be implemented like character
styles, so this means removing the font list from the paragraph
On Mon, Aug 12, 2002 at 06:18:55PM +0300, Dekel Tsur wrote:
Ok: Character styles should be done by using something similar to
MathFontInsets.
Regular font (i.e. commands like \textbf) should be implemented like character
styles, so this means removing the font list from the paragraph
On Mon, Aug 12, 2002 at 05:40:56PM +0200, Andre Poenitz wrote:
Other disadvantages:
1) Current inset code doesn't allow inheritance of font settings from the
current paragraph or from parent inset.
For example, if I have a paragraph which set the font to italics
(e.g. a Theorem
On Mon, Aug 12, 2002 at 01:46:06AM +0200, Lars Gullik Bjønnes wrote:
| p.s. fwiw I agree it is worth waiting a bit longer to do this right. We
| have too many craply-implemented features in lyx and we suffer for
| it
right.
The main problem with badly implemented features, like
On Mon, Aug 12, 2002 at 07:11:55PM +0300, Dekel Tsur wrote:
It allows you to save a position in the document and return to it later.
No big deal I'd say. Something like an invisible label that does not get
saved...
I am not talking about _insets_, I am talking about taking math font
insets
On Mon, Aug 12, 2002 at 05:42:19PM +0200, Lars Gullik Bjønnes wrote:
For the manual fontchanges we automatically create a unnamed
CharacterStyle for it. (some magic internal name)
I'd rather not allow such manual changes. A user must create a new name
if they want bold italic text, even if
John Levon [EMAIL PROTECTED] writes:
| On Mon, Aug 12, 2002 at 05:42:19PM +0200, Lars Gullik Bjønnes wrote:
For the manual fontchanges we automatically create a unnamed
CharacterStyle for it. (some magic internal name)
| I'd rather not allow such manual changes. A user must create a new name
On Sun, Aug 11, 2002 at 08:15:04PM +0300, Dekel Tsur wrote:
> On Thu, Aug 08, 2002 at 08:35:30AM +0200, Andre Poenitz wrote:
> But using insets have other problems.
> The most important one is that an inset cannot be broken across lines
> (e.g.
> +---
> foo foo foo |bar bar
> ---+
On Sun, Aug 11, 2002 at 11:52:09PM +0300, Dekel Tsur wrote:
> The cleanest way is perhaps with insets, but this will require a much
> improved handling of insets: For example, allowing an inset to break over
> two lines. It will be a long time before we can have this, if at all.
Could people
On Mon, Aug 12, 2002 at 12:59:30AM +0100, John Levon wrote:
> > | > A SimpleInset would only contain plain characters _or_ (as in
> > | > exclusive) insets.
> > |
> > | what about space and accent insets ?
> >
> > a space could be regarded as a regular character... an accent inset
> > would be
On Sun, Aug 11, 2002 at 10:23:09PM +0200, Lars Gullik Bjønnes wrote:
> I think we should first of all have a discussion on how to implement
> character styles as cleanly as possible.
Discussion opened?
Ok: Character styles should be done by using something similar to
MathFontInsets.
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> I'm not sure if it's still valid though. And in fact, I'm
John> surprised that fixincludes in gcc doesn't fix this problem. It
John> may be old cruft.
fixincludes does not touch the x11 headers, AFAIK. And I would think
that things
On Mon, Aug 12, 2002 at 09:50:55AM +0200, Andre Poenitz wrote:
>
> Ok: Character styles should be done by using something similar to
> MathFontInsets.
Regular font (i.e. commands like \textbf) should be implemented like character
styles, so this means removing the font list from the paragraph
On Mon, Aug 12, 2002 at 06:18:55PM +0300, Dekel Tsur wrote:
> > Ok: Character styles should be done by using something similar to
> > MathFontInsets.
>
> Regular font (i.e. commands like \textbf) should be implemented like character
> styles, so this means removing the font list from the
On Mon, Aug 12, 2002 at 05:40:56PM +0200, Andre Poenitz wrote:
> > Other disadvantages:
> >
> > 1) Current inset code doesn't allow inheritance of font settings from the
> > current paragraph or from parent inset.
> > For example, if I have a paragraph which set the font to italics
> > (e.g. a
On Mon, Aug 12, 2002 at 01:46:06AM +0200, Lars Gullik Bjønnes wrote:
>
> | p.s. fwiw I agree it is worth waiting a bit longer to do this right. We
> | have too many craply-implemented features in lyx and we suffer for
> | it
>
> right.
The main problem with badly implemented features, like
On Mon, Aug 12, 2002 at 07:11:55PM +0300, Dekel Tsur wrote:
> It allows you to save a position in the document and return to it later.
No big deal I'd say. Something like an invisible label that does not get
saved...
> > I am not talking about _insets_, I am talking about "taking math font
> >
On Mon, Aug 12, 2002 at 05:42:19PM +0200, Lars Gullik Bjønnes wrote:
> For the manual fontchanges we automatically create a unnamed
> CharacterStyle for it. (some magic internal name)
I'd rather not allow such manual changes. A user must create a new name
if they want bold italic text, even if
John Levon <[EMAIL PROTECTED]> writes:
| On Mon, Aug 12, 2002 at 05:42:19PM +0200, Lars Gullik Bjønnes wrote:
>
>> For the manual fontchanges we automatically create a unnamed
>> CharacterStyle for it. (some magic internal name)
>
| I'd rather not allow such manual changes. A user must create a
Is -no-cpp-precomp really necessary ? Why ?
For this particular option, I have confirmed that the Fink project also
found it necessary to use this. In their 1.2.0 configuration, this option
is selected as well.
Given that they are now providing 1.2.0 in their current/unstable setup,
perhaps
On Thu, Aug 08, 2002 at 08:34:21AM +0200, Andre Poenitz wrote:
On Wed, Aug 07, 2002 at 10:53:36PM +0300, Dekel Tsur wrote:
I think it is easy to implement them on top of current math text (without
the user being able to tell that he's in math) But I would not do the
UI part, jsut the
On Thu, Aug 08, 2002 at 08:35:30AM +0200, Andre Poenitz wrote:
On Wed, Aug 07, 2002 at 11:24:55PM +0300, Dekel Tsur wrote:
Actually, it think it possible to implement character styles by just
few modifications to lyxfont.C (and no changes to the data structures).
These might not allow
On Wed, Aug 07, 2002 at 11:26:00PM +0200, Lars Gullik Bjønnes wrote:
|
| Actually, it think it possible to implement character styles by just
| few modifications to lyxfont.C (and no changes to the data structures).
| These might not allow nesting of styles, but this can wait for a better
|
Dekel Tsur [EMAIL PROTECTED] writes:
| On Wed, Aug 07, 2002 at 11:26:00PM +0200, Lars Gullik Bjønnes wrote:
| |
| | Actually, it think it possible to implement character styles by just
| | few modifications to lyxfont.C (and no changes to the data structures).
| | These might not allow
On Sun, Aug 11, 2002 at 09:42:03PM +0200, Lars Gullik Bjønnes wrote:
Dekel Tsur [EMAIL PROTECTED] writes:
| The font structs are already too big.
|
| We are already implementing Character Styles in lyxfont.C (emph,
| noun).
And neither om them should be in lyxfont.
So where do you want
Dekel Tsur [EMAIL PROTECTED] writes:
| On Sun, Aug 11, 2002 at 09:42:03PM +0200, Lars Gullik Bjønnes wrote:
| Dekel Tsur [EMAIL PROTECTED] writes:
| | The font structs are already too big.
| |
| | We are already implementing Character Styles in lyxfont.C (emph,
| | noun).
|
| And
On Sun, Aug 11, 2002 at 10:23:09PM +0200, Lars Gullik Bjønnes wrote:
| Anyway, if I create a patch for character styles using lyxfont which
| doesn't make it more complex than it is now, would you accept it?
I certanly would like not too...
When the goal is to simplifying lyxfont (among
Dekel Tsur [EMAIL PROTECTED] writes:
| On Sun, Aug 11, 2002 at 10:23:09PM +0200, Lars Gullik Bjønnes wrote:
| | Anyway, if I create a patch for character styles using lyxfont which
| | doesn't make it more complex than it is now, would you accept it?
|
| I certanly would like not too...
|
On Sun, Aug 11, 2002 at 11:20:53PM +0200, Lars Gullik Bjønnes wrote:
A SimpleInset would only contain plain characters _or_ (as in
exclusive) insets.
what about space and accent insets ?
regards
john
p.s. fwiw I agree it is worth waiting a bit longer to do this right. We
have too many
John Levon [EMAIL PROTECTED] writes:
| On Sun, Aug 11, 2002 at 11:20:53PM +0200, Lars Gullik Bjønnes wrote:
|
| A SimpleInset would only contain plain characters _or_ (as in
| exclusive) insets.
|
| what about space and accent insets ?
a space could be regarded as a regular character... an
On Mon, Aug 12, 2002 at 01:46:06AM +0200, Lars Gullik Bjønnes wrote:
| A SimpleInset would only contain plain characters _or_ (as in
| exclusive) insets.
|
| what about space and accent insets ?
a space could be regarded as a regular character... an accent inset
would be regarded as a
John Levon [EMAIL PROTECTED] writes:
| On Mon, Aug 12, 2002 at 01:46:06AM +0200, Lars Gullik Bjønnes wrote:
|
| | A SimpleInset would only contain plain characters _or_ (as in
| | exclusive) insets.
| |
| | what about space and accent insets ?
|
| a space could be regarded as a
> Is -no-cpp-precomp really necessary ? Why ?
For this particular option, I have confirmed that the Fink project also
found it necessary to use this. In their 1.2.0 configuration, this option
is selected as well.
Given that they are now providing 1.2.0 in their current/unstable setup,
perh
On Thu, Aug 08, 2002 at 08:34:21AM +0200, Andre Poenitz wrote:
> On Wed, Aug 07, 2002 at 10:53:36PM +0300, Dekel Tsur wrote:
> > > I think it is easy to implement them on top of current math text (without
> > > the user being able to tell that he's in "math") But I would not do the
> > > UI part,
On Thu, Aug 08, 2002 at 08:35:30AM +0200, Andre Poenitz wrote:
> On Wed, Aug 07, 2002 at 11:24:55PM +0300, Dekel Tsur wrote:
> > Actually, it think it possible to implement character styles by just
> > few modifications to lyxfont.C (and no changes to the data structures).
> > These might not
On Wed, Aug 07, 2002 at 11:26:00PM +0200, Lars Gullik Bjønnes wrote:
> |
> | Actually, it think it possible to implement character styles by just
> | few modifications to lyxfont.C (and no changes to the data structures).
> | These might not allow nesting of styles, but this can wait for a
Dekel Tsur <[EMAIL PROTECTED]> writes:
| On Wed, Aug 07, 2002 at 11:26:00PM +0200, Lars Gullik Bjønnes wrote:
| > |
| > | Actually, it think it possible to implement character styles by just
| > | few modifications to lyxfont.C (and no changes to the data structures).
| > | These might not
On Sun, Aug 11, 2002 at 09:42:03PM +0200, Lars Gullik Bjønnes wrote:
> Dekel Tsur <[EMAIL PROTECTED]> writes:
> | > The font structs are already too big.
> |
> | We are already implementing Character Styles in lyxfont.C (emph,
> | noun).
>
> And neither om them should be in lyxfont.
So where
Dekel Tsur <[EMAIL PROTECTED]> writes:
| On Sun, Aug 11, 2002 at 09:42:03PM +0200, Lars Gullik Bjønnes wrote:
| > Dekel Tsur <[EMAIL PROTECTED]> writes:
| > | > The font structs are already too big.
| > |
| > | We are already implementing Character Styles in lyxfont.C (emph,
| > | noun).
| >
|
On Sun, Aug 11, 2002 at 10:23:09PM +0200, Lars Gullik Bjønnes wrote:
> | Anyway, if I create a patch for character styles using lyxfont which
> | doesn't make it more complex than it is now, would you accept it?
>
> I certanly would like not too...
>
> When the goal is to simplifying lyxfont
Dekel Tsur <[EMAIL PROTECTED]> writes:
| On Sun, Aug 11, 2002 at 10:23:09PM +0200, Lars Gullik Bjønnes wrote:
| > | Anyway, if I create a patch for character styles using lyxfont which
| > | doesn't make it more complex than it is now, would you accept it?
| >
| > I certanly would like not
On Sun, Aug 11, 2002 at 11:20:53PM +0200, Lars Gullik Bjønnes wrote:
> A SimpleInset would only contain plain characters _or_ (as in
> exclusive) insets.
what about space and accent insets ?
regards
john
p.s. fwiw I agree it is worth waiting a bit longer to do this right. We
have too many
John Levon <[EMAIL PROTECTED]> writes:
| On Sun, Aug 11, 2002 at 11:20:53PM +0200, Lars Gullik Bjønnes wrote:
|
| > A SimpleInset would only contain plain characters _or_ (as in
| > exclusive) insets.
|
| what about space and accent insets ?
a space could be regarded as a regular character...
On Mon, Aug 12, 2002 at 01:46:06AM +0200, Lars Gullik Bjønnes wrote:
> | > A SimpleInset would only contain plain characters _or_ (as in
> | > exclusive) insets.
> |
> | what about space and accent insets ?
>
> a space could be regarded as a regular character... an accent inset
> would be
John Levon <[EMAIL PROTECTED]> writes:
| On Mon, Aug 12, 2002 at 01:46:06AM +0200, Lars Gullik Bjønnes wrote:
|
| > | > A SimpleInset would only contain plain characters _or_ (as in
| > | > exclusive) insets.
| > |
| > | what about space and accent insets ?
| >
| > a space could be regarded
Hi!
I am happy to report that I have identified and documented the issues to
get Lyx 1.2.0 built on Mac OS X. I realize that the Fink project will get
it working as well; however, I have some doubts that they are
communicating all the issues to the Lyx team to ensure that future
releases build
On Sat, Aug 10, 2002 at 04:01:06PM -0500, George K. Thiruvathukal wrote:
1.1.6, which had the same build problems). I hope that my feedback will be
helpful to you and that you can modify your configure.in (where most all
of the problems are) so there can one day be a clean build on OS X.
It
1 - 100 of 908 matches
Mail list logo