SNU <[EMAIL PROTECTED]> writes:
| Hi,
|
| $ ./autogen.sh
| Using automake (GNU automake15) 1.5
I think your version of automake is a bit too old.
--
Lgb
Bennett Helm wrote:
> Perhaps I'm missing something, but this does not seem to work at all
> for me: C-i still has no effect when the cursor is inside an inset,
> but only works when the cursor is just in front of it.
Are you sure you applied it? It works flawlessly here, and I cannot imagine
On Fri, Oct 14, 2005 at 01:12:01AM +, Luis Rivera wrote:
> >
> > $ ls -l /usr/lib/libresolv.a
> > lrwxrwxrwx 1 kayvan Users 25 Apr 27 15:31 /usr/lib/libresolv.a ->
> /usr/lib/libminires.dll.a
> >
It comes from minires and minires-devel.
---Kayvan
Hi,
$ ./autogen.sh
Using automake (GNU automake15) 1.5
Using autoconf (GNU Autoconf) 2.59
Locating GNU m4... /usr/local/bin/gm4
...
Building Makefile templates...
.
src/tex2lyx/Makefile.am:36: invalid unused variable name: `LINKED_SOURCES'
done.
...
$
Regards,
Rob.
Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Luis Rivera wrote:
> > I think this is the wrong approach, if there is some way to implement
> > script/macro running right from inside LyX.
> >
> > If Bo Peng is right, he can try turning all shell scripts into python;
> > and if the developers embe
Kayvan A. Sylvan <[EMAIL PROTECTED]> writes:
>
> >
> > ld cannot find -lresolv
> >
> > Perhaps I'm missing some other library from cygwin...
> >
>
> I think you are missing some library. On my Cygwin, I have:
>
> $ ls -l /usr/lib/libresolv.a
> lrwxrwxrwx 1 kayvan Users 25 Apr 27 15:31 /us
Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
> Luis Rivera <[EMAIL PROTECTED]> writes:
>
> | Lars Gullik Bjønnes ...> writes:
> |
> | >
> | > Luis Rivera ...> writes:
> | >
> | > | Anyway, I went ahead and tried
> | > |
> | > | ./configure --with-frontend=xforms --with-extra-prefix=
John Levon <[EMAIL PROTECTED]> writes:
| On Fri, Oct 14, 2005 at 12:41:32AM +0100, Angus Leeming wrote:
|
| > John Levon wrote:
| > > This seems a horribly euro-centric point of view. (Says the guy who can
| > > only speak one language...)
| >
| > Really? Which one?
|
| Northern.
At least you
John Levon <[EMAIL PROTECTED]> writes:
| > languages if volunteers come and help out. Don't worry about composed
| > Unicode glyphs for now - it's a corner case that can be handled once
| > someone feels the heat (which will probably when hell freezes over AFAICT).
|
| This seems a horribly eur
On Fri, Oct 14, 2005 at 12:41:32AM +0100, Angus Leeming wrote:
> John Levon wrote:
> > This seems a horribly euro-centric point of view. (Says the guy who can
> > only speak one language...)
>
> Really? Which one?
Northern.
john
John Levon wrote:
> This seems a horribly euro-centric point of view. (Says the guy who can
> only speak one language...)
Really? Which one?
On Thu, Oct 13, 2005 at 10:29:30PM +0200, Asger Ottar Alstrup wrote:
> The reason I suggest a unicode inset is that we already have it: the
> latex accent inset.
Our inset infrastructure is not in a position to accomodate something
like this.
> languages if volunteers come and help out. Don't w
On Thu, Oct 13, 2005 at 10:01:50PM +, Luis Rivera wrote:
> Kayvan A. Sylvan <[EMAIL PROTECTED]> writes:
>
> >
> >
> > There are a couple of vagaries:
> >
> > 1) Any compiler more recent than gcc-3.3.3 seems to screw me up. Even
> >if I recompile xforms and qt-3.
> >
>
> I compiled wit
Luis Rivera wrote:
>> There are a couple of vagaries:
>>
>> 1) Any compiler more recent than gcc-3.3.3 seems to screw me up. Even
>>if I recompile xforms and qt-3.
> I compiled with xforms with gcc 3.4.4, and save for the error at
> supporting nls, it went on fine...
>
>> 2) The qt-3 build n
Asger Ottar Alstrup <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > No. I am not sure... but it depends... a combining character can be
| > used to produce accents as well... why not an umlaut on top of an
| > grave on top of an 'e'.
|
| The reason I suggest a unicode inset is that w
Kayvan A. Sylvan <[EMAIL PROTECTED]> writes:
>
>
> There are a couple of vagaries:
>
> 1) Any compiler more recent than gcc-3.3.3 seems to screw me up. Even
>if I recompile xforms and qt-3.
>
I compiled with xforms with gcc 3.4.4, and save for the error at supporting nls,
it went on fine.
Luis Rivera <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| >
| > Luis Rivera <[EMAIL PROTECTED]> writes:
| >
| > | Anyway, I went ahead and tried
| > |
| > | ./configure --with-frontend=xforms --with-extra-prefix=/usr/local
| > | --without-latex-config --di
Lars Gullik Bjønnes wrote:
No. I am not sure... but it depends... a combining character can be
used to produce accents as well... why not an umlaut on top of an
grave on top of an 'e'.
The reason I suggest a unicode inset is that we already have it: the
latex accent inset.
Of course you can
On Oct 13, 2005, at 2:21 PM, Juergen Spitzmueller wrote:
Jean-Marc Lasgouttes wrote:
If special code is needed, what about putting it in
InsetTabular::dispatch, or in some other InsetTabular method?
The attached patch might be more at your goût.
Jürgen
<2066.diff>
Perhaps I'm missing so
Angus Leeming wrote:
Not in LyX.
qtconfig in your qt3/bin directory.
That doesn't really explain why LyX 1.3 behaves correctly where LyX 1.4
does not.
Michael
Jean-Marc Lasgouttes wrote:
> If special code is needed, what about putting it in
> InsetTabular::dispatch, or in some other InsetTabular method?
The attached patch might be more at your goût.
Jürgen
Index: text3.C
===
RCS file: /usr
Michael Gerz wrote:
> Ok,
>
> I am able to run LyX on Windows again. However, the selected font is
> pretty ugly. It seems that LyX 1.4 is not able to find reasonable fonts
> (LyX 1.3 does!) and so Qt decides to take the first font in
> alphabetically order. This font is not only choosen for disp
Ok,
I am able to run LyX on Windows again. However, the selected font is
pretty ugly. It seems that LyX 1.4 is not able to find reasonable fonts
(LyX 1.3 does!) and so Qt decides to take the first font in
alphabetically order. This font is not only choosen for displaying a LyX
document but al
--- [EMAIL PROTECTED] wrote:
> Dear Bo,
>
> >> > I found that I could convert all the python script to .exe.
> >> > Thus I can remove Pyhthon dependecy.
> >>
> >> Are you sure?
>
> > Also, there are some dynamically generated sh scripts that might be
> > translated to dynamically generated pytho
Michael Gerz wrote:
Hello,
this patch fixes the cursor positioning for vspace insets. So far, the
cursor is placed way too high. With this patch, the cursor is aligned
with the label text. The patch also fixes the label size computation
(wrong font size).
I have tested the patch extensivel
Luis Rivera wrote:
> I think this is the wrong approach, if there is some way to implement
> script/macro running right from inside LyX.
>
> If Bo Peng is right, he can try turning all shell scripts into python;
> and if the developers embed python within LyX, you don't need to call
> python.exe,
Dear Jean-Marc,
Bo>> convert.exe and aspell.exe should be easy to handle,
> be a static version also. Concerning aspell, the main problem will be
> the dictionaries.
I agree, spellchecking is hard to install It was hard for me to install
aspell, it took few mounth to get it working. It was hard to
Dear Bo,
> Please send the detailed instructions on how to do this to the list.
Ok. Here comes, the detailed how to use it guide.
First we need some general build.bat (or build.cmd) file for running the
packaging:
$ python setup.py py2exe
After running the command script, the package generated
<[EMAIL PROTECTED]> writes:
>
> Dears,
>
> I found that I could convert all the python script to .exe.
> Thus I can remove Pyhthon dependecy.
> In case I know well, there are some python script left in the script
> directory.
> I could relocate lyx2lyx here, and convert other scripts to .exe.
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| Lars> Ad. Asgers idea of a class UnicodeGlyph... (I'd prefere it to
| Lars> not be an inset), we could have all chars in a Paragraph have
| Lars> that type. Internally we could use some tricks to not use too
| Lars> much memory for glyphs that doe
Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
> Luis Rivera <[EMAIL PROTECTED]> writes:
>
> | Anyway, I went ahead and tried
> |
> | ./configure --with-frontend=xforms --with-extra-prefix=/usr/local
> | --without-latex-config --disable-pch --disable-nls
> |
>
> You can try with --with-in
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> I am not saying that we must support everything Unicode can in
Lars> 1.5, but we must at least think about this.
Lars> We might decide that we don't have to worry about combining
Lars> chars at all (but I fear that we have to).
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> fonts deal with glyphs (or rather the display engine), we must
| Lars> deal with codepoints all the grit (which surely a lib like ICU
| Lars> can help us with)
|
| Could y
On Thu, 13 Oct 2005, Paul A. Rubin wrote:
> [EMAIL PROTECTED] wrote:
> > Hi
> >
> > This might sound weird, but I'm looking for Borland Turbo C 3.0 (2.0 might
> > work) in order to compile some special example drivers for DOS. Does
> > anyone have an idea where TC30 or TC20 might be available? (
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> OK, at least part of this patch was tested by me and found
Martin> functional. Saw no side effects (and couldn't really imagine
Martin> any). So, I would say, put it in.
I did that.
JMarc
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
>> Bennett, Angus, I would appreciate if you could test it. I think
>> the code to handle package in configure is much cleaner now.
Bennett> Works for me.
I think it will be OK for the same reasons on windows, so I committed
it.
JMarc
[EMAIL PROTECTED] wrote:
Hi
This might sound weird, but I'm looking for Borland Turbo C 3.0 (2.0 might
work) in order to compile some special example drivers for DOS. Does
anyone have an idea where TC30 or TC20 might be available? (My network is
acting up right now... I can't even access Borlan
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> fonts deal with glyphs (or rather the display engine), we must
Lars> deal with codepoints all the grit (which surely a lib like ICU
Lars> can help us with)
Could you tell me succinctly what a codepoint is?
Also, what languages
Angus Leeming <[EMAIL PROTECTED]> writes:
| Asger Alstrup wrote:
| >> | Lars Gullik Bjønnes wrote:
| >> | Sure. But that's not information needed by the CORE, is it? The core
| >> | does act on (strings of) single codepoints. All paragraph breaking
| >> | etc, acts on single code points.
| >>
| >
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> before that fix, we checked for cell.size(), which was too
Juergen> lose, because two different cells might have the same size
Juergen> (which was the case in bug 1808), and the idea of the fix was
Juergen> just a stricte
Jean-Marc Lasgouttes wrote:
> Well, I do not really understand the fix to 1808 anyway, but if the
> idea was right, this patch is the right way to do it.
before that fix, we checked for cell.size(), which was too lose, because two
different cells might have the same size (which was the case in bu
Asger Alstrup <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Angus Leeming <[EMAIL PROTECTED]> writes:
| > | Lars Gullik Bjønnes wrote:
| > | Sure. But that's not information needed by the CORE, is it? The core does
| > | act on (strings of) single codepoints. All paragraph breaking
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Almost. The attached works like a charme (I also tested the
Juergen> case of bug 1808). What do you think?
Well, I do not really understand the fix to 1808 anyway, but if the
idea was right, this patch is the right way t
Hi
This might sound weird, but I'm looking for Borland Turbo C 3.0 (2.0 might
work) in order to compile some special example drivers for DOS. Does
anyone have an idea where TC30 or TC20 might be available? (My network is
acting up right now... I can't even access Borland's site).
regards
/Christ
Jean-Marc Lasgouttes wrote:
> bool samePar(StableDocIterator const & i1, StableDocIterator const & i2)
> {
> StableDocIterator tmpi2 = i2;
> tmpi2.back().pos() = i1.back().pos();
> return i1 == tmpi2;
> }
>
> Would that work?
Almost. The attached works like a charme (I also
On Thu, 2005-10-13 at 01:52 +0200, Lars Gullik Bjønnes wrote:
> I have been trying to look at the ICU api, but I find the
> documentation utterly confusing and hard to get a clear understanding
> on how it works. (Probably caused be me not finding a "Hello World"
> code snippet)
>
> Also, I must s
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Jean-Marc Lasgouttes wrote:
>> I guess the fact that we skip 244 is not significant because
>> tex2lyx does not really support InsetSpace anyway, right?
Juergen> Right. I just checked this. Only ~ is supported currently.
Jean-Marc Lasgouttes wrote:
> I guess the fact that we skip 244 is not significant because tex2lyx
> does not really support InsetSpace anyway, right?
Right. I just checked this. Only ~ is supported currently.
Jürgen
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Georg Baum wrote:
>> > Patch attached. Please review.
>>
>> Looks good and works for me.
>>
>> > Am I right that norhing has to be done on lyx2lyx reversion?
>>
>> I think so, since \quoting_style was only the default
Georg Baum wrote:
> > Patch attached. Please review.
>
> Looks good and works for me.
>
> > Am I right that norhing has to be done on lyx2lyx reversion?
>
> I think so, since \quoting_style was only the default setting for inserting
> new quotes, and it was an optional parameter.
Thanks for review
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> stack.top().cell and undo.cell are not the same, because
Juergen> pos() is different. It probably would be enough to just
Juergen> compare idx(). But how?
If I understand correctly, you problem is that a stable iterator
Juergen Spitzmueller wrote:
> Jose' Matos wrote:
>> > Additionally, we could force \quotes_times to 2 between 229 and 230.
>>
>> What is the difference if you don't do it?
>
> Files up to the forthcoming version might have the described bug (single
> quotes enabled, which does not make sense and
Juergen Spitzmueller wrote:
> Jose' Matos wrote:
>> > Should I prepare a patch with another file format change?
>>
>> Yes.
>
> Patch attached. Please review.
Looks good and works for me.
> Am I right that norhing has to be done on lyx2lyx reversion?
I think so, since \quoting_style was only th
Asger Alstrup wrote:
>> | Lars Gullik Bjønnes wrote:
>> | Sure. But that's not information needed by the CORE, is it? The core
>> | does act on (strings of) single codepoints. All paragraph breaking
>> | etc, acts on single code points.
>>
>> How can it? When perhapsh three codepoints ends up beei
Write some text and undo: you have to undo each single char. Normally, LyX is
supposed to do some grouping.
It fails in undo.C: 80
if (!undo_finished
&& kind != Undo::ATOMIC
&& !stack.empty()
==> && stack.top().cell == undo.cell
&& stack.top().ki
Lars Gullik Bjønnes wrote:
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| Sure. But that's not information needed by the CORE, is it? The core does
| act on (strings of) single codepoints. All paragraph breaking etc, acts on
| single code points.
How can it? When perha
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Jean-Marc Lasgouttes wrote:
>> There is also a bug that I never filed :) Insert>File is dead
>> broken.
Juergen> In which respect?
I am glad you ask. Look at BufferView::Pimpl::MenuInsertLyXFile. There
it does
b
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| Thanks for supplying the bigger picture. I've only one point to make:
|
| > (Even UCS-4 is not "one-codepoint" "one-glyph", combining chars are
| > required for proper display)
|
| Sure. But that's not information needed by
> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes:
Bo> convert.exe and aspell.exe should be easy to handle,
Well, it seems that convert.exe uses a lot of libraries, but there may
be a static version also. Concerning aspell, the main problem will be
the dictionaries.
Bo> and packing miktex is not
Lars Gullik Bjønnes wrote:
Thanks for supplying the bigger picture. I've only one point to make:
> (Even UCS-4 is not "one-codepoint" "one-glyph", combining chars are
> required for proper display)
Sure. But that's not information needed by the CORE, is it? The core does
act on (strings of) singl
Angus Leeming wrote:
Lars Gullik Bjønnes wrote:
Would be nice if some of you could have a look at this lib as well,
and see what you think of it. I know it is _The_ Unicode lib to use,
but still...
I agree that ICU is bloated, complicated and antiqued. I'm not sure there
is anything better o
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > I have been trying to look at the ICU api, but I find the
| > documentation utterly confusing and hard to get a clear understanding
| > on how it works. (Probably caused be me not finding a "Hello World"
| > code snippet)
|
62 matches
Mail list logo
