>> Daniel Naber writes:
DN> Hi, I'd like to add the 'replace all' stuff to the cvs version.
DN> But I cannot call "make updatesrc" beacuse there's no Makefile
DN> (makefile.eigen only warns my not to run it, because it's only
DN> intended for the maintainer).
DN> Do I have to copy th
Hi,
I'd like to add the 'replace all' stuff to the cvs version. But I cannot
call "make updatesrc" beacuse there's no Makefile (makefile.eigen only
warns my not to run it, because it's only intended for the maintainer).
Do I have to copy the files etc. by hand?
Regards
Daniel
--
PGP Key fing
>> Paul Seelig writes:
PS> On 20 Mar 1999, Lars Gullik Bjønnes wrote: Anybody has already
PS> seen this?
>> yes. (or was that a rethorical question?)
>>
PS> No, not at all. I was actually referring to
:-) Yes, I saw it when it was posted to linux-announce, I just figured
that it wa
On 20 Mar 1999, Lars Gullik Bjønnes wrote:
> PS> Anybody has already seen this?
>
> yes. (or was that a rethorical question?)
>
No, not at all. I was actually referring to
--- snip -
Date: Sun, 14 Mar 1999 15:52:16 GMT
From: "zhao.jia.wei" <[EMAIL PROTECTED]>
>> Paul Seelig writes:
PS> --Multipart_Fri_Mar_19_23:23:53_1999-1 Content-Type: text/plain;
PS> charset=US-ASCII
PS> Anybody has already seen this?
PS> P. *8^)
yes. (or was that a rethorical question?)
Lgb
Anybody has already seen this?
P. *8^)
-BEGIN PGP SIGNED MESSAGE-
Get
http://hpws3.ihep.ac.cn/~zhaojw/chineselyxwrap.tgz
and try to make the Lyx a Chinese document composer.
( see http://www.ihep.ac.cn/~yumj to get the chinput package.)
- --
This article has been digitally sig
We should perhaps make a "LyX in the Press" page.
Lgb
--- Start of forwarded message ---
Date: Thu, 18 Mar 1999 15:22:49 +0100
Message-Id: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Subject: LyX Feedback
Reply-to: [EMAIL PROTECTED]
Make a link to this exc
>> Jean-Marc Lasgouttes writes:
>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
#else #include #include #endif
AAN> Yes, this should work.
Lars> No it would not work. and are totally
Lars> different, one is a C++ standard header the other is a C (or
Lars>
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>>> #else #include #include #endif
AAN> Yes, this should work.
Lars> No it would not work. and are totally
Lars> different, one is a C++ standard header the other is a C (or
Lars> POSIX) standard header.
Yes, I came to this co
On Fri, Mar 19, 1999 at 07:17:12PM +0100, Asger Alstrup Nielsen wrote:
> [Unions]
[Value Implementation]
> So, in the Paragraph structure, I propose that we simply have this:
>
> struct Paragraph {
>
> map settings;
> };
>
> So the "settings" map is our state of the paragraph.
>> Asger Alstrup Nielsen writes:
AAN> [Unions]
>> That is probably the only C keyword that I have never used, so I
>> know its
AAN> name ;-)
AAN> Let me repeat the code I presented for the Value system:
AAN> struct Value { union { double real; int integer; bool boolean;
AAN> str
>> Jean-Marc Lasgouttes writes:
[...]
Allan> So, do I resort all the tag arrays or do you change toupper()
Allan> to tolower() in compare_no_case() ?
JL> I think we should use tolower in compare_no_case. However, I
JL> don't know what Lars' (?) comments about not being posix mean
JL>
[Unions]
> That is probably the only C keyword that I have never used, so I know its
name ;-)
Let me repeat the code I presented for the Value system:
struct Value {
union {
double real;
int integer;
bool boolean;
string str;
wstring wstr;
>> Asger Alstrup Nielsen writes:
>> Can't we simply add a test for working namespaces and then in the
>> code use:
>>
>> #ifdef LYX_WORKING_NAMESPACES #include using
>> std::string; using std::wstring; #include // or whatever
>> other STL headers you want using map;
AAN> Of co
On Fri, Mar 19, 1999 at 06:22:10PM +0100, Jean-Marc Lasgouttes wrote:
> Jose> One thing that docbook uses are labels inside the the
> Jose> different tags. Is it possible to have reserve space to this in
> Jose> a sensible way?
>
> Hmm, labels as in LaTeX \label? Yes, it would be really nice
> "Jose" == Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes:
Jose> On Fri, Mar 19, 1999 at 06:10:15PM +0100, Jean-Marc Lasgouttes
Jose> wrote:
>> >From the top of my head we'll need at least two additional
>> variables: - a boolean indicating whether the heading is numbered
>> or not -
On Fri, Mar 19, 1999 at 06:10:15PM +0100, Jean-Marc Lasgouttes wrote:
> >From the top of my head we'll need at least two additional variables:
> - a boolean indicating whether the heading is numbered or not
> - a text inset containing the optional caption
One thing that docbook uses are labels
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> I'm inclined to think that having a specific Heading inset may be a
>> flaw. That kind of info should be pushed into a layout file so we
>> have more generic handling of documents.
Asger> Yes, you are right. We don't need a
> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
Allan> Lars, if it is required by Posix to use toupper() for the
Allan> character comparisons then I found the remaining problem. All
Allan> our tag arrays like lyxrcTags are sorted according to lowercase
Allan> ordering (ie. tolower()).
Fo
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> 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 ortho
> "Miyata" == Miyata Shigeru <[EMAIL PROTECTED]> writes:
Miyata> No, I didn't know that. If you are not using main stream
Miyata> systems like MS Windoze or Linux, some of the informations are
Miyata> not so easy to obtain. I really think he should have
Miyata> announced these stuffs here,
> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
Allan> What about testing if even exists? Or testing if
Allan> exists if doesn't? or if Asger's tests
Allan> fail testing if we can use instead?
Do you have examples of compilers where these headers do not exist? Do
you think we'll be
> I'm inclined to think that having a specific Heading inset may be a flaw.
> That kind of info should be pushed into a layout file so we have more
> generic handling of documents.
Yes, you are right. We don't need a specific Heading object.
At the top level, we could only have "paragraph" obj
> > The question is, how to integrate it:
The real easy solution is to do #4:
4) Use the LyX server.
Then this feature can exists as an add-on package, and even be used with LyX
v1.0.0 (and older). Of course, we should do 1) at some point.
Greets,
Asger
> Can't we simply add a test for working namespaces and then in the code
> use:
>
> #ifdef LYX_WORKING_NAMESPACES
> #include
> using std::string;
> using std::wstring;
> #include // or whatever other STL headers you want
> using map;
Of course, you mean "using std::map;"
On Fri, 19 Mar 1999, Allan Rae wrote:
> 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 docum
26 matches
Mail list logo
