Re: HTML export to different formats

2009-09-06 Thread rgheck
On 09/05/2009 02:08 PM, Alex Fernandez wrote: On Sat, Sep 5, 2009 at 5:20 PM, rgheck wrote: But that is precisely the point: We're not talking about four extra entries. We're not going to do something special for HTML here, as much as you would apparently like us to do so. Actually I

Re: HTML export to different formats

2009-09-05 Thread Jean-Marc Lasgouttes
Le 05/09/2009 20:08, Alex Fernandez a écrit : I just don't think that principles should always trump common sense. Or that all formats are born equal. Indeed. I _never_ use HTML for LyX documents ;) JMarc

Re: HTML export to different formats

2009-09-05 Thread Alex Fernandez
On Sat, Sep 5, 2009 at 5:20 PM, rgheck wrote: > But that is precisely the point: We're not talking about four extra entries. > We're not going to do something special for HTML here, as much as you would > apparently like us to do so. Actually I was not waiting for you to do it; I was volunteering

Re: HTML export to different formats

2009-09-05 Thread Abdelrazak Younes
On 05/09/2009 17:20, Jürgen Spitzmüller wrote: Abdelrazak Younes wrote: I could have bet this will end like that ;-) BTW, I get: GuiApplication.cpp: In member function ‘virtual bool lyx::frontend::GuiApplication::x11EventFilter(XEvent*)’: GuiApplication.cpp:1641: error: ‘class lyx::

Re: HTML export to different formats

2009-09-05 Thread Jürgen Spitzmüller
Abdelrazak Younes wrote: > I could have bet this will end like that ;-) BTW, I get: GuiApplication.cpp: In member function ‘virtual bool lyx::frontend::GuiApplication::x11EventFilter(XEvent*)’: GuiApplication.cpp:1641: error: ‘class

Re: HTML export to different formats

2009-09-05 Thread rgheck
On 09/05/2009 11:10 AM, Alex Fernandez wrote: On Sat, Sep 5, 2009 at 4:51 PM, rgheck wrote: Sure, why not. Maybe in a submenu. Otherwise why do you have them? That would be the worry about clutter. Thanks :) I understand the worry, I just don't share it in this instance. S

Re: HTML export to different formats

2009-09-05 Thread Abdelrazak Younes
On 05/09/2009 17:11, Jürgen Spitzmüller wrote: Jürgen Spitzmüller wrote: Your proposal meanwhile is "do the dirty work I won't bother to do". I did not say I don't bother to implement it. I said I do not have time at the moment to finish what I've started. But I also proposed my

Re: HTML export to different formats

2009-09-05 Thread Jürgen Spitzmüller
Jürgen Spitzmüller wrote: > > Your proposal meanwhile is "do the > > dirty work I won't bother to do". > > I did not say I don't bother to implement it. I said I do not have time at > the moment to finish what I've started. But I also proposed my help. Never mind. I finished the viewer part mys

Re: HTML export to different formats

2009-09-05 Thread Alex Fernandez
On Sat, Sep 5, 2009 at 4:51 PM, rgheck wrote: >> Sure, why not. Maybe in a submenu. Otherwise why do you have them? > > That would be the worry about clutter. Thanks :) I understand the worry, I just don't share it in this instance. Surely you can live with 4 additional entries in the Export menu

Re: HTML export to different formats

2009-09-05 Thread rgheck
On 09/05/2009 10:27 AM, Alex Fernandez wrote: On Sat, Sep 5, 2009 at 3:55 PM, rgheck wrote: LyX currently checks for htlatex, latex2html, and hevea, and it ought also to check for plastex (I keep meaning to do that). I have all of these. Should they all be on the menu, along with elyxer?

Re: HTML export to different formats

2009-09-05 Thread Alex Fernandez
On Sat, Sep 5, 2009 at 3:55 PM, rgheck wrote: > LyX currently checks for htlatex, latex2html, and hevea, and it ought also > to check for plastex (I keep meaning to do that). I have all of these. > Should they all be on the menu, along with elyxer? Sure, why not. Maybe in a submenu. Otherwise why

Re: HTML export to different formats

2009-09-05 Thread rgheck
On 09/05/2009 07:51 AM, Jürgen Spitzmüller wrote: Alex Fernandez wrote: 1. Honestly, I can manage the Python part, but my C++ skills are dubious at best. I am not confident to do this kind of development. I was in the same situation when I started LyX development (minus the Python ski

Re: HTML export to different formats

2009-09-05 Thread rgheck
On 09/05/2009 08:17 AM, Alex Fernandez wrote: Then you have not understood my proposal: I don't want to clutter the menu at all. Tell me, how many HTML converters do you currently have on your machine? If the answer is 0 or 1, you would get exactly the same entries as you already have: 0 or 1. On

Re: HTML export to different formats

2009-09-05 Thread Jürgen Spitzmüller
Alex Fernandez wrote: > Then you have not understood my proposal: I don't want to clutter the > menu at all. Tell me, how many HTML converters do you currently have > on your machine? I think 4 or 5. > If the answer is 0 or 1, you would get exactly the > same entries as you already have: 0 or 1.

Re: HTML export to different formats

2009-09-05 Thread Alex Fernandez
On Sat, Sep 5, 2009 at 1:51 PM, Jürgen Spitzmüller wrote: > You already said that you do not care about, e.g., CJKLyX converters. For > others, these are crucial. Other users do not care about HTML converters, > because they do not use it (me, for instance). Sure, I do not care about them, but I d

Re: HTML export to different formats

2009-09-05 Thread Jürgen Spitzmüller
Alex Fernandez wrote: >1. Honestly, I can manage the Python part, but my C++ skills are >dubious at best. I am not confident to do this kind of development. I was in the same situation when I started LyX development (minus the Python skills). In a sense, I still am. > 2. I don't really think thi

Re: HTML export to different formats

2009-09-05 Thread Alex Fernandez
On Sat, Sep 5, 2009 at 10:57 AM, Jürgen Spitzmüller wrote: > OK, let's try to turn this discussion to a more productive direction. Do you > want to volunteer to help us doing it properly? No, sorry. I really can't because of a couple of reasons: 1. Honestly, I can manage the Python part, but my C

Re: HTML export to different formats

2009-09-05 Thread Jürgen Spitzmüller
Jürgen Spitzmüller wrote: > * in configure.py, check for \viewer_alternatives and > \converter_alternatives next to the \viewer and \converter we already > check for. That is: the first found viewer/converter in the list > (currently the one that is used exclusively) is stored as \viewer or >

Re: HTML export to different formats

2009-09-05 Thread Jürgen Spitzmüller
Alex Fernandez wrote: > But that is not the argument I am making. Instead, it is: this nice > little hack solves a problem (HTML export with different tools) in the > long term, and it does not add to the big issue (clutter in the export > menu) significantly. The "better" solution is an overall im

Re: HTML export to different formats

2009-09-04 Thread rgheck
On 09/04/2009 05:25 PM, Sam Liddicott wrote: Alex Fernandez wrote: ... But that is not the argument I am making. Instead, it is: this nice little hack solves a problem (HTML export with different tools) in the long term, and it does not add to the big issue (clutter in the export menu) signific

Re: HTML export to different formats

2009-09-04 Thread Sam Liddicott
Alex Fernandez wrote: ... But that is not the argument I am making. Instead, it is: this nice little hack solves a problem (HTML export with different tools) in the long term, and it does not add to the big issue (clutter in the export menu) significantly. The "better" solution is an overall imp

Re: HTML export to different formats

2009-09-04 Thread Alex Fernandez
José, thanks for taking the time to explain things. 2009/9/4 José Matos : > Alex please notice that we have heard this kind of argument all over the > years, why don't we add this nice little hack that will solve problem in the > short term instead of taking a more thoughtful approach and fix it i

Re: HTML export to different formats

2009-09-04 Thread José Matos
On Friday 04 September 2009 Alex Fernandez wrote: > > So I would prefer to add different HTML converters first (since people > are requesting that), and then worry about clutter. Sounds more > logical to me. Alex please notice that we have heard this kind of argument all over the years, why don't

Re: HTML export to different formats

2009-09-04 Thread Alex Fernandez
On Fri, Sep 4, 2009 at 3:34 PM, Jean-Marc Lasgouttes wrote: > We can't add one menu entry corresponding to each possible use of each > possible user/contributor. We have been doing this already too much, and > from time to time it is nice to do some cleanup instead.? Yes, it is nice, but IMHO the

Re: HTML export to different formats

2009-09-04 Thread Jürgen Spitzmüller
Alex Fernandez wrote: > I think that requesting such a feature is wrapping the bandage before > you get the cut: nobody has asked for it and it is likely it will > never be a problem anyway. Why not create different HTML converters > and see if it is actually a problem. In that case, just undo the

Re: HTML export to different formats

2009-09-04 Thread Jean-Marc Lasgouttes
Le 04/09/2009 15:32, rgheck a écrit : A really nice option, I think, would be to allow people to select more than one HTML converter to have available. And if they did, then we could perhaps have a submenu that listed them. And even to show in prefs the converters that are disabled because the

Re: HTML export to different formats

2009-09-04 Thread Jean-Marc Lasgouttes
Le 04/09/2009 15:17, Alex Fernandez a écrit : Please search the archieves. I've explained my POV several times in the past, I'm too lazy to rephrase again. Sorry, I can't find a thorough explanation, just terse one-liners like: http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg150669.ht

Re: HTML export to different formats

2009-09-04 Thread rgheck
On 09/04/2009 09:17 AM, Alex Fernandez wrote: On Fri, Sep 4, 2009 at 3:09 PM, Jürgen Spitzmüller wrote: Alex Fernandez wrote: The information is not lost; it is a Reconfigure away. All you lost are the possible customizations. Please search the archieves. I've explained my P

Re: HTML export to different formats

2009-09-04 Thread Alex Fernandez
On Fri, Sep 4, 2009 at 3:09 PM, Jürgen Spitzmüller wrote: > Alex Fernandez wrote: >> The information is not lost; it is a Reconfigure away. All you lost >> are the possible customizations. > > Please search the archieves. I've explained my POV several times in the past, > I'm too lazy to rephrase a

Re: HTML export to different formats

2009-09-04 Thread Jürgen Spitzmüller
Alex Fernandez wrote: > The information is not lost; it is a Reconfigure away. All you lost > are the possible customizations. Please search the archieves. I've explained my POV several times in the past, I'm too lazy to rephrase again. Jürgen

Re: HTML export to different formats

2009-09-04 Thread Alex Fernandez
On Fri, Sep 4, 2009 at 1:02 PM, Jürgen Spitzmüller wrote: > Alex Fernandez wrote: >> Isn't that already in Preferences, under "External Formats"? You can >> remove any converters you don't want. > > I'm not thinking of "removing", but of enabling/disabling (without losing > given information). The

Re: HTML export to different formats

2009-09-04 Thread Jürgen Spitzmüller
Alex Fernandez wrote: > Isn't that already in Preferences, under "External Formats"? You can > remove any converters you don't want. I'm not thinking of "removing", but of enabling/disabling (without losing given information). Jürgen

Re: HTML export to different formats

2009-09-04 Thread Alex Fernandez
On Fri, Sep 4, 2009 at 10:54 AM, Jürgen Spitzmüller wrote: > Alex Fernandez wrote: >> What would be a proper way for you? > > Configure all available converters and let the user select in preferences > which converters he wants to see in the menus. Isn't that already in Preferences, under "Externa

Re: HTML export to different formats

2009-09-04 Thread Jürgen Spitzmüller
Alex Fernandez wrote: > What would be a proper way for you? Configure all available converters and let the user select in preferences which converters he wants to see in the menus. Jürgen

Re: HTML export to different formats

2009-09-04 Thread Alex Fernandez
On Fri, Sep 4, 2009 at 10:34 AM, Jürgen Spitzmüller wrote: >> Would it be OK to >> separate the formats into HTML (eLyXer), HTML (hevea) and so on?  This >> way users would be able to tell what they have installed and choose >> between the different exporters if available. > > The same would need t

Re: HTML export to different formats

2009-09-04 Thread Jürgen Spitzmüller
Alex Fernandez wrote: > Would it be OK to > separate the formats into HTML (eLyXer), HTML (hevea) and so on? This > way users would be able to tell what they have installed and choose > between the different exporters if available. The same would need to be done for any other converter. But then,

Re: HTML Export Update

2009-06-05 Thread rgheck
Jean-Marc Lasgouttes wrote: rgheck writes: The issue here, I think, would be with eps and the like. LyX accepts a lot of formats that one wouldn't assume browsers could display inline. I think tex4ht by default converts everything to png. Is there a list of valid formats somewhere? I

Re: HTML Export Update

2009-06-05 Thread Jean-Marc Lasgouttes
rgheck writes: > The issue here, I think, would be with eps and the like. LyX accepts a > lot of formats that one wouldn't assume browsers could display inline. > I think tex4ht by default converts everything to png. Is there a list of valid formats somewhere? I understand that svg, for example,

Re: HTML Export Update

2009-06-05 Thread rgheck
Jean-Marc Lasgouttes wrote: Abdelrazak Younes writes: For graphics I think we need two options: 1) link to the original file 2) resize to LateX settings and copy the graphic file to 'file.dir' along 'file.html' Why? We can use the original file but specify its size in the html, can't

Re: HTML Export Update

2009-06-05 Thread rgheck
Pavel Sanda wrote: There are enough MathML compliant browser out there, no need to complicate our life with the bonus is that this will help the transition to XML if we ever manage to do that. So, if I was you ;-), I'd implement things in this order: 1) all images reusing the instant preview

Re: HTML Export Update

2009-06-05 Thread Abdelrazak Younes
Jean-Marc Lasgouttes wrote: Abdelrazak Younes writes: For graphics I think we need two options: 1) link to the original file 2) resize to LateX settings and copy the graphic file to 'file.dir' along 'file.html' Why? We can use the original file but specify its size in the html, can't

Re: HTML Export Update

2009-06-05 Thread Pavel Sanda
Abdelrazak Younes wrote: >> There are also just a lot of questions about how to handle various things, >> so I'd welcome any thoughts about that. E.g., what should we do with >> InsetInclude? Include it? i would include it by default > Independently we should offer the > option to split the fi

Re: HTML Export Update

2009-06-05 Thread Jean-Marc Lasgouttes
Abdelrazak Younes writes: > For graphics I think we need two options: > 1) link to the original file > 2) resize to LateX settings and copy the graphic file to 'file.dir' > along 'file.html' Why? We can use the original file but specify its size in the html, can't we? > I think we should conside

Re: HTML Export Update

2009-06-05 Thread Abdelrazak Younes
rgheck wrote: rgh...@lyx.org wrote: Author: rgheck Date: Thu Jun 4 20:18:45 2009 New Revision: 29939 URL: http://www.lyx.org/trac/changeset/29939 This completes the major infrastructure for HTML output. Few of the insets work yet, but it handles everything else reasonably well, even tough

Re: html export gone screwy?

2001-12-15 Thread Dekel Tsur
On Fri, Dec 14, 2001 at 03:07:13PM -0500, Richard E. Hawkins wrote: > > > I don't think I've ever seen anything this ugly . . . *all* of the > formatting is lost. > > I haven't used it in a couple of months, but this is downright screwy . > . . The bug is not in LyX, it is in latex2html. For

Re: Html export

2000-03-11 Thread Asger K. Alstrup Nielsen
> The default command for exporting html with tth is > tth -t < '$$FName' > '$$OutName' > However, it should be > tth -t -L`basename '$$FName' .tex` < '$$FName' > '$$OutName'" > (with the latter, tth can convert the bibliography, do correct reference etc.) > > This has an effect only i

Re: HTML export bug

1999-11-21 Thread Kayvan A. Sylvan
On Mon, Nov 22, 1999 at 12:06:07AM +0100, Ronny Standtke wrote: > > Hi all, > > I just installed tth-2.51 and lyx-1.1.2 to try out the new HTML export feature. > But it always fails. When I run lyx from a terminal the following error message > appears: > This is a known bug in lyx. Change the

Re: html-export problem with 1.1.1

1999-10-29 Thread Nils Jeppe
On 29 Oct 1999, Jean-Marc Lasgouttes wrote: > Nils> Saved files also have the - to _ conversion bug. At least last > Nils> time I checked they did. It's pretty annoying. > > You mean that you create file new-file.lyx, save it, and find out that > it has been saved under the name new_file.lyx? I

Re: html-export problem with 1.1.1

1999-10-29 Thread Jean-Marc Lasgouttes
> "Nils" == Nils Jeppe <[EMAIL PROTECTED]> writes: Nils> On 29 Oct 1999, Jean-Marc Lasgouttes wrote: Yeah this Nils> minus-to-underscore problem is VERY annoying. It affects saved Nils> files too... this should definitely be fixed ASAP. >> What do you mean with saved files? Can you be more s

Re: html-export problem with 1.1.1

1999-10-29 Thread Nils Jeppe
On 29 Oct 1999, Jean-Marc Lasgouttes wrote: > Nils> Yeah this minus-to-underscore problem is VERY annoying. It > Nils> affects saved files too... this should definitely be fixed ASAP. > > What do you mean with saved files? Can you be more specific? Saved files also have the - to _ conversion b

Re: html-export problem with 1.1.1

1999-10-29 Thread Jean-Marc Lasgouttes
> "Nils" == Nils Jeppe <[EMAIL PROTECTED]> writes: Nils> On Thu, 28 Oct 1999, David L. Johnson wrote: >> I had mentioned earlier that a - in a filename was converted to a _ >> in the output *.tex file. This apparently is still present in >> 1.1.1, which creates a Nils> Yeah this minus-to-und

Re: html-export problem with 1.1.1

1999-10-29 Thread Jean-Marc Lasgouttes
> "David" == David L Johnson <[EMAIL PROTECTED]> writes: David> I had mentioned earlier that a - in a filename was converted to David> a _ in the output *.tex file. This apparently is still present David> in 1.1.1, which creates a problem with html export, seeing as David> how tth is looking

Re: html-export problem with 1.1.1

1999-10-29 Thread Nils Jeppe
On Thu, 28 Oct 1999, David L. Johnson wrote: > I had mentioned earlier that a - in a filename was converted to a _ in the > output *.tex file. This apparently is still present in 1.1.1, which creates a Yeah this minus-to-underscore problem is VERY annoying. It affects saved files too... this s