Re: Error while exporting format: \converter

[Hal Kierstead via lyx-users]

> On Jan 6, 2024, at 6:36 PM, Steve Litt  wrote:
> 
> Hal Kierstead via lyx-users said on Sat, 6 Jan 2024 08:14:34 -0700
> 
>> All -
>> 
>> I got this message,  "Error while exporting format: \converter”, when
>> trying to view a master document. It has happened in the past, but I
>> forget how to correct it. Can someone help?
> 
> Your first step is to copy the document and reduce it to an MWE. An MWE
> is the tiniest possible document that still reproduces the symptom.
> Armed with the MWE, you can either troubleshoot it yourself or actually
> get help.
> 
> HTH,
> 
> SteveT
> 
> Steve Litt 
> 
Steve -
Pauls’s comment was enough for me to fix the problem. It had nothing to do with 
MWE’s:
> What format are you using to view the document, and do you have a converter 
> set up for that format?
Hal
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Error while exporting format: \converter

[Steve Litt]

Hal Kierstead via lyx-users said on Sat, 6 Jan 2024 08:14:34 -0700

>All -
>
>I got this message,  "Error while exporting format: \converter”, when
>trying to view a master document. It has happened in the past, but I
>forget how to correct it. Can someone help?

Your first step is to copy the document and reduce it to an MWE. An MWE
is the tiniest possible document that still reproduces the symptom.
Armed with the MWE, you can either troubleshoot it yourself or actually
get help.

HTH,

SteveT

Steve Litt 

Autumn 2023 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Error while exporting format: \converter----Thanks

[Hal Kierstead via lyx-users]

Paul -

Many thanks; your question was enough for me to find the problem. For some 
reason, the Default Output Format with tex fonts was blank—I fixed this. I have 
no idea how this happened all of a sudden. Anyway it works now.

Hal

> On Jan 6, 2024, at 9:20 AM, Paul Rubin  wrote:
> 
> 
> 
> On 1/6/24 10:14, Hal Kierstead via lyx-users wrote:
>> All -
>> 
>> I got this message,  "Error while exporting format: \converter”, when trying 
>> to view a master document. It has happened in the past, but I forget how to 
>> correct it. Can someone help?
>> 
>> I am using Lyx 2.3.7 on with MacOS: 11.7.10.
>> 
>> Thanks,
>> 
>> Hal
> What format are you using to view the document, and do you have a converter 
> set up for that format?
> 
> Paul
> 
> -- 
> lyx-users mailing list
> lyx-users@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-users

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Error while exporting format: \converter

[Paul Rubin]

On 1/6/24 10:14, Hal Kierstead via lyx-users wrote:

All -

I got this message,  "Error while exporting format: \converter”, when trying to 
view a master document. It has happened in the past, but I forget how to correct it. 
Can someone help?

I am using Lyx 2.3.7 on with MacOS: 11.7.10.

Thanks,

Hal
What format are you using to view the document, and do you have a 
converter set up for that format?


Paul

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Error while exporting format: \converter

[Hal Kierstead via lyx-users]

All -

I got this message,  "Error while exporting format: \converter”, when trying to 
view a master document. It has happened in the past, but I forget how to 
correct it. Can someone help?

I am using Lyx 2.3.7 on with MacOS: 11.7.10.

Thanks,

Hal
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Error when exporting to LyX Archive (zip)

[José Matos]

On Wed, 2023-12-06 at 16:37 +0100, kzsta...@gmail.com wrote:
> When exporting to  LyX Archive (zip) in LyX-2.4.0-beta5 on Windows-
> 11, I get the message “Cannot convert file”; see the attached screen
> print. It appears that this is caused by the use of xrange in
> lyxpak.py; see the attached part of the log file of LyX running as
> lyx -dbg all.  In LyX-2.3.7, exporting works fine.
> LyX-2.3 uses Python2, and LyX-2.4 uses Python3. In Python3, xrange
> has been removed, and replaced by an extended version of range; see
> https://docs.python.org/3/whatsnew/3.0.html#views-and-iterators-instead-of-lists
>  
> Kees

You are right. :-)

The fix is quite simple as you suggest, replace xrange with range.

One small note about the above, 2.4 can still work with Python 2.
Fortunately, in this regard, the above change is compatible with Python
2 and so it is the correct, and safe, choice to apply to LyX 2.4.

I took this opportunity to check for other occurrences of xrange in 2.4
and that was the last case.
-- 
José Abílio
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Error when exporting to LyX Archive (zip)

[kzstatis]

When exporting to  LyX Archive (zip) in LyX-2.4.0-beta5 on Windows-11, I get
the message "Cannot convert file"; see the attached screen print. It appears
that this is caused by the use of xrange in lyxpak.py; see the attached part
of the log file of LyX running as lyx -dbg all.  In LyX-2.3.7, exporting
works fine.

LyX-2.3 uses Python2, and LyX-2.4 uses Python3. In Python3, xrange has been
removed, and replaced by an extended version of range; see
https://docs.python.org/3/whatsnew/3.0.html#views-and-iterators-instead-of-l
ists

 

Kees

 

 

 



testxp.lyx
Description: application/lyx
BufferParams.cpp (Undo.cpp330): Checking whether document is in a system dir... 
( no
596): --- End of group 7 of buffer 014A8D7EEF00support\FileName.cpp 
(629): Checksumming "
F:/Users/Kees/Documenten/Papers/LyX/Test/Pak/testxp.lyx" 3132205323 lasted 2 ms.
BufferView.cpp (3555Converter.cpp (527): Converting from  lyx to lyxzip
):  *** START DRAWING ***Converter.cpp (681): Calling python -tt 
$$s/scripts/lyxpak.py 
"F:/Users/Kees/Documenten/Papers/LyX/Test/Pak/"/"testxp.lyx"

BufferView.cpp (3600): Strategy: FullScreenUpdate
support\Systemcall.cpp (TextMetrics.cpp265): Running: python -tt "C:/Program 
Files/LyX 2.4/Resources/scripts/lyxpak.py" 
"F:/Users/Kees/Documenten/Papers/LyX/Test/Pak/"/"testxp.lyx"
 (2120): main text redraw pit=0 row=0 full_repaint
BufferView.cpp (3624):   *** END DRAWING ***
BufferView.cpp (611):  Updating scrollbar: height: 1 curr par: 0 default height 
25
BufferView.cpp (627): storing height for pit 0 : 73
Traceback (most recent call last):
  File "C:\Program Files\LyX 2.4\Resources\scripts\lyxpak.py", line 393, in 

argv = [argv_unicode[i].encode('utf-8') for i in xrange(1, argc.value)]
 ^^
NameError: name 'xrange' is not defined. Did you mean: 'range'?
support\Systemcall.cpp (306): Systemcall: 'python -tt "C:/Program Files/LyX 
2.4/Resources/scripts/lyxpak.py" 
"F:/Users/Kees/Documenten/Papers/LyX/Test/Pak/"/"testxp.lyx"' finished with 
exit code 1
Error: Cannot convert file
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: change xml info when exporting to LyXHTML

[Steve Litt]

Lorenzo Bertini said on Mon, 11 Jul 2022 10:29:16 +0200

>Il 11/07/22 08:02, Steve Litt ha scritto:
>> Lorenzo Bertini said on Mon, 11 Jul 2022 04:00:56 +0200
>>> beware it will be put BEFORE any
>>> layout generated CSS, so anything hardcoded by the layout will
>>> override your custom rules; in this case you will have to edit the
>>> specific layout (a couple lines in the local layout, nothing
>>> daunting). This is documented in the "Customization" tutorial.  
>> 
>> Sounds like a misunderstanding of the "cascading" part of Cascading
>> Style Sheets (CSS).  
>
>Eh, I might, but this is what I observe. Cross checking is welcome.

Whoa, I'm sorry, my bad. What I meant was it's *the developer's"
misunderstanding of cascading, not the person reporting the behavior.
Sorry.

SteveT

Steve Litt 
Summer 2022 featured book: Making Mental Models: Advanced Edition
http://www.troubleshooters.com/mmm
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: change xml info when exporting to LyXHTML

[Lorenzo Bertini]

Il 11/07/22 08:02, Steve Litt ha scritto:

Lorenzo Bertini said on Mon, 11 Jul 2022 04:00:56 +0200




LyX has two (three?) ways of inserting custom stuff in the  of a
LyXHTML document, like for example CSS:

1. if you write your own layout file, or use the convenient "local
layout" section in the document settings (so you don't have to bother
with files), LyX will put in the  all the relevant CSS.

2. you can put "AddToHTMLPreamble" in a local layout to have custom
snippets added to the ; beware it will be put BEFORE any layout
generated CSS, so anything hardcoded by the layout will override your
custom rules; in this case you will have to edit the specific layout
(a couple lines in the local layout, nothing daunting). This is
documented in the "Customization" tutorial.


Sounds like a misunderstanding of the "cascading" part of Cascading
Style Sheets (CSS).


Eh, I might, but this is what I observe. Cross checking is welcome.





3(?). Some time ago I asked on lyx-devel for a "preamble tab" in
document settings, but for LyXHTML instead of LaTeX. This would put
everything inside it AFTER everything in the head so it would have the
last words on everything. The patch I made is in
https://www.lyx.org/trac/ticket/12061.


18 months ago. Well, you did your part.


I posted the patch on lyx-devel way before (its been years) but it's 
nobody's fault it never make it through. Its a workaround at best, and 
not something wanted by everybody (me included, it feels against LyX's 
way of doing things). Richard originally asked for it to be posted, but 
then had no time to follow up. Nobody is at fault here.





If you think something LyX puts in the preamble is outdated or
hardcoding too much, feel free to report it on the bug tracker
https://www.lyx.org/trac/wiki/BugTrackerHome. I'm reporting everything
I find about LyXHTML but I always feel like I'm the only one using it


Ixnay on bugtrackers. I'm not going to learn 30 different bugtrackers,
when they consistently ask the wrong questions and aren't responded to
anyway. I'd rather code around this stuff myself.


SteveT

Steve Litt
March 2022 featured book: Making Mental Models: Advanced Edition
http://www.troubleshooters.com/mmm


This is very far from my experience with bug trackers; to me they all 
ask the same (right) questions, there's nothing new to learn, and I get 
answers most of the time. I'm sorry if circumstances led you to believe 
this.


Lorenzo
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: change xml info when exporting to LyXHTML

[Steve Litt]

Lorenzo Bertini said on Mon, 11 Jul 2022 04:00:56 +0200


>
>LyX has two (three?) ways of inserting custom stuff in the  of a 
>LyXHTML document, like for example CSS:
>
>1. if you write your own layout file, or use the convenient "local 
>layout" section in the document settings (so you don't have to bother 
>with files), LyX will put in the  all the relevant CSS.
>
>2. you can put "AddToHTMLPreamble" in a local layout to have custom 
>snippets added to the ; beware it will be put BEFORE any layout 
>generated CSS, so anything hardcoded by the layout will override your 
>custom rules; in this case you will have to edit the specific layout
>(a couple lines in the local layout, nothing daunting). This is
>documented in the "Customization" tutorial.

Sounds like a misunderstanding of the "cascading" part of Cascading
Style Sheets (CSS). 

>
>3(?). Some time ago I asked on lyx-devel for a "preamble tab" in 
>document settings, but for LyXHTML instead of LaTeX. This would put 
>everything inside it AFTER everything in the head so it would have the 
>last words on everything. The patch I made is in 
>https://www.lyx.org/trac/ticket/12061.

18 months ago. Well, you did your part.

>If you think something LyX puts in the preamble is outdated or 
>hardcoding too much, feel free to report it on the bug tracker 
>https://www.lyx.org/trac/wiki/BugTrackerHome. I'm reporting everything
>I find about LyXHTML but I always feel like I'm the only one using it

Ixnay on bugtrackers. I'm not going to learn 30 different bugtrackers,
when they consistently ask the wrong questions and aren't responded to
anyway. I'd rather code around this stuff myself.


SteveT

Steve Litt 
March 2022 featured book: Making Mental Models: Advanced Edition
http://www.troubleshooters.com/mmm
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: change xml info when exporting to LyXHTML

[Steve Litt]

Lorenzo Bertini said on Mon, 11 Jul 2022 04:00:56 +0200


>If you think something LyX puts in the preamble is outdated or 
>hardcoding too much, feel free to report it on the bug tracker 
>https://www.lyx.org/trac/wiki/BugTrackerHome. I'm reporting everything
>I find about LyXHTML but I always feel like I'm the only one using it
>:).

I don't use bugtrackers. They're all different, requiring learning
each one, they ask the wrong questions, and in most cases bugtrackers
are where problems go to die.

On April 10 2022 I took an hour or so creating CSS that reproduced LyX'
standard of not indenting the first paragraph after a heading, and
posted it on the list, asking that somebody forward it to the
developer's list. I posted the complete CSS. I solved the problem and
all I got for my trouble was criticism. Screw it.

SteveT

Steve Litt 
March 2022 featured book: Making Mental Models: Advanced Edition
http://www.troubleshooters.com/mmm
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: change xml info when exporting to LyXHTML

[Lorenzo Bertini]

Il 10/07/22 23:50, Steve Litt ha scritto:

tush via lyx-users said on Sat, 09 Jul 2022 15:54:06 +


I want to override the default information LyX provides to my document
when I export it to xml with Export->LyXHTML

At the moment the info inserted to  tag is



http://www.w3.org/Math/DTD/mathml2/xhtml-math11-f.dtd;>

http://www.w3.org/1999/xhtml;>







I am writing my own layout file in which all my customization will be
inserted.

I want for example to change the first line simply to



to add



and to include my style sheet:



What changes should I make to the my .layout file?

I haven't found this information I am looking for in the Customization
manual.


LyX has two (three?) ways of inserting custom stuff in the  of a 
LyXHTML document, like for example CSS:


1. if you write your own layout file, or use the convenient "local 
layout" section in the document settings (so you don't have to bother 
with files), LyX will put in the  all the relevant CSS.


2. you can put "AddToHTMLPreamble" in a local layout to have custom 
snippets added to the ; beware it will be put BEFORE any layout 
generated CSS, so anything hardcoded by the layout will override your 
custom rules; in this case you will have to edit the specific layout (a 
couple lines in the local layout, nothing daunting). This is documented 
in the "Customization" tutorial.


3(?). Some time ago I asked on lyx-devel for a "preamble tab" in 
document settings, but for LyXHTML instead of LaTeX. This would put 
everything inside it AFTER everything in the head so it would have the 
last words on everything. The patch I made is in 
https://www.lyx.org/trac/ticket/12061.


I've been working around LyX quirks when it comes to adding custom stuff 
to LyXHTML for a long time, feel free to ask anything.




You're speaking my language tush!

It's been years since I looked at any kind of LyX HTML export, but if
it's what you're saying now, I might revisit the situation.

I think what you're asking for is best handled by a post-processor that
modifies the exported well-formed XML HTML5. Easy and fast with a
Python program that:

* Replaces existing doctype with 

* Gets rid of that silly  line.
   HTML specs say that the UTF-8 line belongs in the ". Like you said, the language line
   belongs in  or whatever language you want.

* Replaces the exporter's CSS stylesheet with your own. I don't think
   you want to mess with your LyX styles in your layout file because you
   WANT your PDF styles to look very different from your HTML styles.

This is all accomplished with a very easy to write Python program that
will postprocess the exported file in a half a second. If the exported
file is *really* well formed XML, you can check it with my
xmlchecker.py shown at
http://troubleshooters.com/web/validating.htm#xmlchecker .

HTH,

SteveT

Steve Litt
Summer 2022 featured book: Making Mental Models: Advanced Edition
http://www.troubleshooters.com/mmm


If you think something LyX puts in the preamble is outdated or 
hardcoding too much, feel free to report it on the bug tracker 
https://www.lyx.org/trac/wiki/BugTrackerHome. I'm reporting everything I 
find about LyXHTML but I always feel like I'm the only one using it :).


Lorenzo
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: change xml info when exporting to LyXHTML

[Steve Litt]

tush via lyx-users said on Sat, 09 Jul 2022 15:54:06 +

>I want to override the default information LyX provides to my document
>when I export it to xml with Export->LyXHTML
>
>At the moment the info inserted to  tag is
>
>
>
>"http://www.w3.org/Math/DTD/mathml2/xhtml-math11-f.dtd;>
>
>http://www.w3.org/1999/xhtml;>
>
>
>
>
>
>
>
>I am writing my own layout file in which all my customization will be
>inserted.
>
>I want for example to change the first line simply to
>
>
>
>to add
>
>
>
>and to include my style sheet:
>
>
>
>What changes should I make to the my .layout file?
>
>I haven't found this information I am looking for in the Customization
>manual.

You're speaking my language tush!

It's been years since I looked at any kind of LyX HTML export, but if
it's what you're saying now, I might revisit the situation.

I think what you're asking for is best handled by a post-processor that
modifies the exported well-formed XML HTML5. Easy and fast with a
Python program that:

* Replaces existing doctype with 

* Gets rid of that silly  line.
  HTML specs say that the UTF-8 line belongs in the ". Like you said, the language line
  belongs in  or whatever language you want.

* Replaces the exporter's CSS stylesheet with your own. I don't think
  you want to mess with your LyX styles in your layout file because you
  WANT your PDF styles to look very different from your HTML styles.

This is all accomplished with a very easy to write Python program that
will postprocess the exported file in a half a second. If the exported
file is *really* well formed XML, you can check it with my
xmlchecker.py shown at
http://troubleshooters.com/web/validating.htm#xmlchecker .

HTH,

SteveT

Steve Litt 
Summer 2022 featured book: Making Mental Models: Advanced Edition
http://www.troubleshooters.com/mmm
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

change xml info when exporting to LyXHTML

[tush via lyx-users]

I want to override the default information LyX provides to my document when I 
export it to xml with Export->LyXHTML

At the moment the info inserted to  tag is



http://www.w3.org/Math/DTD/mathml2/xhtml-math11-f.dtd;>

http://www.w3.org/1999/xhtml;>







I am writing my own layout file in which all my customization will be inserted.

I want for example to change the first line simply to



to add



and to include my style sheet:



What changes should I make to the my .layout file?

I haven't found this information I am looking for in the Customization manual.-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Image paths when exporting from Lyx

[muzzle]

Hello everyone,
I have partially solved my previous issue
https://tex.stackexchange.com/questions/524505/image-path-when-exporting-from-lyx/552722#552722.


The one problem I have left is that lyx removes the image extension when
exporting to latex (when using the "nice" flag); this forces me to specify
the image extension in the pandoc command which is not very flexible. Do
you have any idea how to get lyx to output the image file name including
the extension?

Best,

Emme

On Tue, Jan 21, 2020 at 9:43 PM Scott Kostyshak  wrote:

> On Tue, Jan 21, 2020 at 04:40:06PM +0100, muzzle wrote:
> > Hello,
> >
> > I am trying to setup LyX to export directly to the reStructuredText
> format.
> > I adapted these instructions
> > <https://lemmster.de/lyx-export-to-markdown.html> just replacing
> markdown
> > with rst.
> >
> > Unfortunately LyX changes the path of every image.
> >
> > e.g. this figure
> >
> > .. figure::
> 0_home_muzzle_Nextcloud_Stuff_Stuff_documentation_source_img_pressure.jpg
> >:alt: Pressure
> >:width: 80.0%
> >
> >Pressure
> >
> > should be
> >
> > .. figure:: img/pressure.jpg
> >:alt: Pressure
> >:width: 80.0%
> >
> >Pressure
> >
> > I think LyX is replacing the image path with that of a copy of the image
> > created to allow the converter to do its job. This is the correct
> behavior
> > if the output format will somehow embed the image in the document, but
> that
> > is not the case for reStructuredText (or for markdown, for that matter).
> >
> > If I export the lyx file as latex from the GUI, and then convert it to
> > reStructuredText using the command
> >
> > pandoc --wrap=none -f latex -t rst -o file.rst file.tex
> >
> > the image path is correct, is there a way to obtain the same effect from
> > the UI conversion and export system?
> >
> > Best,
> >
> > Emme
>
> Hi Emme,
>
> It's helpful to always cross-reference your posts. That way, if someone
> solves your question on one list, others with the same problem who find
> your other post can follow the link and see the solution. Here's your
> other post:
>
>
> https://tex.stackexchange.com/questions/524505/image-path-when-exporting-from-lyx
>
> I don't know the answer to you question but I hope someone else does!
>
> Best of luck,
>
> Scott
>

Thanks Scott,
In the maean while
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: mac os x exporting shortcuts

[Kornel Benko]

Am Tue, 28 Apr 2020 14:27:50 +0200
schrieb Salvatore Modica :

> I would like to export shortcuts to another computer, but I should know
> where they are stored - which I don't.
> Can you tell me?
> Many thanks
> Salvatore
> 

Your own shortcuts are in userdir/bind/user.bind.

Kornel


pgp02oNdHAW_B.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

mac os x exporting shortcuts

[Salvatore Modica]

I would like to export shortcuts to another computer, but I should know
where they are stored - which I don't.
Can you tell me?
Many thanks
Salvatore

-- 
Salvatore Modica
www.unipa.it/modica
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Image paths when exporting from Lyx

[Scott Kostyshak]

On Tue, Jan 21, 2020 at 04:40:06PM +0100, muzzle wrote:
> Hello,
> 
> I am trying to setup LyX to export directly to the reStructuredText format.
> I adapted these instructions
> <https://lemmster.de/lyx-export-to-markdown.html> just replacing markdown
> with rst.
> 
> Unfortunately LyX changes the path of every image.
> 
> e.g. this figure
> 
> .. figure:: 
> 0_home_muzzle_Nextcloud_Stuff_Stuff_documentation_source_img_pressure.jpg
>:alt: Pressure
>:width: 80.0%
> 
>Pressure
> 
> should be
> 
> .. figure:: img/pressure.jpg
>:alt: Pressure
>:width: 80.0%
> 
>Pressure
> 
> I think LyX is replacing the image path with that of a copy of the image
> created to allow the converter to do its job. This is the correct behavior
> if the output format will somehow embed the image in the document, but that
> is not the case for reStructuredText (or for markdown, for that matter).
> 
> If I export the lyx file as latex from the GUI, and then convert it to
> reStructuredText using the command
> 
> pandoc --wrap=none -f latex -t rst -o file.rst file.tex
> 
> the image path is correct, is there a way to obtain the same effect from
> the UI conversion and export system?
> 
> Best,
> 
> Emme

Hi Emme,

It's helpful to always cross-reference your posts. That way, if someone
solves your question on one list, others with the same problem who find
your other post can follow the link and see the solution. Here's your
other post:

  
https://tex.stackexchange.com/questions/524505/image-path-when-exporting-from-lyx

I don't know the answer to you question but I hope someone else does!

Best of luck,

Scott


signature.asc
Description: PGP signature
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Image paths when exporting from Lyx

[muzzle]

Hello,

I am trying to setup LyX to export directly to the reStructuredText format.
I adapted these instructions
 just replacing markdown
with rst.

Unfortunately LyX changes the path of every image.

e.g. this figure

.. figure:: 
0_home_muzzle_Nextcloud_Stuff_Stuff_documentation_source_img_pressure.jpg
   :alt: Pressure
   :width: 80.0%

   Pressure

should be

.. figure:: img/pressure.jpg
   :alt: Pressure
   :width: 80.0%

   Pressure

I think LyX is replacing the image path with that of a copy of the image
created to allow the converter to do its job. This is the correct behavior
if the output format will somehow embed the image in the document, but that
is not the case for reStructuredText (or for markdown, for that matter).

If I export the lyx file as latex from the GUI, and then convert it to
reStructuredText using the command

pandoc --wrap=none -f latex -t rst -o file.rst file.tex

the image path is correct, is there a way to obtain the same effect from
the UI conversion and export system?

Best,

Emme
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Exporting ePub / XML: always SIGSEV

[jezZiFeR]

Dear Eberhard,

thanks very much for the promising hint and sorry for answering late:
I am still trying to understand lwarp. It is already installed, and also the 
lwarpmk utility is set up, but I think I need a little time to get through 
this. I will give you a feedback when I have got it.

All best
Jess





Am 27. Apr. 2019, 16:49 +0200 schrieb Dr Eberhard Lisse :
> Have you looked at lwarp on CTAN?
>
> el
>
> On 2019-04-26 19:48 , jezZiFeR wrote:
> > Dear Anders,
> >
> > thank you so much! I have now found a possibility to use ePub. It is
> > still not perfect and up to now is not useful for publishing etc., but
> > for private use it is fine. The following seems to work for me:
> >
> > export–LyXhtml (here LyX is not getting a SIGSEV)
> > then I convert the XHTML-file in Calibre to ePub
> >
> > Calibre is really extremely useful… I think I will try a little bit
> > around with LyX and Calibre in the next time, but for the moment this
> > works for me.
> >
> > All best
> > Jess
>

Re: Exporting ePub / XML: always SIGSEV

[Dr Eberhard Lisse]

Have you looked at lwarp on CTAN?

el

On 2019-04-26 19:48 , jezZiFeR wrote:
> Dear Anders,
> 
> thank you so much!  I have now found a possibility to use ePub.  It is
> still not perfect and up to now is not useful for publishing etc., but
> for private use it is fine.  The following seems to work for me:
> 
> export–LyXhtml (here LyX is not getting a SIGSEV)
> then I convert the XHTML-file in Calibre to ePub
> 
> Calibre is really extremely useful… I think I will try a little bit
> around with LyX and Calibre in the next time, but for the moment this
> works for me.
> 
> All best
> Jess

Re: Exporting ePub / XML: always SIGSEV

[anek]

Thanks for the feedback Jess.


Good to hear it is working well.




All the best!


Anders




Ha det bra!


Anders







On Fri, Apr 26, 2019 at 7:48 PM +0200, "jezZiFeR"  wrote:















Dear Anders,


thank you so much! I have now found a possibility to use ePub. It is still not 
perfect and up to now is not useful for publishing etc., but for private use it 
is fine. The following seems to work for me:


export–LyXhtml (here LyX is not getting a SIGSEV)
then I convert the XHTML-file in Calibre to ePub


Calibre is really extremely useful… I think I will try a little bit around with 
LyX and Calibre in the next time, but for the moment this works for me.


All best
Jess











Am 25. Apr. 2019, 21:53 +0200 schrieb Anders Ekberg :


On 25 Apr 2019, at 21:36, jezZiFeR  wrote:




Hello Anders,


thanks a lot! This sounds good, but I do normally only use LyX and run into new 
problems. First I tried several possibilities to export to TeX is with also 
with »weitere Formate und Optionen« (more formats and options) – here it 
worked. In all other cases (file – export – LaTeX (plain) or export – export as 
– LaTeX (normal) or export – export as – LaTeX (XeTeX)) I have got a 
SIGSEV-signal again. 


Well, then I opened the TeX-file in TeXShop (I dont have TeX Studio). In the 
prefs there is no build, and I did not know ho to continue from here.
 Then I just tried:


export – XML text


This produced an XML-file. I do not know if the file would work, because I do 
not know how to continue from here. Did Could I also use calibre for converting 
from XML to ePub?


Thanks, best
Jess





Looks like you have a problem with your installation. I would try to reinstall 
(and if problems remain to a Tools > Reconfigure and open Terminal and run sudo 
texhash).

Anyway, to your question: Calibre is free to download, so you can download it 
and then add the xml-file to Calibre (Add book…) and then convert to EPUB 
(Convert books…). If it works or not should depend on the status the XML-file, 
but that is outside my knowledge (I was just happy when the recipe I posted 
worked ;-)


All the best!
Anders

Re: Exporting ePub / XML: always SIGSEV

[jezZiFeR]

Dear Anders,

thank you so much! I have now found a possibility to use ePub. It is still not 
perfect and up to now is not useful for publishing etc., but for private use it 
is fine. The following seems to work for me:

export–LyXhtml (here LyX is not getting a SIGSEV)
then I convert the XHTML-file in Calibre to ePub

Calibre is really extremely useful… I think I will try a little bit around with 
LyX and Calibre in the next time, but for the moment this works for me.

All best
Jess





Am 25. Apr. 2019, 21:53 +0200 schrieb Anders Ekberg :
> On 25 Apr 2019, at 21:36, jezZiFeR  wrote:
> >
> > Hello Anders,
> >
> > thanks a lot! This sounds good, but I do normally only use LyX and run into 
> > new problems. First I tried several possibilities to export to TeX is with 
> > also with »weitere Formate und Optionen« (more formats and options) – here 
> > it worked. In all other cases (file – export – LaTeX (plain) or export – 
> > export as – LaTeX (normal) or export – export as – LaTeX (XeTeX)) I have 
> > got a SIGSEV-signal again.
> >
> > Well, then I opened the TeX-file in TeXShop (I dont have TeX Studio). In 
> > the prefs there is no build, and I did not know ho to continue from here.
> >  Then I just tried:
> >
> > export – XML text
> >
> > This produced an XML-file. I do not know if the file would work, because I 
> > do not know how to continue from here. Did Could I also use calibre for 
> > converting from XML to ePub?
> >
> > Thanks, best
> > Jess
>
> Looks like you have a problem with your installation. I would try to 
> reinstall (and if problems remain to a Tools > Reconfigure and open Terminal 
> and run sudo texhash).
> Anyway, to your question: Calibre is free to download, so you can download it 
> and then add the xml-file to Calibre (Add book…) and then convert to EPUB 
> (Convert books…). If it works or not should depend on the status the 
> XML-file, but that is outside my knowledge (I was just happy when the recipe 
> I posted worked ;-)
>
> All the best!
> Anders
>

Re: Exporting ePub / XML: always SIGSEV

[jezZiFeR]

Dear Stephan,

thank you, I continue finding workarounds, at least this now only happens if I 
try to export via »export as«. The other possibilities seem to work though.

All best
Jess




Am 26. Apr. 2019, 10:52 +0200 schrieb Stephan Witt :
> Am 26.04.2019 um 10:28 schrieb jezZiFeR :
> >
> > Dear Stephan,
> >
> > hm, now I have got a SIGSEV-signal again and could reproduce it every time 
> > I use the dialogue with »export as«, like this:
> >
> > file–export–export as
> >
> > I get the message, that there are no information to export to the chosen 
> > format:
> > »Keine Informationen vorhanden, um das Format HTML zu exportieren.«
> > and the SIGSEV-error-message. So this time I could send the stack trace, 
> > see below.
>
> Dear Jess,
>
> thank you for it. Of course it looks like garbage for mere mortal people.

:)
at least i could find the lyx–frontend–action–action in line 6… :)

>
> If I try to interpret it I can see in line (6) our code is involved the last 
> time before the crash. Here the method named lyx::frontend::Action::action is 
> called and this method does nearly nothing except calling some configured 
> method indirectly. A crash here means the internal memory structures of the 
> running LyX got corrupted at some point in time before. Unfortunately these 
> things happen unnoticed at the time the code to blame is executed. Probably 
> there is some memory passed back to the OS too early.
>
> So, I don’t have a solution for this crash. But it’s almost sure it’s 
> unrelated with the availability of the export function.
>
> Best regards,
> Stephan
>
> >
> > Thanks in advance, all best
> > Jess
> >
> >
> >
> > —
> >
> > ( 1) 1 lyx 0x00010560d5d6 
> > _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
> >  : 1 lyx 0x00010560d5d6 
> > _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
> >  + 199
> > ( 2) 2 lyx 0x00010560d9e1 
> > _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
> >  : 2 lyx 0x00010560d9e1 
> > _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
> >  + 135
> > ( 3) 3 lyx 0x0001053a71ce _ZN3lyxL13error_handlerEi : 3 lyx 
> > 0x0001053a71ce _ZN3lyxL13error_handlerEi + 603
> > ( 4) 4 libsystem_platform.dylib 0x7fff5d488b3d _sigtramp : 4 
> > libsystem_platform.dylib 0x7fff5d488b3d _sigtramp + 29
> > ( 5) 5 libsystem_malloc.dylib 0x7fff5d44c807 malloc_zone_malloc : 5 
> > libsystem_malloc.dylib 0x7fff5d44c807 malloc_zone_malloc + 103
> > ( 6) 6 lyx 0x0001055f60aa _ZN3lyx8frontend6Action6actionEv : 6 lyx 
> > 0x0001055f60aa _ZN3lyx8frontend6Action6actionEv + 74
> > ( 7) 7 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv : 
> > 7 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 3113
> > ( 8) 8 QtWidgets 0x000106bce457 _ZN7QAction8activateENS_11ActionEventE 
> > : 8 QtWidgets 0x000106bce457 _ZN7QAction8activateENS_11ActionEventE + 
> > 263
> > ( 9) 9 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv : 
> > 9 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 3113
> > ( 10) 10 QtCore 0x000106781ac1 _ZN7QObject5eventEP6QEvent : 10 QtCore 
> > 0x000106781ac1 _ZN7QObject5eventEP6QEvent + 801
> > ( 11) 11 QtWidgets 0x000106bd7dfd 
> > _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent : 11 QtWidgets 
> > 0x000106bd7dfd 
> > _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 301
> > ( 12) 12 QtWidgets 0x000106bd9177 
> > _ZN12QApplication6notifyEP7QObjectP6QEvent : 12 QtWidgets 
> > 0x000106bd9177 _ZN12QApplication6notifyEP7QObjectP6QEvent + 391
> > ( 13) 13 lyx 0x00010561cb6b 
> > _ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent : 13 lyx 
> > 0x00010561cb6b 
> > _ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent + 21
> > ( 14) 14 QtCore 0x000106757be4 
> > _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent : 14 QtCore 
> > 0x000106757be4 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent 
> > + 164
> > ( 15) 15 QtCore 0x000106758d6b 
> > _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData : 
> > 15 QtCore 0x000106758d6b 
> > _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData + 
> > 891
> > ( 16) 16 libqcocoa.dylib 0x00010926010e 
> > _ZN28QCocoaEventDispatcherPrivate19processPostedEventsEv : 16 
> > libqcocoa.dylib 0x00010926010e 
> > _ZN28QCocoaEventDispatcherPrivate19processPostedEventsEv + 190
> > ( 17) 17 libqcocoa.dylib 0x0001092609d1 
> > _ZN28QCocoaEventDispatcherPrivate26postedEventsSourceCallbackEPv : 17 
> > libqcocoa.dylib 0x0001092609d1 
> > _ZN28QCocoaEventDispatcherPrivate26postedEventsSourceCallbackEPv + 33
> > ( 18) 18 CoreFoundation 0x7fff3006d395 
> > 

Re: Exporting ePub / XML: always SIGSEV

[Stephan Witt]

Am 26.04.2019 um 10:28 schrieb jezZiFeR :
> 
> Dear Stephan,
> 
> hm, now I have got a SIGSEV-signal again and could reproduce it every time I 
> use the dialogue with »export as«, like this:
> 
> file–export–export as
> 
> I get the message, that there are no information to export to the chosen 
> format:
> »Keine Informationen vorhanden, um das Format HTML zu exportieren.«
> and the SIGSEV-error-message. So this time I could send the stack trace, see 
> below.

Dear Jess,

thank you for it. Of course it looks like garbage for mere mortal people.

If I try to interpret it I can see in line (6) our code is involved the last 
time before the crash. Here the method named lyx::frontend::Action::action is 
called and this method does nearly nothing except calling some configured 
method indirectly. A crash here means the internal memory structures of the 
running LyX got corrupted at some point in time before. Unfortunately these 
things happen unnoticed at the time the code to blame is executed. Probably 
there is some memory passed back to the OS too early.

So, I don’t have a solution for this crash. But it’s almost sure it’s unrelated 
with the availability of the export function.

Best regards,
Stephan

> 
> Thanks in advance, all best
> Jess
> 
> 
> 
> —
> 
> ( 1) 1 lyx 0x00010560d5d6 
> _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
>  : 1 lyx 0x00010560d5d6 
> _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
>  + 199
> ( 2) 2 lyx 0x00010560d9e1 
> _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
>  : 2 lyx 0x00010560d9e1 
> _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
>  + 135
> ( 3) 3 lyx 0x0001053a71ce _ZN3lyxL13error_handlerEi : 3 lyx 
> 0x0001053a71ce _ZN3lyxL13error_handlerEi + 603
> ( 4) 4 libsystem_platform.dylib 0x7fff5d488b3d _sigtramp : 4 
> libsystem_platform.dylib 0x7fff5d488b3d _sigtramp + 29
> ( 5) 5 libsystem_malloc.dylib 0x7fff5d44c807 malloc_zone_malloc : 5 
> libsystem_malloc.dylib 0x7fff5d44c807 malloc_zone_malloc + 103
> ( 6) 6 lyx 0x0001055f60aa _ZN3lyx8frontend6Action6actionEv : 6 lyx 
> 0x0001055f60aa _ZN3lyx8frontend6Action6actionEv + 74
> ( 7) 7 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv : 7 
> QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 3113
> ( 8) 8 QtWidgets 0x000106bce457 _ZN7QAction8activateENS_11ActionEventE : 
> 8 QtWidgets 0x000106bce457 _ZN7QAction8activateENS_11ActionEventE + 263
> ( 9) 9 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv : 9 
> QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 3113
> ( 10) 10 QtCore 0x000106781ac1 _ZN7QObject5eventEP6QEvent : 10 QtCore 
> 0x000106781ac1 _ZN7QObject5eventEP6QEvent + 801
> ( 11) 11 QtWidgets 0x000106bd7dfd 
> _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent : 11 QtWidgets 
> 0x000106bd7dfd _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent 
> + 301
> ( 12) 12 QtWidgets 0x000106bd9177 
> _ZN12QApplication6notifyEP7QObjectP6QEvent : 12 QtWidgets 0x000106bd9177 
> _ZN12QApplication6notifyEP7QObjectP6QEvent + 391
> ( 13) 13 lyx 0x00010561cb6b 
> _ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent : 13 lyx 
> 0x00010561cb6b _ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent 
> + 21
> ( 14) 14 QtCore 0x000106757be4 
> _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent : 14 QtCore 
> 0x000106757be4 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 
> 164
> ( 15) 15 QtCore 0x000106758d6b 
> _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData : 15 
> QtCore 0x000106758d6b 
> _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData + 891
> ( 16) 16 libqcocoa.dylib 0x00010926010e 
> _ZN28QCocoaEventDispatcherPrivate19processPostedEventsEv : 16 libqcocoa.dylib 
> 0x00010926010e _ZN28QCocoaEventDispatcherPrivate19processPostedEventsEv + 
> 190
> ( 17) 17 libqcocoa.dylib 0x0001092609d1 
> _ZN28QCocoaEventDispatcherPrivate26postedEventsSourceCallbackEPv : 17 
> libqcocoa.dylib 0x0001092609d1 
> _ZN28QCocoaEventDispatcherPrivate26postedEventsSourceCallbackEPv + 33
> ( 18) 18 CoreFoundation 0x7fff3006d395 
> __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ : 18 
> CoreFoundation 0x7fff3006d395 
> __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
> ( 19) 19 CoreFoundation 0x7fff3006d33b __CFRunLoopDoSource0 : 19 
> CoreFoundation 0x7fff3006d33b __CFRunLoopDoSource0 + 108
> ( 20) 20 CoreFoundation 0x7fff30050dd1 __CFRunLoopDoSources0 : 20 
> CoreFoundation 0x7fff30050dd1 __CFRunLoopDoSources0 + 195
> ( 21) 21 CoreFoundation 0x7fff3005037a __CFRunLoopRun : 21 CoreFoundation 
> 0x7fff3005037a 

Re: Exporting ePub / XML: always SIGSEV

[jezZiFeR]

Dear Stephan,

hm, now I have got a SIGSEV-signal again and could reproduce it every time I 
use the dialogue with »export as«, like this:

file–export–export as

I get the message, that there are no information to export to the chosen format:
»Keine Informationen vorhanden, um das Format HTML zu exportieren.«
and the SIGSEV-error-message. So this time I could send the stack trace, see 
below.

Thanks in advance, all best
Jess



—

( 1) 1 lyx 0x00010560d5d6 
_ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
 : 1 lyx 0x00010560d5d6 
_ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
 + 199
( 2) 2 lyx 0x00010560d9e1 
_ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
 : 2 lyx 0x00010560d9e1 
_ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
 + 135
( 3) 3 lyx 0x0001053a71ce _ZN3lyxL13error_handlerEi : 3 lyx 
0x0001053a71ce _ZN3lyxL13error_handlerEi + 603
( 4) 4 libsystem_platform.dylib 0x7fff5d488b3d _sigtramp : 4 
libsystem_platform.dylib 0x7fff5d488b3d _sigtramp + 29
( 5) 5 libsystem_malloc.dylib 0x7fff5d44c807 malloc_zone_malloc : 5 
libsystem_malloc.dylib 0x7fff5d44c807 malloc_zone_malloc + 103
( 6) 6 lyx 0x0001055f60aa _ZN3lyx8frontend6Action6actionEv : 6 lyx 
0x0001055f60aa _ZN3lyx8frontend6Action6actionEv + 74
( 7) 7 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv : 7 
QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 3113
( 8) 8 QtWidgets 0x000106bce457 _ZN7QAction8activateENS_11ActionEventE : 8 
QtWidgets 0x000106bce457 _ZN7QAction8activateENS_11ActionEventE + 263
( 9) 9 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv : 9 
QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 3113
( 10) 10 QtCore 0x000106781ac1 _ZN7QObject5eventEP6QEvent : 10 QtCore 
0x000106781ac1 _ZN7QObject5eventEP6QEvent + 801
( 11) 11 QtWidgets 0x000106bd7dfd 
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent : 11 QtWidgets 
0x000106bd7dfd _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 
301
( 12) 12 QtWidgets 0x000106bd9177 
_ZN12QApplication6notifyEP7QObjectP6QEvent : 12 QtWidgets 0x000106bd9177 
_ZN12QApplication6notifyEP7QObjectP6QEvent + 391
( 13) 13 lyx 0x00010561cb6b 
_ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent : 13 lyx 
0x00010561cb6b _ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent + 
21
( 14) 14 QtCore 0x000106757be4 
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent : 14 QtCore 
0x000106757be4 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 
164
( 15) 15 QtCore 0x000106758d6b 
_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData : 15 
QtCore 0x000106758d6b 
_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData + 891
( 16) 16 libqcocoa.dylib 0x00010926010e 
_ZN28QCocoaEventDispatcherPrivate19processPostedEventsEv : 16 libqcocoa.dylib 
0x00010926010e _ZN28QCocoaEventDispatcherPrivate19processPostedEventsEv + 
190
( 17) 17 libqcocoa.dylib 0x0001092609d1 
_ZN28QCocoaEventDispatcherPrivate26postedEventsSourceCallbackEPv : 17 
libqcocoa.dylib 0x0001092609d1 
_ZN28QCocoaEventDispatcherPrivate26postedEventsSourceCallbackEPv + 33
( 18) 18 CoreFoundation 0x7fff3006d395 
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ : 18 CoreFoundation 
0x7fff3006d395 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 
17
( 19) 19 CoreFoundation 0x7fff3006d33b __CFRunLoopDoSource0 : 19 
CoreFoundation 0x7fff3006d33b __CFRunLoopDoSource0 + 108
( 20) 20 CoreFoundation 0x7fff30050dd1 __CFRunLoopDoSources0 : 20 
CoreFoundation 0x7fff30050dd1 __CFRunLoopDoSources0 + 195
( 21) 21 CoreFoundation 0x7fff3005037a __CFRunLoopRun : 21 CoreFoundation 
0x7fff3005037a __CFRunLoopRun + 1219
( 22) 22 CoreFoundation 0x7fff3004fc64 CFRunLoopRunSpecific : 22 
CoreFoundation 0x7fff3004fc64 CFRunLoopRunSpecific + 463
( 23) 23 HIToolbox 0x7fff2f2e6ab5 RunCurrentEventLoopInMode : 23 HIToolbox 
0x7fff2f2e6ab5 RunCurrentEventLoopInMode + 293
( 24) 24 HIToolbox 0x7fff2f2e66f4 ReceiveNextEventCommon : 24 HIToolbox 
0x7fff2f2e66f4 ReceiveNextEventCommon + 371
( 25) 25 HIToolbox 0x7fff2f2e6568 
_BlockUntilNextEventMatchingListInModeWithFilter : 25 HIToolbox 
0x7fff2f2e6568 _BlockUntilNextEventMatchingListInModeWithFilter + 64
( 26) 26 AppKit 0x7fff2d5a1363 _DPSNextEvent : 26 AppKit 0x7fff2d5a1363 
_DPSNextEvent + 997
( 27) 27 AppKit 0x7fff2d5a0102 -[NSApplication: 27 AppKit 
0x7fff2d5a0102 -[NSApplication(NSEvent) 
_nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362
( 28) 28 AppKit 0x7fff2d59a165 -[NSApplication run] : 28 AppKit 
0x7fff2d59a165 -[NSApplication run] + 699

Re: Exporting ePub / XML: always SIGSEV

[jezZiFeR]

Dear Stephan,

this is strange, I now could not reproduce the SIGSEV anymore, which I have 
always got over the last months. I could also not find out, what I might have 
changed. The only thing is that I removed the TeX 2017-version meanwhile, but I 
used 2018 anyhow. This is why I do not think, that this might affect this, but 
it is the only thing I really changed. I have tried it with different documents.

But still it is not possible to build an XML etc. If I try to do this via
export as
I still get those messages for any format:
»Keine Informationen vorhanden, um das Format OpenDocument (Pandoc) zu 
exportieren.«
»Keine Informationen vorhanden, um das Format HTML (MS Word) zu exportieren.«
»Keine Informationen vorhanden, um das Format HTML (MS Word) zu exportieren.«
So: there is no information to export to format X, but at least i do not get 
the SIGSEV anymore.

If I get the SIGSEV again later, I will send you the stack trace then.

Best
Jess




Am 25. Apr. 2019, 22:50 +0200 schrieb Stephan Witt :
> Am 25.04.2019 um 22:14 schrieb jezZiFeR :
> >
> > Dear Stephan,
> >
> > with the tutorial it seems that I also do not get a SIGSEV in some cases, 
> > but I also get it when I go via:
> > file–export–export as…
> >
> > When I tried this for.html I also got this message: »Kann keinen 
> > LaTeX-Befehl für das Zeichen '⌃' (Code-Punkt 0x2303) finden.
> > Einige Zeichen Ihres Dokuments sind mit der gewählten Kodierung 
> > wahrscheinlich nicht darstellbar.
> > Eine Änderung der Dokumentkodierung auf 'utf8' könnte helfen.«
> >
> > This means something like the is no LaTeX-command for »^« and it is 
> > suggested to change the document’s coding to utf 8, which is not possible 
> > for the tutorial-file.
>
> Yes, this is a problem with the tutorial in LyX 2.3.2 and will be fixed in 
> 2.3.3.
>
> >
> > Maybe it is interesting, that the dialogue of two different documents (mine 
> > & German tutorial) produce different export-possibilities and the tutorial 
> > has much more. I add two screenshots to make it clearer.
>
> Hmmm, the export possibilities efficiently depend on the existing converters. 
> The longer list doesn’t necessarily mean more possibilities… I don’t know 
> off-hand how the lists are constructed and why they contain useless entries.
>
> >
> > Excuse me, what is the »sack trace«? Should I send you the details of the 
> > SIGSEV?
>
> Yes, please.
>
> Best regards,
> Stephan
>
> > I will continue trying some more documents tomorrow.
> >
> > Thank you, all best
> > Jess
> >
> >
> >
> >
> >
> >
> >
> > Am 25. Apr. 2019, 21:52 +0200 schrieb Stephan Witt :
> > > Am 25.04.2019 um 18:56 schrieb jezZiFeR :
> > > >
> > > > Hello,
> > > >
> > > > I try to export ePubs for a while now and it never worked in different 
> > > > configurations. LyX was always freezing. In the moment I use OS 
> > > > 10.14.3, Intel and LyX 2.3.2 with TeXLive 2018.
> > > >
> > > > When I do the following:
> > > > + file – export as – DocBook (XML) and then try to save I get the 
> > > > follwing error:
> > > > »Keine Informationen vorhanden, um das Format DocBook (XML) zu 
> > > > exportieren.«
> > > > In English this means something like »There is no information to export 
> > > > the format DocBook (XML).
> > > > + Now I click »cancel« and get a SIGSEV-signal, like every time.
> > > >
> > > > Does anybody have a hint what I could do? Would be very good to use 
> > > > XML, maybe there is a workaround.
> > > >
> > > > Thanks, all best
> > > > Jess
> > >
> > > Hello Jess,
> > >
> > > I’m on Mac OS 10.14.4 with LyX 2.3.2. I’m unable to export to DocBook 
> > > too. But - at least with the Tutorial - I don’t get a crash on Cancel.
> > >
> > > Can you send me the stack trace please and tell me if it happens with 
> > > every LyX document or with some of your documents only?
> > >
> > > Best regards,
> > > Stephan
> >  > 22.04.20.png>
>

Re: Exporting ePub / XML: always SIGSEV

[Dr Eberhard Lisse]

This was mentioned last week, as being fixed for the next version with
this workaround.

el

> On 2019-04-19 17:48 , Jürgen Spitzmüller wrote:
[...]
>> A quick workaround: switch to utf8 encoding and add this to the
>> preamble: \DeclareUnicodeCharacter{2303}{\textasciicircum} HTH
[...]
On 2019-04-25 22:14 , jezZiFeR wrote:
[...]
> This means something like the is no LaTeX-command for »^« and it is
> suggested to change the document’s coding to utf 8, which is not
> possible for the tutorial-file.
[...]

Re: Exporting ePub / XML: always SIGSEV

[Stephan Witt]

Am 25.04.2019 um 22:14 schrieb jezZiFeR :
> 
> Dear Stephan,
> 
> with the tutorial it seems that I also do not get a SIGSEV in some cases, but 
> I also get it when I go via:
> file–export–export as…
> 
> When I tried this for.html I also got this message: »Kann keinen LaTeX-Befehl 
> für das Zeichen '⌃' (Code-Punkt 0x2303) finden. 
> Einige Zeichen Ihres Dokuments sind mit der gewählten Kodierung 
> wahrscheinlich nicht darstellbar.
> Eine Änderung der Dokumentkodierung auf 'utf8' könnte helfen.«
> 
> This means something like the is no LaTeX-command for »^« and it is suggested 
> to change the document’s coding to utf 8, which is not possible for the 
> tutorial-file.

Yes, this is a problem with the tutorial in LyX 2.3.2 and will be fixed in 
2.3.3.

> 
> Maybe it is interesting, that the dialogue of two different documents (mine & 
> German tutorial) produce different export-possibilities and the tutorial has 
> much more. I add two screenshots to make it clearer.

Hmmm, the export possibilities efficiently depend on the existing converters. 
The longer list doesn’t necessarily mean more possibilities… I don’t know 
off-hand how the lists are constructed and why they contain useless entries.

> 
> Excuse me, what is the »sack trace«? Should I send you the details of the 
> SIGSEV?

Yes, please.

Best regards,
Stephan

> I will continue trying some more documents tomorrow.
> 
> Thank you, all best
> Jess
> 
> 
> 
> 
> 
> 
> 
> Am 25. Apr. 2019, 21:52 +0200 schrieb Stephan Witt :
>> Am 25.04.2019 um 18:56 schrieb jezZiFeR :
>>> 
>>> Hello,
>>> 
>>> I try to export ePubs for a while now and it never worked in different 
>>> configurations. LyX was always freezing. In the moment I use OS 10.14.3, 
>>> Intel and LyX 2.3.2 with TeXLive 2018.
>>> 
>>> When I do the following:
>>> + file – export as – DocBook (XML) and then try to save I get the follwing 
>>> error:
>>> »Keine Informationen vorhanden, um das Format DocBook (XML) zu exportieren.«
>>> In English this means something like »There is no information to export the 
>>> format DocBook (XML).
>>> + Now I click »cancel« and get a SIGSEV-signal, like every time.
>>> 
>>> Does anybody have a hint what I could do? Would be very good to use XML, 
>>> maybe there is a workaround.
>>> 
>>> Thanks, all best
>>> Jess
>> 
>> Hello Jess,
>> 
>> I’m on Mac OS 10.14.4 with LyX 2.3.2. I’m unable to export to DocBook too. 
>> But - at least with the Tutorial - I don’t get a crash on Cancel.
>> 
>> Can you send me the stack trace please and tell me if it happens with every 
>> LyX document or with some of your documents only?
>> 
>> Best regards,
>> Stephan
>  22.04.20.png>

Re: Exporting ePub / XML: always SIGSEV

[Stephan Witt]

Am 25.04.2019 um 18:56 schrieb jezZiFeR :
> 
> Hello,
> 
> I try to export ePubs for a while now and it never worked in different 
> configurations. LyX was always freezing. In the moment I use OS 10.14.3, 
> Intel and LyX 2.3.2 with TeXLive 2018.
> 
> When I do the following:
> + file – export as – DocBook (XML) and then try to save I get the follwing 
> error:
> »Keine Informationen vorhanden, um das Format DocBook (XML) zu exportieren.«
> In English this means something like »There is no information to export the 
> format DocBook (XML).
> + Now I click »cancel« and get a SIGSEV-signal, like every time.
> 
> Does anybody have a hint what I could do? Would be very good to use XML, 
> maybe there is a workaround.
> 
> Thanks, all best
> Jess

Hello Jess,

I’m on Mac OS 10.14.4 with LyX 2.3.2. I’m unable to export to DocBook too. But 
- at least with the Tutorial - I don’t get a crash on Cancel.

Can you send me the stack trace please and tell me if it happens with every LyX 
document or with some of your documents only?

Best regards,
Stephan

Re: Exporting ePub / XML: always SIGSEV

[Anders Ekberg]

On 25 Apr 2019, at 21:36, jezZiFeR  wrote:
> 
> Hello Anders,
> 
> thanks a lot! This sounds good, but I do normally only use LyX and run into 
> new problems. First I tried several possibilities to export to TeX is with 
> also with »weitere Formate und Optionen« (more formats and options) – here it 
> worked. In all other cases (file – export – LaTeX (plain) or export – export 
> as – LaTeX (normal) or export – export as – LaTeX (XeTeX)) I have got a 
> SIGSEV-signal again. 
> 
> Well, then I opened the TeX-file in TeXShop (I dont have TeX Studio). In the 
> prefs there is no build, and I did not know ho to continue from here.
>  Then I just tried:
> 
> export – XML text
> 
> This produced an XML-file. I do not know if the file would work, because I do 
> not know how to continue from here. Did Could I also use calibre for 
> converting from XML to ePub?
> 
> Thanks, best
> Jess

Looks like you have a problem with your installation. I would try to reinstall 
(and if problems remain to a Tools > Reconfigure and open Terminal and run sudo 
texhash).
Anyway, to your question: Calibre is free to download, so you can download it 
and then add the xml-file to Calibre (Add book…) and then convert to EPUB 
(Convert books…). If it works or not should depend on the status the XML-file, 
but that is outside my knowledge (I was just happy when the recipe I posted 
worked ;-)

All the best!
Anders

Re: Exporting ePub / XML: always SIGSEV

[jezZiFeR]

Hello Anders,

thanks a lot! This sounds good, but I do normally only use LyX and run into new 
problems. First I tried several possibilities to export to TeX is with also 
with »weitere Formate und Optionen« (more formats and options) – here it 
worked. In all other cases (file – export – LaTeX (plain) or export – export as 
– LaTeX (normal) or export – export as – LaTeX (XeTeX)) I have got a 
SIGSEV-signal again.

Well, then I opened the TeX-file in TeXShop (I dont have TeX Studio). In the 
prefs there is no build, and I did not know ho to continue from here.
 Then I just tried:

export – XML text

This produced an XML-file. I do not know if the file would work, because I do 
not know how to continue from here. Did Could I also use calibre for converting 
from XML to ePub?

Thanks, best
Jess




Am 25. Apr. 2019, 20:55 +0200 schrieb Anders Ekberg :
>
> 25 apr. 2019 kl. 18:56 skrev jezZiFeR :
>
> > Hello,
> >
> > I try to export ePubs for a while now and it never worked in different 
> > configurations. LyX was always freezing. In the moment I use OS 10.14.3, 
> > Intel and LyX 2.3.2 with TeXLive 2018.
> >
> > When I do the following:
> > + file – export as – DocBook (XML) and then try to save I get the follwing 
> > error:
> > »Keine Informationen vorhanden, um das Format DocBook (XML) zu exportieren.«
> > In English this means something like »There is no information to export the 
> > format DocBook (XML).
> > + Now I click »cancel« and get a SIGSEV-signal, like every time.
> >
> > Does anybody have a hint what I could do? Would be very good to use XML, 
> > maybe there is a workaround.
> >
> > Thanks, all best
> > Jess
>
> Also on Mac. I never really got the XML to work. So unfortunately no 
> workaround. Instead I use
>
> \usepackage{pxfonts} in preamble
> Pictures as eps
> No non-standard letters in picture names etc
> Export to plain tex
> Open in TeX-studio
> Create user-command htlatex %.tex (in Preferences > Build)
> Add html-file to Calibre (Add book...)
> Convert to EPUB (Convert books...)
>
> Has worked very well also for complex documents.
>
> /Anders

Re: Exporting ePub / XML: always SIGSEV

[Anders Ekberg]

25 apr. 2019 kl. 18:56 skrev jezZiFeR :
> 
> Hello,
> 
> I try to export ePubs for a while now and it never worked in different 
> configurations. LyX was always freezing. In the moment I use OS 10.14.3, 
> Intel and LyX 2.3.2 with TeXLive 2018.
> 
> When I do the following:
> + file – export as – DocBook (XML) and then try to save I get the follwing 
> error:
> »Keine Informationen vorhanden, um das Format DocBook (XML) zu exportieren.«
> In English this means something like »There is no information to export the 
> format DocBook (XML).
> + Now I click »cancel« and get a SIGSEV-signal, like every time.
> 
> Does anybody have a hint what I could do? Would be very good to use XML, 
> maybe there is a workaround.
> 
> Thanks, all best
> Jess

Also on Mac. I never really got the XML to work. So unfortunately no 
workaround. Instead I use

\usepackage{pxfonts} in preamble
Pictures as eps
No non-standard letters in picture names etc
Export to plain tex
Open in TeX-studio
Create user-command htlatex %.tex (in Preferences > Build)
Add html-file to Calibre (Add book...)
Convert to EPUB (Convert books...)

Has worked very well also for complex documents.

/Anders

Exporting ePub / XML: always SIGSEV

[jezZiFeR]

Hello,

I try to export ePubs for a while now and it never worked in different 
configurations. LyX was always freezing. In the moment I use OS 10.14.3, Intel 
and LyX 2.3.2 with TeXLive 2018.

When I do the following:
+ file – export as – DocBook (XML) and then try to save I get the follwing 
error:
»Keine Informationen vorhanden, um das Format DocBook (XML) zu exportieren.«
In English this means something like »There is no information to export the 
format DocBook (XML).
+ Now I click »cancel« and get a SIGSEV-signal, like every time.

Does anybody have a hint what I could do? Would be very good to use XML, maybe 
there is a workaround.

Thanks, all best
Jess

Re: Trouble exporting multi-part documents

[Dr Eberhard Lisse]

Neither do I.

But I see that in your suggestion.

On 2019-04-13 18:45 , Daniel wrote:
> On 13/04/2019 16:47, Dr Eberhard Lisse wrote:
>> On 2019-04-13 16:34 , Daniel wrote:
[...]>>> I don't understand what you mean. My suggestion means you don't
need to
>>> more than one LyX master file.
>>>
>>> Daniel
>>>
>> My suggestion is that you do, but minimal ones, and have once "master"
>> include file which all import.
>>
>> Otherwise if you make a change to one file you have to pay attention
>> making the change in all files.
>>
>> el
> 
> I don't see anything in the original question that would lead to the
> problem you mention.
> 
> Daniel
> 
> 

Re: Trouble exporting multi-part documents

[Daniel]

On 13/04/2019 16:47, Dr Eberhard Lisse wrote:

On 2019-04-13 16:34 , Daniel wrote:

On 13/04/2019 15:01, Dr Eberhard Lisse wrote:

On 2019-04-12 16:43 , Daniel wrote:

A similar way, but without the need of extra master documents, to
achieve this is to have all parts in child documents, including one with
the Title and TOC, etc. Then you can deactivate child documents via the
Document > Settings of the master as seems fitting.

Daniel

If make the changes in each LyX "master" file you run in to the

problem

of having to keep track of the changes.

Therefor it's better having "master" LyX files and an include.tex for
all common changes.

el



I don't understand what you mean. My suggestion means you don't need to
more than one LyX master file.

Daniel


My suggestion is that you do, but minimal ones, and have once "master"
include file which all import.

Otherwise if you make a change to one file you have to pay attention
making the change in all files.

el


I don't see anything in the original question that would lead to the 
problem you mention.


Daniel

Re: Trouble exporting multi-part documents

[Dr Eberhard Lisse]

My suggestion is that you do, but minimal ones, and have once "master"
include file which all import.

Otherwise if you make a change to one file you have to pay attention
making the change in all files.

el

On 2019-04-13 16:34 , Daniel wrote:
> On 13/04/2019 15:01, Dr Eberhard Lisse wrote:
>> On 2019-04-12 16:43 , Daniel wrote:
>>> A similar way, but without the need of extra master documents, to
>>> achieve this is to have all parts in child documents, including one with
>>> the Title and TOC, etc. Then you can deactivate child documents via the
>>> Document > Settings of the master as seems fitting.
>>>
>>> Daniel
>>> > If make the changes in each LyX "master" file you run in to the
>>> problem
>> of having to keep track of the changes.
>>
>> Therefor it's better having "master" LyX files and an include.tex for
>> all common changes.
>>
>> el
>>
> 
> I don't understand what you mean. My suggestion means you don't need to
> more than one LyX master file.
> 
> Daniel
> 
> 

Re: Trouble exporting multi-part documents

[Daniel]

On 13/04/2019 15:01, Dr Eberhard Lisse wrote:

On 2019-04-12 16:43 , Daniel wrote:

A similar way, but without the need of extra master documents, to
achieve this is to have all parts in child documents, including one with
the Title and TOC, etc. Then you can deactivate child documents via the
Document > Settings of the master as seems fitting.

Daniel
> If make the changes in each LyX "master" file you run in to the problem

of having to keep track of the changes.

Therefor it's better having "master" LyX files and an include.tex for
all common changes.

el



I don't understand what you mean. My suggestion means you don't need to 
more than one LyX master file.


Daniel

Re: Trouble exporting multi-part documents

[Dr Eberhard Lisse]

If make the changes in each LyX "master" file you run in to the problem
of having to keep track of the changes.

Therefor it's better having "master" LyX files and an include.tex for
all common changes.

el

On 2019-04-12 16:43 , Daniel wrote:
> On 11/04/2019 10:08, Helge Hafting wrote:
>>
>> Den 01.04.2019 20:58, skrev Paul Johnson:
>>> I have a dissertation template for students at my University. There
>>> is a main thesis document and then the separate chapters are in
>>> subdirectories. (http://crmda.ku.edu/node/555)
>>>
>>> Currently, in version, "KU-thesis-20190201.zip
>>> ",
>>> it appears to work for everybody to use LyX to edit either the main
>>> document or the individual chapters.
>>>
>>> However, I have students who want to use the dissertation template as
>>> raw LaTexX files, rather than within LyX.  Here I run into a bad
>>> problem.
>>>
>> [...]
>>
>> The problem happens when some file is both used as a child document
>> and as a freestanding document, and you wish to work on the TeX files
>> instead of in LyX.
>>
>>
>> Here is a solution:
>>
>> Use your dissertation & chapter files as-is, I guess you have good
>> reasons for dividing up the document like that. (And it is something
>> both LyX and LaTeX does well too.)
>>
>> But never use a chapter file alone. Instead, create a dummy master
>> document for each chapter file. It should contain no text, but the
>> same settings & preamble as the real master document. And it should
>> include that single chapter file. This way, the chapter file is a
>> child document to the dissertation, but also a child document to the
>> "chapter master document".
>>
>> No change for those who work on the dissertation as a whole - they
>> need the dissertation master file and the chapter files. They won't
>> need the "chapter master" files.
>>
>> Those who wish to work on a single chapter, can then open the chapter
>> master file and do an export from there. They should get two LaTeX
>> files; the master and the chapter file. The  chapter latex file won't
>> work alone, but they will run pdflatex against the chapter master
>> which will include the chapter tex file they work on.  If need be,
>> such a chapter tex file can be moved back and forth between those who
>> work on a complete dissertation and those who do single-chapter work.
>> Because it is now an included file in either case - included from a
>> dissertation master or from a chapter master.
>>
>>
>> This works fine - unless users find it too complicated having two files.
>>
>> Helge Hafting
>>
>>
> 
> A similar way, but without the need of extra master documents, to
> achieve this is to have all parts in child documents, including one with
> the Title and TOC, etc. Then you can deactivate child documents via the
> Document > Settings of the master as seems fitting.
> 
> Daniel
> 
> 

Re: Trouble exporting multi-part documents

[Daniel]

On 11/04/2019 10:08, Helge Hafting wrote:


Den 01.04.2019 20:58, skrev Paul Johnson:
I have a dissertation template for students at my University. There is 
a main thesis document and then the separate chapters are in 
subdirectories. (http://crmda.ku.edu/node/555)


Currently, in version, "KU-thesis-20190201.zip 
", it 
appears to work for everybody to use LyX to edit either the main 
document or the individual chapters.


However, I have students who want to use the dissertation template as 
raw LaTexX files, rather than within LyX.  Here I run into a bad problem.



[...]

The problem happens when some file is both used as a child document and 
as a freestanding document, and you wish to work on the TeX files 
instead of in LyX.



Here is a solution:

Use your dissertation & chapter files as-is, I guess you have good 
reasons for dividing up the document like that. (And it is something 
both LyX and LaTeX does well too.)


But never use a chapter file alone. Instead, create a dummy master 
document for each chapter file. It should contain no text, but the same 
settings & preamble as the real master document. And it should include 
that single chapter file. This way, the chapter file is a child document 
to the dissertation, but also a child document to the "chapter master 
document".


No change for those who work on the dissertation as a whole - they need 
the dissertation master file and the chapter files. They won't need the 
"chapter master" files.


Those who wish to work on a single chapter, can then open the chapter 
master file and do an export from there. They should get two LaTeX 
files; the master and the chapter file. The  chapter latex file won't 
work alone, but they will run pdflatex against the chapter master which 
will include the chapter tex file they work on.  If need be, such a 
chapter tex file can be moved back and forth between those who work on a 
complete dissertation and those who do single-chapter work. Because it 
is now an included file in either case - included from a dissertation 
master or from a chapter master.



This works fine - unless users find it too complicated having two files.

Helge Hafting




A similar way, but without the need of extra master documents, to 
achieve this is to have all parts in child documents, including one with 
the Title and TOC, etc. Then you can deactivate child documents via the 
Document > Settings of the master as seems fitting.


Daniel

Re: Trouble exporting multi-part documents

[Helge Hafting]

Den 01.04.2019 20:58, skrev Paul Johnson:
I have a dissertation template for students at my University. There is 
a main thesis document and then the separate chapters are in 
subdirectories. (http://crmda.ku.edu/node/555)


Currently, in version, "KU-thesis-20190201.zip 
", 
it appears to work for everybody to use LyX to edit either the main 
document or the individual chapters.


However, I have students who want to use the dissertation template as 
raw LaTexX files, rather than within LyX.  Here I run into a bad problem.



[...]

The problem happens when some file is both used as a child document and 
as a freestanding document, and you wish to work on the TeX files 
instead of in LyX.



Here is a solution:

Use your dissertation & chapter files as-is, I guess you have good 
reasons for dividing up the document like that. (And it is something 
both LyX and LaTeX does well too.)


But never use a chapter file alone. Instead, create a dummy master 
document for each chapter file. It should contain no text, but the same 
settings & preamble as the real master document. And it should include 
that single chapter file. This way, the chapter file is a child document 
to the dissertation, but also a child document to the "chapter master 
document".


No change for those who work on the dissertation as a whole - they need 
the dissertation master file and the chapter files. They won't need the 
"chapter master" files.


Those who wish to work on a single chapter, can then open the chapter 
master file and do an export from there. They should get two LaTeX 
files; the master and the chapter file. The  chapter latex file won't 
work alone, but they will run pdflatex against the chapter master which 
will include the chapter tex file they work on.  If need be, such a 
chapter tex file can be moved back and forth between those who work on a 
complete dissertation and those who do single-chapter work. Because it 
is now an included file in either case - included from a dissertation 
master or from a chapter master.



This works fine - unless users find it too complicated having two files.

Helge Hafting

Re: Trouble exporting multi-part documents

[Dr Eberhard Lisse]

Paul,

my understanding is that this is the intended behavior.

Child Documents are just that, Child Documents.

If you want a Child Document to be freestanding it must be surrounded at
the very least by something like


\documentclass{scrartcl}
\begin{document}
%[Child Document goes here]
\end{document}


And of course you must put the contents of the Master Document's
preamble into the Child Document for which I find it helpful to use 
something like

\input{include.tex}

in every Child Document's preamble anyway.

greetings, el


On 01/04/2019 20:58, Paul Johnson wrote:[...]
> However, I have students who want to use the dissertation template as
> raw LaTexX files, rather than within LyX. Here I run into a bad
> problem.
> 
> In my 20190201 version, the people who want to edit the exported LaTeX
> file in raw LaTeX could not compile the document.  There's an error
> about commands in the chapter heading that are only allowed in the
> document preamble.  From that error message, I tracked back to changes
> I made and I understand what is going wrong.
> 
> If I start with the master document and do Export to LaTeX (pdflatex),
> the individual chapter .tex files are created.  They are not
> free-standing documents.  At the top, there was no preamble.  It
> starts in line 1 with the chapter name
[...]

Re: Trouble exporting multi-part documents

[Baris Erkus]

On 01-Apr-19 9:58 PM, Paul Johnson wrote:
I have a dissertation template for students at my University. There is a main 
thesis document and then the separate chapters are in subdirectories. 
(http://crmda.ku.edu/node/555)

Currently, in version, 
"KU-thesis-20190201.zip<http://crmda.dept.ku.edu/guides/43.KU_Thesis/KU-thesis-20190201.zip>",
 it appears to work for everybody to use LyX to edit either the main document 
or the individual chapters.

However, I have students who want to use the dissertation template as raw 
LaTexX files, rather than within LyX.  Here I run into a bad problem.

In my 20190201 version, the people who want to edit the exported LaTeX file in 
raw LaTeX could not compile the document.  There's an error about commands in 
the chapter heading that are only allowed in the document preamble.  From that 
error message, I tracked back to changes I made and I understand what is going 
wrong.

If I start with the master document and do Export to LaTeX (pdflatex), the 
individual chapter .tex files are created.  They are not free-standing 
documents. At the top, there was no preamble. It starts in line 1 with the 
chapter name

\chapter{Elementary Regression}

and also the includegraphics lines have full project paths:

\includegraphics[width=4in]{Chapter2/importfigs/carinced}

Those chapters could not be compiled individually.

I thought I'd get around this problem by using LyX to individually exporting 
each separate chapter as a tex document. I did not realize that caused an 
entirely different export than I got by starting with the master document in 
LyX and doing export LaTeX(pdflatex).

My individually exported chapter files allows the users to edit the individual 
.tex chapters, but when they try to compile the master document, they get 
errors caused by the fact that the individual chapters have their own preambles 
AND the graphics paths are incorrect.

Because I individually exported the .tex files within the Chapter directories, 
then the master document level Export to LaTeX does not replace the existing 
chapters.  Thus I am allowed to zip up the directory and have a master document 
that does not compile because the child documents have preambles in them.

Now that I understand the problem, I wonder if other people have noticed this 
and if they have suggestions for a fix?

I wondered if perhaps we might have the necessary preamble created as a 
separate file in each chapter with some if/then magic in each chapter preamble 
to specify whether or not the master file is in control.

Some fix about the figure paths is necessary as well, I don't have a guess 
about that.

pj

--
Paul E. Johnson   http://pj.freefaculty.org
Director, Center for Research Methods and Data Analysis http://crmda.ku.edu

To write to me directly, please address me at pauljohn at ku.edu<http://ku.edu>.

Hello,

I have recently developed a LyX template of our university graduate thesis from 
the LaTeX template (https://github.com/ituast/itutezLyX). I have checked the 
zip file you gave the link, and I can tell that the structure of the LyX files 
is very similar to what I did. I have encountered similar problems. We can find 
(or develop) solutions or procedures for these problems.

Including a LyX file within a master LyX file is different than including a 
LaTeX file within a master LaTeX file. Because in LyX, you can specify which 
preamble is to be used through the document settings. For LaTeX, there is no 
such thing, as it is a lower-level process of management/compilation, where the 
user has to handle everything.

As you have mentioned, when you export a LyX file to a LaTeX file, LyX always 
puts a preamble, which is smtg that you you may not want if the resulting LaTeX 
file is to be included in a master LaTeX file. The exporter may have an option 
to ignore the preamble. If you want to implement it, you may need to go the 
executable of the exporter and search through the command-line help using a 
help flag (--help, --? or smtg like that). On the other hand, you may still 
want to have a working preamble to be able to compile the individual LaTeX file 
to see the result immediately, before inserting it back to the LyX file. The 
problem with that is thesis class file may have a complicated structure, where 
you should have all major parts together, otherwise, an individual child file 
will not compile. So, in this case, it may be a good idea to compile it as a 
complete thesis, but to include the interested chapter only, which will make 
the compilation faster.

So the problem to me is very specific and isolated. In my case, what I did, I 
developed a unique procedure and tested it for each of this type of student 
request. Then asked the students to follow that unique procedure. In your case, 
we need to define clearly what exactly the students want to do. According to 
you mail, what I understood is this: The students want to be able to work on 
the child LyX files, 

Trouble exporting multi-part documents

[Paul Johnson]

I have a dissertation template for students at my University. There is a
main thesis document and then the separate chapters are in subdirectories. (
http://crmda.ku.edu/node/555)

Currently, in version, "KU-thesis-20190201.zip
<http://crmda.dept.ku.edu/guides/43.KU_Thesis/KU-thesis-20190201.zip>", it
appears to work for everybody to use LyX to edit either the main document
or the individual chapters.

However, I have students who want to use the dissertation template as raw
LaTexX files, rather than within LyX.  Here I run into a bad problem.

In my 20190201 version, the people who want to edit the exported LaTeX file
in raw LaTeX could not compile the document.  There's an error about
commands in the chapter heading that are only allowed in the document
preamble.  From that error message, I tracked back to changes I made and I
understand what is going wrong.

If I start with the master document and do Export to LaTeX (pdflatex), the
individual chapter .tex files are created.  They are not free-standing
documents. At the top, there was no preamble. It starts in line 1 with the
chapter name

\chapter{Elementary Regression}

and also the includegraphics lines have full project paths:

\includegraphics[width=4in]{Chapter2/importfigs/carinced}

Those chapters could not be compiled individually.

I thought I'd get around this problem by using LyX to individually
exporting each separate chapter as a tex document. I did not realize that
caused an entirely different export than I got by starting with the master
document in LyX and doing export LaTeX(pdflatex).

My individually exported chapter files allows the users to edit the
individual .tex chapters, but when they try to compile the master document,
they get errors caused by the fact that the individual chapters have their
own preambles AND the graphics paths are incorrect.

Because I individually exported the .tex files within the Chapter
directories, then the master document level Export to LaTeX does not
replace the existing chapters.  Thus I am allowed to zip up the directory
and have a master document that does not compile because the child
documents have preambles in them.

Now that I understand the problem, I wonder if other people have noticed
this and if they have suggestions for a fix?

I wondered if perhaps we might have the necessary preamble created as a
separate file in each chapter with some if/then magic in each chapter
preamble to specify whether or not the master file is in control.

Some fix about the figure paths is necessary as well, I don't have a guess
about that.

pj

-- 
Paul E. Johnson   http://pj.freefaculty.org
Director, Center for Research Methods and Data Analysis http://crmda.ku.edu

To write to me directly, please address me at pauljohn at ku.edu.

Re: Exporting as PDF (cropped) is not cropping

[list_email]

> On Oct 19, 2018, at 4:09 AM, Daniel  wrote:
> 
> On 19/10/2018 11:54, list_em...@icloud.com wrote:
>> When I open a new document, type an equation, and export as PDF (cropped), I 
>> expect to see a PDF file that has zero extra white space around the 
>> graphical portion of the math. Instead, I see an entire page with the 
>> equation on the first line. I.e., no cropping. What am I doing wrong?
>> LyX 2.3.0
>> Jerry
>> 
> 
> Works for me on with LyX 2.3.1 on Windows 10. It crops from the equation to 
> the page number, so the area is quite large but not the whole page. If I set 
> the page layout page style to empty (via Document > Settings), I get the 
> formula only.
> 
> (For a short time the full page is shown in the PDF viewer but it is almost 
> immediately replaced by its cropped version.)
> 
> Daniel
> 
Daniel nailed it for me. I just needed to set the Page Style to plain so that 
no header-footer decorations and no page numbers appear. If they do appear, the 
cropping is such that headers-footers and the page number are included.

Thanks.

Jerry

Re: Exporting as PDF (cropped) is not cropping

[Paul A. Rubin]

On 10/19/18 5:54 AM, list_em...@icloud.com wrote:

When I open a new document, type an equation, and export as PDF (cropped), I 
expect to see a PDF file that has zero extra white space around the graphical 
portion of the math. Instead, I see an entire page with the equation on the 
first line. I.e., no cropping. What am I doing wrong?

LyX 2.3.0

Jerry
When you say "entire page", do you mean a full page in both dimensions? 
I just tried it, and I got a PDF with a full page (including page 
number) in the vertical dimension but a width just barely enough to hold 
the equation.


If you need cropping in both directions, I would suggest using the 
"standalone" document class. If the equation is inline, that should be 
sufficient. If the equation is display mode (centered on the page), you 
can either (a) convert it to inline and switch to display mode for 
subscripts and superscripts inside the inline equation (then export 
normally, no cropping required), (b) leave the equation in display mode 
and add the "preview" class option, then export normally, or (c) do (b) 
but export cropped. Methods (a) and (c) should produce an equation with 
minimal whitespace on any side; method (b) will (I think) crop 
vertically but not horizontally.


Paul

Re: Exporting as PDF (cropped) is not cropping

[Rich Shepard]

On Fri, 19 Oct 2018, list_em...@icloud.com wrote:


When I open a new document, type an equation, and export as PDF (cropped),
I expect to see a PDF file that has zero extra white space around the
graphical portion of the math. Instead, I see an entire page with the
equation on the first line. I.e., no cropping. What am I doing wrong?


Jerry,

  How about providing a minimal working example?

  Is the equation the only line in the document? Is it an inline or display
equation? What other characteristics are selected on the Insert -> Math
menu?

  The more details the better.

Regards,

Rich

Re: Exporting as PDF (cropped) is not cropping

[Daniel]

On 19/10/2018 11:54, list_em...@icloud.com wrote:

When I open a new document, type an equation, and export as PDF (cropped), I 
expect to see a PDF file that has zero extra white space around the graphical 
portion of the math. Instead, I see an entire page with the equation on the 
first line. I.e., no cropping. What am I doing wrong?

LyX 2.3.0

Jerry



Works for me on with LyX 2.3.1 on Windows 10. It crops from the equation 
to the page number, so the area is quite large but not the whole page. 
If I set the page layout page style to empty (via Document > Settings), 
I get the formula only.


(For a short time the full page is shown in the PDF viewer but it is 
almost immediately replaced by its cropped version.)


Daniel

Exporting as PDF (cropped) is not cropping

[list_email]

When I open a new document, type an equation, and export as PDF (cropped), I 
expect to see a PDF file that has zero extra white space around the graphical 
portion of the math. Instead, I see an entire page with the equation on the 
first line. I.e., no cropping. What am I doing wrong?

LyX 2.3.0

Jerry

Re: Figure layout messed up when exporting to latex and importing again

[Uwe Thuemmel]

Great. Thanks. I'm looking forward to the new release.

Uwe


On 31.08.18 16:08, Jürgen Spitzmüller wrote:

Am Freitag, den 31.08.2018, 14:57 +0200 schrieb Uwe Thuemmel:

I often go back and force between LyX and LaTeX. Unfortunately,
exporting from LyX to LaTeX (pdflatex) and importing again into LyX
messes up the layout of (sub)figures.
More particularly, I'd like subfigures to appear side by side. In the
original LyX file, this looks as follows, and in the PDF figures
appear side by side

(figure_layout_original.lyx)
If I now export to LaTeX (pdflatex), and compile the .tex file
(figure_layout.tex), the figures still appear side by side.
However, if I import back into LyX (import from LaTeX, plain), the
figures appear below one another.

(figure_layout_imported.lyx)
I then have to readjust the layout for all subfigures. Do you have
any suggestions how to avoid this behavior. To replicate the issue,
find a minimum working example with the files mentioned above at:
https://www.dropbox.com/sh/3c6ea1mztonqrgs/AADidw2HLdqv74d6MO2iUmVea?dl=0

It's a bug. The good news is that I seem to have fixed it while fixing
another subfigure import bug (https://www.lyx.org/trac/ticket/10385)

The fix is in LyX 2.3.1 which is just around the corner.

Jürgen


Regards,
Uwe
P.S. I'm running LyX Version 2.3.0 on macOS High Sierra

Re: Figure layout messed up when exporting to latex and importing again

[Jürgen Spitzmüller]

Am Freitag, den 31.08.2018, 14:57 +0200 schrieb Uwe Thuemmel:
> I often go back and force between LyX and LaTeX. Unfortunately,
> exporting from LyX to LaTeX (pdflatex) and importing again into LyX
> messes up the layout of (sub)figures.
> More particularly, I'd like subfigures to appear side by side. In the
> original LyX file, this looks as follows, and in the PDF figures
> appear side by side
> 
> (figure_layout_original.lyx)
> If I now export to LaTeX (pdflatex), and compile the .tex file
> (figure_layout.tex), the figures still appear side by side. 
> However, if I import back into LyX (import from LaTeX, plain), the
> figures appear below one another.
> 
> (figure_layout_imported.lyx)
> I then have to readjust the layout for all subfigures. Do you have
> any suggestions how to avoid this behavior. To replicate the issue,
> find a minimum working example with the files mentioned above at: 
> https://www.dropbox.com/sh/3c6ea1mztonqrgs/AADidw2HLdqv74d6MO2iUmVea?dl=0

It's a bug. The good news is that I seem to have fixed it while fixing
another subfigure import bug (https://www.lyx.org/trac/ticket/10385)

The fix is in LyX 2.3.1 which is just around the corner.

Jürgen

> Regards,
> Uwe
> P.S. I'm running LyX Version 2.3.0 on macOS High Sierra


signature.asc
Description: This is a digitally signed message part

Re: Figure layout messed up when exporting to latex and importing again

[Scott Kostyshak]

Hi Uwe,

Thanks for writing in. Responses below.

On Fri, Aug 31, 2018 at 02:57:04PM +0200, Uwe Thuemmel wrote:
> I often go back and force between LyX and LaTeX. Unfortunately, exporting
> from LyX to LaTeX (pdflatex) and importing again into LyX messes up the
> layout of (sub)figures.

We can discuss the specifics of this below, but I just want to say that
even if this is fixed, you will without doubt run into problems with
doing this back and forth workflow. LyX can export and import LaTeX, but
the import is never going to be perfect. It's such a difficult problem
to convert between all possible permutations of LaTeX (which allows a
lot of different ways of writing things) into LyX, even for a LaTeX file
that LyX exported! I thus recommend that you use mainly LyX or mainly
LaTeX for any given project. Otherwise you might get headaches.

> More particularly, I'd like subfigures to appear side by side. In the
> original LyX file, this looks as follows, and in the PDF figures appear side
> by side
> 
> (figure_layout_original.lyx)
> 
> If I now export to LaTeX (pdflatex), and compile the .tex file
> (figure_layout.tex), the figures still appear side by side.

If you got different output, this would be a LyX bug. Whenever you view
a PDF from LyX, what happens under the hood is that LyX first exports to
LaTeX. So the LaTeX exported from LyX should give the same PDF result
(assuming run with the same engine).

> However, if I import back into LyX (import from LaTeX, plain), the figures
> appear below one another.
> 
> (figure_layout_imported.lyx)
> 
> I then have to readjust the layout for all subfigures. Do you have any
> suggestions how to avoid this behavior. To replicate the issue, find a
> minimum working example with the files mentioned above at:
> https://www.dropbox.com/sh/3c6ea1mztonqrgs/AADidw2HLdqv74d6MO2iUmVea?dl=0

If you don't get a reply here, please make a LyX ticket on

  http://www.lyx.org/trac

When you create the ticket, please select the component "tex2lyx".

Although I discouraged the workflow you have set up above, the good side
to it is you will likely find a lot of potential improvements to the
import, tex2lyx, so if you create trac tickets with minimal examples for
each of them, it's possible they could be fixed. tex2lyx usually
receives fixes for each new LyX release.

Best,

Scott


signature.asc
Description: PGP signature

Figure layout messed up when exporting to latex and importing again

[Uwe Thuemmel]

I often go back and force between LyX and LaTeX. Unfortunately, 
exporting from LyX to LaTeX (pdflatex) and importing again into LyX 
messes up the layout of (sub)figures.


More particularly, I'd like subfigures to appear side by side. In the 
original LyX file, this looks as follows, and in the PDF figures appear 
side by side


(figure_layout_original.lyx)

If I now export to LaTeX (pdflatex), and compile the .tex file 
(figure_layout.tex), the figures still appear side by side.


However, if I import back into LyX (import from LaTeX, plain), the 
figures appear below one another.


(figure_layout_imported.lyx)

I then have to readjust the layout for all subfigures. Do you have any 
suggestions how to avoid this behavior. To replicate the issue, find a 
minimum working example with the files mentioned above at: 
https://www.dropbox.com/sh/3c6ea1mztonqrgs/AADidw2HLdqv74d6MO2iUmVea?dl=0


Regards,
Uwe

P.S. I'm running LyX Version 2.3.0 on macOS High Sierra

Exporting one branch from command line

[Gioele Barabucci]

Is it possible to activate a LyX branch from the command line while 
exporting to a PDF file?


The documentation [1] says that the following command should work, but 
it does not in my tests.


lyx -x "command-sequence branch-activate b1" -E pdf2 outfile.pdf 
infile.lyx


A PDF is exported but the branch "b1" is not activated.

I asked in this TeX.StackExchange question [2, minimal LyX file 
attached] if there are other ways to export a specific branch and the 
only answer I got works only partially.


The user scottkosty suggested

lyx -x "command-sequence branch-activate b1; buffer-export pdf2 
outfile.pdf; undo; lyx-quit" infile.lyx


This solution kind of works, but the `lyx-quit` command at the end 
reports an error because it is executed before the export has finished.


My questions to you:

* How come the command in the documentation does not work?
* Is it possible to tell the `lyx-quit` command to wait until the file 
has been exported? Or is there a `sleep` command in LyX?
* Is there a better way to export a particular branch to a PDF file from 
the command line with no human interaction?


Regards,

[1] https://wiki.lyx.org/FAQ/ImportExport#cl
[1] 
https://tex.stackexchange.com/questions/82/exporting-one-branch-from-command-line/444506#444506


--
Gioele Barabucci 

Re: LyX 2.3.0 on Mac: Exporting to LaTeX (pdflatex) messes up paths to tables and figures

[Dr Eberhard Lisse]

You can tell knitr where to put the figures exactly, it does create a
figure directory, but I do not have this issue either, when using knitr.

Latest version of everything?

el

On 2018-05-16 16:22 , Uwe Thuemmel wrote:
> I realised that the problem appears when I am using the knitr module
> (but not always). I now found a workaround which is to have an empty
> master document which does not contain the knitr module — and which
> then contains the actual document with the knitr module via \input.
> 
> I still need to construct a simple example to make the error
> reproducible.
> 
> @Joel: I think I had also experienced the error in earlier LyX
> versions.
> 
> Best, Uwe
[..

Re: LyX 2.3.0 on Mac: Exporting to LaTeX (pdflatex) messes up paths to tables and figures

[Uwe Thuemmel]

I realised that the problem appears when I am using the knitr module (but not 
always). I now found a workaround which is to have an empty master document 
which does not contain the knitr module — and which then contains the actual 
document with the knitr module via \input.

I still need to construct a simple example to make the error reproducible.

@Joel: I think I had also experienced the error in earlier LyX versions.

Best, Uwe


On 16. May 2018 at 16:12:24, Dr Eberhard Lisse (nos...@lisse.na) wrote:

I don't have any issues with subdirectories.  

Can it be that the names are generic? Try using myfigures and mytables  
or something like that and see if this changes things.  

And, in any case there is always perl -i -p -e 's+\_+/*g' *.lyx or  
similar :-)-O  

el  


On 13/05/2018 22:55, Joel Kulesza wrote:  
> On Sun, May 13, 2018 at 9:37 AM, Uwe Thuemmel <accou...@uwethuemmel.com  
> <mailto:accou...@uwethuemmel.com>> wrote:  
>  
> Dear fellow users,  
>  
> I have figures (as pdf) and tables (as LyX child documents) in  
> subdirectories ./figures and ./tables. When I export from LyX  
> 2.3.0 on Mac to LaTeX (pdflatex), the relative paths to these  
> figures and tables are messed up. In particular, they are  
> replaced by absolute paths where ‘/‘ is replaced by ‘_'. For  
> example, a relative path /figures/figure1.pdf is replaced by  
> something like 1_users_user_project_project1_figures_figure1.pdf.  
> In addition, LyX places pdf files with these names as  
> 1_users_user_project_project1_figures_figure1.pdf in the same  
> directory as the main LyX file (but does not do so for the tables  
> contained in LyX child documents). As a result, the TeX file does  
> not compile correctly and I have to edit it by hand to adjust the  
> paths. I’d much rather see LyX keep the relative paths when  
> exporting to LaTeX. Sometimes this actually works - but I don’t  
> know why. Can anyone help?  
>  
> Thank you,  
> Uwe  
>  
>  
> Uwe,  
>  
> I experienced something that may be similar on Mac. Are you able to  
> test also with LyX 2.2.3? In my case, LyX 2.2.3 would behave how I  
> expect but not LyX 2.3.0.  
>  
> Also, are you able to post a MWE  
> <https://wiki.lyx.org/FAQ/MinimalExample> that has the problem for  
> others to test with?  
>  
> Thanks,  
> Joel  
>  

Re: LyX 2.3.0 on Mac: Exporting to LaTeX (pdflatex) messes up paths to tables and figures

[Dr Eberhard Lisse]

I don't have any issues with subdirectories.

Can it be that the names are generic?  Try using myfigures and mytables
or something like that and see if this changes things.

And, in any case there is always perl -i -p -e 's+\_+/*g' *.lyx or
similar :-)-O

el


On 13/05/2018 22:55, Joel Kulesza wrote:
> On Sun, May 13, 2018 at 9:37 AM, Uwe Thuemmel <accou...@uwethuemmel.com
> <mailto:accou...@uwethuemmel.com>> wrote:
> 
> Dear fellow users,
> 
> I have figures (as pdf) and tables (as LyX child documents) in
> subdirectories ./figures and ./tables.  When I export from LyX
> 2.3.0 on Mac to LaTeX (pdflatex), the relative paths to these
> figures and tables are messed up.  In particular, they are
> replaced by absolute paths where ‘/‘ is replaced by ‘_'.  For
> example, a relative path /figures/figure1.pdf is replaced by
> something like 1_users_user_project_project1_figures_figure1.pdf.
> In addition, LyX places pdf files with these names as
> 1_users_user_project_project1_figures_figure1.pdf in the same
> directory as the main LyX file (but does not do so for the tables
> contained in LyX child documents).  As a result, the TeX file does
> not compile correctly and I have to edit it by hand to adjust the
> paths.  I’d much rather see LyX keep the relative paths when
> exporting to LaTeX. Sometimes this actually works - but I don’t
> know why.  Can anyone help?
> 
> Thank you,
> Uwe
> 
> 
> Uwe,
> 
> I experienced something that may be similar on Mac.  Are you able to
> test also with LyX 2.2.3?  In my case, LyX 2.2.3 would behave how I
> expect but not LyX 2.3.0.
> 
> Also, are you able to post a MWE
> <https://wiki.lyx.org/FAQ/MinimalExample> that has the problem for
> others to test with?
> 
> Thanks,
> Joel
> 

Re: LyX 2.3.0 on Mac: Exporting to LaTeX (pdflatex) messes up paths to tables and figures

[Joel Kulesza]

On Sun, May 13, 2018 at 9:37 AM, Uwe Thuemmel <accou...@uwethuemmel.com>
wrote:

> Dear fellow users,
>
> I have figures (as pdf) and tables (as LyX child documents) in
> subdirectories ./figures and ./tables. When I export from LyX 2.3.0 on Mac
> to LaTeX (pdflatex), the relative paths to these figures and tables are
> messed up. In particular, they are replaced by absolute paths where ‘/‘ is
> replaced by ‘_'. For example, a relative path /figures/figure1.pdf is
> replaced by something like 1_users_user_project_project1_figures_figure1.pdf.
> In addition, LyX places pdf files with these names as
> 1_users_user_project_project1_figures_figure1.pdf in the same directory
> as the main LyX file (but does not do so for the tables contained in LyX
> child documents). As a result, the TeX file does not compile correctly and
> I have to edit it by hand to adjust the paths. I’d much rather see LyX keep
> the relative paths when exporting to LaTeX. Sometimes this actually works -
> but I don’t know why. Can anyone help?
>
> Thank you,
> Uwe
>

Uwe,

I experienced something that may be similar on Mac.  Are you able to test
also with LyX 2.2.3?  In my case, LyX 2.2.3 would behave how I expect but
not LyX 2.3.0.

Also, are you able to post a MWE <https://wiki.lyx.org/FAQ/MinimalExample>
that has the problem for others to test with?

Thanks,
Joel

LyX 2.3.0 on Mac: Exporting to LaTeX (pdflatex) messes up paths to tables and figures

[Uwe Thuemmel]

Dear fellow users,

I have figures (as pdf) and tables (as LyX child documents) in subdirectories 
./figures and ./tables. When I export from LyX 2.3.0 on Mac to LaTeX 
(pdflatex), the relative paths to these figures and tables are messed up. In 
particular, they are replaced by absolute paths where ‘/‘ is replaced by ‘_'. 
For example, a relative path /figures/figure1.pdf is replaced by something like 
1_users_user_project_project1_figures_figure1.pdf. In addition, LyX places pdf 
files with these names as 1_users_user_project_project1_figures_figure1.pdf in 
the same directory as the main LyX file (but does not do so for the tables 
contained in LyX child documents). As a result, the TeX file does not compile 
correctly and I have to edit it by hand to adjust the paths. I’d much rather 
see LyX keep the relative paths when exporting to LaTeX. Sometimes this 
actually works - but I don’t know why. Can anyone help?

Thank you,
Uwe

Re: Exporting lyx file with multiple class options

[Paul A. Rubin]

On 01/21/2017 03:19 PM, David Rosenberg wrote:
I routinely need to make 2 versions of my beamer slides: handout and 
not-handout.  My current plan to do this is to have a program that 
rewrites the lyx file win two different ways (with and without the 
 handout option), and compile each. I'm wondering if there's an easier 
way?


e.g. Is it possible to make a new export option that writes two 
versions of the file?  Not sure how customizable the exports are...


Thanks!

The following should work (I think), though I'm not sure it's easier 
than writing an external script:


1. Copy beamer.layout to a new file (for the sake of argument,
   "beamer-handout.layout") and put it in your local layout directory.
   Edit it to contain the handout option in the ClassOptions section.
2. Reconfigure LyX, so that it knows about the layout.
3. Bind some unused keyboard combination to the command
   'textclass-apply beamer-handout'. You might want to bind a second
   combination to 'textclass-apply beamer' so that you can toggle back
   and forth at will.
4. After creating a presentation (in either format), export it the
   usual way, whack the right key combo to switch to the other format,
   and export again.

Paul

Exporting lyx file with multiple class options

[David Rosenberg]

I routinely need to make 2 versions of my beamer slides: handout and
not-handout.  My current plan to do this is to have a program that rewrites
the lyx file win two different ways (with and without the  handout option),
and compile each.  I'm wondering if there's an easier way?

e.g. Is it possible to make a new export option that writes two versions of
the file?  Not sure how customizable the exports are...

Thanks!

Re: Exporting all files for publisher

[Rich Shepard]

On Thu, 18 Aug 2016, Richard Heck wrote:


Easiest way: Open your user preferences file in a text editor. (Look at
Help> About LyX if you need to find your user directory. Open the
"preferences" file from that directory.) Now add:

   \format "ltxbib" "tex" "LaTeX (With Bib)" "" "" ""
"document,menu=export" ""

to the Format section, and

   \converter "pdflatex" "ltxbib" "python -tt
$$s/scripts/include_bib.py $$i $$o" "needaux"

to the converter section. When you restart LyX, you should have an
export option "LaTeX (with Bib)".


  Wonderful, Richard!

Thanks very much,

Rich

Re: Exporting all files for publisher

[Rich Shepard]

On Thu, 18 Aug 2016, Richard Heck wrote:


You don't have "User directory: ~/.lyx/? Anyway, that is the default on
Linux.


Richard,

  Sure do. Did not see that in the about box and can't recall the last time
I modified anything in there.

Thanks for the pointer,

Rich

Re: Exporting all files for publisher

[Richard Heck]

On 08/18/2016 06:42 PM, Rich Shepard wrote:
> On Thu, 18 Aug 2016, Richard Heck wrote:
>
>> Easiest way: Open your user preferences file in a text editor. (Look at
>> Help> About LyX if you need to find your user directory.
>
> Richard,
>
>   I see nothing in Help > About LyX germane to user preferences, other
> than
> /usr/share/lyx/.

You don't have "User directory: ~/.lyx/? Anyway, that is the default on
Linux.

rh

Re: Exporting all files for publisher

[Rich Shepard]

On Thu, 18 Aug 2016, Richard Heck wrote:


Easiest way: Open your user preferences file in a text editor. (Look at
Help> About LyX if you need to find your user directory.


Richard,

  I see nothing in Help > About LyX germane to user preferences, other than
/usr/share/lyx/.


Open the "preferences" file from that directory.)


  This is where I'm stuck. I am not finding a preferences file here:

/usr/share/lyx/# ls

CREDITSdoc/languages   syntax.default
RELEASE-NOTES  encodings   latexfonts  templates/
autocorrectexamples/   layouts/tex/
bind/  external_templates  layouttranslations  ui/
chkconfig.ltx  fonts/  lyx2lyx/unicodesymbols
commands/  images/ scripts/xfonts/
configure.py*  kbd/symbols

Rich

Re: Exporting all files for publisher

[Richard Heck]

On 08/18/2016 06:07 PM, Rich Shepard wrote:
>   It's been a decade since my book, written using LyX, was sent to
> Springer
> as a collection of .tex, .aux, .bib, and other files. I now have a paper
> accepted by a science journal and when I export the file as plain LaTeX
> there is a .tex file but no .bib file.
>
>   The end of the .tex file has:
>
> \bibliographystyle{humannat}
> \bibliography{3_home_rshepard_documents_jabrefdb}
>
>   How do I save a .bib file containing only the references cited in the
> article so I can send that to the editor?

Easiest way: Open your user preferences file in a text editor. (Look at
Help> About LyX if you need to find your user directory. Open the
"preferences" file from that directory.) Now add:

\format "ltxbib" "tex" "LaTeX (With Bib)" "" "" ""
"document,menu=export" ""

to the Format section, and

\converter "pdflatex" "ltxbib" "python -tt
$$s/scripts/include_bib.py $$i $$o" "needaux"

to the converter section. When you restart LyX, you should have an
export option "LaTeX (with Bib)". This will actually produce a LaTeX
file with the contents of the bib file replacing the two lines you
mentioned. You can just send that.

We do not include this by default with LyX because it does not work with
sectioned bibliographies.

Richard

Exporting all files for publisher

[Rich Shepard]

  It's been a decade since my book, written using LyX, was sent to Springer
as a collection of .tex, .aux, .bib, and other files. I now have a paper
accepted by a science journal and when I export the file as plain LaTeX
there is a .tex file but no .bib file.

  The end of the .tex file has:

\bibliographystyle{humannat}
\bibliography{3_home_rshepard_documents_jabrefdb}

  How do I save a .bib file containing only the references cited in the
article so I can send that to the editor?

TIA,

Rich

Re: Exporting to ODF or MS Office ignores any bibliography styles

[Nikola Ivan Leder]

> Gordon have you had a chance to test LyX 2.2.0 + newest pandoc +
> exporting to ODF? If not, don't do it just for me. I only ask out of
> curiosity whether those results are much worse that copy/pasting the
> html.
> 
> Scott
> 


Interestingly enough...  references don't show up AT ALL in my document 
with pandoc export to ODT...

Re: Exporting to ODF or MS Office ignores any bibliography styles

[gordon cooper]

On 16/06/16 09:03, Nikola Ivan Leder wrote:

gordon cooper  kinect.co.nz> writes:


   We have had reasonable success with Lyx exports to ODF by using
html as an intermediate step, then copy pasting the html into
open document.   Although we have not tested bib styles, and
have had some problems with table frames.  Numbering and
heading styles are preserved.

Gordon.




Yes, I have used this approach on occasion, but it really "show HTML"
gives pretty much the same output as "OpenOffice tex4ht" export...   the
references are always sorted aplhabetically and bib styles ignored.

 Thank you for that comment Nikola.  Our projects are related to
   IT system documentation and have not required to use bib. We do
   use many external references and the html method does this without
   errors.  Have needed to create a new index at the ODT copy stage
   otherwise it tries to link back.  Experience so far has been that what
   ever method is used, there will always be a need for some editing of
   the converted documents.

Re: Exporting to ODF or MS Office ignores any bibliography styles

[Nikola Ivan Leder]

gordon cooper  kinect.co.nz> writes:

> 
>   We have had reasonable success with Lyx exports to ODF by using
> html as an intermediate step, then copy pasting the html into
> open document.   Although we have not tested bib styles, and
> have had some problems with table frames.  Numbering and
> heading styles are preserved.
> 
> Gordon.
> 
> 


Yes, I have used this approach on occasion, but it really "show HTML" 
gives pretty much the same output as "OpenOffice tex4ht" export...   the 
references are always sorted aplhabetically and bib styles ignored.

Re: Exporting to ODF or MS Office ignores any bibliography styles

[Scott Kostyshak]

On Thu, Jun 16, 2016 at 08:43:10AM +1200, gordon cooper wrote:
>  We have had reasonable success with Lyx exports to ODF by using
> html as an intermediate step, then copy pasting the html into
> open document.   Although we have not tested bib styles, and
> have had some problems with table frames.  Numbering and
> heading styles are preserved.
> 
> Gordon.
> 
> 

Gordon have you had a chance to test LyX 2.2.0 + newest pandoc +
exporting to ODF? If not, don't do it just for me. I only ask out of
curiosity whether those results are much worse that copy/pasting the
html.

Scott


signature.asc
Description: PGP signature

Re: Exporting to ODF or MS Office ignores any bibliography styles

[gordon cooper]

 We have had reasonable success with Lyx exports to ODF by using
html as an intermediate step, then copy pasting the html into
open document.   Although we have not tested bib styles, and
have had some problems with table frames.  Numbering and
heading styles are preserved.

Gordon.

Re: Exporting to ODF or MS Office ignores any bibliography styles

[Scott Kostyshak]

On Wed, Jun 15, 2016 at 08:21:38AM +0200, Liviu Andronic wrote:
> On Mon, Jun 13, 2016 at 11:01 PM, Scott Kostyshak <skost...@lyx.org> wrote:
> > On Mon, Jun 13, 2016 at 08:52:33PM +, Nikola Ivan Leder wrote:
> >> I am using Lyx to write my thesis and have run into several problems with
> >> exporting regarding references.
> >>
> >> I need are numerical references in numbered by order of appearance in the
> >> text (not sorted alphabetically) with vancouver style.
> >>
> >> I set this up with natbib and bibtex8 with vancouver style.
> >> The export to PDF or DVI via luatex gets me a perfect document, everything
> >> else gives me alphabetically ordered references, completely ignoring any
> >> changes I make to document/settings/bibliography.
> >>
> >> My bibliography is in .bib made with Jabref.
> >>
> >>
> >> I need export to word or ODF so I can copy/paste certain parts of the text
> >> to various web forms and such...  as well as for correspondence with my
> >> mentor etc..
> >>
> >> Is there any way to "fix" the export function?
> >> If I just select all text in the PDF and paste it in a text processor,
> >> there is a lot of manual work to get it to look proper.
> >>
> >> thank you in advance!
> >>
> >> P.S.  tried this in Linux and Windows, behavior is exactly the same
> >>
> >
> > Hi Nikola,
> >
> > I would consider it a miracle if exporting to ODF/Word worked perfectly.
> > LyX is not actually responsible for the export. LyX just uses other
> > exporters that you have installed on your machine.
> >
> > If you happen to be using the newest LyX version, 2.2.0, LyX now
> > supports exporting to ODF using Pandoc. I have no idea if the export is
> > better/worse than with tex4ht, but Pandoc is under much more active
> > development I believe so there is a chance it is better. So you could
> > try installing LyX 2.2.0 and the newest version of Pandoc.
> >
> > If you are not using LyX 2.2.0, I would warn you to be careful when
> > changing from LyX 2.1.x to 2.2.0 at an important time. Make sure you
> > have time to address unwanted consequences of using a major version
> > upgrade.
> 
> 
> > If you happen to be on Ubuntu, you can easily use 2.2.0
> > alongside 2.1.x so they do not interfere with each other. For more
> >
> Actually that's a 'not yet'. 2.2.0 will be installed on top of 2.1.4.
> I'm still to prepare the separate packages for 2.1.5 (which would
> indeed install alongside 2.2.0), but this won't come until the end of
> the month.

Oops, thanks for correcting me on this.

Scott

> 
> 
> Liviu
> 
> 
> > information, see:
> > https://wiki.lyx.org/LyX/LyXOnUbuntu#toc3
> >
> > Best,
> >
> > Scott
> >
> > p.s. please respond to the list, and not to me personally


signature.asc
Description: PGP signature

Re: Exporting to ODF or MS Office ignores any bibliography styles

[Liviu Andronic]

On Mon, Jun 13, 2016 at 11:01 PM, Scott Kostyshak <skost...@lyx.org> wrote:
> On Mon, Jun 13, 2016 at 08:52:33PM +, Nikola Ivan Leder wrote:
>> I am using Lyx to write my thesis and have run into several problems with
>> exporting regarding references.
>>
>> I need are numerical references in numbered by order of appearance in the
>> text (not sorted alphabetically) with vancouver style.
>>
>> I set this up with natbib and bibtex8 with vancouver style.
>> The export to PDF or DVI via luatex gets me a perfect document, everything
>> else gives me alphabetically ordered references, completely ignoring any
>> changes I make to document/settings/bibliography.
>>
>> My bibliography is in .bib made with Jabref.
>>
>>
>> I need export to word or ODF so I can copy/paste certain parts of the text
>> to various web forms and such...  as well as for correspondence with my
>> mentor etc..
>>
>> Is there any way to "fix" the export function?
>> If I just select all text in the PDF and paste it in a text processor,
>> there is a lot of manual work to get it to look proper.
>>
>> thank you in advance!
>>
>> P.S.  tried this in Linux and Windows, behavior is exactly the same
>>
>
> Hi Nikola,
>
> I would consider it a miracle if exporting to ODF/Word worked perfectly.
> LyX is not actually responsible for the export. LyX just uses other
> exporters that you have installed on your machine.
>
> If you happen to be using the newest LyX version, 2.2.0, LyX now
> supports exporting to ODF using Pandoc. I have no idea if the export is
> better/worse than with tex4ht, but Pandoc is under much more active
> development I believe so there is a chance it is better. So you could
> try installing LyX 2.2.0 and the newest version of Pandoc.
>
> If you are not using LyX 2.2.0, I would warn you to be careful when
> changing from LyX 2.1.x to 2.2.0 at an important time. Make sure you
> have time to address unwanted consequences of using a major version
> upgrade.


> If you happen to be on Ubuntu, you can easily use 2.2.0
> alongside 2.1.x so they do not interfere with each other. For more
>
Actually that's a 'not yet'. 2.2.0 will be installed on top of 2.1.4.
I'm still to prepare the separate packages for 2.1.5 (which would
indeed install alongside 2.2.0), but this won't come until the end of
the month.


Liviu


> information, see:
> https://wiki.lyx.org/LyX/LyXOnUbuntu#toc3
>
> Best,
>
> Scott
>
> p.s. please respond to the list, and not to me personally

Re: Exporting to ODF or MS Office ignores any bibliography styles

[Bruce Muirhead]

  From: Scott Kostyshak <skost...@lyx.org>
 To: Nikola Ivan Leder <nikola.le...@gmail.com> 
Cc: lyx-users@lists.lyx.org
 Sent: Tuesday, 14 June 2016, 7:01
 Subject: Re: Exporting to ODF or MS Office ignores any bibliography styles
   
On Mon, Jun 13, 2016 at 08:52:33PM +, Nikola Ivan Leder wrote:
> I am using Lyx to write my thesis and have run into several problems with 
> exporting regarding references.
> 
> I need are numerical references in numbered by order of appearance in the 
> text (not sorted alphabetically) with vancouver style.
> 
> I set this up with natbib and bibtex8 with vancouver style. 
> The export to PDF or DVI via luatex gets me a perfect document, everything 
> else gives me alphabetically ordered references, completely ignoring any 
> changes I make to document/settings/bibliography.
> 
> My bibliography is in .bib made with Jabref.
> 
> 
> I need export to word or ODF so I can copy/paste certain parts of the text 
> to various web forms and such...  as well as for correspondence with my 
> mentor etc..
> 
> Is there any way to "fix" the export function?  
> If I just select all text in the PDF and paste it in a text processor, 
> there is a lot of manual work to get it to look proper.
> 
> thank you in advance!
> 
> P.S.  tried this in Linux and Windows, behavior is exactly the same
> 

You need to read the  pandoc user guide, which should be installed with pandoc, 
or is easily findable with a search.
LyX is not set up to produce bibliographies and references with pandoc. Rather, 
there are specific ways that the references and bibliography have to be set up, 
which means that you need to find and use the appropriate pandoc options.
I've only just commenced looking at this, so I cannot help with detail, except 
to say
1. tex4ht may not be under the most active development, but it continues to 
produce good output for me with citations and bibliography.

2. It seems the easiest way to use pandoc for citations and references (until 
you work out how to modify the LyX command---under preferences>output--- to get 
what you want) is to save as a LaTeX file and run pandoc on the command line.
Bruce




  

Re: Exporting to ODF or MS Office ignores any bibliography styles

[Scott Kostyshak]

On Mon, Jun 13, 2016 at 08:52:33PM +, Nikola Ivan Leder wrote:
> I am using Lyx to write my thesis and have run into several problems with 
> exporting regarding references.
> 
> I need are numerical references in numbered by order of appearance in the 
> text (not sorted alphabetically) with vancouver style.
> 
> I set this up with natbib and bibtex8 with vancouver style. 
> The export to PDF or DVI via luatex gets me a perfect document, everything 
> else gives me alphabetically ordered references, completely ignoring any 
> changes I make to document/settings/bibliography.
> 
> My bibliography is in .bib made with Jabref.
> 
> 
> I need export to word or ODF so I can copy/paste certain parts of the text 
> to various web forms and such...  as well as for correspondence with my 
> mentor etc..
> 
> Is there any way to "fix" the export function?  
> If I just select all text in the PDF and paste it in a text processor, 
> there is a lot of manual work to get it to look proper.
> 
> thank you in advance!
> 
> P.S.  tried this in Linux and Windows, behavior is exactly the same
> 

Hi Nikola,

I would consider it a miracle if exporting to ODF/Word worked perfectly.
LyX is not actually responsible for the export. LyX just uses other
exporters that you have installed on your machine.

If you happen to be using the newest LyX version, 2.2.0, LyX now
supports exporting to ODF using Pandoc. I have no idea if the export is
better/worse than with tex4ht, but Pandoc is under much more active
development I believe so there is a chance it is better. So you could
try installing LyX 2.2.0 and the newest version of Pandoc.

If you are not using LyX 2.2.0, I would warn you to be careful when
changing from LyX 2.1.x to 2.2.0 at an important time. Make sure you
have time to address unwanted consequences of using a major version
upgrade. If you happen to be on Ubuntu, you can easily use 2.2.0
alongside 2.1.x so they do not interfere with each other. For more
information, see:
https://wiki.lyx.org/LyX/LyXOnUbuntu#toc3

Best,

Scott

p.s. please respond to the list, and not to me personally


signature.asc
Description: PGP signature

Exporting to ODF or MS Office ignores any bibliography styles

[Nikola Ivan Leder]

I am using Lyx to write my thesis and have run into several problems with 
exporting regarding references.

I need are numerical references in numbered by order of appearance in the 
text (not sorted alphabetically) with vancouver style.

I set this up with natbib and bibtex8 with vancouver style. 
The export to PDF or DVI via luatex gets me a perfect document, everything 
else gives me alphabetically ordered references, completely ignoring any 
changes I make to document/settings/bibliography.

My bibliography is in .bib made with Jabref.


I need export to word or ODF so I can copy/paste certain parts of the text 
to various web forms and such...  as well as for correspondence with my 
mentor etc..

Is there any way to "fix" the export function?  
If I just select all text in the PDF and paste it in a text processor, 
there is a lot of manual work to get it to look proper.

thank you in advance!

P.S.  tried this in Linux and Windows, behavior is exactly the same

Exporting to arXiv.org

[Michael Manthey]

I'm having trouble exporting LyX output to arXiv.org, who apparently
want some kind of naked version of TeX as input. The only LYX output
option that gets through arXiv's automated filter is html, which then
entails hand editing to make presentable. Yet I can find only one
mention of this on Google (old and doesn't work any more). Surely some
LyX user must know the magic incantations to make Tex output that
arXiv.org will accept!

-Mike Manthey

Re: Exporting to arXiv.org

[David L. Johnson]

On 11/07/2013 05:59 PM, Michael Manthey wrote:

I'm having trouble exporting LyX output to arXiv.org, who apparently
want some kind of naked version of TeX as input.
I just went through this myself (although my co-authors insisted on 
using TeX directly).  See http://arxiv.org/abs/1311.0289 . But they have 
accepted LyX-generated LaTeX from me in the past. They don't want pdf 
files that have been generated by TeX; they can determine that by 
(usually) the beginning of the pdf file and then dump it back to you.  
This has to do with fonts; some fonts don't display pdf well on all 
possible machines.

  The only LYX output
option that gets through arXiv's automated filter is html, which then
entails hand editing to make presentable.
I would not consider that reasonable.  Try exporting to plain LaTeX.  
That should work.  Submit diagrams as separate files. Submit 
bibliographies generated by bibtex by running latex, then bibtex.  Also, 
make sure all necessary files are found from the same directory.

  Yet I can find only one
mention of this on Google (old and doesn't work any more). Surely some
LyX user must know the magic incantations to make Tex output that
arXiv.org will accept!


The easiest is if you don't have a separate bibtex file, and if you have 
no diagrams.  Then the export to plain LaTeX should be all they need.


If it doesn't work, contact me off-list and I will try to help.

--
 
David L. Johnson

Department of Mathematics
Lehigh University

Re: Exporting to arXiv.org

[PhilipPirrip]

I had no troubles with arXiv in the past, if I could export my file(s) 
to .tex and compile them on my linux PC, the same worked with them.

If you're exporting for pdflatex, make sure you upload figures as pdf.
They accept .bib files, or at least they used to, no need for special 
prep. as in the case of am. phys. soc. journals that was discussed here 
recently.

Exporting to arXiv.org

[Michael Manthey]

I'm having trouble exporting LyX output to arXiv.org, who apparently
want some kind of naked version of TeX as input. The only LYX output
option that gets through arXiv's automated filter is html, which then
entails hand editing to make presentable. Yet I can find only one
mention of this on Google (old and doesn't work any more). Surely some
LyX user must know the magic incantations to make Tex output that
arXiv.org will accept!

-Mike Manthey

Re: Exporting to arXiv.org

[David L. Johnson]

On 11/07/2013 05:59 PM, Michael Manthey wrote:

I'm having trouble exporting LyX output to arXiv.org, who apparently
want some kind of naked version of TeX as input.
I just went through this myself (although my co-authors insisted on 
using TeX directly).  See http://arxiv.org/abs/1311.0289 . But they have 
accepted LyX-generated LaTeX from me in the past. They don't want pdf 
files that have been generated by TeX; they can determine that by 
(usually) the beginning of the pdf file and then dump it back to you.  
This has to do with fonts; some fonts don't display pdf well on all 
possible machines.

  The only LYX output
option that gets through arXiv's automated filter is html, which then
entails hand editing to make presentable.
I would not consider that reasonable.  Try exporting to plain LaTeX.  
That should work.  Submit diagrams as separate files. Submit 
bibliographies generated by bibtex by running latex, then bibtex.  Also, 
make sure all necessary files are found from the same directory.

  Yet I can find only one
mention of this on Google (old and doesn't work any more). Surely some
LyX user must know the magic incantations to make Tex output that
arXiv.org will accept!


The easiest is if you don't have a separate bibtex file, and if you have 
no diagrams.  Then the export to plain LaTeX should be all they need.


If it doesn't work, contact me off-list and I will try to help.

--
 
David L. Johnson

Department of Mathematics
Lehigh University

Re: Exporting to arXiv.org

[PhilipPirrip]

I had no troubles with arXiv in the past, if I could export my file(s) 
to .tex and compile them on my linux PC, the same worked with them.

If you're exporting for pdflatex, make sure you upload figures as pdf.
They accept .bib files, or at least they used to, no need for special 
prep. as in the case of am. phys. soc. journals that was discussed here 
recently.

Exporting to arXiv.org

[Michael Manthey]

I'm having trouble exporting LyX output to arXiv.org, who apparently
want some kind of naked version of TeX as input. The only LYX output
option that gets through arXiv's automated filter is html, which then
entails hand editing to make presentable. Yet I can find only one
mention of this on Google (old and doesn't work any more). Surely some
LyX user must know the magic incantations to make Tex output that
arXiv.org will accept!

-Mike Manthey

Re: Exporting to arXiv.org

[David L. Johnson]

On 11/07/2013 05:59 PM, Michael Manthey wrote:

I'm having trouble exporting LyX output to arXiv.org, who apparently
want some kind of naked version of TeX as input.
I just went through this myself (although my co-authors insisted on 
using TeX directly).  See http://arxiv.org/abs/1311.0289 . But they have 
accepted LyX-generated LaTeX from me in the past. They don't want pdf 
files that have been generated by TeX; they can determine that by 
(usually) the beginning of the pdf file and then dump it back to you.  
This has to do with fonts; some fonts don't display pdf well on all 
possible machines.

  The only LYX output
option that gets through arXiv's automated filter is html, which then
entails hand editing to make presentable.
I would not consider that reasonable.  Try exporting to plain LaTeX.  
That should work.  Submit diagrams as separate files. Submit 
bibliographies generated by bibtex by running latex, then bibtex.  Also, 
make sure all necessary files are found from the same directory.

  Yet I can find only one
mention of this on Google (old and doesn't work any more). Surely some
LyX user must know the magic incantations to make Tex output that
arXiv.org will accept!


The easiest is if you don't have a separate bibtex file, and if you have 
no diagrams.  Then the export to plain LaTeX should be all they need.


If it doesn't work, contact me off-list and I will try to help.

--
 
David L. Johnson

Department of Mathematics
Lehigh University

Re: Exporting to arXiv.org

[PhilipPirrip]

I had no troubles with arXiv in the past, if I could export my file(s) 
to .tex and compile them on my linux PC, the same worked with them.

If you're exporting for pdflatex, make sure you upload figures as pdf.
They accept .bib files, or at least they used to, no need for special 
prep. as in the case of am. phys. soc. journals that was discussed here 
recently.

Re: exporting tex for newbies

[Bob Alvarez]

Here is how exported a tex file for an AIP journal. It was easier than I
thought it would be--thanks Lyx developers!

1. Put Lyx file same directory as the graphics files.Modify the graphics
file addresses in the Lyx file if you, like me, have them in a separate
directory while writing the manuscript.  Make sure the Lyx file works by
previewing the pdf.
2. Do a File|export|pdflatex.
3. I think this automatically converts the graphics files to pdf, which are
needed for the .tex file to work. If not, try running pdflatex from the DOS
command line. It should be in the system path from your Lyx installation.
4. The pdflatex creates several files in the directory including one with a
.bbl extension. Open that one with a text editor like Notepad and select
all of it and copy to the clipboard.
5. Open the .tex file in the text editor, scroll to the end and look for
the two lines starting with bibfiles ... and options ...
6. delete those lines and paste in the contents of the .bbl file in their
place. Save the modified .tex file

That's it. The journal website seems to accept the file.

additional notes:
The journal website converts my .eps graphics files to .pdf so I did not
have to upload them.



On Tue, Sep 17, 2013 at 1:34 PM, Bob Alvarez cobol...@gmail.com wrote:

  On 9/17/13 1:01 PM, Murat Yildizoglu wrote:

 Dear Bob,
 In general, providing the exported latex file (File/Export/Latex menu
 item), the bbl file that contains your bibliography (if you use bibtex),
 and the figures in a format accepted by the journal  is sufficient.



  Thanks for your reply. Some questions:


1. What is a 'bbl' file? Is that the same as my bibtex file? If not,
how do I produce it?
2. There are multiple latex export options e.g. Latex (Luatex), Latex
(xetex), ... Which one do you suggest I use?

 Bob

Re: exporting tex for newbies

[Bob Alvarez]

Here is how exported a tex file for an AIP journal. It was easier than I
thought it would be--thanks Lyx developers!

1. Put Lyx file same directory as the graphics files.Modify the graphics
file addresses in the Lyx file if you, like me, have them in a separate
directory while writing the manuscript.  Make sure the Lyx file works by
previewing the pdf.
2. Do a File|export|pdflatex.
3. I think this automatically converts the graphics files to pdf, which are
needed for the .tex file to work. If not, try running pdflatex from the DOS
command line. It should be in the system path from your Lyx installation.
4. The pdflatex creates several files in the directory including one with a
.bbl extension. Open that one with a text editor like Notepad and select
all of it and copy to the clipboard.
5. Open the .tex file in the text editor, scroll to the end and look for
the two lines starting with bibfiles ... and options ...
6. delete those lines and paste in the contents of the .bbl file in their
place. Save the modified .tex file

That's it. The journal website seems to accept the file.

additional notes:
The journal website converts my .eps graphics files to .pdf so I did not
have to upload them.



On Tue, Sep 17, 2013 at 1:34 PM, Bob Alvarez cobol...@gmail.com wrote:

  On 9/17/13 1:01 PM, Murat Yildizoglu wrote:

 Dear Bob,
 In general, providing the exported latex file (File/Export/Latex menu
 item), the bbl file that contains your bibliography (if you use bibtex),
 and the figures in a format accepted by the journal  is sufficient.



  Thanks for your reply. Some questions:


1. What is a 'bbl' file? Is that the same as my bibtex file? If not,
how do I produce it?
2. There are multiple latex export options e.g. Latex (Luatex), Latex
(xetex), ... Which one do you suggest I use?

 Bob

Re: exporting tex for newbies

[Bob Alvarez]

Here is how exported a tex file for an AIP journal. It was easier than I
thought it would be--thanks Lyx developers!

1. Put Lyx file same directory as the graphics files.Modify the graphics
file addresses in the Lyx file if you, like me, have them in a separate
directory while writing the manuscript.  Make sure the Lyx file works by
previewing the pdf.
2. Do a File|export|pdflatex.
3. I think this automatically converts the graphics files to pdf, which are
needed for the .tex file to work. If not, try running pdflatex from the DOS
command line. It should be in the system path from your Lyx installation.
4. The pdflatex creates several files in the directory including one with a
.bbl extension. Open that one with a text editor like Notepad and select
all of it and copy to the clipboard.
5. Open the .tex file in the text editor, scroll to the end and look for
the two lines starting with "bibfiles ..." and "options ..."
6. delete those lines and paste in the contents of the .bbl file in their
place. Save the modified .tex file

That's it. The journal website seems to accept the file.

additional notes:
The journal website converts my .eps graphics files to .pdf so I did not
have to upload them.



On Tue, Sep 17, 2013 at 1:34 PM, Bob Alvarez  wrote:

>  On 9/17/13 1:01 PM, Murat Yildizoglu wrote:
>
> Dear Bob,
> In general, providing the exported latex file (File/Export/Latex menu
> item), the bbl file that contains your bibliography (if you use bibtex),
> and the figures in a format accepted by the journal  is sufficient.
>
>
>
>  Thanks for your reply. Some questions:
>
>
>1. What is a 'bbl' file? Is that the same as my bibtex file? If not,
>how do I produce it?
>2. There are multiple latex export options e.g. Latex (Luatex), Latex
>(xetex), ... Which one do you suggest I use?
>
> Bob
>

exporting tex for newbies

[Bob Alvarez]

I recently had a paper accepted by an American Institute of Physics 
journal. The paper was reviewed from pdf documents created by Lyx but 
now the AIP emails: Please upload your article file as a Word or Tex 
file. AIP production cannot use a PDF as the article source file. I 
assume they want to reformat the article for the standard of the journal.


I have read several threads on the  User's group and this does not seem 
as simple as doing a  File|export|latex.

Some issues that seem to come up are handling citations, and figures.

Can anyone suggest a step-by-step method for a Tex newbie to create a 
package that I can send them? The package might include the Latex file 
created by one of the export options (please specify which one), my 
bibtex file, plus ???


BTW, my figures are all in eps format and I assume the AIP can use those??

FWIW, I am using Lyx 2.0.6 on a Windows 7 64 bit system.

Bob

Re: exporting tex for newbies

[Murat Yildizoglu]

Dear Bob,
In general, providing the exported latex file (File/Export/Latex menu
item), the bbl file that contains your bibliography (if you use bibtex),
and the figures in a format accepted by the journal  is sufficient.

Le mardi 17 septembre 2013, Bob Alvarez a écrit :

 I recently had a paper accepted by an American Institute of Physics
 journal. The paper was reviewed from pdf documents created by Lyx but now
 the AIP emails: Please upload your article file as a Word or Tex file. AIP
 production cannot use a PDF as the article source file. I assume they want
 to reformat the article for the standard of the journal.

 I have read several threads on the  User's group and this does not seem as
 simple as doing a  File|export|latex.
 Some issues that seem to come up are handling citations, and figures.

 Can anyone suggest a step-by-step method for a Tex newbie to create a
 package that I can send them? The package might include the Latex file
 created by one of the export options (please specify which one), my bibtex
 file, plus ???

 BTW, my figures are all in eps format and I assume the AIP can use those??

 FWIW, I am using Lyx 2.0.6 on a Windows 7 64 bit system.

 Bob



-- 
Prof. Murat Yildizoglu

Université Montesquieu Bordeaux IV
GREThA (UMR CNRS 5113)
Avenue Léon Duguit
33608 Pessac cedex
France

Bureau : E-331

mail: yildi-at-u-bordeaux4.fr

web: yildizoglu.info

Re: exporting tex for newbies

[PhilipPirrip]

export latex (pdflatex)

run pdflatex on the name of your tex file  (once or twice)

run bibtex on the same, but without .tex extension (i think)

bibtex will produce .bbl file

copy the contents of the .bbl file to the end of your .tex (replacing 
bibliography command that's already there)


check if the new .tex works, without having .bib file in the folder

send .tex to the publisher


you might need to convert your .eps to .pdf



I believe that many of these files can be already found in LyX temp 
folder after successful compilation of your .lyx

Re: exporting tex for newbies

[Bob Alvarez]

On 9/17/13 1:01 PM, Murat Yildizoglu wrote:

Dear Bob,
In general, providing the exported latex file (File/Export/Latex menu
item), the bbl file that contains your bibliography (if you use bibtex),
and the figures in a format accepted by the journal  is sufficient.



Thanks for your reply. Some questions:

1. What is a 'bbl' file? Is that the same as my bibtex file? If not,
   how do I produce it?
2. There are multiple latex export options e.g. Latex (Luatex), Latex
   (xetex), ... Which one do you suggest I use?

Bob

Re: exporting tex for newbies

[Steve Litt]

On Tue, 17 Sep 2013 12:23:10 -0700
Bob Alvarez cobol...@gmail.com wrote:

 I recently had a paper accepted by an American Institute of Physics 
 journal. The paper was reviewed from pdf documents created by Lyx but 
 now the AIP emails: Please upload your article file as a Word or Tex 
 file. AIP production cannot use a PDF as the article source file. I 
 assume they want to reformat the article for the standard of the
 journal.

Bob,

If they really mean TeX, as opposed to LaTeX, then I don't think LyX
can do that. LyX produces LaTeX, not TeX.

If LaTeX is acceptable, then I think it's as simple as:

lyx --export latex

I know there's also a way to do it from LyX's menu system, but I don't
have it open right now. I think it's File-Export.

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance

exporting tex for newbies

[Bob Alvarez]

I recently had a paper accepted by an American Institute of Physics 
journal. The paper was reviewed from pdf documents created by Lyx but 
now the AIP emails: Please upload your article file as a Word or Tex 
file. AIP production cannot use a PDF as the article source file. I 
assume they want to reformat the article for the standard of the journal.


I have read several threads on the  User's group and this does not seem 
as simple as doing a  File|export|latex.

Some issues that seem to come up are handling citations, and figures.

Can anyone suggest a step-by-step method for a Tex newbie to create a 
package that I can send them? The package might include the Latex file 
created by one of the export options (please specify which one), my 
bibtex file, plus ???


BTW, my figures are all in eps format and I assume the AIP can use those??

FWIW, I am using Lyx 2.0.6 on a Windows 7 64 bit system.

Bob

Re: exporting tex for newbies

[Murat Yildizoglu]

Dear Bob,
In general, providing the exported latex file (File/Export/Latex menu
item), the bbl file that contains your bibliography (if you use bibtex),
and the figures in a format accepted by the journal  is sufficient.

Le mardi 17 septembre 2013, Bob Alvarez a écrit :

 I recently had a paper accepted by an American Institute of Physics
 journal. The paper was reviewed from pdf documents created by Lyx but now
 the AIP emails: Please upload your article file as a Word or Tex file. AIP
 production cannot use a PDF as the article source file. I assume they want
 to reformat the article for the standard of the journal.

 I have read several threads on the  User's group and this does not seem as
 simple as doing a  File|export|latex.
 Some issues that seem to come up are handling citations, and figures.

 Can anyone suggest a step-by-step method for a Tex newbie to create a
 package that I can send them? The package might include the Latex file
 created by one of the export options (please specify which one), my bibtex
 file, plus ???

 BTW, my figures are all in eps format and I assume the AIP can use those??

 FWIW, I am using Lyx 2.0.6 on a Windows 7 64 bit system.

 Bob



-- 
Prof. Murat Yildizoglu

Université Montesquieu Bordeaux IV
GREThA (UMR CNRS 5113)
Avenue Léon Duguit
33608 Pessac cedex
France

Bureau : E-331

mail: yildi-at-u-bordeaux4.fr

web: yildizoglu.info

Re: exporting tex for newbies

[PhilipPirrip]

export latex (pdflatex)

run pdflatex on the name of your tex file  (once or twice)

run bibtex on the same, but without .tex extension (i think)

bibtex will produce .bbl file

copy the contents of the .bbl file to the end of your .tex (replacing 
bibliography command that's already there)


check if the new .tex works, without having .bib file in the folder

send .tex to the publisher


you might need to convert your .eps to .pdf



I believe that many of these files can be already found in LyX temp 
folder after successful compilation of your .lyx

Re: exporting tex for newbies

[Bob Alvarez]

On 9/17/13 1:01 PM, Murat Yildizoglu wrote:

Dear Bob,
In general, providing the exported latex file (File/Export/Latex menu
item), the bbl file that contains your bibliography (if you use bibtex),
and the figures in a format accepted by the journal  is sufficient.



Thanks for your reply. Some questions:

1. What is a 'bbl' file? Is that the same as my bibtex file? If not,
   how do I produce it?
2. There are multiple latex export options e.g. Latex (Luatex), Latex
   (xetex), ... Which one do you suggest I use?

Bob

Re: exporting tex for newbies

[Steve Litt]

On Tue, 17 Sep 2013 12:23:10 -0700
Bob Alvarez cobol...@gmail.com wrote:

 I recently had a paper accepted by an American Institute of Physics 
 journal. The paper was reviewed from pdf documents created by Lyx but 
 now the AIP emails: Please upload your article file as a Word or Tex 
 file. AIP production cannot use a PDF as the article source file. I 
 assume they want to reformat the article for the standard of the
 journal.

Bob,

If they really mean TeX, as opposed to LaTeX, then I don't think LyX
can do that. LyX produces LaTeX, not TeX.

If LaTeX is acceptable, then I think it's as simple as:

lyx --export latex

I know there's also a way to do it from LyX's menu system, but I don't
have it open right now. I think it's File-Export.

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance

exporting tex for newbies

[Bob Alvarez]

I recently had a paper accepted by an American Institute of Physics 
journal. The paper was reviewed from pdf documents created by Lyx but 
now the AIP emails: "Please upload your article file as a Word or Tex 
file. AIP production cannot use a PDF as the article source file." I 
assume they want to reformat the article for the standard of the journal.


I have read several threads on the  User's group and this does not seem 
as simple as doing a  File|export|latex.

Some issues that seem to come up are handling citations, and figures.

Can anyone suggest a step-by-step method for a Tex newbie to create a 
package that I can send them? The package might include the Latex file 
created by one of the export options (please specify which one), my 
bibtex file, plus ???


BTW, my figures are all in eps format and I assume the AIP can use those??

FWIW, I am using Lyx 2.0.6 on a Windows 7 64 bit system.

Bob