Bo Peng <[EMAIL PROTECTED]> writes:
> I strongly believe that the next big thing for lyx should be ODF or
> Word/XML compatibility.
I agree completely and wholeheartedly.
Andreas
I spent hours, under both linux and windows, trying to use tex4ht to
convert even a simplest tex file to open office. The generated .odt
file just does not work. This is after I follow closely the
instructions in
http://facweb.knowlton.ohio-state.edu/pviton/support/tex4ht.html and
passed all the
On Feb 14, 2007, at 7:22 PM, Jens Noeckel wrote:
Hi Bennett,
I tried out the new Intel-Mac binary on the FTP server but got a
crash because the Application tried to load a library from a non-
existent path: libintl.3.dylib on my computer doesn't exist in /usr/
local/lib, but LyX looks for i
- Original Message -
>> From: Georg Baum <[EMAIL PROTECTED]>
>> To: lyx-devel@lists.lyx.org
>> Date: 2007-02-15 04:49:28
>> Subject: Re: Beta schedule
>>
>>
>> It would look like the attached patch. I chose one encoding for each of
>> chinese, japanese and korean. Did I chose the most
> "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes:
Michael> Hi, here comes the promised (long time ago) cleanup patch for
Michael> plain text output.
Why are some labels ("foot") lowercase and some other ("Branch")
capitalized?
Would it be possible to set correctly the inset names and u
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> I've placed the Intel Mac binary here:
Bennett> http://edisk.fandm.edu/bennett.helm/LyX/LyX-1.4.4-Mac-Intel.dmg
Bennett> I always forget where I should upload the binaries, so let me
Bennett> know if I should put it somewhere e
Bo Peng wrote:
> Public release of LyX version 1.4.4
> ===
Can anyone test lyx windows installers from http://www.lyx.org/~bpeng?
This is the first time I build an installer for 1.4.x so I would like
to get some feedbacks before they are moved to the official pla
> >
> > $ ./lyx
> > terminate called after throwing an instance of 'std::logic_error'
> > what(): basic_string::_S_construct NULL not valid
> > Aborted
just for the record - the whole problem was linking with the old libraries
on the system.
pavel
Am Mittwoch, 14. Februar 2007 12:24 schrieb José Matos:
> But if no better solution is available then the menu solution is the
least
> worse. :-)
It would look like the attached patch. I chose one encoding for each of
chinese, japanese and korean. Did I chose the most commonly used ones? Is
Am Mittwoch, 14. Februar 2007 15:53 schrieb Jean-Marc Lasgouttes:
> > "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes:
>
> Michael> we haven't done anything so far. What is your proposed
> Michael> solution?
>
> Return to the 1.4 solution (that is add the _() in the one place where
> it
> Public release of LyX version 1.4.4
> ===
Can anyone test lyx windows installers from http://www.lyx.org/~bpeng?
This is the first time I build an installer for 1.4.x so I would like
to get some feedbacks before they are moved to the official places.
Cheers,
Bo
On Feb 14, 2007, at 10:03 AM, Jean-Marc Lasgouttes wrote:
Public release of LyX version 1.4.4
===
I've placed the Intel Mac binary here:
http://edisk.fandm.edu/bennett.helm/LyX/LyX-1.4.4-Mac-Intel.dmg
I always forget where I should upload the binaries, so let
On Wednesday 14 February 2007 4:43:19 pm Michael Gerz wrote:
> Hi,
>
> here comes the promised (long time ago) cleanup patch for plain text
> output.
>
> OK to commit?
Is anyone opposed to this patch?
> Michael
--
José Abílio
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> Next...:
Is this better?
JMarc
Index: src/frontends/qt4/QLMenubar.C
===
--- src/frontends/qt4/QLMenubar.C (revision 17186)
+++ src/frontends/qt4/QLMenubar.C (work
Michael Gerz wrote:
> Jürgen Spitzmüller schrieb:
>> Did you have a look at the new changes (or so) package at ctan? I think
>> it uses soul instead of ulem (which cannot break accros lines IIRC), and
>> it seems to do a pretty good job.
>>
> AFAICS, it does not support change bars.
You're righ
Hi,
here comes the promised (long time ago) cleanup patch for plain text output.
OK to commit?
Michael
Index: src/insets/insetenv.h
===
--- src/insets/insetenv.h (Revision 17187)
+++ src/insets/insetenv.h (Arbeitskopie)
@@ -32,6 +3
> "Jürgen" == Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
Jürgen> I guess it was slowed down because a lot of crap was passed
Jürgen> and checked by handleFoundFile, e.g. things like
Jürgen> (prettyref) ... or package varioref ... (FMi)
Jürgen> (Now, with the blanks check moved to handleF
Michael Gerz wrote:
> Georg Baum schrieb:
>> Since I believe that \output_changes was decoupled from \tracking_changes
>> on purpose 1) iss not an option, so 2) is left. As I said, that will
>> change 1.5 documents unwantedly, but that is IMHO better than doing the
>> same to 1.4 documents.
>>
>
> $ ./lyx
> terminate called after throwing an instance of 'std::logic_error'
> what(): basic_string::_S_construct NULL not valid
> Aborted
backtrace from gdb:
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct NULL not valid
Program r
Georg Baum schrieb:
Michael Gerz wrote:
Hi,
is there any reason why copying and pasting text from LyX to a text
editor results in a different output than plain text export?
I don't think so. What exactly is the difference?
E.g., a footnote is not output with copy&paste.
Michael
Georg Baum schrieb:
1) Go back to the 1.4 behaviour and let \tracking_changes take precdence
over \output_changes
2) Do a file format change and convert all files with
\tracking_changes false
\output_changes true
to
\tracking_changes false
\output_changes false
Since I believe that \output_
Michael Gerz wrote:
> Hi,
>
> is there any reason why copying and pasting text from LyX to a text
> editor results in a different output than plain text export?
I don't think so. What exactly is the difference?
Georg
Jean-Marc Lasgouttes lyx.org> writes:
>
>
> Public release of LyX version 1.4.4
> ===
>
> We are pleased to announce the release of LyX 1.4.4.
Hooray! *applauses*
Andreas
> "christian" == christian ridderstrom <[EMAIL PROTECTED]> writes:
christian> Here's an alternative I think read slightly better (I'm
christian> probably to late, but maybe..)
It was better indeed, but I read it to late :)
JMarc
Michael Gerz wrote:
> Georg Baum schrieb:
>> This is no surprise since lyx2lyx adds "\output_changes true" when you
>> convert from 1.3 to 1.4, so this will affect _a lot_ of files.
>>
> And what does it do to \changes_track? Let me guess: It sets it to false.
>
> If guessed correctly, than it
On 2/15/07, José Matos <[EMAIL PROTECTED]> wrote:
On Wednesday 14 February 2007 9:54:29 am Georg Baum wrote:
> > I vote against. This was bug 2313:
>
> Me too.
Me too.
Poll ends. I will train my fingers C-s. :-)
Cheers,
Bo
Public release of LyX version 1.4.4
===
We are pleased to announce the release of LyX 1.4.4. This is of course
a bug fix release, but some new features sneaked in, among which:
- Outline support: it is now possible to move around parts of
documents in the Table
> OTOH I don't think we should include any new features for 1.5, and this could
> also wait until 1.6, so I can be tested properly.
>
I don't consider this as a new feature but as a final step in the CT
refinement.
This looks to me like a big change since we suddenly do not require
pplatex. Any
> "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes:
Michael> we haven't done anything so far. What is your proposed
Michael> solution?
Return to the 1.4 solution (that is add the _() in the one place where
it has been removed), and think about it later. This is not a very
interesting prob
José Matos wrote:
On Wednesday 14 February 2007 1:31:30 pm Jean-Marc Lasgouttes wrote:
"José" == José Matos <[EMAIL PROTECTED]> writes:
José> I would think that a paragraph in the release announcement
José> saying that this is the expected penultimate release in the
José> stable 1.4 series an
On Wed, 14 Feb 2007, Jean-Marc Lasgouttes wrote:
"José" == José Matos <[EMAIL PROTECTED]> writes:
José> I would think that a paragraph in the release announcement
José> saying that this is the expected penultimate release in the
José> stable 1.4 series and the first beta of the 1.5 developme
On Wednesday 14 February 2007 1:31:30 pm Jean-Marc Lasgouttes wrote:
> > "José" == José Matos <[EMAIL PROTECTED]> writes:
>
> José> I would think that a paragraph in the release announcement
> José> saying that this is the expected penultimate release in the
> José> stable 1.4 series and the
Jürgen Spitzmüller schrieb:
Did you have a look at the new changes (or so) package at ctan? I think it
uses soul instead of ulem (which cannot break accros lines IIRC), and it
seems to do a pretty good job.
AFAICS, it does not support change bars.
OTOH I don't think we should include any ne
Jean-Marc Lasgouttes wrote:
> I saw you wrote this was slowing things down. What was the slow code
> that got triggered?
It is just a feeling, it didn't do any measuring.
I guess it was slowed down because a lot of crap was passed and checked by
handleFoundFile, e.g. things like
(prettyref) ...
> "José" == José Matos <[EMAIL PROTECTED]> writes:
José> I would think that a paragraph in the release announcement
José> saying that this is the expected penultimate release in the
José> stable 1.4 series and the first beta of the 1.5 development
José> series will be release this week. (or
Michael Gerz wrote:
> Any opinions?
Did you have a look at the new changes (or so) package at ctan? I think it
uses soul instead of ulem (which cannot break accros lines IIRC), and it
seems to do a pretty good job.
OTOH I don't think we should include any new features for 1.5, and this could
a
Hi,
is there any reason why copying and pasting text from LyX to a text
editor results in a different output than plain text export?
Michael
José Matos wrote:
> I would like to see the cjk-pathes commited before the beta. It would be
> nice to have Jürgen's fixes to the regex's but this is not a blocker, that
> is we had this bug for so long that one other release will not matter. :-)
The most important fix is in. The refinement can be
> "Jürgen" == Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
Jürgen> Jean-Marc Lasgouttes wrote:
>> And if people have their local texmf in a directory with spaces? A
>> change to a global .sty file would not get detected, right?
Jürgen> with my latest change, it would (as long as the TEXMF t
Georg Baum schrieb:
I do consider that a bug, because users may not even be aware that CT is on
in their 1.4 documents. Did you know that it is on in all but one file in
our own documentation (both 1.4 and 1.5)?
$ grep 'output_changes true' lib/doc/*.lyx | wc -l
59
$ grep 'output_changes' lib/d
Michael Gerz schrieb:
So you are telling me that 1.4 checks whether there is any change in
the doc and if not, it does not include dvipost?
While we are discussing dvipost: I would like to get rid of it for 1.5.0!
dvipost has two drawbacks:
1. It only works with DVI output, pdflatex is badly ig
On Wednesday 14 February 2007 12:59:51 pm José Matos wrote:
> FWIW I attach the difference between the latex output generated by
> lyx-1.4 and lyx-1.5 to the User's Guide from lyx-1.4.3
Argh now it is real. :-)
--
José Abílio
userguide-latex.diff.gz
Description: GNU Zip compressed data
Michael Gerz wrote:
> Georg Baum schrieb:
>> Of course it has to be different. The problem is that these outputs come
>> from exactly the same file. It has
>>
>> \output_changes true
>>
>> but 1.4 does not output any dvipost stuff because there is no unaccepted
>> change in the file. I don't know
On Wednesday 14 February 2007 12:43:47 pm Michael Gerz wrote:
>
> Anyway, I think that user are more or less aware that output may be
> different when CT output is activated. If there is some discrepancy
> between 1.4 and 1.5 in CT output mode, I don't consider this as a bug.
FWIW I attach the d
On Wednesday 14 February 2007 12:50:17 pm Georg Baum wrote:
> The default for now is to use the encoding from the locale (if you give the
> --cjk switch without an argument). This is what CJK-LyX itself does. IMHO
> this is better than having the file command tell that the korean file is in
> 8859
José Matos wrote:
> I did not want to remove the user's preference but just to get a
> reasonable
> default. The user should always be able to override the option.
The default for now is to use the encoding from the locale (if you give the
--cjk switch without an argument). This is what CJK-L
Jean-Marc Lasgouttes schrieb:
The idea was to be able to return untranslated strings to the
lyxserver so that they could be acted on (for example error messages).
I'd propose to restore things as they were, and keep the decision
about what the best design is for later.
JMarc,
we haven't d
Georg Baum schrieb:
Of course it has to be different. The problem is that these outputs come
from exactly the same file. It has
\output_changes true
but 1.4 does not output any dvipost stuff because there is no unaccepted
change in the file. I don't know whether that is a bug in 1.4 or in 1.5 o
On Wednesday 14 February 2007 11:05:12 am Michael Gerz wrote:
> I looked at the diff - I see a 1.5-generated TeX file with CT output
> activated and a 1.4-generated TeX file with CT output disabled.
For the same 1.4 original file, this is the problem. So either the CT option
was ignored in lyx-
- Original Message -
>> From: Jos�_Matos <[EMAIL PROTECTED]>
>> To: lyx-devel@lists.lyx.org
>> Date: 2007-02-14 18:39:15
>> Subject: Re: Beta schedule
>>
>> > Then how about using Import menu button, such as "Import -> CJK-LyX-1.4.x
>> > -> {Korean(euc-kr), Chinese(big5),...}" ?.
Michael Gerz wrote:
Abdelrazak Younes schrieb:
This commit fixes the crash and the bug with a minor side effect: The
cursor goes out of the inset.
Only if there is leading space or in any case?
Yes (and also only if the paragraph is empty afterward).
I do hope it leaves the
inset only in ra
Abdelrazak Younes schrieb:
You're a fief Jose :-)
Joke aside, it would be nice to have a dual announcement LyX-1.4.4 and
first 1.5-beta. This would draw bigger attention than separated ones.
Not necessarily. IMHO two different announcements within a short period
of time draw even more attentio
Abdelrazak Younes schrieb:
This commit fixes the crash and the bug with a minor side effect: The
cursor goes out of the inset.
Only if there is leading space or in any case? I do hope it leaves the
inset only in rare cases...
Anyway, thanks for fixing the bug.
Michael
José Matos wrote:
> On Wednesday 14 February 2007 11:35:46 am Abdelrazak Younes wrote:
>> You're a fief Jose :-)
>
> :-)
>
>> Joke aside, it would be nice to have a dual announcement LyX-1.4.4 and
>> first 1.5-beta. This would draw bigger attention than separated ones.
>
> I would think tha
On Wednesday 14 February 2007 11:35:46 am Abdelrazak Younes wrote:
> You're a fief Jose :-)
:-)
> Joke aside, it would be nice to have a dual announcement LyX-1.4.4 and
> first 1.5-beta. This would draw bigger attention than separated ones.
I would think that a paragraph in the release annou
Michael Gerz wrote:
> I looked at the diff - I see a 1.5-generated TeX file with CT output
> activated and a 1.4-generated TeX file with CT output disabled.
>
> Are we comparing applies and pies here? Nobody ever stated that TeX
> output has to be the same with CT output on and off. In fact, the
José Matos wrote:
On Tuesday 13 February 2007 2:43:58 pm Abdelrazak Younes wrote:
Jean-Marc Lasgouttes wrote:
Subjects says it all, really. I will make the last adjustments to the
annoncements and friends today.
Jose, what are you going to answer? You cannot let JMarc beat you so
easily...
On Wednesday 14 February 2007 9:54:29 am Georg Baum wrote:
> > I vote against. This was bug 2313:
>
> Me too.
Me too.
--
José Abílio
On Tuesday 13 February 2007 2:43:58 pm Abdelrazak Younes wrote:
> Jean-Marc Lasgouttes wrote:
> > Subjects says it all, really. I will make the last adjustments to the
> > annoncements and friends today.
>
> Jose, what are you going to answer? You cannot let JMarc beat you so
> easily...
But tha
Georg Baum wrote:
> This is obviously a boost speciality. A normal regex e.g. in grep would
> match, but it seems that in boost you need to use regex_search instead of
> regex_match if you also want matches that do not cover the whole string.
Indeed. Thanks.
> Maybe using regex_search is also the
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> I can now reproduce bug 3225
Abdelrazak> http://bugzilla.lyx.org/show_bug.cgi?id=3225
Abdelrazak> This is tricky as this involved the dEPM mechanism
Abdelrazak> somehow. The problem is that th
On Wednesday 14 February 2007 9:57:05 am Georg Baum wrote:
> We should not do that. Some programs (including file) pretend to be able to
> detect encodings automatically. But it is the very nature of encodings that
> you have to specify which one you use. Those programs that try to detect
> the enc
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
I can now reproduce bug 3225
http://bugzilla.lyx.org/show_bug.cgi?id=3225
This is tricky as this involved the dEPM mechanism somehow.
More exactly it is stripLeadingSpaces() that is triggered...
This commit fixes the crash and the bug with
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> I can now reproduce bug 3225
Abdelrazak> http://bugzilla.lyx.org/show_bug.cgi?id=3225
Abdelrazak> This is tricky as this involved the dEPM mechanism
Abdelrazak> somehow. The problem is that the leading empty space is
Jean-Marc Lasgouttes wrote:
> What I would do is:
>
> 1/take the name up to the first space. If it is a known file name,
> stop there
>
> 2/ add the token up to next space; if the file exists stop, otherwise,
> go back to 2/.
>
> This is getting a bit too complicated for my taste, but it should
> w
Georg Baum schrieb:
Why? Can you point me to the relevant posting? I don't find it anymore.
IIRC José and me came to the conclusion that LyX 1.4 can handle all 1.5
docs and lyx2lyx already took care of the 1.4->1.3 conversion.
The problem is that the beamer templates (before Enrico changed
Michael Gerz wrote:
Abdelrazak Younes schrieb:
Abdelrazak Younes wrote:
I can now reproduce bug 3225
http://bugzilla.lyx.org/show_bug.cgi?id=3225
This is tricky as this involved the dEPM mechanism somehow.
More exactly it is stripLeadingSpaces() that is triggered...
One question Uwe, how i
Abdelrazak Younes schrieb:
Abdelrazak Younes wrote:
I can now reproduce bug 3225
http://bugzilla.lyx.org/show_bug.cgi?id=3225
This is tricky as this involved the dEPM mechanism somehow.
More exactly it is stripLeadingSpaces() that is triggered...
One question Uwe, how is it that you have a
Jürgen Spitzmüller wrote:
> Georg Baum wrote:
>> I don't understand why
>> that is there, it should also work without.
>
> It doesn't. Complex lines are not found then.
This is obviously a boost speciality. A normal regex e.g. in grep would
match, but it seems that in boost you need to use regex
Abdelrazak Younes wrote:
I can now reproduce bug 3225
http://bugzilla.lyx.org/show_bug.cgi?id=3225
This is tricky as this involved the dEPM mechanism somehow.
More exactly it is stripLeadingSpaces() that is triggered...
One question Uwe, how is it that you have a leading space in the text
d
Abdelrazak Younes wrote:
I can now reproduce bug 3225
http://bugzilla.lyx.org/show_bug.cgi?id=3225
The weird thing about this bug is that LCursor::fixIfBroken() will
correctly fix the CursorSlice if the LyX window is not maximised but not
if it maximized with a 1280*1024 screen.
Abdel.
I can now reproduce bug 3225
http://bugzilla.lyx.org/show_bug.cgi?id=3225
This is tricky as this involved the dEPM mechanism somehow. The problem
is that the leading empty space is erased (because par beginning with
empty spaces are not allowed) but the CursorSlice corresponding to the
is not
Jean-Marc Lasgouttes wrote:
> And if people have their local texmf in a directory with spaces? A
> change to a global .sty file would not get detected, right?
with my latest change, it would (as long as the TEXMF tree would not contain
weird spaces-dots-combinations).
BTW you would be surprised
Georg Baum wrote:
José Matos wrote:
On Wednesday 14 February 2007 9:35:39 am ChangGil Han wrote:
Hello,
Then how about using Import menu button, such as "Import -> CJK-LyX-1.4.x
-> {Korean(euc-kr), Chinese(big5),...}" ?. I hope I am not asking
too much!
Yes, that would be easily doable
In the lyx1.5svn, if using the language's default encoding (default option
in the setting dialog) hebrew text inserted into headers (such as title,
author and date) is displayed as gibbrish.
The other text in the document is displayed correctly. One possible solution
is changing the encoding manua
José Matos wrote:
> On Wednesday 14 February 2007 9:35:39 am ChangGil Han wrote:
>> Hello,
>> Then how about using Import menu button, such as "Import -> CJK-LyX-1.4.x
>> -> {Korean(euc-kr), Chinese(big5),...}" ?. I hope I am not asking
>> too much!
Yes, that would be easily doable. What do
Jean-Marc Lasgouttes wrote:
>> "Georg" == Georg Baum
>> <[EMAIL PROTECTED]>
>> writes:
>
> Georg> Since this fix will be also in 1.4.4 the packagers need to
> Georg> update any lyxrc.dist file if they are shipping one. And I
> Georg> would also mention it in the release notes, since p
Jean-Marc Lasgouttes wrote:
> Since I am planning to release today, I'd rather skip it for now.
OK. I'll come back with it for 1.4.5.
Jürgen
Jean-Marc Lasgouttes wrote:
>> "Bo" == Bo Peng <[EMAIL PROTECTED]>
>> writes:
>
> Bo> I need another two positive votes to proceed. :-)
>
> I vote against. This was bug 2313:
Me too.
> In particular, the argument of Alt-F S is weird, since Ctrl+S is
> guaranteed by CUA to be Save in al
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Since this fix will be also in 1.4.4 the packagers need to
Georg> update any lyxrc.dist file if they are shipping one. And I
Georg> would also mention it in the release notes, since people might
Georg> have customized their preferences
Bo Peng wrote:
At least emacs.bind has Cntl-S. That's standard Windows-ese as well,
so I'd be
suprised if cua.bind didn't have it too. No need to go through the
file menu
at all.
But my patch will do no harm. Also, in terms of logic: why cannot I
save a clean file? I should be able to save my
> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes:
>> At least emacs.bind has Cntl-S. That's standard Windows-ese as
>> well, so I'd be suprised if cua.bind didn't have it too. No need to
>> go through the file menu at all.
Bo> But my patch will do no harm. Also, in terms of logic: why cannot
Bo>
On Wednesday 14 February 2007 9:35:39 am ChangGil Han wrote:
> Hello,
>
> >> > It is not essential, but it would be extremely convenient if with the
> >> > use
> >>
> >> of this lyx2lyx we could just "open" the cjk-lyx file from the lyx-svn.
> >>
> >> How could that work? The problem is twofold:
>
> "Jürgen" == Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
Jürgen> Jürgen Spitzmüller wrote:
>> + // search for strings in (...) that must not contain + // a
>> blank, but must contain a dot + static regex reg1_1("\\(([^
>> ()]+\\.+[^ ()]+)");
Jürgen> BTW this regex change also fixes bug 32
> "Jürgen" == Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
Jürgen> Abdelrazak Younes wrote:
>> Then don't forget that the temp directory might be in a path with
>> spaces, ex:
>>
>> C:\Documents and Settings\toto\temp\
Jürgen> Not a problem. The log file does not contains this path, just
J
Bo Peng wrote:
There's an autosave facility in LyX. You don't need to do this at all.
I'm
pretty certain I tried damn hard to make it work under Windows.
I know. This likes a habit .., whenever I stop typing, my fingers will
be doing Alt-F-S. I have actually defined a more convenient shortcut
> "Jürgen" == Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
Jürgen> Jean-Marc Lasgouttes wrote:
>> Are you sure that spaces never happen? What about files in
>> c:\program files\something\something else\?
Jürgen> I don't know what's happening on windows exactly. Here on
Jürgen> linux, those
Hello,
- Original Message -
>> From: Georg Baum <[EMAIL PROTECTED]>
>> To: lyx-devel@lists.lyx.org
>> Date: 2007-02-14 01:42:31
>> Subject: Re: Beta schedule
>>
>> > "lyx2lyx -c eux-kr cjk-lyx_file > lyx-svn_file" correctly translates CJK
>> characters in cjk-lyx_file.
>>
>> OK, th
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Instead of working around this Qt hack why not just rename
Abdelrazak> our menu item to "LyX Preferences", "LyX About", etc? Then
Abdelrazak> in en.po (which does not exist now but could be created),
Abdelrazak> we jus
> "forenr" == forenr <[EMAIL PROTECTED]> writes:
forenr> Author: forenr Date: Tue Feb 13 23:41:39 2007 New Revision:
forenr> 17176
forenr> URL: http://www.lyx.org/trac/changeset/17176 Log: Was
forenr> forgetting this
Typically the kind of thing that would be very very bad just before a
rele
Michael Gerz wrote:
> Georg Baum schrieb:
>>> This is due to the following line in the .lyx file:
>>>
>>> \output_changes true
>>>
>>> Simply uncheck "Document->Change Tracking->Show Changes in Output"
>>> and everything is ok. I dont know why this is not a problem in 1.4.x.
>>> Indeed, 1.4.x seem
Georg Baum schrieb:
This is due to the following line in the .lyx file:
\output_changes true
Simply uncheck "Document->Change Tracking->Show Changes in Output"
and everything is ok. I dont know why this is not a problem in 1.4.x.
Indeed, 1.4.x seems not using dvipost in this case:
That me
Andre Poenitz schrieb:
On Tue, Feb 13, 2007 at 04:14:11PM +0100, Abdelrazak Younes wrote:
Then don't forget that the temp directory might be in a path with
spaces, ex:
C:\Documents and Settings\toto\temp\
I know, this is shit, and I'd really prefer LyX to just just C:\temp\
which, AFAIK,
Pavel Sanda wrote:
>> If you do have automake, is this a $PATH problem? I am not an automake
>> expert so I can not really help here.
>
> i can tweak the problem myself, thats not the problem.
>
> the real question here is whether lyx doesnt allow automake 1.10 on
> purpose or its just leftover.
94 matches
Mail list logo
