On Fri, 2007-05-25 at 16:00 +0200, Abdelrazak Younes wrote:
> Darren Freeman wrote:
> > On Mon, 2007-05-21 at 14:28 +0200, Jürgen Spitzmüller wrote:
> >> Darren Freeman wrote:
> >>> This is not very helpful! What if I don't want to change the encoding,
> >>> fearful as I am of needless change.
> >>
Richard Heck wrote:
I'm forwarding this to lyx-devel, as encoding is a tough issue.
rh
Original Message
Subject:difference between cite inside and outside bibliography
environment
Date: Mon, 28 May 2007 22:45:04 +0200 (CEST)
From: [EMAIL PROTECTED]
To: [EMAIL P
Uwe Stöhr wrote:
>>>"\\newcommand{\\lyxcareof}{\\leavevmode\\hbox{\\raise.75ex\\hbox{c}\\kern-.15em/\\kern-.125em\\smash{\\lower.3ex\\hbox{o}}}\\ignorespaces}"
>
>>> ""
>>
>> \newcommand*\lyxcareof{%
>> \mbox{\raisebox{.8ex}{c}\kern-.175em\raisebox{.2ex}{/}%
>> \kern-.18em\raisebox{-.2ex}{o}}}
>
On Tue, May 29, 2007 at 01:01:22AM +0200, Lars Gullik Bjønnes wrote:
> [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
>
> | Dov Feldstern <[EMAIL PROTECTED]> writes:
> |
> | | José Matos wrote:
> | | > On Monday 28 May 2007 23:06:18 Andre Poenitz wrote:
> | | >> Sure, go ahead.
> | | > BTW, wh
On Mon, May 28, 2007 at 11:42:04PM +0100, José Matos wrote:
> On Monday 28 May 2007 23:06:18 Andre Poenitz wrote:
> > Sure, go ahead.
>
> BTW, what is the encoding of our source files? I would like to have
> them all utf8.
UTF8 is ok for comments and such (most noatbly quite a few names are n
Hi,
You can test the Hebrew he.po file by replacing this file with the old
one in the po directory in the source. Then you should compile lyx
again and install it (If forget to do "make install" the Hebrew won't
work). Later, you can start lyx in Hebrew by "LC_ALL=he_IL lyx".
Sincerely,
Ran Rut
Hi,
Dov Feldstern writes:
Actually, F11 is not needed either. The language command is a toggle,
so just using F12 >would toggle between the primary language (whatever
it is) and Hebrew. I don't know why >F11 is needed; I asked Ran about
it, and he said that sometimes F12 didn't work well, but >
Am 29.05.2007 um 00:42 schrieb José Matos:
On Monday 28 May 2007 23:06:18 Andre Poenitz wrote:
Sure, go ahead.
BTW, what is the encoding of our source files? I would like to
have them all
utf8.
+1
Plessse UTF8
Stefan
Andre'
--
José Abílio
PGP.sig
Description: Signier
Am 29.05.2007 um 00:59 schrieb Dov Feldstern:
Lars Gullik Bjønnes wrote:
Dov Feldstern <[EMAIL PROTECTED]> writes:
| José Matos wrote:
| > On Monday 28 May 2007 23:06:18 Andre Poenitz wrote:
| >> Sure, go ahead.
| > BTW, what is the encoding of our source files? I would like to
| > have them
[EMAIL PROTECTED] wrote:
Author: uwestoehr
Date: Mon May 28 23:09:09 2007
New Revision: 18549
URL: http://www.lyx.org/trac/changeset/18549
Log:
add Koji Yokota to the credits
Modified:
lyx-devel/trunk/lib/CREDITS
Er, did you add him to generate_contributions.py as well?
Angus
Enrico Forestieri wrote:
I don't understand. Seems that you are still using wchar_t ...
This crash is very similar to the one I was getting on cygwin after the
switch to unicode. I remember that someway I was able to fix it by
using the STLport library, before the real fix by Georg. Have a look
a
Richard Heck <[EMAIL PROTECTED]> writes:
| Jean-Marc Lasgouttes wrote:
| > Abdelrazak> I dared a few months ago and I've cleaned up a lot of the
| > Abdelrazak> Lexer class. But it was too late in the game and I gave up
| > Abdelrazak> because of the promised XML transition.
| >
| > Yes, but never
Jean-Marc Lasgouttes wrote:
> Abdelrazak> I dared a few months ago and I've cleaned up a lot of the
> Abdelrazak> Lexer class. But it was too late in the game and I gave up
> Abdelrazak> because of the promised XML transition.
>
> Yes, but nevertheless the part that reads the .lyx file is weird (th
Lars Gullik Bjønnes wrote:
Dov Feldstern <[EMAIL PROTECTED]> writes:
| José Matos wrote:
| > On Monday 28 May 2007 23:06:18 Andre Poenitz wrote:
| >> Sure, go ahead.
| > BTW, what is the encoding of our source files? I would like to
| > have them all utf8.
| >
| >> Andre'
| >
|
| Jose --- pat
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| Dov Feldstern <[EMAIL PROTECTED]> writes:
|
| | José Matos wrote:
| | > On Monday 28 May 2007 23:06:18 Andre Poenitz wrote:
| | >> Sure, go ahead.
| | > BTW, what is the encoding of our source files? I would like to
| | > have them all utf8.
| |
I'm forwarding this to lyx-devel, as encoding is a tough issue.
rh
Original Message
Subject:difference between cite inside and outside bibliography
environment
Date: Mon, 28 May 2007 22:45:04 +0200 (CEST)
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Hello,
Dov Feldstern <[EMAIL PROTECTED]> writes:
| José Matos wrote:
| > On Monday 28 May 2007 23:06:18 Andre Poenitz wrote:
| >> Sure, go ahead.
| > BTW, what is the encoding of our source files? I would like to
| > have them all utf8.
| >
| >> Andre'
| >
|
| Jose --- patches are not applying cleanly
Dov Feldstern wrote:
José Matos wrote:
On Monday 28 May 2007 23:06:18 Andre Poenitz wrote:
Sure, go ahead.
BTW, what is the encoding of our source files? I would like to have
them all utf8.
Andre'
Sorry --- Lars is the culprit ;)
Jose --- patches are not applying cleanly anymore b
José Matos wrote:
On Monday 28 May 2007 23:06:18 Andre Poenitz wrote:
Sure, go ahead.
BTW, what is the encoding of our source files? I would like to have them all
utf8.
Andre'
Jose --- patches are not applying cleanly anymore because of the
whitespace cleanup :( ...
José Matos <[EMAIL PROTECTED]> writes:
| On Monday 28 May 2007 23:06:18 Andre Poenitz wrote:
| > Sure, go ahead.
|
| BTW, what is the encoding of our source files? I would like to have them
all
| utf8.
I guess most are latin1.
--
Lgb
On Monday 28 May 2007 23:06:18 Andre Poenitz wrote:
> Sure, go ahead.
BTW, what is the encoding of our source files? I would like to have them all
utf8.
> Andre'
--
José Abílio
Dov Feldstern wrote:
Abdelrazak Younes wrote:
Stefan Schimanski wrote:
I have fixed the logic now in my patch to equal that of LyX 1.4
exactly (see attached).
I've tested this last patch and all seems fine to me WRT cursor
movement. The code cleanup is good too.
Abdel.
Do you not get a
Uwe Stöhr wrote:
Dov, Elazar,
can I commit the other patches from Ran until you agreed to a proper
bind file?:
> 1) Updated he.po file:
> http://www.yousendit.com/download/UVJpaklxeFhubVUwTVE9PQ
>
> 2) Updated Intro:
> http://www.yousendit.com/download/UVJpakl0R0ZtUUUwTVE9PQ
>
> 3) Upd
Elazar Leibovich wrote:
Isn't that wise that the language will be automatically detected by
the input-language. ie, English letters will always be English,
Hebrew/Arabic letters will always be Hebrew/Arabic and neutral
characters will be the same language of the paragraph.
That way, the user won'
On Mon, May 28, 2007 at 11:41:08PM +0200, Lars Gullik Bjønnes wrote:
>
> I'd like to do some whitespace cleanup to trunk before we branch.
Sure, go ahead.
Andre'
Dov, Elazar,
can I commit the other patches from Ran until you agreed to a proper bind file?:
> 1) Updated he.po file:
> http://www.yousendit.com/download/UVJpaklxeFhubVUwTVE9PQ
>
> 2) Updated Intro:
> http://www.yousendit.com/download/UVJpakl0R0ZtUUUwTVE9PQ
>
> 3) Updated Splash:
> http://www.y
I'd like to do some whitespace cleanup to trunk before we branch.
Any objections?
(space at end of line, on line by its own, space followed by tab etc.)
--
Lgb
Stephen Hartke wrote:
Bug: When a math inset is at the end of the line, and the cursor is after
and outside the math inset, hitting the back arrow key goes before the math
inset instead of inside it.
This is fixed now, thanks for reporting it, though!
Abdelrazak Younes wrote:
Stefan Schimanski wrote:
I have fixed the logic now in my patch to equal that of LyX 1.4
exactly (see attached).
I've tested this last patch and all seems fine to me WRT cursor
movement. The code cleanup is good too.
Abdel.
Do you not get a crash with this versio
On Mon, May 28, 2007 at 04:13:26PM -0500, Stephen Hartke wrote:
> Hello! LyX is a fantastic program---I've been using it for about five years
> now. For the last couple years, I've been using Lyx 1.3.4 with a few
> modifications. Since the beta3 of Lyx 1.5.0 just came out, I thought I'd
> give i
Hello! LyX is a fantastic program---I've been using it for about five years
now. For the last couple years, I've been using Lyx 1.3.4 with a few
modifications. Since the beta3 of Lyx 1.5.0 just came out, I thought I'd
give it a spin. Overall, it's great! However, there's a few things about
ho
Koji Yokota schrieb:
No, I have to be more formal :)
OK thanks. You are now also listed in our credits.
regards Uwe
Jean-Marc Lasgouttes wrote:
I suspect it is only the last two lines
\bind "F12" "language hebrew"
\bind "F11" "language english"
If it is the case, the file should read
[some useful comments]
\bind_file cua
\bind "F12" "language hebrew"
\bind "F11" "language english"
I believe this is correc
"Elazar Leibovich" <[EMAIL PROTECTED]> writes:
| Isn't that wise that the language will be automatically detected by
| the input-language. ie, English letters will always be English,
| Hebrew/Arabic letters will always be Hebrew/Arabic and neutral
| characters will be the same language of the para
Isn't that wise that the language will be automatically detected by
the input-language. ie, English letters will always be English,
Hebrew/Arabic letters will always be Hebrew/Arabic and neutral
characters will be the same language of the paragraph.
That way, the user won't be forced to learn new
On Monday 28 May 2007 18:16:32 Jean-Marc Lasgouttes wrote:
> Agreed.
+1
> JMarc
--
José Abílio
On Monday 28 May 2007 20:44:57 Jean-Marc Lasgouttes wrote:
> Yes, but nevertheless the part that reads the .lyx file is weird (the
> parts that reads other files is OK-ish).
I have read this code, fixed some things and I can only agree. :-)
> JMarc
--
José Abílio
Stefan Schimanski wrote:
I have fixed the logic now in my patch to equal that of LyX 1.4 exactly
(see attached).
I've tested this last patch and all seems fine to me WRT cursor
movement. The code cleanup is good too.
Abdel.
Patch is attached to http://bugzilla.lyx.org/show_bug.cgi?id=2475.
Can somebody with deeper understanding please comment why this "dirty
trick" was needed? Haven't found any bad effect without it.
Stefan
PGP.sig
Description: Signierter Teil der Nachricht
Stefan Schimanski wrote:
>> It seems to me that the old way was more straightforward for
>> exactly the
>> same behavior. What are the advantages of the new approach?
>
> The advantages are that it is implemented and probably shorter
> without touching every cursor function. Otherwise there is no
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Uwe Stöhr <[EMAIL PROTECTED]> writes: | 4) I've asked before
Lars> about having a localized Hebrew bind file, and I | was given a
Lars> positive answer. Alas, the file was never committed. So, | here
Lars> is the file again: |
L
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> I dared a few months ago and I've cleaned up a lot of the
Abdelrazak> Lexer class. But it was too late in the game and I gave up
Abdelrazak> because of the promised XML transition.
Yes, but nevertheless the part that
> "Stefan" == Stefan Schimanski <[EMAIL PROTECTED]> writes:
Stefan> And I haven't seen a wide drawer yet in any Mac up. Usually
Stefan> they are vertically layouted and only are 1/3 of the window
Stefan> width or so. Moving it to the same size of the main window
Stefan> somehow looks strange.
Stefan Schimanski wrote:
Drawers can be very wide, and with current Macs having wide screens,
it strikes me as appropriate to use up the screen width with the
source view rather than screen height. (See attached screenshot.)
On reflection, perhaps drawers aren't the best way to go; maybe a
fl
Andre Poenitz wrote:
On Sat, May 26, 2007 at 10:23:01AM +0200, Stefan Schimanski wrote:
The logic is in fact not very complicated. The assumption is that you
only want a new target_x if you go up/down from inside a row.
So far the logic was that target_x is the target coordinate where we
want
Jean-Marc Lasgouttes wrote:
"Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> IMHO the greatest advantage is a clearly defined format. (and I
Lars> am not sure we can really reuse a on-the-shelf parser anyway.
Lars> Except the more simplistic sax parsers that is.)
This means also
Richard Heck wrote:
Abdelrazak Younes wrote:
Richard Heck wrote:
This patch addresses these bugs:
http://bugzilla.lyx.org/show_bug.cgi?id=3741
http://bugzilla.lyx.org/show_bug.cgi?id=3756
The latter is more a policy question, but the bug report seems right to
me: How double-clicking behaves sho
On Sat, May 26, 2007 at 10:23:01AM +0200, Stefan Schimanski wrote:
> The logic is in fact not very complicated. The assumption is that you
> only want a new target_x if you go up/down from inside a row.
So far the logic was that target_x is the target coordinate where we
want to go to. It is set
On Sat, May 26, 2007 at 01:52:44AM +0200, Peter Kümmel wrote:
> > | > | #include not there.
> > | >
> > | > In C++ iso646.h is not needed to get or/and etc.
> > |
> > | when you use gcc
> >
> > When you use a compiler that follows the C++ standard.
> >
>
> Yes I know, GCC will save the world.
Le 27 mai 07 à 00:55, Mael Hilléreau a écrit :
According to Apple's "Bundle Programming Guide",
The Finder identifies packages by any of the following mechanisms:
* The directory has a known
extension: .app, .bundle, .framework, .plugin, .kext, and so on.
* The directory has its bundle bit s
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Am Montag, 28. Mai 2007 10:58 schrieb Abdelrazak Younes:
>> OK, then shouldn't we switch altogether to the unicodesymbols file
>> and forget about this inputenc package? Or maybe this is too much
>> work?
Georg> That would blow up the
On Mon, May 28, 2007 at 11:00:24AM +0200, Georg Baum wrote:
> Am Montag, 28. Mai 2007 10:48 schrieb Jürgen Spitzmüller:
> > Georg Baum wrote:
> > > Note that adding the symbols in question to the unicodesymbols file
> will
> > > automatically solve the problem of broken latex export for greek
>
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> IMHO the greatest advantage is a clearly defined format. (and I
Lars> am not sure we can really reuse a on-the-shelf parser anyway.
Lars> Except the more simplistic sax parsers that is.)
This means also that we can get rid of t
Drawers can be very wide, and with current Macs having wide
screens, it strikes me as appropriate to use up the screen width
with the source view rather than screen height. (See attached
screenshot.)
On reflection, perhaps drawers aren't the best way to go; maybe a
floating window would b
The offset now just keeps track how far off we are after up/down (if
you do not hit the exact pixel column. To decide now if you really
want a new target_x as described above, you additionally check if
your current cursor position plus the offset is pixel-wise exactly
the old target_x. Then it's v
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| Abdelrazak Younes <[EMAIL PROTECTED]> writes:
|
| | Lars Gullik Bjønnes wrote:
| | > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| | > | Edwin Leuven wrote:
| | > | > José Matos wrote:
| | > | >> I am not sure what you mean above. The xml format
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Edwin Leuven wrote:
| > | > José Matos wrote:
| > | >> I am not sure what you mean above. The xml format is just the middle
| > | >> man. The data inside lyx remain th
Richard Heck wrote:
> Try this, just to check: Create a new document; put a listings include
> in it; save and close. Open the document. Open the include and type
> something in the label field; hit return; re-open the dialog. This
> should work. Now create a new include inset, and set it to "inclu
Edwin Leuven wrote:
> afaics you need to select the whole row to switch the lines on/off (this
> is openoffice 2.1, the same behavior as in word i think)
If the cursor is in the cell without selection, the lines of the whole row
will be toggled, only if you select the cell (in word, I need to sel
Abdelrazak Younes wrote:
> Richard Heck wrote:
>> This patch addresses these bugs:
>> http://bugzilla.lyx.org/show_bug.cgi?id=3741
>> http://bugzilla.lyx.org/show_bug.cgi?id=3756
>> The latter is more a policy question, but the bug report seems right to
>> me: How double-clicking behaves shouldn't
Abdelrazak Younes wrote:
> Edwin Leuven wrote:
>> and a crucial question is of course the following:
>> who is planning to work on this (and finish it)?
> I would help.
Me, too, as I have time.
Richard
--
==
Richard G Heck, Jr
Profe
Angus Leeming wrote:
> Richard Heck wrote:
>> For some reason, changing the type of the dialog switches the default
>> button from OK to Cancel. This restores the correct default. Must be a
>> QT bug.
>>
>> Still seeking two OKs...or at least some reaction!
>
> Hi, Richard.
>
> The button is change
On Monday 28 May 2007 16:30:55 Uwe Stöhr wrote:
> Can this be committed?
If Hebrew developers agree on this sure. :-)
> regards Uwe
--
José Abílio
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Edwin Leuven wrote:
| > José Matos wrote:
| >> I am not sure what you mean above. The xml format is just the middle
| >> man. The data inside lyx remain the same.
| > and a crucial question is of course the following:
| >
On Mon, 28 May 2007, Uwe Stöhr wrote:
That is probably done by word. iconv is not used here (at least not
directly, maybe internally by qt, but if it would do this change whan
asked to convert from utf16 (QString) to ucs4 (docstring) it would be
a bug). Paste from word to a real text editor,
Uwe Stöhr <[EMAIL PROTECTED]> writes:
| 4) I've asked before about having a localized Hebrew bind file, and I
| was given a positive answer. Alas, the file was never committed. So,
| here is the file again:
| http://www.yousendit.com/download/UVJpaklxeFhRYTgwTVE9PQ
This 4. one puzzles me a bit. W
Richard Heck wrote:
For some reason, changing the type of the dialog switches the default
button from OK to Cancel. This restores the correct default. Must be a
QT bug.
Still seeking two OKs...or at least some reaction!
Hi, Richard.
The button is changed because the GUI view is telling the Bu
Ran wrote:
Hi,
I've made I few updates:
1) Updated he.po file:
http://www.yousendit.com/download/UVJpaklxeFhubVUwTVE9PQ
2) Updated Intro:
http://www.yousendit.com/download/UVJpakl0R0ZtUUUwTVE9PQ
3) Updated Splash:
http://www.yousendit.com/download/UVJpaklqVEhENlEwTVE9PQ
4) I've asked before
Lars Gullik Bjønnes wrote:
| who is planning to work on this (and finish it)?
I am. The DTD is some 70-80% finished I guess.
Quite a bit of writing is done, parsing/reading is not begun.
i was asking because we should be sure in advance that there is enough
competent and motivated manpower to
>>"\\newcommand{\\lyxcareof}{\\leavevmode\\hbox{\\raise.75ex\\hbox{c}\\kern-.15em/\\kern-.125em\\smash{\\lower.3ex\\hbox{o}}}\\ignorespaces}"
>> ""
>
> \newcommand*\lyxcareof{%
> \mbox{\raisebox{.8ex}{c}\kern-.175em\raisebox{.2ex}{/}%
> \kern-.18em\raisebox{-.2ex}{o}}}
Thanks I use now your sol
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Edwin Leuven wrote:
| > José Matos wrote:
| >> I am not sure what you mean above. The xml format is just the middle
| >> man. The data inside lyx remain the same.
| > and a crucial question is of course the following:
| > who is planning to work on t
Jürgen Spitzmüller wrote:
About the ui: I find it irritating that I have to select the whole row
now to switch lines on/off.
you find it irritating because it is different, but ui-wise i think it
is much more intuitive...
Not for me.
And why should we do it differently than we used to
becau
Edwin Leuven <[EMAIL PROTECTED]> writes:
| José Matos wrote:
| > I am not sure what you mean above. The xml format is just the middle
| > man. The data inside lyx remain the same.
|
| and a crucial question is of course the following:
|
| who is planning to work on this (and finish it)?
I am. T
Edwin Leuven wrote:
José Matos wrote:
I am not sure what you mean above. The xml format is just the middle
man. The data inside lyx remain the same.
and a crucial question is of course the following:
who is planning to work on this (and finish it)?
I agree that we should make sure that we h
José Matos wrote:
On Monday 28 May 2007 15:50:11 Charles de Miramon wrote:
I fail to see what are the big advantages (except reusing an on-the-shelf
parser). Moving away from LaTeX logic will complexify the LyX -> LaTeX
process.
I am not sure what you mean above. The xml format is just the mi
On Mon, May 28, 2007 at 10:20:57AM +0900, Koji Yokota wrote:
> Peter Kümmel wrote:
> > Hasn't Abdel fixed it today? Maybe updating helps.
>
> Yeah, right. With a newer version, Lyx at least proceeds with a
> successful initialization and its GUI appears. However, trial of File ->
> New, File ->
Charles de Miramon <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
|
| > ODF is also xml based afaik.
| >
|
| Yes but the logic of formatting of an ODF file and of a LyX file (modelled
| on LaTeX) is very different. There is no preamble for example in ODF.
Right. It also seems to m
José Matos wrote:
I am not sure what you mean above. The xml format is just the middle
man. The data inside lyx remain the same.
and a crucial question is of course the following:
who is planning to work on this (and finish it)?
(count me out btw, i intend to do a bit of tabular cleaning...)
Abdelrazak Younes wrote:
Richard Heck wrote:
This patch addresses these bugs:
http://bugzilla.lyx.org/show_bug.cgi?id=3741
http://bugzilla.lyx.org/show_bug.cgi?id=3756
The latter is more a policy question, but the bug report seems right to
me: How double-clicking behaves shouldn't depend upon wh
On Monday 28 May 2007 15:50:11 Charles de Miramon wrote:
> I fail to see what are the big advantages (except reusing an on-the-shelf
> parser). Moving away from LaTeX logic will complexify the LyX -> LaTeX
> process.
I am not sure what you mean above. The xml format is just the middle man. The
d
Richard Heck wrote:
This patch addresses these bugs:
http://bugzilla.lyx.org/show_bug.cgi?id=3741
http://bugzilla.lyx.org/show_bug.cgi?id=3756
The latter is more a policy question, but the bug report seems right to
me: How double-clicking behaves shouldn't depend upon whether
something's already
This patch addresses these bugs:
http://bugzilla.lyx.org/show_bug.cgi?id=3741
http://bugzilla.lyx.org/show_bug.cgi?id=3756
The latter is more a policy question, but the bug report seems right to
me: How double-clicking behaves shouldn't depend upon whether
something's already in the selected citati
Lars Gullik Bjønnes wrote:
> ODF is also xml based afaik.
>
Yes but the logic of formatting of an ODF file and of a LyX file (modelled
on LaTeX) is very different. There is no preamble for example in ODF.
This blog is interesting and it seems to me that LaTeX is rather similar to
Wordperfect.
Try this, just to check: Create a new document; put a listings include
in it; save and close. Open the document. Open the include and type
something in the label field; hit return; re-open the dialog. This
should work. Now create a new include inset, and set it to "include".
Close. Re-open the firs
Jürgen,
with a little luck, I will be able to do some translator work this
evening - right in time for pre1.
Michael
Jürgen Spitzmüller schrieb:
Jürgen Spitzmüller wrote:
"Insert table" (just a table, no float) is a string that
don't exist in either nb.po or de.po.
Does the attac
Abdelrazak Younes wrote:
> > For some reason, changing the type of the dialog switches the default
> > button from OK to Cancel. This restores the correct default. Must be a
> > QT bug.
>
> If it is, it must be local to linux. Here (WinXP, Qt4.2.1) the focus
> stays on the OK button.
Here, everyth
Edwin Leuven wrote:
> > The bug is that the top- and bottomlines can no longer be toggled in
> > booktabs mode.
>
> i don't think so.
>
> you cannot toggle the top line on the *first* row and the bottom line on
> the last row.
>
> this is intentional: we don't allow the user to toggle these atm (ju
Richard Heck wrote:
For some reason, changing the type of the dialog switches the default
button from OK to Cancel. This restores the correct default. Must be a
QT bug.
If it is, it must be local to linux. Here (WinXP, Qt4.2.1) the focus
stays on the OK button.
Still seeking two OKs...or a
Jürgen Spitzmüller wrote:
Edwin Leuven wrote:
you're right, going back and forth would be a problem so either we do
the full monty or we forget about this.
for 1.5, you mean. You can commit this immediately to trunk as soon as we have
a BRANCH_1_5_X.
ok
The bug is that the top- and bottom
For some reason, changing the type of the dialog switches the default
button from OK to Cancel. This restores the correct default. Must be a
QT bug.
Still seeking two OKs...or at least some reaction!
rh
--
==
Richard G Heck, Jr
Pro
Charles de Miramon <[EMAIL PROTECTED]> writes:
| José Matos wrote:
|
| >
| > We gain xsl to write converters to other formats
|
| If KOffice can be point of comparison. Before switching to ODF, we had a xml
| format and nobody (well actually one man) wrote any xsl converters because
| it
Edwin Leuven wrote:
> you're right, going back and forth would be a problem so either we do
> the full monty or we forget about this.
for 1.5, you mean. You can commit this immediately to trunk as soon as we have
a BRANCH_1_5_X.
> fwiw, the attached patch is working great and imho very safe (i t
Jürgen Spitzmüller wrote:
What would that mean if someone opens a file done with, say, 1.5.2
(with cline support) with 1.5.1 (without cline support)? Will this
file be displayed and exported correctly? Will it be saved correctly,
so that the file again opens without dataloss in 1.5.2?
you're ri
José Matos wrote:
>
> We gain xsl to write converters to other formats
If KOffice can be point of comparison. Before switching to ODF, we had a xml
format and nobody (well actually one man) wrote any xsl converters because
it seems that everybody hates xslt.
Cheers,
Charles
--
http://www
Jürgen Spitzmüller wrote:
>
> What would that mean if someone opens a file done with, say, 1.5.2 (with
> cline support) with 1.5.1 (without cline support)? Will this file be
> displayed and exported correctly? Will it be saved correctly, so that the
> file again opens without dataloss in 1.5.2?
>
On Monday 28 May 2007 12:07:32 Charles de Miramon wrote:
> What LyX is going to gain with a XML file format ? Except being buzz
> compliant.
We will have our file format supported by all the xml related tools. Think
about the parser, the grammar is easier to define and so on... Currently
there
On Monday 28 May 2007 12:25:08 Jürgen Spitzmüller wrote:
> looks sensible.
+1
> > (btw. Why is the \author updated even if I am not using
> > changetracking? Cannot this be considered information leak?)
>
> I think so, too.
+1
> Jürgen
--
José Abílio
On Monday 28 May 2007 11:16:35 Abdelrazak Younes wrote:
> Jürgen Spitzmüller wrote:
> > Abdelrazak Younes wrote:
> >> Try 'odocstream &'.
> >
> > Yes, this works, thanks.
> >
> > Shall I apply?
>
> Fine with me.
+1
> Abdel.
--
José Abílio
Abdelrazak Younes wrote:
> > What about
> > for 1.5.0 a patch with the file format change and a small logic to tell
> > Lyx to just skip the cline format, if it finds any
> >
> > for 1.5.1 the gui and the latex generator
> >
> > Advice from an ignorant,
>
> This is very sensible IMHO. Is this possi
On Monday 28 May 2007 12:28:55 Jean-Marc Lasgouttes wrote:
> But there are very weird chemical (thermonuclear?) reaction going on
> between Abdel and Lars...
Thermonuclear is not what I associate with chemical reactions. ;-)
> JMarc
--
José Abílio
1 - 100 of 160 matches
Mail list logo
