Re: Feature request
Thanks Jim. I just responded to your feature request. Let's continue the conversation on the trac ticket. Scott On Sat, Feb 1, 2014 at 6:49 PM, Jim Rockford wrote: > Thanks for your attention Scott. I just submitted the enhancement request > you suggested. > > Best, > Jim > > > On Fri, Jan 31, 2014 at 4:43 PM, Scott Kostyshak wrote: >> >> Hi Jim, >> >> Do you think something like the insert table icon would work well for >> matrices? If you haven't tried it yet, click on the "Insert table" >> icon in the top toolbar. If matrices worked in this way, would you >> consider that better or worse than how MathType does it? >> >> Can you open an enhancement request on trac for this? >> http://www.lyx.org/trac >> Also on the trac ticket can you post a screenshot of what MathType >> does? I'm wondering what the user interface is like. >> >> Best, >> >> Scott >> >> On Fri, Jan 31, 2014 at 4:29 PM, Jim Rockford >> wrote: >> > MathType has the nice feature that when you click to insert a matrix, >> > one >> > has the choice of immediately inserting a typical low-dimensional matrix >> > (i.e. 2x2, 3x3, 3x1, etc), in addition to the option of setting the row >> > and >> > column numbers manually. As far as I can tell, in Lyx you must always >> > specify the dimension explicitly. I find this a bit of a nuisance and >> > thus >> > make the feature request. >> > >> > Thanks to the Lyx team for their great work and their consideration of >> > user >> > feature requests. >> > >> > Jim > >
[ANNOUNNCE] LyX 2.0.7.1 Released
Public release of LyX version 2.0.7.1 = We are pleased to announce the release of LyX 2.0.7.1. This is a bugfix release that affects Mac OSX only. Users of other operating systems do *not* need to update to this version, and no binaries will be provided for other operating systems. There were some issues with the menus in LyX 2.0.7 on OSX. Specifically, "dynamic" menu items were lost, and there was a problem restoring the menus from full-screen operation. Both issues are fixed in 2.0.7.1. Other bugs fixed since LyX 2.0.6 are detailed below. The most important of these was #8854, which could lead to file corruption in certain cases and, more often, would lead to errors in generated files (e.g., PDFs). We encourage all LyX users to upgrade from 2.0.6. LyX is a document processor that encourages an approach to writing based on the structure of your documents and not simply their appearance. It is released under a Free and Open Source Software license. You can download LyX 2.0.7.1 from http://www.lyx.org/Download/. If you think you found a bug in LyX 2.0.7.1, either e-mail the LyX developers' mailing list (lyx-devel lists.lyx.org), or open a bug report at http://www.lyx.org/trac/wiki/BugTrackerHome. If you have trouble using LyX or have a question, consult the documentation that comes with LyX and the LyX wiki, which lives at http://wiki.lyx.org/. If you can't find the answer there, e-mail the LyX users' list (lyx-users at lists.lyx.org). We hope you enjoy using LyX 2.0.7.1. The LyX team. http://www.lyx.org What's new in LyX 2.0.7.1 = ** Updates: *** * DOCUMENTATION AND LOCALIZATION - Updated Arabic, French, Interlingua, Japanese, Nynorsk, Swedish and Ukrainian user interface localizations. - Revised French Intro and User Guide. ** Bug fixes: * * DOCUMENT INPUT/OUTPUT - Fix garbage in document export (and maybe other places) by making encoding conversions thread-safe (bug 8854). - Fix output of ulem commands (underline etc.) which was broken as of LyX 2.0.6 (bug 8733). - Fix problem with unbalanced braces in XeTeX output (bug 8765). - Fix problems with unbalanced braces with a secondary CJK language (bug 8215). - Fix state of certain language packages (polyglossia, japanese) in child documents (bug 8770). - Fix compilation of documents containing chemical equations and math integrals (bug 8731). - Fix compilation with nested ("sub") custom floats. - Fix import of CSV-files. - Added h5 and h6 as HTML tags for Paragraph and Subparagraph. - Include alt tag when exporting math as images (bug 8746). * USER INTERFACE - Fix crash when saving document with module that is not present (bug 8523). - Fix crash when changing alignment of several cells in tabular (bug 8859). - Disable invalid actions in empty outliner that could trigger a crash (bug 8885). - Fix warning when setting layout box when Plain Layout is used (bug 8727). - Fix bug where searching for next change may leave an empty paragraph where cursor was (bug 3199). - Fix activation of branches from command line (bug 8627). - Fix display of appendix counters in some classes (bug 8666). - Fix toggling of "misc" font options (bug 8764). - Handle undo correctly when a branch is (de)activated. - Update a bibliography entry's label when it is emptied. - Insets in a bibliography entry are shown as text in the citation dialog. - Correctly detect python scripts required by the preview mechanism. - Fix display of file names with ampersands in the tab header (bug 8757). - The koma-script book class numbers equations by chapter. - Fix shortcut conflict in the citation dialog (bug 8878). - Fix wrong display of style "Description" in "article (paper)" class (bug 8869). - Fix the missing menu entry for "Insert Branch ". - Fix the missing dynamic menus in general and restore correctly from fullscreen. * DOCUMENTATION AND LOCALIZATION - Make the aa.lyx template file and the aa_sample.lyx example file compilable. - Make the AEA.lyx template file compilable. - Make the landslide example file compilable. - Fix problem that the Chinese Tutorial could not be viewed as PDF on some systems. * LYXHTML - Fix problem with size of superscripts and such inside footnotes (bug 8610). - Add missing space before the edition in the bibliography (part of bug 8488). - Fix random character inserted as year modifier in author-year citations. * BUILD/INSTALLATION - Add support for automake 1.13. - Fix compilation with clang LLVM compiler. - Fix Qt tools search when a Qt directory has been specified.
Re: We need ePub/Mobi conversion: was: Book Frontmatter
Well, that's a bit disappointing. Thanks for the full report. I've only used Pandoc for simple conversions, so haven't looked deeply at the configuration options that might help with the problems that you identify below. One last approach might be interesting to try: What about LyX -> (X)html, then process through Pandoc. And instead of using the LyX exporters, try tex4ht to make the html file. And process the html file through tidy before using Pandoc. I haven't tried this, so please don't waste your time on it if inconvenient. Pandoc seems at its strongest when starting with a Markdown file. Cheers, Alan Steve Litt writes: > On Sat, 01 Feb 2014 05:25:58 +1100 > Alan L Tyree wrote: > >> Sorry for the top posting, but this is short. My own view is that an >> ePub exporter for LyX would make it a killer application. >> >> Thanks for your comments, Steve. Have you looked at Pandoc? >> >> Cheers, >> Alan > > Hi Alan, > > I hadn't known about Pandoc. Thanks for the heads-up. I looked up Pandoc > here: > > http://johnmacfarlane.net/pandoc/ > > For the following ascii art, please switch to monospace font... > >.___. .__. > LyXformat->|LyX|->LaTeXformat->|Pandoc|->ePubFormat >` > > The preceding looked simple enough, so I downloaded and installed > Pandoc, and tried it on one of my simpler books. It indeed produced an > ePub, and in certain respects a good one. But not nearly good enough to > sell. No table of contents. No cover. No images: all images referred to > only by their Alt text. All cross reference labels exposed as text with > arbitrary subscript formatting in places. The good news is it managed > to keep footnotes and the like, but that's not good enough. I spoze > theoretically I could have used other options on my lyx -export > command, or on my pandoc command, so these things wouldn't happen, or > perhaps I could have made restrictions on the authoring of my book in > LyX, but these things would need to be examined later. > > Another way to use Pandoc might be this: > >.___. .__. > LyXformat->|LyX|->LaTeXformat->|Pandoc|->xhtml-. >` | > .-' > | > | ._. ._. > `->|xhtml Tweaker|->xhtml->|My xhtml2epub|->ePub > ``` ``` > > The preceding would depend on: > > A) Pandoc retaining enough info, including semantic styles, to make all >book elements > B) Pandoc producing xhtml sane enough that the tweaker is something >that can actually be written. > > So I tried using Pandoc to convert my LaTeX book to (X)html. The result > had no (and this might be an advantage), it had all sorts of > garbage characters (perhaps this could be fixed in the I would > insert), but, the kiss of death is this: It took all my semantic styles > (environments and character styles), kinda-sorta converted them to > presentation, and discarded the semantic styles, so that in my > I can't specify the link between semantic styles and presentation. > Once those semantic styles are gone, no matter how clever a programmer > I am, I don't have the necessary input info to govern the look of my > eBook. This is a showstopper that cannot be recovered from. > > So unless somebody knows of a way to prevent Pandoc from pulling an > MSWord move and prematurely converting semantic to presentational, my > opinion is that Pandoc is worthless for this task. > > Thanks, > > SteveT > > Steve Litt* http://www.troubleshooters.com/ > Troubleshooting Training * Human Performance -- Alan L Tyree http://www2.austlii.edu.au/~alan Tel: 04 2748 6206 sip:172...@iptel.org
Re: We need ePub/Mobi conversion: was: Book Frontmatter
On Sat, 01 Feb 2014 05:25:58 +1100 Alan L Tyree wrote: > Sorry for the top posting, but this is short. My own view is that an > ePub exporter for LyX would make it a killer application. > > Thanks for your comments, Steve. Have you looked at Pandoc? > > Cheers, > Alan Hi Alan, I hadn't known about Pandoc. Thanks for the heads-up. I looked up Pandoc here: http://johnmacfarlane.net/pandoc/ For the following ascii art, please switch to monospace font... .___. .__. LyXformat->|LyX|->LaTeXformat->|Pandoc|->ePubFormat ` The preceding looked simple enough, so I downloaded and installed Pandoc, and tried it on one of my simpler books. It indeed produced an ePub, and in certain respects a good one. But not nearly good enough to sell. No table of contents. No cover. No images: all images referred to only by their Alt text. All cross reference labels exposed as text with arbitrary subscript formatting in places. The good news is it managed to keep footnotes and the like, but that's not good enough. I spoze theoretically I could have used other options on my lyx -export command, or on my pandoc command, so these things wouldn't happen, or perhaps I could have made restrictions on the authoring of my book in LyX, but these things would need to be examined later. Another way to use Pandoc might be this: .___. .__. LyXformat->|LyX|->LaTeXformat->|Pandoc|->xhtml-. ` | .-' | | ._. ._. `->|xhtml Tweaker|->xhtml->|My xhtml2epub|->ePub ``` ``` The preceding would depend on: A) Pandoc retaining enough info, including semantic styles, to make all book elements B) Pandoc producing xhtml sane enough that the tweaker is something that can actually be written. So I tried using Pandoc to convert my LaTeX book to (X)html. The result had no (and this might be an advantage), it had all sorts of garbage characters (perhaps this could be fixed in the I would insert), but, the kiss of death is this: It took all my semantic styles (environments and character styles), kinda-sorta converted them to presentation, and discarded the semantic styles, so that in my I can't specify the link between semantic styles and presentation. Once those semantic styles are gone, no matter how clever a programmer I am, I don't have the necessary input info to govern the look of my eBook. This is a showstopper that cannot be recovered from. So unless somebody knows of a way to prevent Pandoc from pulling an MSWord move and prematurely converting semantic to presentational, my opinion is that Pandoc is worthless for this task. Thanks, SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance
Re: Request for Feature on Mac
I think this is correct, and a good idea. el On 2014-02-01, 05:30 , Jerry wrote: > > On Jan 31, 2014, at 3:00 AM, Dr Eberhard Lisse > wrote: > >> Where would I request the following feature: >> >> Many Mac programs offer you the choice to Save, Don't >> Save/Discard, Cancel in the way that is shown in the enclosed >> alpha.jpg, ie if you use the Return/Enter key it'll save, if you >> use the Space key it'll Not Save (Quit) and you have to use the >> mouse to click Cancel. >> >> In Lyx I must use the mouse if I want to discard, because it >> doesn't recognize the Space and it defaults to Save. >> >> Since I work with the keyboard mostly it is a nuisance, hence >> this request. >> >> el > > If someone is going to change this, please also change "Discard" > to "Don't Save" which is standard on OS X. > > Jerry > >