On Fri, 19 Mar 1999 [EMAIL PROTECTED] wrote:
> Modified Files:
> lstrings.h
> Log Message:
> fixed that pesky segfault that occurred while loading files
There is still a problem with identifying some tags but for the most
part your documents will load and LyX will work. Remember old style
On Thu, 18 Mar 1999, Asger Alstrup Nielsen wrote:
> > Jose> If the external declaration says the no omiting tags are
> > Jose> allowed, then it is really needed. XML is a case where you have
> > Jose> to close all the tags, so the document is seen as a tree, the
> > Jose> DOM gives you a way t
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> Mmm, I have been pointed to
> http://cgi.din.or.jp/~kawakami/LyX/index.html
>
> Do you know about this work? Are you working on it?
No, I didn't know that. If you are not using main stream systems
like MS Windoze or Linux, some of the informatio
On Fri, 19 Mar 1999, Daniel Naber wrote:
> Hi,
Hello.
> here's an idea for a new feature for lyx 1.1:
>
> At http://www.cogsci.princeton.edu/~wn/w3wn.html you can find a huge
> database of english words which is freely available - 'wordnet'. The most
> interesting part is probably the synonyms
I should have checked if there were more emails in the thread before
sending my first response...
On Thu, 18 Mar 1999, Asger Alstrup Nielsen wrote:
> > It is not too difficult to add a check for this, I guess. It would be
> > nice if you could give me an example of a minimal program that
> > re
On Thu, 18 Mar 1999, Asger Alstrup Nielsen wrote:
> > Do we really need these 'using' statements now, except that they are
> > the ANSI way of doing things? Are there compilers that will fail to
> > find string and wstring if std:: is not explicitely given?
>
> Yes, there are compilers that fail
Hi,
here's an idea for a new feature for lyx 1.1:
At http://www.cogsci.princeton.edu/~wn/w3wn.html you can find a huge
database of english words which is freely available - 'wordnet'. The most
interesting part is probably the synonyms. It's not very difficult to
integrate this in lyx, so everybo
> It is not too difficult to add a check for this, I guess. It would be
> nice if you could give me an example of a minimal program that
> requires 'using' for std::. I could test on strings, but I'd rather
> have a more orthogonal test.
To see if the compiler supports namespace-qualification, tr
> AAN> Yes, but then we would have N times the wait of loading
> AAN> external code tables, rather than 1 time the waiting for
>
> you only need one or two, why load it if you don't need it?
Because I don't care to implement an encoding parser, just to save maybe 15k of
memory.
Also, notice
> Sectioning and toc levels are defined there only in relation to the preceding
> one. Same level, one level down, one or several levels up. The advantage here
> is: You can cut and paste, move around add or remove levels up to a maximum
of
> 12. The interior logic of those parts will always remai
I just got this report:
>When loading documents with lyxformat 10, it has a lot of trouble,
>particularly with references. COLD does not help. Here is sample Lyx code.
>After the reference (which it fails to resolve), several *sentences* are
>omitted silently from the printout.
The testfile t.
On Tue, 16 Mar 1999 13:30:39 +0100 (MET), Asger K. Alstrup Nielsen wrote:
>> > We will allow more nesting with a HeadingInset with a counter, than with
>> > position in a tree: We can only nest to the number of different
>> > pointers to Insets we have, and this is typically smaller than the ran
>> Jean-Marc Lasgouttes writes:
>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Jean-Marc Lasgouttes writes:
JL> The list looks pretty exhaustive. You could also try to
JL> translate the raw \special{...} (don't know the syntax, sorry)
JL> which does the actual f
>> Garst R Reese writes:
GRR> teTeX.9 will now do ls-R on local and personal directories. LyX
GRR> puts .cls files in a subdir tex If this was texmf/tex then the
GRR> ls-R would be shorter This applies to e.g /usr/local/share/lyx
GRR> and $HOME/.lyx/texmf/tex All that is required is add
>> Andre' Poenitz writes:
AP> A second question: Is there some special reason to use names
AP> starting with underscores? Like LyXGUI::_owner?
I have used that on _private_ variables in some classes. Helps me see
if what kind of variable I am using, especially in large funcs.
Lgb
>> Asger Alstrup Nielsen writes:
AAN> Yes, but then we would have N times the wait of loading
AAN> external code tables, rather than 1 time the waiting for
you only need one or two, why load it if you don't need it?
Lgb
Hi,
I'm using lyx 1.0.1 on my Linux 2.2.3 kernel.
I'm very happy with the easy way, to get fine layout results :-)
But on my system the C-Return in a table with fixed column widths and
multiline setting doesn`t work right.
* Hitting C-Return in the middle of a line in a cell doesn't break the
te
On Thu, 18 Mar 1999 14:33:39 +0100 (MET), Jean-Marc Lasgouttes wrote:
>> "Arnd" == Arnd Hanses <[EMAIL PROTECTED]> writes:
>
>Arnd> Hi all you bleeding edge technology loving LyXers, more exciting
>Arnd> news from xfree86.org:
>
>Arnd> Why not create a minimal LyX-loader which has to be porte
HI!
The cut'n'paste of whole tables is a bit broken:
If I cut a table that has a special width defined for one of its
columns, that information gets lost.
If I cut a table that has a special option like "@{} l", that
information gets inserted in the "width" field of the pasted table.
LyX versi
> "Arnd" == Arnd Hanses <[EMAIL PROTECTED]> writes:
Arnd> On Wed, 17 Mar 1999 16:30:19 +0100 (MET), Jean-Marc Lasgouttes
Arnd> wrote:
>> Hmm, what is the address of this OS/2 port of autoconf 2.13? The
>> original page still states 2.12.
Arnd> Well..., you may try
Arnd> http://r350.ee.ntu.e
> "Mate" == Mate Wierdl <[EMAIL PROTECTED]> writes:
Mate> It is finally up.
That's great news :)
JMarc
> "Mate" == Mate Wierdl <[EMAIL PROTECTED]> writes:
Mate> I am confused: I just noticed that
Mate> [EMAIL PROTECTED]
Mate> is a subscriber to the users' list. This means that the archive
Mate> at bioclox.bot.biologie.uni-tuebingen.de is still active (adds
Mate> new messages)---though it is
> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
Allan> Two consecutive paragraphs in an InsetEnvironment would be in
Allan> the same environment (obviously). But I think what you mean
Allan> is: can this scheme allow two consecutive environments of the
Allan> same type?
What I meant is t
> "Arnd" == Arnd Hanses <[EMAIL PROTECTED]> writes:
Arnd> Hi all you bleeding edge technology loving LyXers, more exciting
Arnd> news from xfree86.org:
Arnd> Why not create a minimal LyX-loader which has to be ported for
Arnd> one time only to any OS, you would like LyX to run, and will
Arnd
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> [How to get intelligent font changes. Allan suggests that we
Asger> map the font structure in the data representation in some way.]
Asger> I suggest that we ignore the issue in the data representation
Asger> part, and jus
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> Ask a real web designer. Or Asger, who chose the fonts. All the cvs
>> stuff is in blocks, but (at least in netscape) it's not
>> shown in a different font.
Asger> Netscape is broken. Get a real browser that understands the
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> Do we really need these 'using' statements now, except that they
>> are the ANSI way of doing things? Are there compilers that will
>> fail to find string and wstring if std:: is not explicitely given?
Asger> Yes, there are co
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> My example was not support to provide an identifier for each inset,
>> but for each inset *class*. Just a way to avoid those enums. I'm
>> not sure it makes sense, however. That's just a way to allow insets
>> unknown to the ke
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> Another example is the quote inset: it uses information from the
>> buffer (encoding, language) to determine the LaTeX output.
Asger> This is also solved the "painter way": When we ask an inset to
Asger> write some LaTeX, we p
> The current linear support relies upon recursion (at least in writing to
> files) and duplication of code to place the end markers and control
> output. If we move everything to Insets then the export routines are
> dependent upon Insets (either as member functions of the Inset or as
> multiple-
> Another example is the quote inset: it uses information from the
> buffer (encoding, language) to determine the LaTeX output.
This is also solved the "painter way": When we ask an inset to write some
LaTeX, we pass a Buffer pointer to it.
Alternatively, the Quote inset will be done a different
[How to get intelligent font changes. Allan suggests that we map the font
structure in the data representation in some way.]
I suggest that we ignore the issue in the data representation part, and just
record font changes in a linear fashion as already proposed.
Then, the problem is a problem o
> Ask a real web designer. Or Asger, who chose the fonts. All the cvs stuff is
> in blocks, but (at least in netscape) it's not shown in a different
> font.
Netscape is broken. Get a real browser that understands the specs.
Ok, you don't want to do that, so we'll have to fix it instead. I'll
> Do we really need these 'using' statements now, except that they are
> the ANSI way of doing things? Are there compilers that will fail to
> find string and wstring if std:: is not explicitely given?
Yes, there are compilers that fail without it. The case in point is the Visual
C++ compilers v
> What remains to to is provide a correct 16bit LString replacement, right?
Yes.
> Asger> We need to change all the LStrings to ordinary "string"s.
>
> I thought you wanted to keep LString? Do you mean you want to
> reintroduce them later when needed?
I want to keep LString, but only use it
> Jose> If the external declaration says the no omiting tags are
> Jose> allowed, then it is really needed. XML is a case where you have
> Jose> to close all the tags, so the document is seen as a tree, the
> Jose> DOM gives you a way to navigate the document as a tree like
> Jose> structure. S
> My example was not support to provide an identifier for each inset,
> but for each inset *class*. Just a way to avoid those enums. I'm not
> sure it makes sense, however. That's just a way to allow insets
> unknown to the kernel to register themselves.
The better way is just to use strings. Th
Hi,
I haven't copied Alan's last message but I totally support is view.
With such a scheme it would be very easy both to output docbook and xml
documents.
José
teTeX.9 will now do ls-R on local and personal directories.
LyX puts .cls files in a subdir tex
If this was texmf/tex then the ls-R would be shorter
This applies to e.g /usr/local/share/lyx
and $HOME/.lyx/texmf/tex
All that is required is add another level before the tex directory.
--
Thanks, Gar
39 matches
Mail list logo