>From your log of autogen.sh output it appears you need to upgrade to
automake-1.4
Allan. (ARRae)
On Wed, 15 Dec 1999, Greg Lee wrote:
>
> On Wed, 15 Dec 1999, Asger K. Alstrup Nielsen wrote:
>
> > > Surely those voices didn't mean paragraph-level support without
> > > also sentence- and word-level support. When you cite from a
> > > different language, the citation is obviously not always
On 15 Dec 1999, Lars Gullik Bjønnes wrote:
> "Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
>
> | > Another solution would be to add an --enable-assertions flag which
> | > defaults to 'yes' for development versions, but which can be turned
> | > off (for speed reasons).
> |
> | This is
Has anybody experiences to share ?
I am having problems with the autogen.sh script, seems that some things
are still missing on my system.
When I run autogen.sh I get some messages (file attached), then when I
try to run
./configure I see the following:
loading cache ./config.cache
./configur
Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes:
| On Tue, Dec 14, 1999 at 03:50:38PM +0100, Jean-Marc Lasgouttes wrote:
| > > "Jose" == Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes:
| >
| > Jose> Content-Type: text/plain; charset=iso-8859-1
| > Jose> Content-Transfer-Encoding
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| > Another solution would be to add an --enable-assertions flag which
| > defaults to 'yes' for development versions, but which can be turned
| > off (for speed reasons).
|
| This is the better solution, because the distinction between deve
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| > About i18n, I've read the "encoding.lyx" article written by Asger
| > Alstrup Nielsen. (By the way, the file is no longer available at the URL
| > where I got it before. Is it no longer available?) The article is
|
| Good quest
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| Lgb, how long will it take to create those branches and give
| the relevant people write access to the repository?
To crate a branch takse close to no time, to give people asscess takes
longer. And a screening process is also needed.
In a
"Andre' Poenitz" <[EMAIL PROTECTED]> writes:
| > Lars> Is this also treu after reading the file again? What keynap are
| >
|
| This is about the third or fourth mail from Lars that gets cited in the
| list although I did not receive the original. Since the question looks
| like Lars asked me (i
On Wed, 15 Dec 1999, Asger K. Alstrup Nielsen wrote:
> > Surely those voices didn't mean paragraph-level support without
> > also sentence- and word-level support. When you cite from a
> > different language, the citation is obviously not always
> > going to be a separate paragraph.
>
> As it
> "Peter" == Peter Suetterlin <[EMAIL PROTECTED]> writes:
Hi Pit,
Thanks for the patches, I'll commit them soon.
Peter> - The ballon tool tips are not translated. I'm not sure wether
Peter> this has ever since been the case, but i thought they have been
Peter> at some point...
They used t
Hi Folks,
as promised, I took some time to look through the german po-files.
Attached are 2 patches for de.po and de_menus.bind.
They are against 1.1.4pre1.
Furthermore I found 2 (minor) glitches:
- The ballon tool tips are not translated. I'm not sure wether this
has ever since been th
>
> On Tue, Dec 14, 1999 at 01:19:23PM +0100, Asger K. Alstrup Nielsen wrote:
> >
> > Yes, this patch is very cool. Hebrew support can be considered a FURF,
> > and it's great to see somebody do something about it.
>
> Yay!
>
> Dekel, how is this patch related to TeX--XeT? I seem to remember
> "Jose" == Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes:
Jose> I will, and since no is volunteer I volunteer myself to change
Jose> the sgml load stuff. Your plan (in a previous mail message) is a
Jose> good starting point. As I see it in the Changelog this hasn't
Jose> been done,
On Tue, Dec 14, 1999 at 03:50:38PM +0100, Jean-Marc Lasgouttes wrote:
> > "Jose" == Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes:
>
> Jose> Content-Type: text/plain; charset=iso-8859-1
> Jose> Content-Transfer-Encoding: 8bit
>
> Jose> Hi, I have tested the latest cvs and lyx. With t
On Wed, Dec 15, 1999 at 04:10:47PM +0100, Jean-Marc Lasgouttes wrote:
> > "Andre'" == Andre' Poenitz <[EMAIL PROTECTED]> writes:
>
> >> + ofs << "\n";
>
> Andre'> Aehm.. sorry, forgot one. "userName"? I thought big brother
> Andre'> was dropped a few weeks ago ;-)
>
> Well spotted. Jose', w
Wed Dec 15 1999, Andre' Poenitz ->
> >
> > IMHO, you either should use only tabs to indent, or only spaces.
> > Otherwise, you'll have problems when:
> > * Showing in a proportional font
> > * Showing with a different tab setting (!=3D 8)
>
> Erm, exactly that is the patch supposed to do. Sinc
> "Andre'" == Andre' Poenitz <[EMAIL PROTECTED]> writes:
Lars> Is this also treu after reading the file again? What keynap are
>>
Andre'> This is about the third or fourth mail from Lars that gets
Andre'> cited in the list although I did not receive the original.
Andre'> Since the question l
> Lars> Is this also treu after reading the file again? What keynap are
>
This is about the third or fourth mail from Lars that gets cited in the
list although I did not receive the original. Since the question looks
like Lars asked me (it was my problem) I should have received at least
one copy
> "Andre'" == Andre' Poenitz <[EMAIL PROTECTED]> writes:
>> + ofs << "\n";
Andre'> Aehm.. sorry, forgot one. "userName"? I thought big brother
Andre'> was dropped a few weeks ago ;-)
Well spotted. Jose', would you care providing a sensible header
without user name and copyright, before I ch
> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> The LaTeXWriter was not written. However, it would be an easy
Asger> task to do it. The AsciiWriter exists in the old development
Asger> branch, and only needs to be extended with a few routines
Asger> before a usable LaT
>
> IMHO, you either should use only tabs to indent, or only spaces.
> Otherwise, you'll have problems when:
> * Showing in a proportional font
> * Showing with a different tab setting (!=3D 8)
Erm, exactly that is the patch supposed to do. Since most of the lyx
sources are tab-indented I chan
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Is this also treu after reading the file again? What keynap are
Lars> you using?
Lars> Seems like Lyx does not think that this char can be directly
Lars> showed/dispplayed, and used a InsetLatexInset to show it.
After debuggi
Tue Dec 14 1999, Andre' Poenitz ->
> There are quite a few places where spaces had been used instead of tabs.
> I put a patch under
>
> http://mathematik.htwm.de/Software/LyX/spacing-patch-1
>
> or a bit shorter
>
> http://mathematik.htwm.de/Software/LyX/spacing-patch-1.gz
>
> that change
> Another solution would be to add an --enable-assertions flag which
> defaults to 'yes' for development versions, but which can be turned
> off (for speed reasons).
This is the better solution, because the distinction between development
versions and stable releases is being blurred these days.
> Surely those voices didn't mean paragraph-level support without
> also sentence- and word-level support. When you cite from a
> different language, the citation is obviously not always
> going to be a separate paragraph.
As it happens, sub-paragraph-level support is markedly more
difficult tha
On Wed, 15 Dec 1999, Asger K. Alstrup Nielsen wrote:
...
> not affect the left-to-right 8-bit languages, except maybe for a
> small performance penalty. However, several voices say that
> paragraph-level language support is important, so it seems that
Surely those voices didn't mean paragraph-l
On Wed, 15 Dec 1999, Jules Bean wrote:
> My instinct says that most people aren't going to care in the slightest
> about a doubling of internal buffer sizes. The combination of cheap
> memory, cheap hard disks, and sensible VM systems makes this not much of
> an issue, IMO.
Can't you make it a
> My instinct says that most people aren't going to care in the slightest
> about a doubling of internal buffer sizes. The combination of cheap
> memory, cheap hard disks, and sensible VM systems makes this not much of
> an issue, IMO.
*grin* Well, I did not want to write obvious things ;-)
And
> "Jules" == Jules Bean <[EMAIL PROTECTED]> writes:
Jules> On Wed, 15 Dec 1999, Andre' Poenitz wrote:
>> Concerning the multi-byte encoding: We should have a discussion
>> whether it is sensible to use Unicode internally. The world is
>> changing and last years' arguments won't fit anymore.
On Wed, 15 Dec 1999, Andre' Poenitz wrote:
>
> Concerning the multi-byte encoding: We should have a discussion whether
> it is sensible to use Unicode internally. The world is changing and last
> years' arguments won't fit anymore. We could get rid of almost all of
> the encoding stuff at the pr
"Seak, Teng-Fong" <[EMAIL PROTECTED]> wrote:
> Chinese (as well as Japanese and Korean) can also be written from right to
> left, even though this isn't very common nowadays. Actually, in tradition,
> Chinese is written from top to the bottom, then from right to left. But I
> don't think L
"Seak, Teng-Fong" <[EMAIL PROTECTED]> wrote:
> Actually, newer versions of XFree86 support already natively Unicode, so
> do a lot of commercial X (if not all).
It also introduces Big5 support. Other multibyte encodings have been
supported for quite some time.
>
Hello there,
I was about to remove the --with-debug flag of configure and noticed
that Allan has actually been using DEBUG_AS_DEFAULT in bullet code.
Wouldn't it make sense to condition on DEVEL_VERSION instead? At least
we would be sure that the invariants are actually tested.
Another solution
Lars Gullik Bjønnes wrote:
> Note that we cannot live with that way of updating po files, most of
> the po files miss a lot to work ok with the current lyx sources.
Yeek, I know, I'm a bit stuffed with work. When is 1.1.4 scheduled?
I'll try to overhaul the menu stuff till then...
Pit
--
~
> I disagree. Merging branches after a year or so of development in these
> not-so-modular LyX sources is a major pain and I think it's a sure bet
> to assume that most of the work spent in these branches will be lost.
Oh, I disagree. It's very easy to keep a branch up-to-date.
It's only a matte
> So it's time to create a few cvs-branches.
I disagree. Merging branches after a year or so of development in these
not-so-modular LyX sources is a major pain and I think it's a sure bet
to assume that most of the work spent in these branches will be lost
(for quite a while at least). You see it
> About i18n, I've read the "encoding.lyx" article written by Asger
> Alstrup Nielsen. (By the way, the file is no longer available at the URL
> where I got it before. Is it no longer available?) The article is
Good question. Lgb, what happened with the old ftp.devel.lyx.org content?
Hi fellow LyXers from all over the world,
These days, we are overwhelmed with patches that extend the scope
of LyX to Hebrew, Chinese, Korean, Japanese, and what have you.
This is great, and very much appreciated.
Now, the question is how to handle this. It seems to me that the
Hebrew patch is
> "miyata" == miyata <[EMAIL PROTECTED]> writes:
miyata> A half year ago, Duncan Simpson <[EMAIL PROTECTED]> wrote:
>> mathed's lexer has some really stupid hacks in it. Following TeX on
>> what is a macro makes the code *much* simpler and would eliminate
>> even more if I could rebuild math
I would like to report that Korean as well as Japanese support for the
lyx-1.1.3 is now possible. The binary package in the rpm format and the
source package in the compressed atr format are available at
ftp://stone.phys.pusan.ac.kr/pub/lyx-kr.
The patch is entirely based on the patch against l
41 matches
Mail list logo
