On Wed, 10 Mar 1999, Jean-Marc Lasgouttes wrote:
> > "Daniel" == Daniel Naber <[EMAIL PROTECTED]> writes:
>
> Daniel> Jean-Marc Lasgouttes wrote:
> >> I do not have this problem here. What compiler are you using? Did
> >> you specify --with-included-string?
>
> Daniel> It doesn't help, it c
I've gone throught the assorted documentation again, and can't find an
answer to my latest question: how do I skip space between *groups* of
paragraphs of Standard? I could do it with ERT, but is there something
I'm missing here?
rick
--
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> Concerning the problems particular to the OS/2 port, I prefer to
> accept the changes after a (virtual) nod from SMiyata, since I have no
> way to check whether things work as advertized.
The fix to lib/configure.cmd is a correct one. I'm not su
"Asger Alstrup Nielsen" <[EMAIL PROTECTED]> wrote:
> So, in conclusion, I think you mostly agree that the design is sound, and
> complete enough to support the needs for the Asian encodings?
Yes and thank you very much for the reply. I understand your points better:
> Notice that the main thin
> (All the math glyphs are part of Unicode.)
Sorry, this is not true. What I meant was that we can make sure all the needed
math glyphs are part of our Unicode encoding, using the private area.
Greets,
Asger
> I did that, but only to find out that it does not compile because it
> does not know what wstring is. So, should I disable the build of
> encoding now? I'd rather build it even if it is not used.
Cool, thanks.
Since things do not compile for you, I can tell you are using a lame compiler
;-)
> Sorry, I have not read your document nor followed this thread, but I have
> a question: are the math encodings contempled in your scheme? I'm not sure
> if they are part of unicode but in the MathML page there are listed
> several encodings for symbols and Greek: http://www.w3.org/TR/REC-MathML/
> The bug is still there in 1.0.1 when you have several error boxes in a
> row: all but the right-most only respond to clicks on the left-hand end of
> the box.
Damn. I knew this was in there, but I thought it was ok. But I didn't
consider the error boxes. If it weren't for those, it is very s
Hello,
I just want to report a compiler warning:
lyxlib.h: In function `char * date()':
In file included from *manyfiles*
lyxlib.h:27: warning: comparison between signed and unsigned
Compiler bug or wrong declaration somewhere? I suppose its harmless,
but as I know nothing about *serious* devel
Asger,
Sorry, I have not read your document nor followed this thread, but I have
a question: are the math encodings contempled in your scheme? I'm not sure
if they are part of unicode but in the MathML page there are listed
several encodings for symbols and Greek: http://www.w3.org/TR/REC-MathML/
JMarc> What is the linke that your gcc uses? I think it might be a resurgence
JMarc> of the infamous static initialization order for the LString
JMarc> class. Could you provide us with a backtrace with debug information?
Hi again,
gcc uses the GNU linker from /uni/global/lib/gcc-lib/mips-sgi-iri
> "Brad" == <[EMAIL PROTECTED]> writes:
Brad> ENVIRONMENT: Insert a field of type Section* (probably plain
Brad> Section as well) with a page break above it
Brad> GUI PATH: Insert->Import ASCII File->Import as Lines choose a
Brad> file from the file browser
Brad
> "Daniel" == Daniel Naber <[EMAIL PROTECTED]> writes:
Daniel> Jean-Marc Lasgouttes wrote:
>> I do not have this problem here. What compiler are you using? Did
>> you specify --with-included-string?
Daniel> It doesn't help, it crashes again with the same output. I'm
Daniel> using egcs 1.1.1
Jean-Marc Lasgouttes wrote:
> I do not have this problem here. What compiler are you using? Did you
> specify --with-included-string?
It doesn't help, it crashes again with the same output. I'm using egcs
1.1.1 on a (mostly unmodified) SuSE 6.0 system.
Regards
Daniel
--
PGP Key fingerprint
Hello all--
First off, thanks for a really functional program!!!
Secondly, I don't know if this is a bug or not.
ENVIRONMENT: Insert a field of type Section* (probably plain
Section as well) with a page break above it
GUI PATH: Insert->Import ASCII File->Import as Li
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> I split the support into two halves: An EncodingConverter
Asger> hierarchy that does the dirty work of converting, and then a
Asger> bunch of functions that the outside world sees (through the
Asger> Encoding.h header file)
The bug is still there in 1.0.1 when you have several error boxes in a
row: all but the right-most only respond to clicks on the left-hand end of
the box.
--
http://www.cl.cam.ac.uk/users/rrt1001/ | maxim, n. wisdom for fools
Hi!
I updated the Encoding stuff in the CVS according to the new design document
about it.
I split the support into two halves: An EncodingConverter hierarchy that does
the dirty work of converting, and then a bunch of functions that the outside
world sees (through the Encoding.h header file).
> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> No. T1 is an output encoding, that is the encoding of the font used
>> in the dvi file. This has nothing to do with the input encoding,
>> which is the encoding that LaTeX reads, in order to translate
>> internally to its own
> No. T1 is an output encoding, that is the encoding of the font used in
> the dvi file. This has nothing to do with the input encoding, which is
> the encoding that LaTeX reads, in order to translate internally to its
> own 7bit format.
>
> LaTeX will *never* have to read a file in T1 encoding.
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> T1 is the LaTeX encoding, except that the glyphs from A0-FF can
Asger> be represented as a single character. T1 corresponds closely
Asger> to what I think we export into LaTeX file in LyX v1.0, when the
Asger> encoding is
[T1 encoding]
> Except that there are a lot of characters and accents at the places
> where latin1 places control characters.
I suspect that those "control characters" are only used when fonts are encoded.
Can LaTeX accept a file with characters and accents at those control
characters?
> What do
> "Martin" == Martin Ostermann <[EMAIL PROTECTED]> writes:
Martin> On Tue, 9 Mar 1999 12:23:05 +0100 (MET), Jean-Marc Lasgouttes
Martin> <[EMAIL PROTECTED]> said:
ost> Anyway, by a binary search I found out that the offending
ost> function is
ost> void MathedIter::Insert(MathedInset* p, int
On Tue, 9 Mar 1999 12:23:05 +0100 (MET), Jean-Marc Lasgouttes
<[EMAIL PROTECTED]> said:
ost> Anyway, by a binary search I found out that the offending
ost> function is
ost> void MathedIter::Insert(MathedInset* p, int type) { ...
> Yes. If you have any idea on why it happens, we'd be interested.
> "fpetitje" == fpetitje <[EMAIL PROTECTED]> writes:
fpetitje> In Solaris development tools there is a nice bcheck
fpetitje> script. With it, we can run any non stripped ELF executable
fpetitje> under the debugger and a report on memory related problems
fpetitje> is produced. bcheck -all src
> "Volker" == Volker Enderlein <[EMAIL PROTECTED]> writes:
Volker> Hi, I've got some problems while running LyX 1.0.0 (02/23/99)
Volker> and 1.0.1 (03/04/99) on my SGI-Workstation (SGI Indigo2 IMPACT
Volker> 1, IRIX64 wega 6.2 06101031 IP28). During the Compilation
Volker> with the native
> "Daniel" == Daniel Naber <[EMAIL PROTECTED]> writes:
Daniel> Asger Alstrup Nielsen wrote:
>> 1.1 does work for implementing new things, although it's unstable.
>> If you can build the stuff, you should be able to port it. If you
>> can't build it, let us know what fails, and we should fix
> "Pawel" == Pawel Sokolowski <[EMAIL PROTECTED]> writes:
Pawel> The following bug only occurs when I set LANG environment to
Pawel> pl, however I only tested: pl,de,no and C. It occurs when
Pawel> there is no any document opened ( only gray background ) and I
Pawel> select menu (pl): Plik->
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> After reading it, the idea makes indeed sense. But this means that
>> we will disallow all compilers where C++ string is not good enough
>> (gcc 2.7.x and even 2.8.x currently, not too mention probably many
>> proprietary compi
> "Serge" == Serge Winitzki <[EMAIL PROTECTED]> writes:
Serge> Hi, This is to report some minor problems and troubles I've had
Serge> with the latest LyX 1.0.1.
Serge> Compiling lyx 1.0.1 on linux 2.0.34 slackware 3.5 (libc5) using
Serge> gcc version egcs-1.1b (egcs-2.91.57): compilation err
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes:
Amir> Has something like this been mentioned before? When you
Amir> collapse a figure, you get a little red "fig". Wouldn't it be
Amir> neat if instead you got the label with which you had labelled
Amir> that fig? (Of course, this wouldn't
> After reading it, the idea makes indeed sense. But this means that we
> will disallow all compilers where C++ string is not good enough (gcc
> 2.7.x and even 2.8.x currently, not too mention probably many
> proprietary compilers).
Maybe we have to build our own standard string and wstring imple
> "Jan" == Jan W Stumpel <[EMAIL PROTECTED]> writes:
Jan> On Tue, 9 Mar 1999, Jean-Marc Lasgouttes wrote:
>>
Jan> \screen_font_roman -winfonts-"times new roman" and that did not
Jan> work.
>> I guess this should have worked too, in fact.
Jan> It doesn't; the message reads
Jan> LyX: Unknow
33 matches
Mail list logo
