On Sat, Jan 07, 2023 at 11:39:20AM -0500, Richard Kimberly Heck wrote:
> On 1/6/23 14:02, Jürgen Spitzmüller wrote:
> > Am Freitag, dem 06.01.2023 um 13:51 -0500 schrieb Richard Kimberly
> > Heck:
> > > And not that it matters, but git blame makes it look like I'm the one
> > > who forgot this. I'm
On 1/6/23 14:02, Jürgen Spitzmüller wrote:
Am Freitag, dem 06.01.2023 um 13:51 -0500 schrieb Richard Kimberly
Heck:
And not that it matters, but git blame makes it look like I'm the one
who forgot this. I'm not.
I know. A closer look at the logs revealed tat you just fixed up the
method.
I th
Am Freitag, dem 06.01.2023 um 13:51 -0500 schrieb Richard Kimberly
Heck:
> And not that it matters, but git blame makes it look like I'm the one
> who forgot this. I'm not.
I know. A closer look at the logs revealed tat you just fixed up the
method.
--
Jürgen
--
lyx-devel mailing list
lyx-devel
On 1/6/23 13:39, Richard Kimberly Heck wrote:
On 1/6/23 08:41, Jürgen Spitzmüller wrote:
Am Freitag, dem 06.01.2023 um 13:03 +0100 schrieb Jürgen Spitzmüller:
A revert routine is missing that removes the newpage inset before
such bibtex insets (in the formats before, a clear(double)page is
part
On 1/6/23 08:41, Jürgen Spitzmüller wrote:
Am Freitag, dem 06.01.2023 um 13:03 +0100 schrieb Jürgen Spitzmüller:
A revert routine is missing that removes the newpage inset before
such bibtex insets (in the formats before, a clear(double)page is
part of the code the bibtex insert generates.
Adde
Am Freitag, dem 06.01.2023 um 13:03 +0100 schrieb Jürgen Spitzmüller:
> A revert routine is missing that removes the newpage inset before
> such bibtex insets (in the formats before, a clear(double)page is
> part of the code the bibtex insert generates.
Added at d89a48483e3906.
--
Jürgen
signa
Am Donnerstag, dem 05.01.2023 um 23:45 -0500 schrieb Scott Kostyshak:
> If convert_bibtex_clearpage(document) in lyx_2_0.py is commented out,
> then the issue goes away (just to give an idea of where the bug is).
A revert routine is missing that removes the newpage inset before such
bibtex insets
On Sunday, January 03, 2016 04:32:49 AM Scott Kostyshak wrote:
> Hopefully we can make progress on unit tests in the 2.3 cycle, for both
> lyx2lyx and our C++ code and anything else. I would be happy to
> eventually learn the testing framework and try to contribute.
+1
I wholeheartedly agree with
On Sun, Jan 03, 2016 at 10:24:47AM +0100, Georg Baum wrote:
> Scott Kostyshak wrote:
>
> > On Fri, Jan 01, 2016 at 01:22:53PM +0100, Kornel Benko wrote:
> >>
> >> What we have now is _one_ step in this direction.
> >
> > Dedicated tests requires understanding of the underlying mechanism. I do
>
Scott Kostyshak wrote:
> On Fri, Jan 01, 2016 at 01:22:53PM +0100, Kornel Benko wrote:
>>
>> What we have now is _one_ step in this direction.
>
> Dedicated tests requires understanding of the underlying mechanism. I do
> not know much at all about lyx2lyx (I'm not sure Kornel does either?).
I
On Fri, Jan 01, 2016 at 01:22:53PM +0100, Kornel Benko wrote:
> Am Donnerstag, 31. Dezember 2015 um 19:33:59, schrieb Georg Baum
>
> > This is not a bug. The conversion 501->500 must be lossy, since the format
Thanks for the explanation. Good to know there is no bug.
> This is not causing pro
Am Donnerstag, 31. Dezember 2015 um 19:33:59, schrieb Georg Baum
> Scott Kostyshak wrote:
>
> > The test fails after doing lyx2lyx:
> >
> > cd lib/examples/fr
> > lyx -e lyx21x Foils.lyx
> > mv Foils.21.lyx Foils.lyx
> >
> > After doing a (manual) bisect, I narrowed the failure down to the 500
Scott Kostyshak wrote:
> The test fails after doing lyx2lyx:
>
> cd lib/examples/fr
> lyx -e lyx21x Foils.lyx
> mv Foils.21.lyx Foils.lyx
>
> After doing a (manual) bisect, I narrowed the failure down to the 500 vs.
> 501 format change:
>
> cd lib/examples/fr && git checkout Foils.lyx &&
> /hom
On Thu, Dec 31, 2015 at 01:38:56PM +0100, Georg Baum wrote:
> Am 28.12.2015 um 08:27 schrieb Scott Kostyshak:
> >On Mon, Dec 28, 2015 at 08:25:11AM +0100, Kornel Benko wrote:
> >>Am Montag, 28. Dezember 2015 um 02:02:45, schrieb Scott Kostyshak
> >>
> >>>On Sun, Dec 27, 2015 at 05:39:06PM +0100, K
Am 28.12.2015 um 08:27 schrieb Scott Kostyshak:
On Mon, Dec 28, 2015 at 08:25:11AM +0100, Kornel Benko wrote:
Am Montag, 28. Dezember 2015 um 02:02:45, schrieb Scott Kostyshak
On Sun, Dec 27, 2015 at 05:39:06PM +0100, Kornel Benko wrote:
Am Sonntag, 27. Dezember 2015 um 11:23:36, schrieb Sco
On 05/27/2014 01:33 AM, Patrick O'Keeffe wrote:
On 5/26/2014 2:27 PM, José Matos wrote:
The problem according to my analysis is the line
lastpar = ''.join(contents[-1])
where contents is an empty list.
So probably something like
if not contents: continue
would work.
A more precise fix may
On 5/26/2014 2:27 PM, José Matos wrote:
The problem according to my analysis is the line
lastpar = ''.join(contents[-1])
where contents is an empty list.
So probably something like
if not contents: continue
would work.
A more precise fix may be preferred:
lastpar = ''.join(contents[-1] if
On 04/24/2014 02:47 PM, Georg Baum wrote:
Richard Heck wrote:
This is close to right, but the problem is in the conversion of layouts.
It's fine not to quote the names. Look at e.g. logicalmkup.module. Mone
of the InsetLayout names are quoted, yet they work fine. The problem is
that there is so
Richard Heck wrote:
> This is close to right, but the problem is in the conversion of layouts.
> It's fine not to quote the names. Look at e.g. logicalmkup.module. Mone
> of the InsetLayout names are quoted, yet they work fine. The problem is
> that there is some buggy conversion code, and it seem
Of coures I meant: layout2layout bug.
On 04/22/2014 10:42 PM, Richard Heck wrote:
On 04/22/2014 08:20 PM, aparsloe wrote:
The Customisation manual (downloaded with LyX 2.1.0 an hour ago) says
in Section 5.3.9:
The layout for a Flex inset is being defined. In this case, ||
must be of the for
On Fri, Aug 17, 2007 at 05:20:08PM +0300, Dov Feldstern wrote:
> Dov Feldstern wrote:
> > The bigger problem, though, has nothing to do with your code: it looks like
> > lyx2lyx (at least when run from the command line) is just ignoring anything
> > with format above 276. If you change your file
Bo Peng schrieb:
Open any 1.5.x document, say faq, export to 1.4, open faq.lyx14, view
pdf, I see
LaTex Error: File 'armtex.sty' not found.
Fixed:
http://www.lyx.org/trac/changeset/18250
regards Uwe
On Wednesday 09 May 2007 17:08:52 Uwe Stöhr wrote:
> > Open any 1.5.x document, say faq, export to 1.4, open faq.lyx14, view
> > pdf, I see
> >
> > LaTex Error: File 'armtex.sty' not found.
>
> Thanks for the report. The armtex-package shouldn't be set in every case to
> the preamble, only when Arm
Open any 1.5.x document, say faq, export to 1.4, open faq.lyx14, view
pdf, I see
LaTex Error: File 'armtex.sty' not found.
Thanks for the report. The armtex-package shouldn't be set in every case to the preamble, only when
Armenian was used as document language. I'll have a look.
regards Uw
Abdelrazak Younes wrote:
Helge Hafting wrote:
Angus Leeming wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Can you try to change the utf-8 to ucs-4 conversion to use either
"UCS-4BE" or "UCS-4LE", instead of "UCS-4"? Also the conversion the
other way ucs-4 -> ucs-2, try with UCS-2BE an
Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
> UTF-8 is chars so BOM has no place there...
Right. I see that now, but it was the act of (trying to) explain that revealed
to me that I actually didn't understand things after all. I now understand
that Windows file formats tend to output directl
Angus Leeming <[EMAIL PROTECTED]> writes:
| Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| >> Can you try to change the utf-8 to ucs-4 conversion to use either
| >> "UCS-4BE" or "UCS-4LE", instead of "UCS-4"? Also the conversion the
| >> other way ucs-4 -> ucs-2, try with UCS-2BE and UCS-2LE.
|
Georg Baum wrote:
Abdelrazak Younes wrote:
Well, the reference labels (and cross-reference) are part of the lyx
format aren't they?
They are. And that is the proof that you now have the ucs4 conversion
machinery working: The labels are currently not stored in docstring, but in
std::string as
Abdelrazak Younes wrote:
> Well, the reference labels (and cross-reference) are part of the lyx
> format aren't they?
They are. And that is the proof that you now have the ucs4 conversion
machinery working: The labels are currently not stored in docstring, but in
std::string as read in from the f
Helge Hafting wrote:
> I thought UTF-8 didn't care about endianness, being a single-byte
> encoding?
That would be great: stuffing the whole unicode range in a single-byte
encoding, but for obvious reasons that does not work.
You are right that the endianness is not a problem in utf8, since it d
Helge Hafting wrote:
Angus Leeming wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Can you try to change the utf-8 to ucs-4 conversion to use either
"UCS-4BE" or "UCS-4LE", instead of "UCS-4"? Also the conversion the
other way ucs-4 -> ucs-2, try with UCS-2BE and UCS-2LE.
And
Helge Hafting <[EMAIL PROTECTED]> writes:
> I thought UTF-8 didn't care about endianness, being a single-byte
> encoding? A conversion to UCS-4 can go wrong if he convert
> to the wrong UCS-4 format, but utf-8 is supposed to be
> the same no matter what endianness the machine uses?
Sigh. Yes, you
Angus Leeming wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Can you try to change the utf-8 to ucs-4 conversion to use either
"UCS-4BE" or "UCS-4LE", instead of "UCS-4"? Also the conversion the
other way ucs-4 -> ucs-2, try with UCS-2BE and UCS-2LE.
And with the attached patch where I h
Angus Leeming wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Can you try to change the utf-8 to ucs-4 conversion to use either
"UCS-4BE" or "UCS-4LE", instead of "UCS-4"? Also the conversion the
other way ucs-4 -> ucs-2, try with UCS-2BE and UCS-2LE.
And with the attached pa
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> Can you try to change the utf-8 to ucs-4 conversion to use either
>> "UCS-4BE" or "UCS-4LE", instead of "UCS-4"? Also the conversion the
>> other way ucs-4 -> ucs-2, try with UCS-2BE and UCS-2LE.
> And with the attached patch where I have put LE eve
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Abdelrazak Younes wrote:
| > Georg Baum wrote:
| >> Abdelrazak Younes wrote:
| >>
| >>> No, I've reverted to 245. Maybe my problem is that lyx doesn't call the
| >>> right lyx2lyx version... I am launching lyx from the sc
Abdelrazak Younes wrote:
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Abdelrazak Younes wrote:
| > Georg Baum wrote:
| >> Abdelrazak Younes wrote:
| >>
| >>> No, I've reverted to 245. Maybe my problem is that lyx doesn't
call the
| >>> right lyx2lyx version... I a
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Abdelrazak Younes wrote:
| > Georg Baum wrote:
| >> Abdelrazak Younes wrote:
| >>
| >>> No, I've reverted to 245. Maybe my problem is that lyx doesn't call the
| >>> right lyx2lyx version... I am launching lyx from the sc
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Abdelrazak Younes wrote:
| > Georg Baum wrote:
| >> Abdelrazak Younes wrote:
| >>
| >>> No, I've reverted to 245. Maybe my problem is that lyx doesn't call the
| >>> right lyx2lyx version... I am launching lyx from the sc
Georg Baum wrote:
Abdelrazak Younes wrote:
I have converted by hand Intro.lyx:
D:\program\lyx-msvc\Resources\lyx2lyx>python lyx2lyx -t 249 -o
.\Intro.lyx ..\doc\Intro.lyx
The resulting file seems to have the correct version number:
#LyX 1.5.0svn created this file. For more info see http://www
Abdelrazak Younes wrote:
> I have converted by hand Intro.lyx:
>
> D:\program\lyx-msvc\Resources\lyx2lyx>python lyx2lyx -t 249 -o
> .\Intro.lyx ..\doc\Intro.lyx
>
> The resulting file seems to have the correct version number:
> #LyX 1.5.0svn created this file. For more info see http://www.lyx.or
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Abdelrazak Younes wrote:
| > Georg Baum wrote:
| >> Abdelrazak Younes wrote:
| >>
| >>> No, I've reverted to 245. Maybe my problem is that lyx doesn't call the
| >>> right lyx2lyx version... I am launching lyx from the scons build tree.
| >>
| >> Run
On Monday 25 July 2005 19:45, Georg Baum wrote:
> José, is it intentional that normalize_paragraph_params in lyx_1_4.py does
> not handle \leftindent?
Second try now (after studying the bug):
- Yes, it was a mistake.
- No, by luck it does not have any consequence. I will add it to the list
On Tuesday 02 August 2005 10:57, Georg Baum wrote:
> > The fix is quite easy, just to add it to the list of allowed parameters
> > in
> > normalize_paragraph_params, the problem are all those changes that
> > occurred between 239 and now.
>
> As far as I can see the subsequent conversion functi
Jose' Matos wrote:
> The fix is quite easy, just to add it to the list of allowed parameters
> in
> normalize_paragraph_params, the problem are all those changes that
> occurred between 239 and now.
As far as I can see the subsequent conversion functions are not affected by
normalize_paragrap
On Tuesday 26 July 2005 09:50, Georg Baum wrote:
> Jose' Matos wrote:
> > Will you do it or shall I do it?
>
> Please do it. My input pipe is full ;-)
The fix is quite easy, just to add it to the list of allowed parameters in
normalize_paragraph_params, the problem are all those changes that
Jose' Matos wrote:
> Will you do it or shall I do it?
Please do it. My input pipe is full ;-)
Georg
On Monday 25 July 2005 19:45, Georg Baum wrote:
> José, is it intentional that normalize_paragraph_params in lyx_1_4.py
> does not handle \leftindent?
Nope.
For some reason it escaped our scrutiny. :-(
Will you do it or shall I do it?
> Georg
--
José Abílio
> "Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes:
Jose'> Done, please test.
It seems to work, thanks.
JMarc
On Wednesday 04 August 2004 15:48, Jean-Marc Lasgouttes wrote:
> Jose'> Also since python 2.3 there is a universal end line, where
> Jose'> python deals uniformly with this no matter where you are.
>
> They copied LyX, didn't they?
Don't know. ;-)
> >> LyX ignores all the \r in \r\n endings.
> "Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes:
Jose'> Also since python 2.3 there is a universal end line, where
Jose'> python deals uniformly with this no matter where you are.
They copied LyX, didn't they?
>> Jose'> This will not be reflect on write, as it will use the Jose'>
>> pl
On Wednesday 04 August 2004 15:12, Jean-Marc Lasgouttes wrote:
>
> Isn't there some magic python option to do that transparently? I am
> disappointed.
That place is already taken.
I'm sorry the language of magic options is perl, not python. ;-)
Also since python 2.3 there is a universal end
> "Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes:
Jose'> I will basically look if the first line ends with '\r\n' and
Jose'> from them catch the same ending. If for some reason, it doesn't
Jose'> follow this it will mumble some warning but continue.
Isn't there some magic python option t
On Wednesday 04 August 2004 14:03, Jean-Marc Lasgouttes wrote:
> The 1.4.0cvs UserGuide, which has been produced with 1.3.x and can
> perfectly be read there, produces lots of warnings and error when
> loaded under 1.4.0cvs. It turns out that the problem is that the file
> has DOS-type line endings
Georg Baum wrote:
> The status flag is not converted between file formats 227 and 228,
> because it is not the first parameter. The attached fixes that.
>
> Georg
Thanks, Georg. It's in.
--
Angus
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> On Tue, Mar 11, 2003 at 03:36:20PM +0100, Jean-Marc Lasgouttes
Dekel> wrote:
>> The revtex4 template contains snippets like:
>>
>> \begin_inset Info Use Thanks layout instead of inserting footnotes.
>> Footnotes in the title will do w
On Tue, Mar 11, 2003 at 03:36:20PM +0100, Jean-Marc Lasgouttes wrote:
> The revtex4 template contains snippets like:
>
> \begin_inset Info Use Thanks layout instead of inserting footnotes.
> Footnotes in the title will do weird things in REVTeX 4!
> \end_inset
>
> Obviously lyx2lyx faild to conv
> "José" == José Matos <[EMAIL PROTECTED]> writes:
José> On Tuesday 11 March 2003 14:36, Jean-Marc Lasgouttes wrote:
>>
>>
>> The revtex4 template contains snippets like:
>>
>> \begin_inset Info Use Thanks layout instead of inserting footnotes.
>> Footnotes in the title will do weird things
On Tuesday 11 March 2003 14:36, Jean-Marc Lasgouttes wrote:
>
>
> The revtex4 template contains snippets like:
>
> \begin_inset Info Use Thanks layout instead of inserting footnotes.
> Footnotes in the title will do weird things in REVTeX 4!
> \end_inset
>
> Obviously lyx2lyx faild to convert these
On Friday 06 December 2002 03:02, John Levon wrote:
> attached flummoxes lyx2lyx
>
> File "/home/moz/src/lyx/lyx-devel/lib/lyx2lyx/lyxconvert_216.py", line
> 270, in convert
> update_tabular(body)
> File "/home/moz/src/lyx/lyx-devel/lib/lyx2lyx/lyxconvert_216.py", line
> 46, in update_tabular
60 matches
Mail list logo
