Uwe Stöhr [EMAIL PROTECTED] writes:
Not in my opinion:
- you have only one word in the line in LyX and end it with line-break
How will you show the difference? Ragging is in this case the same as
justified within LyX, but not in the output.
- you have 5 words in the line in LyX and end it
Uwe Stöhr [EMAIL PROTECTED] writes:
Some time ago I started to overhaul tex2lyx to be able to create a
version that will support the fileformat of LyX 1.6.0.
I added support for lots of commands and updated existing support to
the current actual trunk fileformat:
Pavel Sanda wrote:
its in.
I would welcome to a backport to 1.5.3.
Jürgen
Uwe, could you have a look please?
Object::connect: No such signal QPushButton::textChanged(QString)
Object::connect: (sender name: 'exampleDirPB')
Object::connect: (receiver name: 'PrefPathsUi')
Thanks in advance,
Abdel.
Jean-Marc Lasgouttes schrieb:
Having a different color and a suitable label works always.
I am arguing that it is just a stopgap measure. The right thing would
be IMO: try to reproduce justification and use a different graphics
(using color coding for UI is bad) for the line break.
As I
Jean-Marc Lasgouttes schrieb:
http://www.lyx.org/trac/changeset/21813
As you probably know, we cannot go beyond format 249 if we do not
change to unicode support. I do not see this in your patch. What is
the format you output here? It is not really 245, is it?
As I stated in the commit note
could you please try to transfer this code to InsetNewLine::latex()?
I tried this but failed. My problems were where to get the informations about \protect etc. in
newline.cpp.
In my newline patch I have only removed one line from Paragraph.cpp, so the code couldn't be worse
than before.
Uwe Stöhr wrote:
could you please try to transfer this code to InsetNewLine::latex()?
I tried this but failed. My problems were where to get the informations
about \protect etc. in newline.cpp.
In my newline patch I have only removed one line from Paragraph.cpp, so
the code couldn't be
On Tue, 27 Nov 2007 08:57:55 +0100
Abdelrazak Younes [EMAIL PROTECTED] wrote:
Pavel Sanda wrote:
Hello,
among others I use LyX for translation work and as I saw on users list I'm
not
the only one. There are few features which would help me a lot, namely:
- displaying the
In general I think it is time that we switch to bugzilla for these report.
you mean all the reports there ?
pavel
Pavel Sanda wrote:
In general I think it is time that we switch to bugzilla for these report.
you mean all the reports there ?
yes.
Abdel.
Well, I consider you the LateX expert (which I am obviously not) and that's
why I asked you ;-)
Seems that we are two half-experts ;-) What about this: You merge the code from Paragraph.cpp to
Newline.cpp, send me the patch, and I will check that the LaTeX-output is correct.
regards Uwe
Uwe Stöhr wrote:
As I stated in the commit note that it is still 245 (LyX 1.4.0).
I don't understand. Here
http://www.lyx.org/trac/changeset/21813
I see that you use \font_sc, \use_hyperref and other parameters that have been
introduced after 245.
Jürgen
Perhaps. Actually one could start from branch insets. Instead of have
interesting idea, i'll look into it.
windows showing the different language versions. They could then be
side by side. The windows could be like the cells of tables.
yes something like this i have in my mind.
pavel
Jean-Marc Lasgouttes schrieb:
It is not. I do not think that LyX 1.4.x will be able to read a file
that pretends to be 245 but uses nomenclature support or the new
format for bibtex inset.
This tex2lyx version id for LyX 1.6 and not for LyX 1.4.
The process is not that you dump a big
Uwe Stöhr [EMAIL PROTECTED] writes:
Jean-Marc Lasgouttes schrieb:
http://www.lyx.org/trac/changeset/21813
As you probably know, we cannot go beyond format 249 if we do not
change to unicode support. I do not see this in your patch. What is
the format you output here? It is not really 245,
Uwe Stöhr [EMAIL PROTECTED] writes:
This tex2lyx version id for LyX 1.6 and not for LyX 1.4.
Sure, but if we declare that a file is in some version, it should
really be of this version. We are going to have problems otherwise.
The process is not that you dump a big tex2lyx patch and then
Uwe Stöhr wrote:
Well, I consider you the LateX expert (which I am obviously not) and
that's why I asked you ;-)
Seems that we are two half-experts ;-) What about this: You merge the
code from Paragraph.cpp to Newline.cpp, send me the patch, and I will
check that the LaTeX-output is
On Tue, Nov 27, 2007 at 01:38:51AM -, [EMAIL PROTECTED] wrote:
// some ugly stuff
ostringstream h_preamble;
-string h_textclass = article;
-string h_options = string();
-string h_language= english;
-string h_inputencoding =
On Tue, Nov 27, 2007 at 10:01:36AM -, [EMAIL PROTECTED] wrote:
URL: http://www.lyx.org/trac/changeset/21817 Log: Getting rid of
normalizePath() which is unneeded for FileName purpose (the path is
always normalized internally). This commit frees up src/ from
boost::filesystem.
Nice ;-)
Jean-Marc Lasgouttes schrieb:
Sure, but if we declare that a file is in some version, it should
really be of this version. We are going to have problems otherwise.
lyx2lyx does the rest.
Also, since we have new font scheme and you just introduced framed.sty
support (right?) the format can
You added this item to the regression list:
since 26-11-2007 LyX cannot save backup files.
What's that? Please give a recipe. FYI I've modified extensively everything
about file handling
(the FileName class).
- Create a new file
- Save it - newfile1.lyx
- modify it
- Save it -
I don't understand. Here
http://www.lyx.org/trac/changeset/21813
I see that you use \font_sc, \use_hyperref and other parameters that have been
introduced after 245.
Yes, things that are already in the latest fileformat won't be touched in lyx2lyx as far as I
tested. So except of probably
Uwe Stöhr wrote:
Yes, things that are already in the latest fileformat won't be touched in
lyx2lyx as far as I tested. So except of probably only a few cases where
lyx2lyx changes the file to a wrong format, we can support LyX's 1.6's
features and the old ones are converted by lyx2lyx.
So
bash ../development/tools/count_lines_of_included_code.sh debug.h
debug.h : 30091
;-(
Andre'
On Tue, Nov 27, 2007 at 08:54:07PM +0100, Andre Poenitz wrote:
bash ../development/tools/count_lines_of_included_code.sh debug.h
debug.h : 30091
;-(
Using something handcrafted along the lines of
struct LyXErr {
bool
Juergen Spitzmueller [EMAIL PROTECTED] writes:
Uwe Stöhr wrote:
Yes, things that are already in the latest fileformat won't be touched in
lyx2lyx as far as I tested. So except of probably only a few cases where
lyx2lyx changes the file to a wrong format, we can support LyX's 1.6's
make[5]: Entering directory `/cvs/lyx-devel/trunk/src/frontends/qt4'
make[5]: *** No rule to make target `../ButtonPolicy.cpp', needed by
`ButtonPolicy.lo'. Stop.
Seems it's looking for that file in the wrong directory: ../.
--
Uwe, could you have a look please?
This was a copy paste error that I've overseen. It's now fixed.
thanks and regards
Uwe
On Tue, Nov 27, 2007 at 10:25:36PM +0100, Andre Poenitz wrote:
On Tue, Nov 27, 2007 at 08:54:07PM +0100, Andre Poenitz wrote:
bash ../development/tools/count_lines_of_included_code.sh debug.h
debug.h : 30091
;-(
Using something handcrafted along the
On Wed, Nov 28, 2007 at 06:34:20AM +0200, Martin Vermeer wrote:
On Tue, Nov 27, 2007 at 10:25:36PM +0100, Andre Poenitz wrote:
On Tue, Nov 27, 2007 at 08:54:07PM +0100, Andre Poenitz wrote:
bash ../development/tools/count_lines_of_included_code.sh debug.h
debug.h
*** No rule to make target `../ButtonPolicy.cpp', needed by
`ButtonPolicy.lo'. Stop.
try make distclean. this is an automake dependency tracking bug,
I think.
JMarc
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> Not in my opinion:
>
> - you have only one word in the line in LyX and end it with line-break
> How will you show the difference? Ragging is in this case the same as
> justified within LyX, but not in the output.
>
> - you have 5 words in the line in LyX
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> Some time ago I started to overhaul tex2lyx to be able to create a
> version that will support the fileformat of LyX 1.6.0.
>
> I added support for lots of commands and updated existing support to
> the current actual trunk fileformat:
>
Pavel Sanda wrote:
> its in.
I would welcome to a backport to 1.5.3.
Jürgen
Uwe, could you have a look please?
Object::connect: No such signal QPushButton::textChanged(QString)
Object::connect: (sender name: 'exampleDirPB')
Object::connect: (receiver name: 'PrefPathsUi')
Thanks in advance,
Abdel.
Jean-Marc Lasgouttes schrieb:
Having a different color and a suitable label works always.
I am arguing that it is just a stopgap measure. The right thing would
be IMO: try to reproduce justification and use a different graphics
(using color coding for UI is bad) for the line break.
As I
Jean-Marc Lasgouttes schrieb:
http://www.lyx.org/trac/changeset/21813
As you probably know, we cannot go beyond format 249 if we do not
change to unicode support. I do not see this in your patch. What is
the format you output here? It is not really 245, is it?
As I stated in the commit note
> could you please try to transfer this code to InsetNewLine::latex()?
I tried this but failed. My problems were where to get the informations about \protect etc. in
newline.cpp.
In my newline patch I have only removed one line from Paragraph.cpp, so the code couldn't be worse
than before.
Uwe Stöhr wrote:
> could you please try to transfer this code to InsetNewLine::latex()?
I tried this but failed. My problems were where to get the informations
about \protect etc. in newline.cpp.
In my newline patch I have only removed one line from Paragraph.cpp, so
the code couldn't be
On Tue, 27 Nov 2007 08:57:55 +0100
Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
> Pavel Sanda wrote:
> > Hello,
> >
> > among others I use LyX for translation work and as I saw on users list I'm
> > not
> > the only one. There are few features which would help me a lot, namely:
> >
> > -
> In general I think it is time that we switch to bugzilla for these report.
you mean all the reports there ?
pavel
Pavel Sanda wrote:
In general I think it is time that we switch to bugzilla for these report.
you mean all the reports there ?
yes.
Abdel.
> Well, I consider you the LateX expert (which I am obviously not) and that's
why I asked you ;-)
Seems that we are two half-experts ;-) What about this: You merge the code from Paragraph.cpp to
Newline.cpp, send me the patch, and I will check that the LaTeX-output is correct.
regards Uwe
Uwe Stöhr wrote:
> As I stated in the commit note that it is still 245 (LyX 1.4.0).
I don't understand. Here
http://www.lyx.org/trac/changeset/21813
I see that you use \font_sc, \use_hyperref and other parameters that have been
introduced after 245.
Jürgen
> Perhaps. Actually one could start from branch insets. Instead of have
interesting idea, i'll look into it.
> "windows" showing the different language versions. They could then be
> side by side. The windows could be like the cells of tables.
yes something like this i have in my mind.
pavel
Jean-Marc Lasgouttes schrieb:
It is not. I do not think that LyX 1.4.x will be able to read a file
that pretends to be 245 but uses nomenclature support or the new
format for bibtex inset.
This tex2lyx version id for LyX 1.6 and not for LyX 1.4.
The process is not that you dump a big
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> Jean-Marc Lasgouttes schrieb:
>
>>> http://www.lyx.org/trac/changeset/21813
>>
>> As you probably know, we cannot go beyond format 249 if we do not
>> change to unicode support. I do not see this in your patch. What is
>> the format you output here? It is
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> This tex2lyx version id for LyX 1.6 and not for LyX 1.4.
Sure, but if we declare that a file is in some version, it should
really be of this version. We are going to have problems otherwise.
>> The process is not that you dump a big tex2lyx patch and then
Uwe Stöhr wrote:
> Well, I consider you the LateX expert (which I am obviously not) and
that's why I asked you ;-)
Seems that we are two half-experts ;-) What about this: You merge the
code from Paragraph.cpp to Newline.cpp, send me the patch, and I will
check that the LaTeX-output is
On Tue, Nov 27, 2007 at 01:38:51AM -, [EMAIL PROTECTED] wrote:
> // some ugly stuff
> ostringstream h_preamble;
> -string h_textclass = "article";
> -string h_options = string();
> -string h_language= "english";
> -string h_inputencoding
On Tue, Nov 27, 2007 at 10:01:36AM -, [EMAIL PROTECTED] wrote:
> URL: http://www.lyx.org/trac/changeset/21817 Log: Getting rid of
> normalizePath() which is unneeded for FileName purpose (the path is
> always normalized internally). This commit frees up src/ from
> boost::filesystem.
Nice ;-)
Jean-Marc Lasgouttes schrieb:
Sure, but if we declare that a file is in some version, it should
really be of this version. We are going to have problems otherwise.
lyx2lyx does the rest.
Also, since we have new font scheme and you just introduced framed.sty
support (right?) the format can
> You added this item to the regression list:
>
> since 26-11-2007 LyX cannot save backup files.
>
> What's that? Please give a recipe. FYI I've modified extensively everything
about file handling
> (the FileName class).
- Create a new file
- Save it -> newfile1.lyx
- modify it
- Save it ->
> I don't understand. Here
> http://www.lyx.org/trac/changeset/21813
> I see that you use \font_sc, \use_hyperref and other parameters that have been
> introduced after 245.
Yes, things that are already in the latest fileformat won't be touched in lyx2lyx as far as I
tested. So except of
Uwe Stöhr wrote:
> Yes, things that are already in the latest fileformat won't be touched in
> lyx2lyx as far as I tested. So except of probably only a few cases where
> lyx2lyx changes the file to a wrong format, we can support LyX's 1.6's
> features and the old ones are converted by lyx2lyx.
> bash ../development/tools/count_lines_of_included_code.sh debug.h
debug.h : 30091
;-(
Andre'
On Tue, Nov 27, 2007 at 08:54:07PM +0100, Andre Poenitz wrote:
>
> > bash ../development/tools/count_lines_of_included_code.sh debug.h
> debug.h : 30091
>
> ;-(
Using something "handcrafted" along the lines of
struct LyXErr {
bool
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
>
> Uwe Stöhr wrote:
>
> > Yes, things that are already in the latest fileformat won't be touched in
> > lyx2lyx as far as I tested. So except of probably only a few cases where
> > lyx2lyx changes the file to a wrong format, we can support LyX's
make[5]: Entering directory `/cvs/lyx-devel/trunk/src/frontends/qt4'
make[5]: *** No rule to make target `../ButtonPolicy.cpp', needed by
`ButtonPolicy.lo'. Stop.
Seems it's looking for that file in the wrong directory: ../.
--
> Uwe, could you have a look please?
This was a copy paste error that I've overseen. It's now fixed.
thanks and regards
Uwe
On Tue, Nov 27, 2007 at 10:25:36PM +0100, Andre Poenitz wrote:
> On Tue, Nov 27, 2007 at 08:54:07PM +0100, Andre Poenitz wrote:
> >
> > > bash ../development/tools/count_lines_of_included_code.sh debug.h
> > debug.h : 30091
> >
> > ;-(
>
> Using something
On Wed, Nov 28, 2007 at 06:34:20AM +0200, Martin Vermeer wrote:
> On Tue, Nov 27, 2007 at 10:25:36PM +0100, Andre Poenitz wrote:
> > On Tue, Nov 27, 2007 at 08:54:07PM +0100, Andre Poenitz wrote:
> > >
> > > > bash ../development/tools/count_lines_of_included_code.sh debug.h
> > > debug.h
> *** No rule to make target `../ButtonPolicy.cpp', needed by
> `ButtonPolicy.lo'. Stop.
try "make distclean". this is an automake dependency tracking bug,
I think.
JMarc
64 matches
Mail list logo
