On Sat, 2023-12-02 at 11:25 -0500, T Rex wrote:
> sorry, I see that it was treated
Yes, we need to move this to the first place in our FAQ. :-D
Question: What should I do since I have the XYZ problem?
Answer: It is probably fixed in 2.4.0 version, please check there.
In this particular case the
sorry, I see that it was treated
El sáb, 2 dic 2023 a la(s) 09:46, T Rex (sixpa...@gmail.com) escribió:
> When I insert a pdf I get the error:
>
> Traceback (most recent call last):
> File ".../scripts/convertDefault.py", line 64, in
> if sys.argv[1] == 'pdf' and (version >= 0x060206 o
When I insert a pdf I get the error:
Traceback (most recent call last):
File ".../scripts/convertDefault.py", line 64, in
if sys.argv[1] == 'pdf' and (version >= 0x060206 or gm):
^^^
TypeError: '>=' not supported between instances of 'str
On Friday, 5 June 2020 20.27.28 WEST Richard Kimberly Heck wrote:
> Mostly I just wanted to make sure you knew about the re-packaging. It's such
> a trivial change that I wasn't sure I wanted to do it myself
>
> Riki
BTW as followup to this message, I have updated to 2.3.5.2.
The packages ar
On 6/5/20 5:43 AM, José Abílio Matos wrote:
>
> On Friday, 5 June 2020 05.06.19 WEST Richard Kimberly Heck wrote:
>
> > Please ignore the date in Help> About LyX That will be fixed.
>
>
>
> Honestly soon no one will care about the date. :-)
>
> As long as it is in the past.
>
>
>
> > Speaki
On Friday, 5 June 2020 05.06.19 WEST Richard Kimberly Heck wrote:
> Please ignore the date in Help> About LyX That will be fixed.
Honestly soon no one will care about the date. :-)
As long as it is in the past.
> Speaking of which, José, you might want to rebuild
No I do not, I am draggi
On 2011-03-21, Richard Heck wrote:
> On 03/21/2011 03:44 PM, Joost Verburg wrote:
>> So there are two bugs here:
>> * The class conversion errors shouldn't happen
> This is bug #7080.
>> * The log isn't being cleared and previous errors therefore prevent
>> PDF export etc.
> This last is new,
On 03/21/2011 03:44 PM, Joost Verburg wrote:
So there are two bugs here:
* The class conversion errors shouldn't happen
This is bug #7080.
* The log isn't being cleared and previous errors therefore prevent
PDF export etc.
This last is new, and I do not know where it comes from. I guess t
"Richard Heck" wrote in message
news:4d87a8cf.2070...@comcast.net...
Can you please repeat for me exactly what the error is and how I can
reproduce it? There was a bug along these lines a while ago. I'm not sure
why it has resurfaced.
1) Create any module with an inset, e.g.:
InsetLayout Cha
On 03/21/2011 03:21 PM, Joost Verburg wrote:
"Rob Oakes" wrote in message
news:000b01cbe7fa$547ab800$fd702800$@oak-tree.us...
Any idea as to what might be causing them? The export errors bug is
fairly
new. I thought that it might be specific to Mac OS X, but after
updating the
SVN version on m
"Liviu Andronic" wrote in message
news:AANLkTinV1z9NZR2pe_GXk08aB5vF2+gMPG=owm7fx...@mail.gmail.com...
Wild guess: is it possible that after a class change the modules
previously loaded get unloaded? Have you tried removing and
re-inserting all the used modules?
It also happens without changin
"Rob Oakes" wrote in message
news:000b01cbe7fa$547ab800$fd702800$@oak-tree.us...
Any idea as to what might be causing them? The export errors bug is fairly
new. I thought that it might be specific to Mac OS X, but after updating
the
SVN version on my Linux box this morning, I'm getting them th
On Mon, Mar 21, 2011 at 8:01 PM, Rob Oakes wrote:
> Any idea as to what might be causing them?
>
Wild guess: is it possible that after a class change the modules
previously loaded get unloaded? Have you tried removing and
re-inserting all the used modules?
Liviu
<< Also, after going to the document settings I'm no longer able to view
the
PDF output.
These "class switch errors" come back as "export errors", although they are
unrelated to LaTeX. Looks like the log window isn't cleared correctly. >>
Any idea as to what might be causing them? The export
"Rob Oakes" wrote in message
news:c27fccf8-7391-4fe2-87f0-ab02ae46c...@oak-tree.us...
Undefined Flex inset
Also, after going to the document settings I'm no longer able to view the
PDF output.
These "class switch errors" come back as "export errors", although they are
unrelated to LaTeX. Loo
"Rob Oakes" wrote in message
news:c27fccf8-7391-4fe2-87f0-ab02ae46c...@oak-tree.us...
Since yesterday, I've run into a new problem as well. I will occasionally
get another error which says:
Undefined Flex inset
The description says:
"Flex inset Code is undefined because of class conversion f
On Wed, Mar 16, 2011 at 08:06:10PM +0100, Kornel wrote:
> Am Mittwoch, 16. März 2011 schrieb Rob Oakes:
> > > What conversion is supposed to be happening in this case? Do you get any
> > > information on the terminal?
> >
> > Unfortunately, I haven't got a clue. I'm getting some very strange outpu
Hi Liviu,
Thanks for the thoughts.
> This can happen when you re-define an inset. For example:
> - define an inset "inset 1" and make a document containing this inset -
re-define the inset to "inset 2"
> - open the original document containing "inset 1" constructs. At this
point LyX will label th
Am Mittwoch, 16. März 2011 schrieb Rob Oakes:
> > What conversion is supposed to be happening in this case? Do you get any
> > information on the terminal?
>
> Unfortunately, I haven't got a clue. I'm getting some very strange output
> in the terminal. When I try and convert a different file, I'm
On Wed, Mar 16, 2011 at 6:03 PM, Rob Oakes wrote:
> Since yesterday, I've run into a new problem as well. I will occasionally get
> another error which says:
>
> Undefined Flex inset
>
This can happen when you re-define an inset. For example:
- define an inset "inset 1" and make a document contai
> What conversion is supposed to be happening in this case? Do you get any
> information on the terminal?
Unfortunately, I haven't got a clue. I'm getting some very strange output in
the terminal. When I try and convert a different file, I'm getting this:
LyX: Unknown InsetLayout tag [around l
Hi Richard,
Thanks for getting back to me.
> What's the actual LaTeX error? If LyX isn't reporting it in the log, then
> export and do it manually.
That's the problem, there isn't a LaTeX error. If the inset has been added to
the document, then it fails to export to XeTeX and fails with:
Erro
On 03/16/2011 03:25 AM, Rob Oakes wrote:
Dear LyX Developers,
This morning, I've run into a problem which I can't seem to solve and I thought
I would solicit your advice on. Some time ago, I created a module that
automated the creation of Drop Cap Initials through the use of a character
style
Dear LyX Developers,
This morning, I've run into a problem which I can't seem to solve and I thought
I would solicit your advice on. Some time ago, I created a module that
automated the creation of Drop Cap Initials through the use of a character
style. It's been working great up until the last
On Saturday 25 October 2008 09:33:02 Jürgen Spitzmüller wrote:
>
> Yes, I've double-checked, and you're right.
>
> > If that seems right, I'll commit the fix.
>
> I'd say so.
OK.
> Jürgen
--
José Abílio
rgheck wrote:
> I've checked this. If there's nothing in the subcaption in 1.5, you get:
> \subfigure[]{whatever}
> as if there were an empty caption. So I guess we should put in an empty
> caption inset, so that in 1.6 you get:
> \subfloat[]{whatever}
> rather than:
> \subfloat{whateve
Jürgen Spitzmüller wrote:
rgheck wrote:
I've got a working patch where lyx2lyx writes an empty caption inset.
Patch is attached. We could omit the caption inset altogether if we
wanted, but will LyX accept that?
What is the output? I think it should look as comparable as possible. I.e.
rgheck wrote:
> I've got a working patch where lyx2lyx writes an empty caption inset.
> Patch is attached. We could omit the caption inset altogether if we
> wanted, but will LyX accept that?
What is the output? I think it should look as comparable as possible. I.e., if
the 1.5 document outputted
Jürgen Spitzmüller wrote:
rgheck wrote:
One of our users has had a problem converting certain documents into
1.6. Turns out these are documents that have subfigures but NO
subcaption. Right now, lyx2lyx throws an error in this case. It's easy
to fix this, but what should we do? Can we just om
rgheck wrote:
> One of our users has had a problem converting certain documents into
> 1.6. Turns out these are documents that have subfigures but NO
> subcaption. Right now, lyx2lyx throws an error in this case. It's easy
> to fix this, but what should we do? Can we just omit the caption? Should
>
One of our users has had a problem converting certain documents into
1.6. Turns out these are documents that have subfigures but NO
subcaption. Right now, lyx2lyx throws an error in this case. It's easy
to fix this, but what should we do? Can we just omit the caption? Should
we write and empt
On Saturday 21 October 2006 11:12, Georg Baum wrote:
>
> We have more filename encoding problems. Unless there is a very easy fix I
> vote against fixing this in 1.4. In 1.5 we should IMO output all filenames
> to the python script in utf8 encoding and declare that encoding in the
> script.
I ag
Am Samstag, 21. Oktober 2006 02:32 schrieb Uwe Stöhr:
> The problem is that the temporarily generated python files don't have a
> defined encoding. The encoding should be the one of the current OS
> setting. Bo, is this possible to have?
We have more filename encoding problems. Unless there is
Lars Gullik Bjønnes wrote:
Uwe Stöhr <[EMAIL PROTECTED]> writes:
| When I open a LyX-file that is in a path with spaces. I get the
| following error message when included images should be converted to be
| displayed:
|
| ---
| File "C:/Documents and Settings/usti/Local
| Settings/Temp/lyx_tmpd
Uwe Stöhr <[EMAIL PROTECTED]> writes:
| When I open a LyX-file that is in a path with spaces. I get the
| following error message when included images should be converted to be
| displayed:
|
| ---
| File "C:/Documents and Settings/usti/Local
| Settings/Temp/lyx_tmpdir2816a00220/lyxconvert0.py",
When I open a LyX-file that is in a path with spaces. I get the
following error message when included images should be converted to be
displayed:
---
File "C:/Documents and Settings/usti/Local
Settings/Temp/lyx_tmpdir2816a00220/lyxconvert0.py", line 11
SyntaxError: Non-ASCII character '\xfc' i
On Tue, Aug 20, 2002 at 08:59:36AM +0100, José Abílio Oliveira Matos wrote:
> > If no other LyX program is active, please delete the pipe by hand and
> > try again.
>
> Do you get the above?
I did not type it by hand...
> Yes. Since I'm working on those files wait a day or so. :-)
> The e
On Tuesday 20 August 2002 08:32, Andre Poenitz wrote:
> I get:
>
> If no other LyX program is active, please delete the pipe by hand and
> try again.
Do you get the above?
> Traceback (most recent call last):
> File "/usr/local/bin/lyx2lyx", line 173, in ?
> main(sys.argv)
> File "/usr
I get:
If no other LyX program is active, please delete the pipe by hand and
try again.
Traceback (most recent call last):
File "/usr/local/bin/lyx2lyx", line 173, in ?
main(sys.argv)
File "/usr/local/bin/lyx2lyx", line 166, in main
__import__("lyxconvert_" + fmt).convert(header,bod
39 matches
Mail list logo
