Re: configure.py questions

[Jürgen Spitzmüller]

2015-06-04 16:26 GMT+02:00 Richard Heck rgh...@lyx.org:

  On 06/04/2015 03:38 AM, Jürgen Spitzmüller wrote:

  Then you might give Pandoc a try because they state that they can handle
 biblatex as well.

  Interesting. I'll do.


 The (original?) author of the program is someone I know: a philosopher at
 Berkeley. I'm sure
 he's be responsive to feedback.


Thanks for this offer.

I had a quick look at the pandoc docs, and it occurs to me that biblatex is
only supported if LaTeX is used as the output format. So on the way from
LaTeX to docx, for example, biblatex cannot be used. Rather, one has to use
pandocs own citation styles (which pretty much rules it out for me).

Also see:
http://tex.stackexchange.com/questions/174055/latex-biblatex-bibliography-to-other-formats-via-pandoc

Jürgen



 Richard

Re: configure.py questions

[Richard Heck]

On 06/04/2015 03:38 AM, Jürgen Spitzmüller wrote:
2015-06-04 1:35 GMT+02:00 Uwe Stöhr uwesto...@web.de 
mailto:uwesto...@web.de:


Am 02.06.2015 um 17:22 schrieb Jürgen Spitzmüller:

 I never used it, but it would certainly be a valid addition.
Note that,

even if Pandoc seems to handle BibTeX, htlatex is still
outstanding because
it supports Biblatex and biber (and it does it very well).


Then you might give Pandoc a try because they state that they can
handle biblatex as well.


Interesting. I'll do.


The (original?) author of the program is someone I know: a philosopher 
at Berkeley. I'm sure

he's be responsive to feedback.

Richard

Re: configure.py questions

[Jürgen Spitzmüller]

2015-06-04 1:35 GMT+02:00 Uwe Stöhr uwesto...@web.de:

 Am 02.06.2015 um 17:22 schrieb Jürgen Spitzmüller:

  I never used it, but it would certainly be a valid addition. Note that,

 even if Pandoc seems to handle BibTeX, htlatex is still outstanding
 because
 it supports Biblatex and biber (and it does it very well).


 Then you might give Pandoc a try because they state that they can handle
 biblatex as well.


Interesting. I'll do.

Jürgen



 regards Uwe

Re: configure.py questions

[Jürgen Spitzmüller]

2015-06-04 1:35 GMT+02:00 Uwe Stöhr :

> Am 02.06.2015 um 17:22 schrieb Jürgen Spitzmüller:
>
> > I never used it, but it would certainly be a valid addition. Note that,
>
>> even if Pandoc seems to handle BibTeX, htlatex is still outstanding
>> because
>> it supports Biblatex and biber (and it does it very well).
>>
>
> Then you might give Pandoc a try because they state that they can handle
> biblatex as well.
>

Interesting. I'll do.

Jürgen


>
> regards Uwe
>

Re: configure.py questions

[Richard Heck]

On 06/04/2015 03:38 AM, Jürgen Spitzmüller wrote:
2015-06-04 1:35 GMT+02:00 Uwe Stöhr >:


Am 02.06.2015 um 17:22 schrieb Jürgen Spitzmüller:

> I never used it, but it would certainly be a valid addition.
Note that,

even if Pandoc seems to handle BibTeX, htlatex is still
outstanding because
it supports Biblatex and biber (and it does it very well).


Then you might give Pandoc a try because they state that they can
handle biblatex as well.


Interesting. I'll do.


The (original?) author of the program is someone I know: a philosopher 
at Berkeley. I'm sure

he's be responsive to feedback.

Richard

Re: configure.py questions

[Jürgen Spitzmüller]

2015-06-04 16:26 GMT+02:00 Richard Heck :

>  On 06/04/2015 03:38 AM, Jürgen Spitzmüller wrote:
>
>  Then you might give Pandoc a try because they state that they can handle
> biblatex as well.
>
>  Interesting. I'll do.
>
>
> The (original?) author of the program is someone I know: a philosopher at
> Berkeley. I'm sure
> he's be responsive to feedback.
>

Thanks for this offer.

I had a quick look at the pandoc docs, and it occurs to me that biblatex is
only supported if LaTeX is used as the output format. So on the way from
LaTeX to docx, for example, biblatex cannot be used. Rather, one has to use
pandocs own citation styles (which pretty much rules it out for me).

Also see:
http://tex.stackexchange.com/questions/174055/latex-biblatex-bibliography-to-other-formats-via-pandoc

Jürgen


>
> Richard
>
>

Re: configure.py questions

[Uwe Stöhr]

Am 02.06.2015 um 17:22 schrieb Jürgen Spitzmüller:

 I never used it, but it would certainly be a valid addition. Note that,

even if Pandoc seems to handle BibTeX, htlatex is still outstanding because
it supports Biblatex and biber (and it does it very well).


Then you might give Pandoc a try because they state that they can handle 
biblatex as well.


regards Uwe

Re: configure.py questions

[Uwe Stöhr]

Am 02.06.2015 um 17:22 schrieb Jürgen Spitzmüller:

> I never used it, but it would certainly be a valid addition. Note that,

even if Pandoc seems to handle BibTeX, htlatex is still outstanding because
it supports Biblatex and biber (and it does it very well).


Then you might give Pandoc a try because they state that they can handle 
biblatex as well.


regards Uwe

Re: configure.py questions

[Scott Kostyshak]

On Mon, Jun 1, 2015 at 5:24 PM, Uwe Stöhr uwesto...@web.de wrote:
 While we are at it: during my research I read several times that the program
 Pandoc produces nice results for TeX documents and that it can handle
 BibTeX. So maybe we should add support for Pandoc to configure.py.

 If you agree I open an enhancement request (don't have time to implement
 this at the moment).

We have a ticket:
http://www.lyx.org/trac/ticket/6042

I think we just need to figure out which conversions we want.

Scott

Re: configure.py questions

[Richard Heck]

On 06/02/2015 10:51 AM, Scott Kostyshak wrote:

On Mon, Jun 1, 2015 at 5:24 PM, Uwe Stöhr uwesto...@web.de wrote:

While we are at it: during my research I read several times that the program
Pandoc produces nice results for TeX documents and that it can handle
BibTeX. So maybe we should add support for Pandoc to configure.py.

If you agree I open an enhancement request (don't have time to implement
this at the moment).

We have a ticket:
http://www.lyx.org/trac/ticket/6042

I think we just need to figure out which conversions we want.


Yes, that's right. It'd be easy to include the relevant code.

Richard

Re: configure.py questions

[Jürgen Spitzmüller]

2015-06-01 23:24 GMT+02:00 Uwe Stöhr uwesto...@web.de:

 While we are at it: during my research I read several times that the
 program Pandoc produces nice results for TeX documents and that it can
 handle BibTeX. So maybe we should add support for Pandoc to configure.py.

 If you agree I open an enhancement request (don't have time to implement
 this at the moment).


I never used it, but it would certainly be a valid addition. Note that,
even if Pandoc seems to handle BibTeX, htlatex is still outstanding because
it supports Biblatex and biber (and it does it very well). This is highly
relevant for the Humanities, while it is probably less relevant for other
disciplines (conversely, I do not need maths conversion, so I don't care
personally if and how maths formulae are converted). This demonstrates that
there is obviously no tool that fits all. Variatio delectat.

Jürgen




 regards Uwe

Re: configure.py questions

[Scott Kostyshak]

On Mon, Jun 1, 2015 at 5:24 PM, Uwe Stöhr  wrote:
> While we are at it: during my research I read several times that the program
> "Pandoc" produces nice results for TeX documents and that it can handle
> BibTeX. So maybe we should add support for Pandoc to configure.py.
>
> If you agree I open an enhancement request (don't have time to implement
> this at the moment).

We have a ticket:
http://www.lyx.org/trac/ticket/6042

I think we just need to figure out which conversions we want.

Scott

Re: configure.py questions

[Richard Heck]

On 06/02/2015 10:51 AM, Scott Kostyshak wrote:

On Mon, Jun 1, 2015 at 5:24 PM, Uwe Stöhr  wrote:

While we are at it: during my research I read several times that the program
"Pandoc" produces nice results for TeX documents and that it can handle
BibTeX. So maybe we should add support for Pandoc to configure.py.

If you agree I open an enhancement request (don't have time to implement
this at the moment).

We have a ticket:
http://www.lyx.org/trac/ticket/6042

I think we just need to figure out which conversions we want.


Yes, that's right. It'd be easy to include the relevant code.

Richard

Re: configure.py questions

[Jürgen Spitzmüller]

2015-06-01 23:24 GMT+02:00 Uwe Stöhr :

> While we are at it: during my research I read several times that the
> program "Pandoc" produces nice results for TeX documents and that it can
> handle BibTeX. So maybe we should add support for Pandoc to configure.py.
>
> If you agree I open an enhancement request (don't have time to implement
> this at the moment).
>

I never used it, but it would certainly be a valid addition. Note that,
even if Pandoc seems to handle BibTeX, htlatex is still outstanding because
it supports Biblatex and biber (and it does it very well). This is highly
relevant for the Humanities, while it is probably less relevant for other
disciplines (conversely, I do not need maths conversion, so I don't care
personally if and how maths formulae are converted). This demonstrates that
there is obviously no tool that fits all. Variatio delectat.

Jürgen



>
> regards Uwe
>
>
>

Re: configure.py questions

[Uwe Stöhr]

While we are at it: during my research I read several times that the 
program Pandoc produces nice results for TeX documents and that it can 
handle BibTeX. So maybe we should add support for Pandoc to configure.py.


If you agree I open an enhancement request (don't have time to implement 
this at the moment).


regards Uwe

Re: configure.py questions

[Uwe Stöhr]

While we are at it: during my research I read several times that the 
program "Pandoc" produces nice results for TeX documents and that it can 
handle BibTeX. So maybe we should add support for Pandoc to configure.py.


If you agree I open an enhancement request (don't have time to implement 
this at the moment).


regards Uwe

Re: configure.py questions

[Uwe Stöhr]

Am 31.05.2015 um 09:39 schrieb Jürgen Spitzmüller:


I use tex4ht successfully all the time and _strongly_ rely on it. It is the
only tex to odt converter that can properly handle bib(la)tex. All the
lyx/tex to html converters fail on this.

Please do not remove this converter just because it does not work for _you_.


Please read what I wrote: I did not propose to remove the converter but 
to remove it from being displayed by default in the view and export menu.


If tex4ht it works for you we should keep it there. Attached is the 
patch. Would that be OK with you?


Btw. I am wondering that tex4ht works for you. When I try to convert the 
LyX UserGuide tex4ht consumes the full CPU power and then Windows tells 
me that it exceeds some timer something and must be stopped. Also not a 
single of my real life documents can be converted by tex4ht so in fact 
for me it is totally useless.


regards Uwe
diff --git 
a/C:\\Users\\Usti\\AppData\\Local\\Temp\\TortoiseGit\\con8AA6.tmp\\configure-ae577fe-left.py
 b/D:\\LyXGit\\Master\\lib\\configure.py
index 2fe2f3f..911196e 100644
--- 
a/C:\\Users\\Usti\\AppData\\Local\\Temp\\TortoiseGit\\con8AA6.tmp\\configure-ae577fe-left.py
+++ b/D:\\LyXGit\\Master\\lib\\configure.py
@@ -678,7 +678,8 @@ def checkFormatEntries(dtl_tools):
 rc_entry = [r'\Format noteedit   not Noteedit
%%%%vector'])
 #
 checkViewerEditor('an OpenDocument viewer', ['libreoffice', 'lwriter', 
'lowriter', 'oowriter', 'swriter', 'abiword'],
-rc_entry = [r'''\Format odtodt OpenDocument   %% 
%%document,vector,menu=export   
application/vnd.oasis.opendocument.text
+rc_entry = [r'''\Format odtodt OpenDocument (eLyXer)   
%%%%document,vector,menu=export   
application/vnd.oasis.opendocument.text
+\Format odt2   odtOpenDocument (tex4ht)   %% %%
document,vector,menu=export   application/vnd.oasis.opendocument.text
 \Format sxwsxwOpenOffice.Org (sxw) 
document,vector   application/vnd.sun.xml.writer'''])
 #
 checkViewerEditor('a Rich Text and Word viewer', ['libreoffice', 
'lwriter', 'lowriter', 'oowriter', 'swriter', 'abiword'],
@@ -784,6 +785,12 @@ def checkConverterEntries():
 path, elyxer = checkProg('a LyX - HTML (MS Word) converter',
 ['elyxer.py --nofooter --html --directory $$r $$i $$o', 'elyxer 
--nofooter --html --directory $$r $$i $$o'],
 rc_entry = [ r'\converter lyx  wordhtml   %% ' ])
+path, elyxer = checkProg('a LyX - OpenDocument (eLyXer) converter',
+['elyxer.py --html --nofooter --unicode --directory $$r $$i $$o', 
'elyxer --html --nofooter --unicode --directory $$r $$i $$o'],
+rc_entry = [ r'\converter lyx  odt   %%  ' ])
+path, elyxer = checkProg('a LyX - Word converter',
+['elyxer.py --html --nofooter --unicode --directory $$r $$i $$o', 
'elyxer --html --nofooter --unicode --directory $$r $$i $$o'],
+rc_entry = [ r'\converter lyx  word  %%  ' ])
 if elyxer.find('elyxer') = 0:
   addToRC(r'''\copierhtml   python -tt $$s/scripts/ext_copy.py -e 
html,png,jpg,jpeg,css $$i $$o''')
   addToRC(r'''\copierwordhtml   python -tt 
$$s/scripts/ext_copy.py -e html,png,jpg,jpeg,css $$i $$o''')
@@ -830,10 +837,10 @@ def checkConverterEntries():
 # directly available as application.
 # On SuSE the scripts have a .sh suffix, and on debian they are in 
/usr/share/tex4ht/
 # Both SuSE and debian have oolatex
-checkProg('a LaTeX - Open Document converter', [
+checkProg('a LaTeX - Open Document (tex4ht) converter', [
 'oolatex $$i', 'mk4ht oolatex $$i', 'oolatex.sh $$i', 
'/usr/share/tex4ht/oolatex $$i',
 'htlatex $$i \'xhtml,ooffice\' \'ooffice/! -cmozhtf\' \'-coo\' 
\'-cvalidate\''],
-rc_entry = [ r'\converter latex  odt%%   needaux' ])
+rc_entry = [ r'\converter latex  odt2   %%   needaux' ])
 # On windows it is called latex2rt.exe
 checkProg('a LaTeX - RTF converter', ['latex2rtf -p -S -o $$o $$i', 
'latex2rt -p -S -o $$o $$i'],
 rc_entry = [ r'\converter latex  rtf%%   needaux' ])

Re: configure.py questions

[Jürgen Spitzmüller]

2015-05-31 20:11 GMT+02:00 Uwe Stöhr uwesto...@web.de:

  Well, May is now over and thus my time. So I will be happy to find enough
 time to do the documentation work. I fear I will uncover again many bugs
 while doing this.


I am sure you will.



 Nevertheless, It is time to announce a feature-freeze very soon  to stop
 people like me ;-)


Not my call.

Jürgen



 regards Uwe

Re: configure.py questions

[Uwe Stöhr]

Actually, I am getting rather nervous again since I observe that you try to
push in as much features as possible again at a phase when we want to get
the major release ready. We should now try to stabilize the code base, not
de-stabilize it by adding new stuff.


Well, May is now over and thus my time. So I will be happy to find 
enough time to do the documentation work. I fear I will uncover again 
many bugs while doing this.


Nevertheless, It is time to announce a feature-freeze very soon  to stop 
people like me ;-)


regards Uwe

Re: configure.py questions

[Uwe Stöhr]

Am 31.05.2015 um 19:45 schrieb Jürgen Spitzmüller:

 As long as tex4ht is not hidden from the view and export menus, 
adding a second option is finde with me.


OK. I'll add a new format odt2 which refers to eLyXer.


Please refer to comp.text.tex.


I cannot. Gmane does not support this and my ISP provides no NNTP.

However, searching a bit in the lyx-users list I find several complaints 
that tex4ht does not work.


 I don't have LaTeX installed on the Win OS, and don't plan to.

That is sad because otherwise you could check out things users or i 
report. Take for example the Alt+Gr shortcut issue. One year ago I was 
fighting for this but nobody trusted me. Now you had a look and could 
verify that the problem was real.


regards Uwe

Re: configure.py questions

[Jürgen Spitzmüller]

2015-05-31 18:28 GMT+02:00 Uwe Stöhr uwesto...@web.de:

 Please read what I wrote: I did not propose to remove the converter but to
 remove it from being displayed by default in the view and export menu.


I understood, and this is where I object.



 If tex4ht it works for you we should keep it there. Attached is the patch.
 Would that be OK with you?


No. I think tex4ht should be the default tex to odt converter. It is far
superior to eLyXer.



 Btw. I am wondering that tex4ht works for you. When I try to convert the
 LyX UserGuide tex4ht consumes the full CPU power and then Windows tells me
 that it exceeds some timer something and must be stopped. Also not a single
 of my real life documents can be converted by tex4ht so in fact for me it
 is totally useless.


It works for me and apparently many people in the tex forums, also Windows
users.

So this is an issue with your setup.

Jürgen.



 regards Uwe

Re: configure.py questions

[Jürgen Spitzmüller]

2015-05-31 19:52 GMT+02:00 Uwe Stöhr uwesto...@web.de:

  Please refer to comp.text.tex.


 I cannot. Gmane does not support this and my ISP provides no NNTP.


You can read it via Google groups online.



 However, searching a bit in the lyx-users list I find several complaints
 that tex4ht does not work.

  I don't have LaTeX installed on the Win OS, and don't plan to.

 That is sad because otherwise you could check out things users or i
 report. Take for example the Alt+Gr shortcut issue. One year ago I was
 fighting for this but nobody trusted me. Now you had a look and could
 verify that the problem was real.


No, the problem was that you were trying to push that in at an absolutely
inappropriate stage of the development cycle. It was sensible to wait, and
now we have added the change at the appropriate development stage, before
the beta phase sets in. Meanwhile, I didn't hear that this delay caused any
serious troubles. My position did not change.

Actually, I am getting rather nervous again since I observe that you try to
push in as much features as possible again at a phase when we want to get
the major release ready. We should now try to stabilize the code base, not
de-stabilize it by adding new stuff.

Jürgen



 regards Uwe

Re: configure.py questions

[Uwe Stöhr]

Am 31.05.2015 um 18:43 schrieb Jürgen Spitzmüller:


No. I think tex4ht should be the default tex to odt converter. It is far
superior to eLyXer.


But my patch does not change that. With my patch you will get 2 
OpenDocument converters and can choose which one you like.

I can also make odt2 the one for eLyXer and odt for tex4ht if you like.


Btw. I am wondering that tex4ht works for you. When I try to convert the
LyX UserGuide tex4ht consumes the full CPU power and then Windows tells me
that it exceeds some timer something and must be stopped. Also not a single
of my real life documents can be converted by tex4ht so in fact for me it
is totally useless.


It works for me and apparently many people in the tex forums, also Windows
users.


Can you point me to a Win user who can use tex4ht? tex4hat only works 
for simple files like the Splash.lyx or so on Windows. I have not heard 
of a Win user who could use tex4ht to convert our UserGuide.



So this is an issue with your setup.


I heard that you have a Win laptop. Try it out there please and give me 
feedback.


thanks and regards
Uwe

Re: configure.py questions

[Jürgen Spitzmüller]

2015-05-31 19:11 GMT+02:00 Uwe Stöhr uwesto...@web.de:

 Am 31.05.2015 um 18:43 schrieb Jürgen Spitzmüller:

  No. I think tex4ht should be the default tex to odt converter. It is far
 superior to eLyXer.


 But my patch does not change that. With my patch you will get 2
 OpenDocument converters and can choose which one you like.
 I can also make odt2 the one for eLyXer and odt for tex4ht if you like.


As long as tex4ht is not hidden from the view and export menus, adding a
second option is finde with me.



  Btw. I am wondering that tex4ht works for you. When I try to convert the
 LyX UserGuide tex4ht consumes the full CPU power and then Windows tells
 me
 that it exceeds some timer something and must be stopped. Also not a
 single
 of my real life documents can be converted by tex4ht so in fact for me it
 is totally useless.


 It works for me and apparently many people in the tex forums, also Windows
 users.


 Can you point me to a Win user who can use tex4ht? tex4hat only works for
 simple files like the Splash.lyx or so on Windows. I have not heard of a
 Win user who could use tex4ht to convert our UserGuide.


Please refer to comp.text.tex.



  So this is an issue with your setup.


 I heard that you have a Win laptop. Try it out there please and give me
 feedback.


I don't have LaTeX installed on the Win OS, and don't plan to. I have
shrinked the Win partition to the bare minimum, since I usually boot Linux.
I only use Windows if absolutely necessary (if proprietary software is
required in collaboration).

Jürgen

PS. Just as we spoke, I have used tex4ht to generate an ODT (and from
LibreOffice, a Word doc) for a journal. Worked like a charm.



 thanks and regards
 Uwe

Re: configure.py questions

[Jürgen Spitzmüller]

2015-05-31 3:13 GMT+02:00 Uwe Stöhr:

 Many thanks. That is the solution. Attached is the patch for configure.py
 that does what I want. OK to go in?

  - Can we maybe get rid of tex4ht or does anybody use this and gets
 acceptable results.


 As Gunther said, this is a separate issue.


 Sure. But what do you think? I propose to remove that the tex4ht converter
 appears in the main export menu list but leave the converter definition for
 people who still use tex4ht.


I use tex4ht successfully all the time and _strongly_ rely on it. It is the
only tex to odt converter that can properly handle bib(la)tex. All the
lyx/tex to html converters fail on this.

Please do not remove this converter just because it does not work for _you_.

Jürgen

Re: configure.py questions

[Jürgen Spitzmüller]

2015-05-31 3:13 GMT+02:00 Uwe Stöhr:

> Many thanks. That is the solution. Attached is the patch for configure.py
> that does what I want. OK to go in?
>
>  - Can we maybe get rid of tex4ht or does anybody use this and gets
>>> acceptable results.
>>>
>>
>> As Gunther said, this is a separate issue.
>>
>
> Sure. But what do you think? I propose to remove that the tex4ht converter
> appears in the main export menu list but leave the converter definition for
> people who still use tex4ht.
>

I use tex4ht successfully all the time and _strongly_ rely on it. It is the
only tex to odt converter that can properly handle bib(la)tex. All the
lyx/tex to html converters fail on this.

Please do not remove this converter just because it does not work for _you_.

Jürgen

Re: configure.py questions

[Uwe Stöhr]

Am 31.05.2015 um 09:39 schrieb Jürgen Spitzmüller:


I use tex4ht successfully all the time and _strongly_ rely on it. It is the
only tex to odt converter that can properly handle bib(la)tex. All the
lyx/tex to html converters fail on this.

Please do not remove this converter just because it does not work for _you_.


Please read what I wrote: I did not propose to remove the converter but 
to remove it from being displayed by default in the view and export menu.


If tex4ht it works for you we should keep it there. Attached is the 
patch. Would that be OK with you?


Btw. I am wondering that tex4ht works for you. When I try to convert the 
LyX UserGuide tex4ht consumes the full CPU power and then Windows tells 
me that it exceeds some timer something and must be stopped. Also not a 
single of my real life documents can be converted by tex4ht so in fact 
for me it is totally useless.


regards Uwe
diff --git 
"a/C:\\Users\\Usti\\AppData\\Local\\Temp\\TortoiseGit\\con8AA6.tmp\\configure-ae577fe-left.py"
 "b/D:\\LyXGit\\Master\\lib\\configure.py"
index 2fe2f3f..911196e 100644
--- 
"a/C:\\Users\\Usti\\AppData\\Local\\Temp\\TortoiseGit\\con8AA6.tmp\\configure-ae577fe-left.py"
+++ "b/D:\\LyXGit\\Master\\lib\\configure.py"
@@ -678,7 +678,8 @@ def checkFormatEntries(dtl_tools):
 rc_entry = [r'\Format noteedit   not Noteedit   "" 
"%%""%%""vector"""'])
 #
 checkViewerEditor('an OpenDocument viewer', ['libreoffice', 'lwriter', 
'lowriter', 'oowriter', 'swriter', 'abiword'],
-rc_entry = [r'''\Format odtodt "OpenDocument"  "" "%%" 
"%%""document,vector,menu=export"   
"application/vnd.oasis.opendocument.text"
+rc_entry = [r'''\Format odtodt "OpenDocument (eLyXer)"  "" 
"%%""%%""document,vector,menu=export"   
"application/vnd.oasis.opendocument.text"
+\Format odt2   odt"OpenDocument (tex4ht)"  "" "%%" "%%"
"document,vector,menu=export"   "application/vnd.oasis.opendocument.text"
 \Format sxwsxw"OpenOffice.Org (sxw)"  "" """"  
"document,vector"   "application/vnd.sun.xml.writer"'''])
 #
 checkViewerEditor('a Rich Text and Word viewer', ['libreoffice', 
'lwriter', 'lowriter', 'oowriter', 'swriter', 'abiword'],
@@ -784,6 +785,12 @@ def checkConverterEntries():
 path, elyxer = checkProg('a LyX -> HTML (MS Word) converter',
 ['elyxer.py --nofooter --html --directory $$r $$i $$o', 'elyxer 
--nofooter --html --directory $$r $$i $$o'],
 rc_entry = [ r'\converter lyx  wordhtml   "%%" ""' ])
+path, elyxer = checkProg('a LyX -> OpenDocument (eLyXer) converter',
+['elyxer.py --html --nofooter --unicode --directory $$r $$i $$o', 
'elyxer --html --nofooter --unicode --directory $$r $$i $$o'],
+rc_entry = [ r'\converter lyx  odt   "%%"  ""' ])
+path, elyxer = checkProg('a LyX -> Word converter',
+['elyxer.py --html --nofooter --unicode --directory $$r $$i $$o', 
'elyxer --html --nofooter --unicode --directory $$r $$i $$o'],
+rc_entry = [ r'\converter lyx  word  "%%"  ""' ])
 if elyxer.find('elyxer') >= 0:
   addToRC(r'''\copierhtml   "python -tt $$s/scripts/ext_copy.py -e 
html,png,jpg,jpeg,css $$i $$o"''')
   addToRC(r'''\copierwordhtml   "python -tt 
$$s/scripts/ext_copy.py -e html,png,jpg,jpeg,css $$i $$o"''')
@@ -830,10 +837,10 @@ def checkConverterEntries():
 # directly available as application.
 # On SuSE the scripts have a .sh suffix, and on debian they are in 
/usr/share/tex4ht/
 # Both SuSE and debian have oolatex
-checkProg('a LaTeX -> Open Document converter', [
+checkProg('a LaTeX -> Open Document (tex4ht) converter', [
 'oolatex $$i', 'mk4ht oolatex $$i', 'oolatex.sh $$i', 
'/usr/share/tex4ht/oolatex $$i',
 'htlatex $$i \'xhtml,ooffice\' \'ooffice/! -cmozhtf\' \'-coo\' 
\'-cvalidate\''],
-rc_entry = [ r'\converter latex  odt"%%"   "needaux"' ])
+rc_entry = [ r'\converter latex  odt2   "%%"   "needaux"' ])
 # On windows it is called latex2rt.exe
 checkProg('a LaTeX -> RTF converter', ['latex2rtf -p -S -o $$o $$i', 
'latex2rt -p -S -o $$o $$i'],
 rc_entry = [ r'\converter latex  rtf"%%"   "needaux"' ])

Re: configure.py questions

[Jürgen Spitzmüller]

2015-05-31 18:28 GMT+02:00 Uwe Stöhr :

> Please read what I wrote: I did not propose to remove the converter but to
> remove it from being displayed by default in the view and export menu.
>

I understood, and this is where I object.


>
> If tex4ht it works for you we should keep it there. Attached is the patch.
> Would that be OK with you?
>

No. I think tex4ht should be the default tex to odt converter. It is far
superior to eLyXer.


>
> Btw. I am wondering that tex4ht works for you. When I try to convert the
> LyX UserGuide tex4ht consumes the full CPU power and then Windows tells me
> that it exceeds some timer something and must be stopped. Also not a single
> of my real life documents can be converted by tex4ht so in fact for me it
> is totally useless.
>

It works for me and apparently many people in the tex forums, also Windows
users.

So this is an issue with your setup.

Jürgen.


>
> regards Uwe
>

Re: configure.py questions

[Uwe Stöhr]

Am 31.05.2015 um 18:43 schrieb Jürgen Spitzmüller:


No. I think tex4ht should be the default tex to odt converter. It is far
superior to eLyXer.


But my patch does not change that. With my patch you will get 2 
OpenDocument converters and can choose which one you like.

I can also make odt2 the one for eLyXer and odt for tex4ht if you like.


Btw. I am wondering that tex4ht works for you. When I try to convert the
LyX UserGuide tex4ht consumes the full CPU power and then Windows tells me
that it exceeds some timer something and must be stopped. Also not a single
of my real life documents can be converted by tex4ht so in fact for me it
is totally useless.


It works for me and apparently many people in the tex forums, also Windows
users.


Can you point me to a Win user who can use tex4ht? tex4hat only works 
for simple files like the Splash.lyx or so on Windows. I have not heard 
of a Win user who could use tex4ht to convert our UserGuide.



So this is an issue with your setup.


I heard that you have a Win laptop. Try it out there please and give me 
feedback.


thanks and regards
Uwe

Re: configure.py questions

[Jürgen Spitzmüller]

2015-05-31 19:11 GMT+02:00 Uwe Stöhr :

> Am 31.05.2015 um 18:43 schrieb Jürgen Spitzmüller:
>
>  No. I think tex4ht should be the default tex to odt converter. It is far
>> superior to eLyXer.
>>
>
> But my patch does not change that. With my patch you will get 2
> OpenDocument converters and can choose which one you like.
> I can also make odt2 the one for eLyXer and odt for tex4ht if you like.
>

As long as tex4ht is not hidden from the view and export menus, adding a
second option is finde with me.


>
>  Btw. I am wondering that tex4ht works for you. When I try to convert the
>>> LyX UserGuide tex4ht consumes the full CPU power and then Windows tells
>>> me
>>> that it exceeds some timer something and must be stopped. Also not a
>>> single
>>> of my real life documents can be converted by tex4ht so in fact for me it
>>> is totally useless.
>>>
>>
>> It works for me and apparently many people in the tex forums, also Windows
>> users.
>>
>
> Can you point me to a Win user who can use tex4ht? tex4hat only works for
> simple files like the Splash.lyx or so on Windows. I have not heard of a
> Win user who could use tex4ht to convert our UserGuide.
>

Please refer to comp.text.tex.


>
>  So this is an issue with your setup.
>>
>
> I heard that you have a Win laptop. Try it out there please and give me
> feedback.
>

I don't have LaTeX installed on the Win OS, and don't plan to. I have
shrinked the Win partition to the bare minimum, since I usually boot Linux.
I only use Windows if absolutely necessary (if proprietary software is
required in collaboration).

Jürgen

PS. Just as we spoke, I have used tex4ht to generate an ODT (and from
LibreOffice, a Word doc) for a journal. Worked like a charm.


>
> thanks and regards
> Uwe
>

Re: configure.py questions

[Uwe Stöhr]

Am 31.05.2015 um 19:45 schrieb Jürgen Spitzmüller:

> As long as tex4ht is not hidden from the view and export menus, 
adding a second option is finde with me.


OK. I'll add a new format "odt2" which refers to eLyXer.


Please refer to comp.text.tex.


I cannot. Gmane does not support this and my ISP provides no NNTP.

However, searching a bit in the lyx-users list I find several complaints 
that tex4ht does not work.


> I don't have LaTeX installed on the Win OS, and don't plan to.

That is sad because otherwise you could check out things users or i 
report. Take for example the Alt+Gr shortcut issue. One year ago I was 
fighting for this but nobody trusted me. Now you had a look and could 
verify that the problem was real.


regards Uwe

Re: configure.py questions

[Jürgen Spitzmüller]

2015-05-31 19:52 GMT+02:00 Uwe Stöhr :

>  Please refer to comp.text.tex.
>>
>
> I cannot. Gmane does not support this and my ISP provides no NNTP.
>

You can read it via Google groups online.


>
> However, searching a bit in the lyx-users list I find several complaints
> that tex4ht does not work.
>
> > I don't have LaTeX installed on the Win OS, and don't plan to.
>
> That is sad because otherwise you could check out things users or i
> report. Take for example the Alt+Gr shortcut issue. One year ago I was
> fighting for this but nobody trusted me. Now you had a look and could
> verify that the problem was real.
>

No, the problem was that you were trying to push that in at an absolutely
inappropriate stage of the development cycle. It was sensible to wait, and
now we have added the change at the appropriate development stage, before
the beta phase sets in. Meanwhile, I didn't hear that this delay caused any
serious troubles. My position did not change.

Actually, I am getting rather nervous again since I observe that you try to
push in as much features as possible again at a phase when we want to get
the major release ready. We should now try to stabilize the code base, not
de-stabilize it by adding new stuff.

Jürgen


>
> regards Uwe
>

Re: configure.py questions

[Uwe Stöhr]

Actually, I am getting rather nervous again since I observe that you try to
push in as much features as possible again at a phase when we want to get
the major release ready. We should now try to stabilize the code base, not
de-stabilize it by adding new stuff.


Well, May is now over and thus my time. So I will be happy to find 
enough time to do the documentation work. I fear I will uncover again 
many bugs while doing this.


Nevertheless, It is time to announce a feature-freeze very soon  to stop 
people like me ;-)


regards Uwe

Re: configure.py questions

[Jürgen Spitzmüller]

2015-05-31 20:11 GMT+02:00 Uwe Stöhr :

>  Well, May is now over and thus my time. So I will be happy to find enough
> time to do the documentation work. I fear I will uncover again many bugs
> while doing this.
>

I am sure you will.


>
> Nevertheless, It is time to announce a feature-freeze very soon  to stop
> people like me ;-)
>

Not my call.

Jürgen


>
> regards Uwe
>

Re: configure.py questions

[Uwe Stöhr]

Am 29.05.2015 um 17:20 schrieb Richard Heck:


There was also a lot of work on this last summer, remember?


No. (I was not active last summer.)


We should
try to get that finished. There is also a program Rob Oakes wrote that
uses LibreOffice as a converter.


Where can I find this?


There is no way. What you can do, however, is define a new format, the
same way we have several PDF formats defined, and define converters
relative to it.


Many thanks. That is the solution. Attached is the patch for 
configure.py that does what I want. OK to go in?



- Can we maybe get rid of tex4ht or does anybody use this and gets
acceptable results.


As Gunther said, this is a separate issue.


Sure. But what do you think? I propose to remove that the tex4ht 
converter appears in the main export menu list but leave the converter 
definition for people who still use tex4ht.



For this converter, why not?


I have done this.

thanks and regards
Uwe
diff --git 
a/C:\\Users\\Usti\\AppData\\Local\\Temp\\TortoiseGit\\conBC7A.tmp\\configure-ee5760e-left.py
 b/D:\\LyXGit\\Master\\lib\\configure.py
index a705c8f..f066b9f 100644
--- 
a/C:\\Users\\Usti\\AppData\\Local\\Temp\\TortoiseGit\\conBC7A.tmp\\configure-ee5760e-left.py
+++ b/D:\\LyXGit\\Master\\lib\\configure.py
@@ -678,7 +678,8 @@ def checkFormatEntries(dtl_tools):
 rc_entry = [r'\Format noteedit   not Noteedit
%%%%vector'])
 #
 checkViewerEditor('an OpenDocument viewer', ['libreoffice', 'lwriter', 
'lowriter', 'oowriter', 'swriter', 'abiword'],
-rc_entry = [r'''\Format odtodt OpenDocument   %% 
%%document,vector,menu=export   
application/vnd.oasis.opendocument.text
+rc_entry = [r'''\Format odtodt OpenDocument (eLyXer)   
%%%%document,vector,menu=export   
application/vnd.oasis.opendocument.text
+\Format odt2   odtOpenDocument (tex4ht)   %% %%
document,vector,menu=export   application/vnd.oasis.opendocument.text
 \Format sxwsxwOpenOffice.Org (sxw) 
document,vector   application/vnd.sun.xml.writer'''])
 #
 checkViewerEditor('a Rich Text and Word viewer', ['libreoffice', 
'lwriter', 'lowriter', 'oowriter', 'swriter', 'abiword'],
@@ -784,6 +785,12 @@ def checkConverterEntries():
 path, elyxer = checkProg('a LyX - HTML (MS Word) converter',
 ['elyxer.py --nofooter --html --directory $$r $$i $$o'],
 rc_entry = [ r'\converter lyx  wordhtml   %% ' ])
+path, elyxer = checkProg('a LyX - OpenDocument (eLyXer) converter',
+['elyxer.py --html --nofooter --unicode --directory $$r $$i $$o'],
+rc_entry = [ r'\converter lyx  odt   %%  ' ])
+path, elyxer = checkProg('a LyX - Word converter',
+['elyxer.py --html --nofooter --unicode --directory $$r $$i $$o'],
+rc_entry = [ r'\converter lyx  word  %%  ' ])
 if elyxer.find('elyxer') = 0:
   addToRC(r'''\copierhtml   python -tt $$s/scripts/ext_copy.py -e 
html,png,jpg,jpeg,css $$i $$o''')
   addToRC(r'''\copierwordhtml   python -tt 
$$s/scripts/ext_copy.py -e html,png,jpg,jpeg,css $$i $$o''')
@@ -830,10 +837,10 @@ def checkConverterEntries():
 # directly available as application.
 # On SuSE the scripts have a .sh suffix, and on debian they are in 
/usr/share/tex4ht/
 # Both SuSE and debian have oolatex
-checkProg('a LaTeX - Open Document converter', [
+checkProg('a LaTeX - Open Document (tex4ht) converter', [
 'oolatex $$i', 'mk4ht oolatex $$i', 'oolatex.sh $$i', 
'/usr/share/tex4ht/oolatex $$i',
 'htlatex $$i \'xhtml,ooffice\' \'ooffice/! -cmozhtf\' \'-coo\' 
\'-cvalidate\''],
-rc_entry = [ r'\converter latex  odt%%   needaux' ])
+rc_entry = [ r'\converter latex  odt2   %%   needaux' ])
 # On windows it is called latex2rt.exe
 checkProg('a LaTeX - RTF converter', ['latex2rtf -p -S -o $$o $$i', 
'latex2rt -p -S -o $$o $$i'],
 rc_entry = [ r'\converter latex  rtf%%   needaux' ])

Re: configure.py questions

[Uwe Stöhr]

Am 29.05.2015 um 17:20 schrieb Richard Heck:


There was also a lot of work on this last summer, remember?


No. (I was not active last summer.)


We should
try to get that finished. There is also a program Rob Oakes wrote that
uses LibreOffice as a converter.


Where can I find this?


There is no way. What you can do, however, is define a new format, the
same way we have several PDF formats defined, and define converters
relative to it.


Many thanks. That is the solution. Attached is the patch for 
configure.py that does what I want. OK to go in?



- Can we maybe get rid of tex4ht or does anybody use this and gets
acceptable results.


As Gunther said, this is a separate issue.


Sure. But what do you think? I propose to remove that the tex4ht 
converter appears in the main export menu list but leave the converter 
definition for people who still use tex4ht.



For this converter, why not?


I have done this.

thanks and regards
Uwe
diff --git 
"a/C:\\Users\\Usti\\AppData\\Local\\Temp\\TortoiseGit\\conBC7A.tmp\\configure-ee5760e-left.py"
 "b/D:\\LyXGit\\Master\\lib\\configure.py"
index a705c8f..f066b9f 100644
--- 
"a/C:\\Users\\Usti\\AppData\\Local\\Temp\\TortoiseGit\\conBC7A.tmp\\configure-ee5760e-left.py"
+++ "b/D:\\LyXGit\\Master\\lib\\configure.py"
@@ -678,7 +678,8 @@ def checkFormatEntries(dtl_tools):
 rc_entry = [r'\Format noteedit   not Noteedit   "" 
"%%""%%""vector"""'])
 #
 checkViewerEditor('an OpenDocument viewer', ['libreoffice', 'lwriter', 
'lowriter', 'oowriter', 'swriter', 'abiword'],
-rc_entry = [r'''\Format odtodt "OpenDocument"  "" "%%" 
"%%""document,vector,menu=export"   
"application/vnd.oasis.opendocument.text"
+rc_entry = [r'''\Format odtodt "OpenDocument (eLyXer)"  "" 
"%%""%%""document,vector,menu=export"   
"application/vnd.oasis.opendocument.text"
+\Format odt2   odt"OpenDocument (tex4ht)"  "" "%%" "%%"
"document,vector,menu=export"   "application/vnd.oasis.opendocument.text"
 \Format sxwsxw"OpenOffice.Org (sxw)"  "" """"  
"document,vector"   "application/vnd.sun.xml.writer"'''])
 #
 checkViewerEditor('a Rich Text and Word viewer', ['libreoffice', 
'lwriter', 'lowriter', 'oowriter', 'swriter', 'abiword'],
@@ -784,6 +785,12 @@ def checkConverterEntries():
 path, elyxer = checkProg('a LyX -> HTML (MS Word) converter',
 ['elyxer.py --nofooter --html --directory $$r $$i $$o'],
 rc_entry = [ r'\converter lyx  wordhtml   "%%" ""' ])
+path, elyxer = checkProg('a LyX -> OpenDocument (eLyXer) converter',
+['elyxer.py --html --nofooter --unicode --directory $$r $$i $$o'],
+rc_entry = [ r'\converter lyx  odt   "%%"  ""' ])
+path, elyxer = checkProg('a LyX -> Word converter',
+['elyxer.py --html --nofooter --unicode --directory $$r $$i $$o'],
+rc_entry = [ r'\converter lyx  word  "%%"  ""' ])
 if elyxer.find('elyxer') >= 0:
   addToRC(r'''\copierhtml   "python -tt $$s/scripts/ext_copy.py -e 
html,png,jpg,jpeg,css $$i $$o"''')
   addToRC(r'''\copierwordhtml   "python -tt 
$$s/scripts/ext_copy.py -e html,png,jpg,jpeg,css $$i $$o"''')
@@ -830,10 +837,10 @@ def checkConverterEntries():
 # directly available as application.
 # On SuSE the scripts have a .sh suffix, and on debian they are in 
/usr/share/tex4ht/
 # Both SuSE and debian have oolatex
-checkProg('a LaTeX -> Open Document converter', [
+checkProg('a LaTeX -> Open Document (tex4ht) converter', [
 'oolatex $$i', 'mk4ht oolatex $$i', 'oolatex.sh $$i', 
'/usr/share/tex4ht/oolatex $$i',
 'htlatex $$i \'xhtml,ooffice\' \'ooffice/! -cmozhtf\' \'-coo\' 
\'-cvalidate\''],
-rc_entry = [ r'\converter latex  odt"%%"   "needaux"' ])
+rc_entry = [ r'\converter latex  odt2   "%%"   "needaux"' ])
 # On windows it is called latex2rt.exe
 checkProg('a LaTeX -> RTF converter', ['latex2rtf -p -S -o $$o $$i', 
'latex2rt -p -S -o $$o $$i'],
 rc_entry = [ r'\converter latex  rtf"%%"   "needaux"' ])

Re: configure.py questions

[Guenter Milde]

On 2015-05-29, Uwe Stöhr wrote:
 Hello LyXers,

 since I was forced to send many texts I wrote with LyX in the format of 
 MS word, I spend a lot of time to get this to work. The solution is 
 surprisingly simple:
 - creating a HTML file via eLyXer* and then importing it to Word or 
 LibreOffice-

 This way I can now also use MS word or LibreOffice to view and update 
 the view of my LyX files. This is really great and make LyX much more 
 attractive in the Windows world.

 I only have one problem: In configure.py there is already a LaTeX to 
 OpenDocument converter defined. (This is the tex4ht converter which 
 never worked on Windows and which is dead for many years now.)
 I had to add a LyX  to OpenDocument converter. But in LyX when I view my 
 LyX file as OpenDocument always the tex4ht converter is executed not my one.

 What can I do?
 - How can I tell LyX that my to OpenDocument converter is preferred?

Go to ToolsSettingsFile HandlingConverters and change the default lyx-OO
coverter. (See HelpCustomization for details).

 - Can we maybe get rid of tex4ht or does anybody use this and gets 
 acceptable results.

This is a different topic. 

The different export routes all have their pro and con. I had problems
with the Word/OO export via HTML (both, elyxer and native) especially
with mathematics.


 Besides this, I noticed that we add by default the eLyXer footer to the 
 converted HTML files. eLyXer provides the --nofooter option to suppress 
 this advertisement to its own and there is no license reason that 
 doesn't allow use to suppress the footer. So Am I allowed to add the 
 --nofooter option in configure.py?

I think this is a sensible request.

However, you can also easily change this via the ToolsSettings menu.

Günter

Re: configure.py questions

[Richard Heck]

On 05/28/2015 08:09 PM, Uwe Stöhr wrote:

Hello LyXers,

since I was forced to send many texts I wrote with LyX in the format 
of MS word, I spend a lot of time to get this to work. The solution is 
surprisingly simple:
- creating a HTML file via eLyXer* and then importing it to Word or 
LibreOffice-


This way I can now also use MS word or LibreOffice to view and update 
the view of my LyX files. This is really great and make LyX much more 
attractive in the Windows world.


There was also a lot of work on this last summer, remember? We should 
try to get that finished. There is also a program Rob Oakes wrote that 
uses LibreOffice as a converter.


I only have one problem: In configure.py there is already a LaTeX to 
OpenDocument converter defined. (This is the tex4ht converter which 
never worked on Windows and which is dead for many years now.)
I had to add a LyX  to OpenDocument converter. But in LyX when I view 
my LyX file as OpenDocument always the tex4ht converter is executed 
not my one.


This is because it is a shorter path: one converter instead of two.


What can I do?
- How can I tell LyX that my to OpenDocument converter is preferred?


There is no way. What you can do, however, is define a new format, the 
same way we have several PDF formats defined, and define converters 
relative to it.


- Can we maybe get rid of tex4ht or does anybody use this and gets 
acceptable results.


As Gunther said, this is a separate issue.

Besides this, I noticed that we add by default the eLyXer footer to 
the converted HTML files. eLyXer provides the --nofooter option to 
suppress this advertisement to its own and there is no license 
reason that doesn't allow use to suppress the footer. So Am I allowed 
to add the --nofooter option in configure.py?


For this converter, why not?

Richard

Re: configure.py questions

[Richard Heck]

On 05/28/2015 08:09 PM, Uwe Stöhr wrote:


@Richard: I would like to use our LyXHTML output but there are 
problems with the images. In LyXHTML the images sizes (\columnwidth 
etc.) are not respected and therefore it looks horrible in MS Word and 
Libreoffice. eLyXer is in this respect better as you can see by 
exporting the EmbeddedObjjects manual to HTML.

Could LyXHTML be extended that the image sizes are respected?


Do you mean the images are not scaled? This should be fairly easy to fix.

Richard

Re: configure.py questions

[Guenter Milde]

On 2015-05-29, Uwe Stöhr wrote:
> Hello LyXers,

> since I was forced to send many texts I wrote with LyX in the format of 
> MS word, I spend a lot of time to get this to work. The solution is 
> surprisingly simple:
> - creating a HTML file via eLyXer* and then importing it to Word or 
> LibreOffice-

> This way I can now also use MS word or LibreOffice to view and update 
> the view of my LyX files. This is really great and make LyX much more 
> attractive in the Windows world.

> I only have one problem: In configure.py there is already a LaTeX to 
> OpenDocument converter defined. (This is the tex4ht converter which 
> never worked on Windows and which is dead for many years now.)
> I had to add a LyX  to OpenDocument converter. But in LyX when I view my 
> LyX file as OpenDocument always the tex4ht converter is executed not my one.

> What can I do?
> - How can I tell LyX that my to OpenDocument converter is preferred?

Go to Tools>Settings>File Handling>Converters and change the default lyx->OO
coverter. (See Help>Customization for details).

> - Can we maybe get rid of tex4ht or does anybody use this and gets 
> acceptable results.

This is a different topic. 

The different export routes all have their pro and con. I had problems
with the Word/OO export via HTML (both, elyxer and native) especially
with mathematics.


> Besides this, I noticed that we add by default the eLyXer footer to the 
> converted HTML files. eLyXer provides the --nofooter option to suppress 
> this "advertisement" to its own and there is no license reason that 
> doesn't allow use to suppress the footer. So Am I allowed to add the 
> --nofooter option in configure.py?

I think this is a sensible request.

However, you can also easily change this via the Tools>Settings menu.

Günter

Re: configure.py questions

[Richard Heck]

On 05/28/2015 08:09 PM, Uwe Stöhr wrote:


@Richard: I would like to use our LyXHTML output but there are 
problems with the images. In LyXHTML the images sizes (\columnwidth 
etc.) are not respected and therefore it looks horrible in MS Word and 
Libreoffice. eLyXer is in this respect better as you can see by 
exporting the EmbeddedObjjects manual to HTML.

Could LyXHTML be extended that the image sizes are respected?


Do you mean the images are not scaled? This should be fairly easy to fix.

Richard

Re: configure.py questions

[Richard Heck]

On 05/28/2015 08:09 PM, Uwe Stöhr wrote:

Hello LyXers,

since I was forced to send many texts I wrote with LyX in the format 
of MS word, I spend a lot of time to get this to work. The solution is 
surprisingly simple:
- creating a HTML file via eLyXer* and then importing it to Word or 
LibreOffice-


This way I can now also use MS word or LibreOffice to view and update 
the view of my LyX files. This is really great and make LyX much more 
attractive in the Windows world.


There was also a lot of work on this last summer, remember? We should 
try to get that finished. There is also a program Rob Oakes wrote that 
uses LibreOffice as a converter.


I only have one problem: In configure.py there is already a LaTeX to 
OpenDocument converter defined. (This is the tex4ht converter which 
never worked on Windows and which is dead for many years now.)
I had to add a LyX  to OpenDocument converter. But in LyX when I view 
my LyX file as OpenDocument always the tex4ht converter is executed 
not my one.


This is because it is a shorter path: one converter instead of two.


What can I do?
- How can I tell LyX that my to OpenDocument converter is preferred?


There is no way. What you can do, however, is define a new format, the 
same way we have several PDF formats defined, and define converters 
relative to it.


- Can we maybe get rid of tex4ht or does anybody use this and gets 
acceptable results.


As Gunther said, this is a separate issue.

Besides this, I noticed that we add by default the eLyXer footer to 
the converted HTML files. eLyXer provides the --nofooter option to 
suppress this "advertisement" to its own and there is no license 
reason that doesn't allow use to suppress the footer. So Am I allowed 
to add the --nofooter option in configure.py?


For this converter, why not?

Richard