> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Jean-Marc Lasgouttes wrote:
>> Goerg, could you port the changes you did to configure.m4 to
>> configure.py? I'd like to keep them in sync.
Georg> Sure. The attached goes in.
Thanks.
JMarc
Jean-Marc Lasgouttes wrote:
> Goerg, could you port the changes you did to configure.m4 to
> configure.py? I'd like to keep them in sync.
Sure. The attached goes in.
GeorgIndex: lib/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/ly
Goerg, could you port the changes you did to configure.m4 to
configure.py? I'd like to keep them in sync.
JMarc
Georg Baum <[EMAIL PROTECTED]> writes:
| Juergen Spitzmueller wrote:
|
| > Works for me as well.
|
| Fine. Is this OK for 1.4.0?
ok
--
Lgb
Jean-Marc Lasgouttes wrote:
>> "Georg" == Georg Baum
>> <[EMAIL PROTECTED]>
>> writes:
>
> Georg> Juergen Spitzmueller wrote:
>>> Works for me as well.
>
> Georg> Fine. Is this OK for 1.4.0?
>
> I do not like the hardcoding of lyx13x.
Me neither, but I fear that the other possibili
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Juergen Spitzmueller wrote:
>> Works for me as well.
Georg> Fine. Is this OK for 1.4.0?
I do not like the hardcoding of lyx13x. If you are going to do that,
why not directly add lyx13x to the list of backends? Wouldn't that be
less c
Juergen Spitzmueller wrote:
> Works for me as well.
Fine. Is this OK for 1.4.0?
Georg
Georg Baum wrote:
> Here it is. It works for me, could you please test it, too?
Works for me as well.
Jürgen
Am Donnerstag, 2. Februar 2006 11:35 schrieb Juergen Spitzmueller:
> Georg Baum wrote:
> > I think the safest solution right now is simply to make a special case
for
> > the "lyx13" format. I'll send an updated patch this evening.
>
> I agree.
Here it is. It works for me, could you please test i
Georg Baum wrote:
> The problem is that we don't know "from" at that point :-(
I see.
> I have implemented an experimental getShortestPath() method that could be
> used instead of getPath() and the loop. The problem is that this might
> influence other conversions, so it is too risky to do it now
Juergen Spitzmueller wrote:
> Georg Baum wrote:
>> Does it work if you put the lyx backend in the first position
>
> Yes, it works then.
Fine.
> Couldn't we do something like: "use the first backend available (as it is
> now), BUT if the "from" format is equal to any other backend, then use
> t
Georg Baum wrote:
> Does it work if you put the lyx backend in the first position
Yes, it works then.
Couldn't we do something like: "use the first backend available (as it is
now), BUT if the "from" format is equal to any other backend, then use that"?
Jürgen
Georg Baum wrote:
> If x is the backend format, then this works, i. e. it always takes the
> direct path. In your case, it took the first of
>
> x -> y -> z
> y -> z
>
> where x = tex, y = lyx, z = lyx13.
>
I see. Thanks for the explanation.
Jürgen
Juergen Spitzmueller wrote:
> Georg Baum wrote:
>
>>> I see. Isn't this a general problem, then? I guess we don't want the
>>> first, but the most appropriate route.
>>
>> Yes, but currently it is a more theoretical one, since we only have two
>> backends (tex/docbook and text), and the first on
Georg Baum wrote:
>> I see. Isn't this a general problem, then? I guess we don't want the
>> first, but the most appropriate route.
>
> Yes, but currently it is a more theoretical one, since we only have two
> backends (tex/docbook and text), and the first one is more powerful.
I thought that ap
Juergen Spitzmueller wrote:
> I see. Isn't this a general problem, then? I guess we don't want the
> first, but the most appropriate route.
Yes, but currently it is a more theoretical one, since we only have two
backends (tex/docbook and text), and the first one is more powerful.
Georg
Georg Baum wrote:
> I think I know know what happens. Exporter::Export finds the first backend
> that is capable to produce the desired format, and this is the LaTeX
> backend. I don't understand anymore why it works for me.
I see. Isn't this a general problem, then? I guess we don't want the fir
Am Montag, 30. Januar 2006 08:14 schrieb Juergen Spitzmueller:
> Georg Baum wrote:
> > I don't know. It should use the direct lyx -> lyx13 route (and it does
so
> > here). Are you sure that you have the latest version of the patch
> > applied?
>
> Yes. Definitely.
I think I know know what happen
Georg Baum wrote:
> I don't know. It should use the direct lyx -> lyx13 route (and it does so
> here). Are you sure that you have the latest version of the patch
> applied?
Yes. Definitely.
Jürgen
Am Sonntag, 29. Januar 2006 13:40 schrieb Juergen Spitzmueller:
> Now I know what happens: LyX first exports the file to LaTeX, then
converts it
> to LyX (v. 1.4) and finally runs lyx2lyx over that file, which certainly
> already contains the garbage (color is imported as ERT, and the
quotation
Juergen Spitzmueller wrote:
> I have no idea where to look at. Now, when I run lyx2lyx manually, I get a
> correct file, but not if I use Georg's gui.
> Anyway, I have to leave now. I'll have a look later.
Now I know what happens: LyX first exports the file to LaTeX, then converts it
to LyX (v. 1
Georg Baum wrote:
> > Can we (i.e., Juergen) inspect that temp file?
>
> Sure. I suspect that it already contains the nonsense.
I have no idea where to look at. Now, when I run lyx2lyx manually, I get a
correct file, but not if I use Georg's gui.
Anyway, I have to leave now. I'll have a look late
Am Samstag, 28. Januar 2006 12:31 schrieb Martin Vermeer:
> Yes, but that file should be lyx-1.4 format, right? Containing language
> to the effect of "\begin_inset Quote ard" etc. Not yet any "<<".
Correct.
> Can we (i.e., Juergen) inspect that temp file?
Sure. I suspect that it already contain
On Sat, Jan 28, 2006 at 12:30:32PM +0100, Georg Baum wrote:
> Am Samstag, 28. Januar 2006 12:13 schrieb Martin Vermeer:
> > Where in the lyx2lyx code is the Quote inset handled? I tried to look,
> > but didn't find anything. What am I missing? Where is the knowledge
> > located to convert a quote i
Georg Baum wrote:
> Then I would expect LyX to remember that I wanted 1.3 format and keep that
> format even for subsequent saves. That would require far more changes,
> and a lyx2lyx run on every save.
Perhaps we could think on this again later.
> > However, I encountered some reversion problems
Am Samstag, 28. Januar 2006 12:13 schrieb Martin Vermeer:
> Where in the lyx2lyx code is the Quote inset handled? I tried to look,
> but didn't find anything. What am I missing? Where is the knowledge
> located to convert a quote inset to << ?
This is some mixup coming from LaTeX export of LyX. I
Martin Vermeer wrote:
> Do I understand correctly, that the first attachment is what you get
> when exporting the second attachment to 1.3 format?
Yes, text-13.lyx is the result of the "LyX 1.3"-export of test.lyx.
Jürgen
Am Freitag, 27. Januar 2006 18:49 schrieb Juergen Spitzmueller:
> It works for me and I think it is o.k. (although I think a better gui
would be
> to have "LyX 1.3" chosable in the file dialog "File type" combo, where
you
> also could enter an alternative file name).
Then I would expect LyX t
On Fri, Jan 27, 2006 at 06:49:46PM +0100, Juergen Spitzmueller wrote:
> Georg Baum wrote:
...
> However, I encountered some reversion problems. Try to revert the attached
> sample document to 1.3 and notice what happens to the color and the quotation
> marks.
Do I understand correctly, that t
Georg Baum wrote:
> patch -p1 < 2174.diff
Ah, thanks. I used -p0 without thinking.
It works for me and I think it is o.k. (although I think a better gui would be
to have "LyX 1.3" chosable in the file dialog "File type" combo, where you
also could enter an alternative file name).
However, I en
Juergen Spitzmueller wrote:
> Do you have a patch against the cvs archive (or can you tell me how to
> apply this one)?
It was created with makepatch.sh (poor mans cvs substitute if you have
no/only a slow online connection)
You can apply it from the toplevel directory with
patch -p1 < 2174.diff
Georg Baum wrote:
> I'd like to get some testing of this patch (it works for me).
Do you have a patch against the cvs archive (or can you tell me how to apply
this one)?
BTW I have noticed (unrelated to this patch) that Branches are not reverted.
LyX 1.3 complains about two unknown tokens (\bra
This patch fixes bug 2174 (export to 1.3x format). The possibility to export
to 1.3x will motivate more users to switch to 1.4, because they can still
collaborate with others who don't have LyX 1.3.7.
I'd like to get some testing of this patch (it works for me).
Georgdiff -p -r -U 3 -X excl.tmp l
33 matches
Mail list logo
