Can't Export PDF from LyX

[Rizwan khan Jadoon]

I just installed Lyx 2.0  and I can't export any PDFs, although the message
at the bottom says, Successful export to format: pdf2. I'm running
Windows 7 32bit operating system and have both Acrobat Reader 10 and Foxit
Reader installed, with Foxit being the default.  Also, the only options I'm
seeing under Preferences  File Handling  File Formats  PDF (pdflatex)
are None and Custom.  Please help.

Thanks,
Rizwan khan jadoon

-- 
-
Rizwan khan jadoon
MS student

Re: Can't Export PDF from LyX

[Stephan Witt]

Am 03.02.2014 um 09:17 schrieb Rizwan khan Jadoon 
jadoon.rizwankha...@gmail.com:

 I just installed Lyx 2.0  and I can't export any PDFs, although the message 
 at the bottom says, Successful export to format: pdf2. I'm running Windows 
 7 32bit operating system and have both Acrobat Reader 10 and Foxit Reader 
 installed, with Foxit being the default.  Also, the only options I'm seeing 
 under Preferences  File Handling  File Formats  PDF (pdflatex) are None 
 and Custom.  Please help.

What does not work for you exactly?

Export produces an PDF file and saves it into the folder of the main document.

In case you're expecting the viewer opening your output document you shouldn't 
use Export.
Please use View for that task.

Stephan

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 01/31/14, 20:28 , Rainer M Krug wrote:
 
 
 Le vendredi 31 janvier 2014, Richard Heck rgh...@lyx.org 
 mailto:rgh...@lyx.org a écrit :
 
 On 01/30/2014 03:04 AM, Rainer M Krug wrote:
 
 On 01/29/14, 02:41 , Richard Heck wrote:
 
 On 01/28/2014 03:14 PM, Scott Kostyshak wrote:
 
 This should be fixed shortly and a new installer will be uploaded.
 
 As often, this is due to changes in the underlying Qt platform that
 seem to exist only on certain versions of OSX. We have had this
 problem before, and there are other issues about Cocoa versus 
 whatever versus whatever else. It is difficult to test every 
 combination, and we have only a couple active OSX developers. Many 
 of them use trunk (2.1.dev) for obvious sorts of reasons. So, well,
 we could really use a couple people who could test the OSX version
 on a more regular basis.
 
 To facilitate this, may I suggest to create a homebrew recipe to 
 facilitate the installation and update of the latest LyX? At least
 for me, I would likely use (and update) it regularly  as it is no
 hassle at all (in contrast to downloading and installing, or even
 compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how to 
 use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be interested
 in helping. But apparently, it is not that difficult.

I am using this to the devel lits as this does not (yet?) concern a
normal user.

Looking into this, I am wondering: what are the settings to create the
LyX binary for Mac? I could not find a hotwo on how to compile on mac?

Cheers,

Rainer


 
 Cheers,
 
 Rainer
 
 
 
 rh
 
 
 
 
 -- NEW GERMAN FAX NUMBER!!!
 
 Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation 
 Biology, UCT), Dipl. Phys. (Germany)
 
 Centre of Excellence for Invasion Biology Natural Sciences
 Building Office Suite 2039 Stellenbosch University Main Campus,
 Merriman Avenue Stellenbosch South Africa
 
 Cell:   +27 - (0)83 9479 042 Fax:+27 - (0)86
 516 2782 Fax:+49 - (0)321 2125 2244 email:
 rai...@krugs.de mailto:rai...@krugs.de
 
 Skype:  RMkrug Google: r.m.k...@gmail.com
 mailto:r.m.k...@gmail.com
 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEbBAEBAgAGBQJS72ezAAoJENvXNx4PUvmCMiMH+KTsEB7QKNoXQtDwVfTrFUuZ
GEyhhOVHFFpWY9tsDEaGtzFDoCRFL8gPtyxdSKurQiL9zg+WCg6vQdJK02PIhl9d
FvaQWzMEE71JhUJeHiSJyJc/jI38EeObZthnnOqf8BW8hpgbZOPdic5HWokGR1QP
oy02Y42z4/25PaHMu7Q3ZntQZc+Ix8/imBIXUrsYbXYiCx56RQleoOWH0gddznKa
06HbiDmQ4ff9JrqACWzhGunZQxmRUmbcxT9KvnlWisJp7KMTm4IPJxpMgGGZre4Z
W7IvLVq19eXk9ADjmol/zDjIEmAIiy7tJg/q10XECY997ML3hB6XKmAdzrnfJA==
=0uWO
-END PGP SIGNATURE-

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Stephan Witt]

Am 03.02.2014 um 10:56 schrieb Rainer M Krug rai...@krugs.de:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 
 
 On 01/31/14, 20:28 , Rainer M Krug wrote:
 
 
 Le vendredi 31 janvier 2014, Richard Heck rgh...@lyx.org 
 mailto:rgh...@lyx.org a écrit :
 
 On 01/30/2014 03:04 AM, Rainer M Krug wrote:
 
 On 01/29/14, 02:41 , Richard Heck wrote:
 
 On 01/28/2014 03:14 PM, Scott Kostyshak wrote:
 
 This should be fixed shortly and a new installer will be uploaded.
 
 As often, this is due to changes in the underlying Qt platform that
 seem to exist only on certain versions of OSX. We have had this
 problem before, and there are other issues about Cocoa versus 
 whatever versus whatever else. It is difficult to test every 
 combination, and we have only a couple active OSX developers. Many 
 of them use trunk (2.1.dev) for obvious sorts of reasons. So, well,
 we could really use a couple people who could test the OSX version
 on a more regular basis.
 
 To facilitate this, may I suggest to create a homebrew recipe to 
 facilitate the installation and update of the latest LyX? At least
 for me, I would likely use (and update) it regularly  as it is no
 hassle at all (in contrast to downloading and installing, or even
 compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how to 
 use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be interested
 in helping. But apparently, it is not that difficult.
 
 I am using this to the devel lits as this does not (yet?) concern a
 normal user.
 
 Looking into this, I am wondering: what are the settings to create the
 LyX binary for Mac? I could not find a hotwo on how to compile on mac?

Possibly a little bit outdated - but did you consider INSTALL.MacOSX?

Stephan

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 02/03/14, 11:07 , Stephan Witt wrote:
 Am 03.02.2014 um 10:56 schrieb Rainer M Krug rai...@krugs.de:
 
 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
 
 
 
 On 01/31/14, 20:28 , Rainer M Krug wrote:
 
 
 Le vendredi 31 janvier 2014, Richard Heck rgh...@lyx.org 
 mailto:rgh...@lyx.org a écrit :
 
 On 01/30/2014 03:04 AM, Rainer M Krug wrote:
 
 On 01/29/14, 02:41 , Richard Heck wrote:
 
 On 01/28/2014 03:14 PM, Scott Kostyshak wrote:
 
 This should be fixed shortly and a new installer will be
 uploaded.
 
 As often, this is due to changes in the underlying Qt platform
 that seem to exist only on certain versions of OSX. We have had
 this problem before, and there are other issues about Cocoa
 versus whatever versus whatever else. It is difficult to test
 every combination, and we have only a couple active OSX
 developers. Many of them use trunk (2.1.dev) for obvious sorts
 of reasons. So, well, we could really use a couple people who
 could test the OSX version on a more regular basis.
 
 To facilitate this, may I suggest to create a homebrew recipe
 to facilitate the installation and update of the latest LyX? At
 least for me, I would likely use (and update) it regularly  as
 it is no hassle at all (in contrast to downloading and
 installing, or even compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how
 to use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be
 interested in helping. But apparently, it is not that
 difficult.
 
 I am using this to the devel lits as this does not (yet?) concern
 a normal user.
 
 Looking into this, I am wondering: what are the settings to
 create the LyX binary for Mac? I could not find a hotwo on how to
 compile on mac?
 
 Possibly a little bit outdated - but did you consider
 INSTALL.MacOSX?

Shame on me - there it is, in the obvious place.

Thanks, I'll look into it,

Rainer

 
 Stephan
 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS73C6AAoJENvXNx4PUvmC6WYIALVbED9DGwDNo5x7gYpImJCZ
38UW5FRanH8vB5//i6KKBNFsT6/bNCBp4gcR0LjdppGWgM1fgnCBw+TUtDLDPL3j
FYOw7D71+5lQAMT+ZgkVwQX0hrGCF2AJa1vYEUfJygrSv48VrMHDdYpCaLAw/zj6
imqgk/rx6pzaml3otn+BdqGIFzrkhLkfeS+VF08WIWXBhcLOZDG1EFLhBzgagLsd
FP1PI3b0jH8O5xKu5UHrxGCVjVOOx1ZG7hhOXz5EknaPtgGaaOEUc3mdlfpfjIXR
TFD0F47n8jpuGHSqjAJ1EARvUKqZaijQkDnafE0gL9asvscqplSehQaZuzn9Jns=
=stBe
-END PGP SIGNATURE-

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Stephan Witt]

Am 03.02.2014 um 11:34 schrieb Rainer M Krug rai...@krugs.de:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 
 
 On 02/03/14, 11:07 , Stephan Witt wrote:
 Am 03.02.2014 um 10:56 schrieb Rainer M Krug rai...@krugs.de:
 
 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
 
 
 
 On 01/31/14, 20:28 , Rainer M Krug wrote:
 
 
 Le vendredi 31 janvier 2014, Richard Heck rgh...@lyx.org 
 mailto:rgh...@lyx.org a écrit :
 
 On 01/30/2014 03:04 AM, Rainer M Krug wrote:
 
 On 01/29/14, 02:41 , Richard Heck wrote:
 
 On 01/28/2014 03:14 PM, Scott Kostyshak wrote:
 
 This should be fixed shortly and a new installer will be
 uploaded.
 
 As often, this is due to changes in the underlying Qt platform
 that seem to exist only on certain versions of OSX. We have had
 this problem before, and there are other issues about Cocoa
 versus whatever versus whatever else. It is difficult to test
 every combination, and we have only a couple active OSX
 developers. Many of them use trunk (2.1.dev) for obvious sorts
 of reasons. So, well, we could really use a couple people who
 could test the OSX version on a more regular basis.
 
 To facilitate this, may I suggest to create a homebrew recipe
 to facilitate the installation and update of the latest LyX? At
 least for me, I would likely use (and update) it regularly  as
 it is no hassle at all (in contrast to downloading and
 installing, or even compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how
 to use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be
 interested in helping. But apparently, it is not that
 difficult.
 
 I am using this to the devel lits as this does not (yet?) concern
 a normal user.
 
 Looking into this, I am wondering: what are the settings to
 create the LyX binary for Mac? I could not find a hotwo on how to
 compile on mac?
 
 Possibly a little bit outdated - but did you consider
 INSTALL.MacOSX?
 
 Shame on me - there it is, in the obvious place.
 
 Thanks, I'll look into it,

No problem. I'll happily update it's contents to reflect your
findings on this matter. For LyX 2.1.X e.g. the gettext requirement
doesn't exist anymore. The Qt version for production is 4.8.5.
For development I've tried 5.0, 5.1 and 5.2 too. 
Version 5.2 definitively doesn't work - the menu is missing
almost completely. On current Mac systems Qt-Carbon isn't
available anymore.

I'm using the script development/LyX-Mac-binary-release.sh.
Something like that (note the back slashes):

ARCH=x86_64
Qt4Version=4.8.5
Qt4API=-cocoa
LyXVersion=lyx-2.1.0beta2
QtConfigureOptions=-debug-and-release Qt4API=${Qt4API} 
Qt4Version=${Qt4Version} \
 sh ${LyXVersion}/development/LyX-Mac-binary-release.sh \
   --with-sdkroot=10.8 --with-macosx-target=10.6 --with-arch=${ARCH} \
   --with-qt4-dir=$HOME/lyx-build/qt-${Qt4Version}-frameworks${Qt4API}-${ARCH}

Stephan

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Richard Heck]

On 02/03/2014 01:53 AM, Liviu Andronic wrote:

Dear Steve and Alex,

On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt sl...@troubleshooters.com wrote:

On Fri, 31 Jan 2014 22:33:02 +0100
Alex Fernandez ely...@gmail.com wrote:

Ladies and gentlemen, if the preceding paragraph doesn't convince
us we need a good, solid, LyX to ePub and LyX to Mobi conversion



Last year we actually had a GSoC project specifically dealing with
ePub. Josh and Richard made progress on this front, and the code
simply awaits someone with the motivation and the skills to finish the
job. The almost finished feature is available in several GIT branches
here: http://git.lyx.org/?p=gsoc.git;a=summary .


Actually, mostly what this awaits is the release of 2.1, since the main 
work left is to integrate this into trunk. There are still bugs to be 
fixed, of course, in the underlying XHTML export routines, but that's 
always true. Most of the ones Steve mentioned earlier have already been 
fixed.


Richard

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Steve Litt]

On Mon, 03 Feb 2014 10:05:57 -0500
Richard Heck rgh...@lyx.org wrote:

 On 02/03/2014 01:53 AM, Liviu Andronic wrote:
  Dear Steve and Alex,
 
  On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt
  sl...@troubleshooters.com wrote:
  On Fri, 31 Jan 2014 22:33:02 +0100
  Alex Fernandez ely...@gmail.com wrote:
  Ladies and gentlemen, if the preceding paragraph doesn't convince
  us we need a good, solid, LyX to ePub and LyX to Mobi conversion
 
  Last year we actually had a GSoC project specifically dealing with
  ePub. Josh and Richard made progress on this front, and the code
  simply awaits someone with the motivation and the skills to finish
  the job. The almost finished feature is available in several GIT
  branches here: http://git.lyx.org/?p=gsoc.git;a=summary .
 
 Actually, mostly what this awaits is the release of 2.1, since the
 main work left is to integrate this into trunk. There are still bugs
 to be fixed, of course, in the underlying XHTML export routines, but
 that's always true. Most of the ones Steve mentioned earlier have
 already been fixed.
 
 Richard

The instant 2.1 comes out, I'll compile it separate from my
Ubuntu-provided LyX, and try it out.

Thanks,

SteveT

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

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Steve Litt]

On Mon, 3 Feb 2014 07:53:49 +0100
Liviu Andronic landronim...@gmail.com wrote:

 Dear Steve and Alex,
 
 On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt
 sl...@troubleshooters.com wrote:
  On Fri, 31 Jan 2014 22:33:02 +0100
  Alex Fernandez ely...@gmail.com wrote:
   Ladies and gentlemen, if the preceding paragraph doesn't convince
   us we need a good, solid, LyX to ePub and LyX to Mobi conversion
 
 
 Last year we actually had a GSoC project specifically dealing with
 ePub. Josh and Richard made progress on this front, 

Did the progress include an Xhtml export that preserved semantics and
respected HTML semantics such as using h? for leveled headings, p
for paragraphs, and pre for lyx-code and environments derived from
it, and span for character styles? If you got that far and can write
it to disk, I can take it from there.

 and the code
 simply awaits someone with the motivation and the skills to finish the
 job. The almost finished feature is available in several GIT branches
 here: http://git.lyx.org/?p=gsoc.git;a=summary .

If I ever get a day or two to familiarize myself with it, I will. But
of course, I'm really lousy at C++, and in fact hate C++.

I think there are several missed opportunities:

1) If LyX insists on having a native format of XML, which by its nature
   is human-confusing, it should at least be *well formed* XML so that
   it can be handled by an XML parser, and if the programmer is more
   skilled than I, XSLT. The day LyX native format is well formed, and
   maybe even with a DTD, I'll make the converter: me, myself and I.

2) The ePub converter shouldn't be a part of LyX: Most of it should be
   standalone. There's no reason for LyX to need to know *anything*
   about ePub. Just provide a sane Xhtml export, one that doesn't
   substitute div for p, or p for h?, and calls a pre a
   pre. Don't throw away the semantics: Don't convert styles to
   appearances, and don't use div instead of HTML structural elements
   like p, pre, and h?. Give me that, and I can do the rest.

3) I honestly don't think you're ever going to get one programmer to do
   this whole thing. The likelihood is infinitesimal of finding one
   person who: A) has a burning ePub itch to scratch and B) is great at
   C++ and C) Is familiar with LyX's code base. The way to do this
   is as a pipeline, where person A exports what person B needs, and
   person B converts that to what person C needs, etc. The beauty of
   this would be is that, as LyX changes, only person A would need to
   change his code, unless, of course, the rest of the chain needs an
   enhancement. The way I envision it would be either that person A
   would be the person who makes a sane Xhtml export, and person B is
   me. Or, perhaps, if LyX native format is ever well formed and valid
   XML, Person A is me, converting LyX to an Xhtml subset, and person B
   is me, converting the subset to ePub. That way, as LyX changed, I'd
   need to change only the first program.

4) Back when Josh was doing this, neither I nor Rob Oakes knew what we
   know about ePub today. If we had, we could have given Josh and his
   crew much better guidance about what was needed. If anybody wants to
   continue on the road to LyX-ePub, I suggest that person(s) ask us
   lots of questions.

Thanks,

SteveT

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

Lyx 2.1 Beta 2 and 32bit Mac

[Dominik Schmidt]

Hi

has the support for 32 Bit Mac machines been dropped? I am running a Core
Duo with Snow Leopard and the system refuses to install the latest beta.

Thanks for your help!

lyx 2.0.1: .tex import with use of .cls and .sty files

[Jörg Kühne]

Dear user list



Is it generally possible to import a .tex with use of .cls and .sty files to Lyx?

If I import the example.tex to Lyx,

Lyx creates line breaks as follows:







cventry{2011--2012}



{Masters of Commerce}{The University of California}{Berkeley}{textit{GPA

-- 8.0}}{First Class Honours} % Arguments not required can be left empty



What can I do to avoid such errors in Lyx?



Regards



Joerg

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Richard Heck]

On 02/03/2014 11:36 AM, Steve Litt wrote:

On Mon, 03 Feb 2014 10:05:57 -0500
Richard Heck rgh...@lyx.org wrote:


On 02/03/2014 01:53 AM, Liviu Andronic wrote:

Dear Steve and Alex,

On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt
sl...@troubleshooters.com wrote:

On Fri, 31 Jan 2014 22:33:02 +0100
Alex Fernandez ely...@gmail.com wrote:

Ladies and gentlemen, if the preceding paragraph doesn't convince
us we need a good, solid, LyX to ePub and LyX to Mobi conversion

Last year we actually had a GSoC project specifically dealing with
ePub. Josh and Richard made progress on this front, and the code
simply awaits someone with the motivation and the skills to finish
the job. The almost finished feature is available in several GIT
branches here: http://git.lyx.org/?p=gsoc.git;a=summary .

Actually, mostly what this awaits is the release of 2.1, since the
main work left is to integrate this into trunk. There are still bugs
to be fixed, of course, in the underlying XHTML export routines, but
that's always true. Most of the ones Steve mentioned earlier have
already been fixed.

Richard

The instant 2.1 comes out, I'll compile it separate from my
Ubuntu-provided LyX, and try it out.


Sorry, to be clear: The ePub stuff will not be in 2.1. It came too late 
for that. It will go into trunk shortly after 2.1 and be in 2.2, which 
we expect to follow 2.1 much more quickly than usual.


Richard



Thanks,

SteveT

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

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Richard Heck]

On 02/03/2014 11:34 AM, Steve Litt wrote:

On Mon, 3 Feb 2014 07:53:49 +0100
Liviu Andronic landronim...@gmail.com wrote:


Dear Steve and Alex,

On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt
sl...@troubleshooters.com wrote:

On Fri, 31 Jan 2014 22:33:02 +0100
Alex Fernandez ely...@gmail.com wrote:

Ladies and gentlemen, if the preceding paragraph doesn't convince
us we need a good, solid, LyX to ePub and LyX to Mobi conversion



Last year we actually had a GSoC project specifically dealing with
ePub. Josh and Richard made progress on this front,

Did the progress include an Xhtml export that preserved semantics and
respected HTML semantics such as using h? for leveled headings, p
for paragraphs, and pre for lyx-code and environments derived from
it, and span for character styles? If you got that far and can write
it to disk, I can take it from there.


and the code
simply awaits someone with the motivation and the skills to finish the
job. The almost finished feature is available in several GIT branches
here: http://git.lyx.org/?p=gsoc.git;a=summary .

If I ever get a day or two to familiarize myself with it, I will. But
of course, I'm really lousy at C++, and in fact hate C++.

I think there are several missed opportunities:

1) If LyX insists on having a native format of XML, which by its nature
is human-confusing, it should at least be *well formed* XML so that
it can be handled by an XML parser, and if the programmer is more
skilled than I, XSLT. The day LyX native format is well formed, and
maybe even with a DTD, I'll make the converter: me, myself and I.


Unclear if this will ever happen. I started the project, but then got 
busy with other things. It is pretty monumental. But the goal would be 
to use Qt's built-in XML writing and reading, which means it will be 
well-formed.



2) The ePub converter shouldn't be a part of LyX: Most of it should be
standalone. There's no reason for LyX to need to know *anything*
about ePub. Just provide a sane Xhtml export, one that doesn't
substitute div for p, or p for h?, and calls a pre a
pre. Don't throw away the semantics: Don't convert styles to
appearances, and don't use div instead of HTML structural elements
like p, pre, and h?. Give me that, and I can do the rest.


That is what Josh did last summer. The XHTML -- ePub converter is 
written in Python.


Richard

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Liviu Andronic]

On Mon, Feb 3, 2014 at 8:02 PM, Richard Heck rgh...@lyx.org wrote:
 1) If LyX insists on having a native format of XML, which by its nature
 is human-confusing, it should at least be *well formed* XML so that
 it can be handled by an XML parser, and if the programmer is more
 skilled than I, XSLT. The day LyX native format is well formed, and
 maybe even with a DTD, I'll make the converter: me, myself and I.


 Unclear if this will ever happen. I started the project, but then got busy
 with other things. It is pretty monumental. But the goal would be to use
 Qt's built-in XML writing and reading, which means it will be well-formed.

The advantages to having an XML-based native format are numerous:
proper diff of LyX files; more standardized converters to and from
other XML-based formats; tools like pLyX would likely benefit from
this standardization, too. Some of our long-standing issues would be
addressed by such a change, so well worth a try I'd say.

Liviu

Re: lyx 2.0.1: .tex import with use of .cls and .sty files

[Scott Kostyshak]

Hi Jörg,

This is possible but should not be expected to work perfectly. It
depends on whether LyX has a layout file for the class. My suggestions
to you are to upgrade to a newer version of LyX (the importing of .tex
files gets better each version), and if you  have a problem, post an
enhancement request *with an example* of a .tex file you tried to
import (or make up a minimal example) and the error you got at
http://www.lyx.org/trac

Best,

Scott

On Mon, Feb 3, 2014 at 1:54 PM, Jörg Kühne joerg.kue...@gmx.net wrote:
 Dear user list

 Is it generally possible to import a .tex with use of .cls and .sty files to
 Lyx?
 If I import the example.tex to Lyx,
  Lyx creates line breaks as follows:


 \cventry{2011--2012}



 {Masters of Commerce}{The University of California}{Berkeley}{\textit{GPA

 -- 8.0}}{First Class Honours} % Arguments not required can be left empty



 What can I do to avoid such errors in Lyx?



 Regards



 Joerg

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Chris Menzel]

On 01/29/14, 02:41 , Richard Heck wrote:
...We have had
 this problem before, and there are other issues about Cocoa versus
 whatever versus whatever else. It is difficult to test every
 combination, and we have only a couple active OSX developers. Many
 of them use trunk (2.1.dev) for obvious sorts of reasons. So,
 well, we could really use a couple people who could test the OSX
 version on a more regular basis.

Well, I'm running 2.1.0 dev (with good stability) on both OS X 10.9
and Linux on a Chromebook (thanks to Crouton). Tell me what to do to
help.

-chris

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Steve Litt]

On Mon, 3 Feb 2014 20:39:09 +0100
Liviu Andronic landronim...@gmail.com wrote:

 On Mon, Feb 3, 2014 at 8:02 PM, Richard Heck rgh...@lyx.org wrote:
  1) If LyX insists on having a native format of XML, which by its
  nature is human-confusing, it should at least be *well formed* XML
  so that it can be handled by an XML parser, and if the programmer
  is more skilled than I, XSLT. The day LyX native format is well
  formed, and maybe even with a DTD, I'll make the converter: me,
  myself and I.
 
 
  Unclear if this will ever happen. I started the project, but then
  got busy with other things. It is pretty monumental. But the goal
  would be to use Qt's built-in XML writing and reading, which means
  it will be well-formed.
 
 The advantages to having an XML-based native format are numerous:
 proper diff of LyX files; more standardized converters to and from
 other XML-based formats; tools like pLyX would likely benefit from
 this standardization, too. Some of our long-standing issues would be
 addressed by such a change, so well worth a try I'd say.

Liviu,

You *do* mean *well formed* XML-based native format, right?

Yeah, we might as well: We've already done about all the human
readability damage we can do to the format. If it were well formed, at
least it would be simple to make a pretty-print for it.

If we *do* get well formed XML for LyX files, at the same time we
should probably make layout files XML too.  Each paragraph character and
character style (do we really still want to call paragraph styles by
the LaTeX centric name environment?) would have one section
describing its appearance in LyX, and sections describing its
appearance in each of several other output formats. The one for LaTeX
would be LaTeX. The one for Xhtml would be CSS. If it were done like
this, an arbitrary conversion program for a new format could just
list the styles, show the file with those styles applied, and allow the
converter program to supply its own definitions of each style.

This would go a long way toward changing the mission statement of LyX
from a front end for LaTeX to the fastest and easiest way to author
absolutely anything.

SteveT

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

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Steve Litt]

On Mon, 3 Feb 2014 20:20:03 -0500
Steve Litt sl...@troubleshooters.com wrote:


 Liviu,
 
 You *do* mean *well formed* XML-based native format, right?
 
 Yeah, we might as well: We've already done about all the human
 readability damage we can do to the format. If it were well formed, at
 least it would be simple to make a pretty-print for it.

My apologies, everyone, the preceding is a false statement on my part.

I just created a brand new LyX file in 2.0.6, which is the packaged LyX
for Ubuntu 13.10, and there wasn't a bit of XML in it, well formed or
otherwise. It was basically the same format human parseable format it's
been for 10 years, but with a lot more insets and options. But as far
as I can tell, the newlines in the format are meaningful, meaning one
can do a line by line parse, although with today's proliferation of
great features, many implemented as insets, the parse isn't as simple
as it was in 2005.

SteveT

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

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Richard Heck]

On 02/03/2014 08:04 PM, Chris Menzel wrote:

On 01/29/14, 02:41 , Richard Heck wrote:

...We have had
this problem before, and there are other issues about Cocoa versus
whatever versus whatever else. It is difficult to test every
combination, and we have only a couple active OSX developers. Many
of them use trunk (2.1.dev) for obvious sorts of reasons. So,
well, we could really use a couple people who could test the OSX
version on a more regular basis.

Well, I'm running 2.1.0 dev (with good stability) on both OS X 10.9
and Linux on a Chromebook (thanks to Crouton). Tell me what to do to
help.


It has been suggested that someone produce a homebrew recipe that would 
allow more
ordinary users to compile and test the most recent versions, or even 
develop some
system that would produce nightly, or perhaps weekly, builds. It would 
be best if this
could be done for both trunk (2.1.dev) and branch (2.0.8dev, as things 
stand). Those
of us on Linux can do this fairly easily, of course, but it's harder for 
people on OSX
(or, God forbid, Windows). I confess that the one time I tried to 
compile LyX on OSX

I failed and gave up.

Richard

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Liviu Andronic]

On Tue, Feb 4, 2014 at 2:38 AM, Steve Litt sl...@troubleshooters.com wrote:
 On Mon, 3 Feb 2014 20:20:03 -0500
 Steve Litt sl...@troubleshooters.com wrote:


 Liviu,

 You *do* mean *well formed* XML-based native format, right?

 Yeah, we might as well: We've already done about all the human
 readability damage we can do to the format. If it were well formed, at
 least it would be simple to make a pretty-print for it.

 My apologies, everyone, the preceding is a false statement on my part.

 I just created a brand new LyX file in 2.0.6, which is the packaged LyX
 for Ubuntu 13.10, and there wasn't a bit of XML in it, well formed or
 otherwise. It was basically the same format human parseable format it's
 been for 10 years, but with a lot more insets and options. But as far

Quick question: What are your reasons / needs for being able to
humanly parse the file format? Would a tool like pLyX address these
needs: http://wiki.lyx.org/Examples/FindAndReplaceLyXFormatElements ?

Liviu

 as I can tell, the newlines in the format are meaningful, meaning one
 can do a line by line parse, although with today's proliferation of
 great features, many implemented as insets, the parse isn't as simple
 as it was in 2005.

 SteveT

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



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Can't Export PDF from LyX

[Rizwan khan Jadoon]

I just installed Lyx 2.0  and I can't export any PDFs, although the message
at the bottom says, Successful export to format: pdf2. I'm running
Windows 7 32bit operating system and have both Acrobat Reader 10 and Foxit
Reader installed, with Foxit being the default.  Also, the only options I'm
seeing under Preferences  File Handling  File Formats  PDF (pdflatex)
are None and Custom.  Please help.

Thanks,
Rizwan khan jadoon

-- 
-
Rizwan khan jadoon
MS student

Re: Can't Export PDF from LyX

[Stephan Witt]

Am 03.02.2014 um 09:17 schrieb Rizwan khan Jadoon 
jadoon.rizwankha...@gmail.com:

 I just installed Lyx 2.0  and I can't export any PDFs, although the message 
 at the bottom says, Successful export to format: pdf2. I'm running Windows 
 7 32bit operating system and have both Acrobat Reader 10 and Foxit Reader 
 installed, with Foxit being the default.  Also, the only options I'm seeing 
 under Preferences  File Handling  File Formats  PDF (pdflatex) are None 
 and Custom.  Please help.

What does not work for you exactly?

Export produces an PDF file and saves it into the folder of the main document.

In case you're expecting the viewer opening your output document you shouldn't 
use Export.
Please use View for that task.

Stephan

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 01/31/14, 20:28 , Rainer M Krug wrote:
 
 
 Le vendredi 31 janvier 2014, Richard Heck rgh...@lyx.org 
 mailto:rgh...@lyx.org a écrit :
 
 On 01/30/2014 03:04 AM, Rainer M Krug wrote:
 
 On 01/29/14, 02:41 , Richard Heck wrote:
 
 On 01/28/2014 03:14 PM, Scott Kostyshak wrote:
 
 This should be fixed shortly and a new installer will be uploaded.
 
 As often, this is due to changes in the underlying Qt platform that
 seem to exist only on certain versions of OSX. We have had this
 problem before, and there are other issues about Cocoa versus 
 whatever versus whatever else. It is difficult to test every 
 combination, and we have only a couple active OSX developers. Many 
 of them use trunk (2.1.dev) for obvious sorts of reasons. So, well,
 we could really use a couple people who could test the OSX version
 on a more regular basis.
 
 To facilitate this, may I suggest to create a homebrew recipe to 
 facilitate the installation and update of the latest LyX? At least
 for me, I would likely use (and update) it regularly  as it is no
 hassle at all (in contrast to downloading and installing, or even
 compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how to 
 use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be interested
 in helping. But apparently, it is not that difficult.

I am using this to the devel lits as this does not (yet?) concern a
normal user.

Looking into this, I am wondering: what are the settings to create the
LyX binary for Mac? I could not find a hotwo on how to compile on mac?

Cheers,

Rainer


 
 Cheers,
 
 Rainer
 
 
 
 rh
 
 
 
 
 -- NEW GERMAN FAX NUMBER!!!
 
 Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation 
 Biology, UCT), Dipl. Phys. (Germany)
 
 Centre of Excellence for Invasion Biology Natural Sciences
 Building Office Suite 2039 Stellenbosch University Main Campus,
 Merriman Avenue Stellenbosch South Africa
 
 Cell:   +27 - (0)83 9479 042 Fax:+27 - (0)86
 516 2782 Fax:+49 - (0)321 2125 2244 email:
 rai...@krugs.de mailto:rai...@krugs.de
 
 Skype:  RMkrug Google: r.m.k...@gmail.com
 mailto:r.m.k...@gmail.com
 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEbBAEBAgAGBQJS72ezAAoJENvXNx4PUvmCMiMH+KTsEB7QKNoXQtDwVfTrFUuZ
GEyhhOVHFFpWY9tsDEaGtzFDoCRFL8gPtyxdSKurQiL9zg+WCg6vQdJK02PIhl9d
FvaQWzMEE71JhUJeHiSJyJc/jI38EeObZthnnOqf8BW8hpgbZOPdic5HWokGR1QP
oy02Y42z4/25PaHMu7Q3ZntQZc+Ix8/imBIXUrsYbXYiCx56RQleoOWH0gddznKa
06HbiDmQ4ff9JrqACWzhGunZQxmRUmbcxT9KvnlWisJp7KMTm4IPJxpMgGGZre4Z
W7IvLVq19eXk9ADjmol/zDjIEmAIiy7tJg/q10XECY997ML3hB6XKmAdzrnfJA==
=0uWO
-END PGP SIGNATURE-

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Stephan Witt]

Am 03.02.2014 um 10:56 schrieb Rainer M Krug rai...@krugs.de:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 
 
 On 01/31/14, 20:28 , Rainer M Krug wrote:
 
 
 Le vendredi 31 janvier 2014, Richard Heck rgh...@lyx.org 
 mailto:rgh...@lyx.org a écrit :
 
 On 01/30/2014 03:04 AM, Rainer M Krug wrote:
 
 On 01/29/14, 02:41 , Richard Heck wrote:
 
 On 01/28/2014 03:14 PM, Scott Kostyshak wrote:
 
 This should be fixed shortly and a new installer will be uploaded.
 
 As often, this is due to changes in the underlying Qt platform that
 seem to exist only on certain versions of OSX. We have had this
 problem before, and there are other issues about Cocoa versus 
 whatever versus whatever else. It is difficult to test every 
 combination, and we have only a couple active OSX developers. Many 
 of them use trunk (2.1.dev) for obvious sorts of reasons. So, well,
 we could really use a couple people who could test the OSX version
 on a more regular basis.
 
 To facilitate this, may I suggest to create a homebrew recipe to 
 facilitate the installation and update of the latest LyX? At least
 for me, I would likely use (and update) it regularly  as it is no
 hassle at all (in contrast to downloading and installing, or even
 compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how to 
 use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be interested
 in helping. But apparently, it is not that difficult.
 
 I am using this to the devel lits as this does not (yet?) concern a
 normal user.
 
 Looking into this, I am wondering: what are the settings to create the
 LyX binary for Mac? I could not find a hotwo on how to compile on mac?

Possibly a little bit outdated - but did you consider INSTALL.MacOSX?

Stephan

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 02/03/14, 11:07 , Stephan Witt wrote:
 Am 03.02.2014 um 10:56 schrieb Rainer M Krug rai...@krugs.de:
 
 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
 
 
 
 On 01/31/14, 20:28 , Rainer M Krug wrote:
 
 
 Le vendredi 31 janvier 2014, Richard Heck rgh...@lyx.org 
 mailto:rgh...@lyx.org a écrit :
 
 On 01/30/2014 03:04 AM, Rainer M Krug wrote:
 
 On 01/29/14, 02:41 , Richard Heck wrote:
 
 On 01/28/2014 03:14 PM, Scott Kostyshak wrote:
 
 This should be fixed shortly and a new installer will be
 uploaded.
 
 As often, this is due to changes in the underlying Qt platform
 that seem to exist only on certain versions of OSX. We have had
 this problem before, and there are other issues about Cocoa
 versus whatever versus whatever else. It is difficult to test
 every combination, and we have only a couple active OSX
 developers. Many of them use trunk (2.1.dev) for obvious sorts
 of reasons. So, well, we could really use a couple people who
 could test the OSX version on a more regular basis.
 
 To facilitate this, may I suggest to create a homebrew recipe
 to facilitate the installation and update of the latest LyX? At
 least for me, I would likely use (and update) it regularly  as
 it is no hassle at all (in contrast to downloading and
 installing, or even compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how
 to use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be
 interested in helping. But apparently, it is not that
 difficult.
 
 I am using this to the devel lits as this does not (yet?) concern
 a normal user.
 
 Looking into this, I am wondering: what are the settings to
 create the LyX binary for Mac? I could not find a hotwo on how to
 compile on mac?
 
 Possibly a little bit outdated - but did you consider
 INSTALL.MacOSX?

Shame on me - there it is, in the obvious place.

Thanks, I'll look into it,

Rainer

 
 Stephan
 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS73C6AAoJENvXNx4PUvmC6WYIALVbED9DGwDNo5x7gYpImJCZ
38UW5FRanH8vB5//i6KKBNFsT6/bNCBp4gcR0LjdppGWgM1fgnCBw+TUtDLDPL3j
FYOw7D71+5lQAMT+ZgkVwQX0hrGCF2AJa1vYEUfJygrSv48VrMHDdYpCaLAw/zj6
imqgk/rx6pzaml3otn+BdqGIFzrkhLkfeS+VF08WIWXBhcLOZDG1EFLhBzgagLsd
FP1PI3b0jH8O5xKu5UHrxGCVjVOOx1ZG7hhOXz5EknaPtgGaaOEUc3mdlfpfjIXR
TFD0F47n8jpuGHSqjAJ1EARvUKqZaijQkDnafE0gL9asvscqplSehQaZuzn9Jns=
=stBe
-END PGP SIGNATURE-

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Stephan Witt]

Am 03.02.2014 um 11:34 schrieb Rainer M Krug rai...@krugs.de:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 
 
 On 02/03/14, 11:07 , Stephan Witt wrote:
 Am 03.02.2014 um 10:56 schrieb Rainer M Krug rai...@krugs.de:
 
 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
 
 
 
 On 01/31/14, 20:28 , Rainer M Krug wrote:
 
 
 Le vendredi 31 janvier 2014, Richard Heck rgh...@lyx.org 
 mailto:rgh...@lyx.org a écrit :
 
 On 01/30/2014 03:04 AM, Rainer M Krug wrote:
 
 On 01/29/14, 02:41 , Richard Heck wrote:
 
 On 01/28/2014 03:14 PM, Scott Kostyshak wrote:
 
 This should be fixed shortly and a new installer will be
 uploaded.
 
 As often, this is due to changes in the underlying Qt platform
 that seem to exist only on certain versions of OSX. We have had
 this problem before, and there are other issues about Cocoa
 versus whatever versus whatever else. It is difficult to test
 every combination, and we have only a couple active OSX
 developers. Many of them use trunk (2.1.dev) for obvious sorts
 of reasons. So, well, we could really use a couple people who
 could test the OSX version on a more regular basis.
 
 To facilitate this, may I suggest to create a homebrew recipe
 to facilitate the installation and update of the latest LyX? At
 least for me, I would likely use (and update) it regularly  as
 it is no hassle at all (in contrast to downloading and
 installing, or even compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how
 to use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be
 interested in helping. But apparently, it is not that
 difficult.
 
 I am using this to the devel lits as this does not (yet?) concern
 a normal user.
 
 Looking into this, I am wondering: what are the settings to
 create the LyX binary for Mac? I could not find a hotwo on how to
 compile on mac?
 
 Possibly a little bit outdated - but did you consider
 INSTALL.MacOSX?
 
 Shame on me - there it is, in the obvious place.
 
 Thanks, I'll look into it,

No problem. I'll happily update it's contents to reflect your
findings on this matter. For LyX 2.1.X e.g. the gettext requirement
doesn't exist anymore. The Qt version for production is 4.8.5.
For development I've tried 5.0, 5.1 and 5.2 too. 
Version 5.2 definitively doesn't work - the menu is missing
almost completely. On current Mac systems Qt-Carbon isn't
available anymore.

I'm using the script development/LyX-Mac-binary-release.sh.
Something like that (note the back slashes):

ARCH=x86_64
Qt4Version=4.8.5
Qt4API=-cocoa
LyXVersion=lyx-2.1.0beta2
QtConfigureOptions=-debug-and-release Qt4API=${Qt4API} 
Qt4Version=${Qt4Version} \
 sh ${LyXVersion}/development/LyX-Mac-binary-release.sh \
   --with-sdkroot=10.8 --with-macosx-target=10.6 --with-arch=${ARCH} \
   --with-qt4-dir=$HOME/lyx-build/qt-${Qt4Version}-frameworks${Qt4API}-${ARCH}

Stephan

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Richard Heck]

On 02/03/2014 01:53 AM, Liviu Andronic wrote:

Dear Steve and Alex,

On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt sl...@troubleshooters.com wrote:

On Fri, 31 Jan 2014 22:33:02 +0100
Alex Fernandez ely...@gmail.com wrote:

Ladies and gentlemen, if the preceding paragraph doesn't convince
us we need a good, solid, LyX to ePub and LyX to Mobi conversion



Last year we actually had a GSoC project specifically dealing with
ePub. Josh and Richard made progress on this front, and the code
simply awaits someone with the motivation and the skills to finish the
job. The almost finished feature is available in several GIT branches
here: http://git.lyx.org/?p=gsoc.git;a=summary .


Actually, mostly what this awaits is the release of 2.1, since the main 
work left is to integrate this into trunk. There are still bugs to be 
fixed, of course, in the underlying XHTML export routines, but that's 
always true. Most of the ones Steve mentioned earlier have already been 
fixed.


Richard

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Steve Litt]

On Mon, 03 Feb 2014 10:05:57 -0500
Richard Heck rgh...@lyx.org wrote:

 On 02/03/2014 01:53 AM, Liviu Andronic wrote:
  Dear Steve and Alex,
 
  On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt
  sl...@troubleshooters.com wrote:
  On Fri, 31 Jan 2014 22:33:02 +0100
  Alex Fernandez ely...@gmail.com wrote:
  Ladies and gentlemen, if the preceding paragraph doesn't convince
  us we need a good, solid, LyX to ePub and LyX to Mobi conversion
 
  Last year we actually had a GSoC project specifically dealing with
  ePub. Josh and Richard made progress on this front, and the code
  simply awaits someone with the motivation and the skills to finish
  the job. The almost finished feature is available in several GIT
  branches here: http://git.lyx.org/?p=gsoc.git;a=summary .
 
 Actually, mostly what this awaits is the release of 2.1, since the
 main work left is to integrate this into trunk. There are still bugs
 to be fixed, of course, in the underlying XHTML export routines, but
 that's always true. Most of the ones Steve mentioned earlier have
 already been fixed.
 
 Richard

The instant 2.1 comes out, I'll compile it separate from my
Ubuntu-provided LyX, and try it out.

Thanks,

SteveT

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

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Steve Litt]

On Mon, 3 Feb 2014 07:53:49 +0100
Liviu Andronic landronim...@gmail.com wrote:

 Dear Steve and Alex,
 
 On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt
 sl...@troubleshooters.com wrote:
  On Fri, 31 Jan 2014 22:33:02 +0100
  Alex Fernandez ely...@gmail.com wrote:
   Ladies and gentlemen, if the preceding paragraph doesn't convince
   us we need a good, solid, LyX to ePub and LyX to Mobi conversion
 
 
 Last year we actually had a GSoC project specifically dealing with
 ePub. Josh and Richard made progress on this front, 

Did the progress include an Xhtml export that preserved semantics and
respected HTML semantics such as using h? for leveled headings, p
for paragraphs, and pre for lyx-code and environments derived from
it, and span for character styles? If you got that far and can write
it to disk, I can take it from there.

 and the code
 simply awaits someone with the motivation and the skills to finish the
 job. The almost finished feature is available in several GIT branches
 here: http://git.lyx.org/?p=gsoc.git;a=summary .

If I ever get a day or two to familiarize myself with it, I will. But
of course, I'm really lousy at C++, and in fact hate C++.

I think there are several missed opportunities:

1) If LyX insists on having a native format of XML, which by its nature
   is human-confusing, it should at least be *well formed* XML so that
   it can be handled by an XML parser, and if the programmer is more
   skilled than I, XSLT. The day LyX native format is well formed, and
   maybe even with a DTD, I'll make the converter: me, myself and I.

2) The ePub converter shouldn't be a part of LyX: Most of it should be
   standalone. There's no reason for LyX to need to know *anything*
   about ePub. Just provide a sane Xhtml export, one that doesn't
   substitute div for p, or p for h?, and calls a pre a
   pre. Don't throw away the semantics: Don't convert styles to
   appearances, and don't use div instead of HTML structural elements
   like p, pre, and h?. Give me that, and I can do the rest.

3) I honestly don't think you're ever going to get one programmer to do
   this whole thing. The likelihood is infinitesimal of finding one
   person who: A) has a burning ePub itch to scratch and B) is great at
   C++ and C) Is familiar with LyX's code base. The way to do this
   is as a pipeline, where person A exports what person B needs, and
   person B converts that to what person C needs, etc. The beauty of
   this would be is that, as LyX changes, only person A would need to
   change his code, unless, of course, the rest of the chain needs an
   enhancement. The way I envision it would be either that person A
   would be the person who makes a sane Xhtml export, and person B is
   me. Or, perhaps, if LyX native format is ever well formed and valid
   XML, Person A is me, converting LyX to an Xhtml subset, and person B
   is me, converting the subset to ePub. That way, as LyX changed, I'd
   need to change only the first program.

4) Back when Josh was doing this, neither I nor Rob Oakes knew what we
   know about ePub today. If we had, we could have given Josh and his
   crew much better guidance about what was needed. If anybody wants to
   continue on the road to LyX-ePub, I suggest that person(s) ask us
   lots of questions.

Thanks,

SteveT

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

Lyx 2.1 Beta 2 and 32bit Mac

[Dominik Schmidt]

Hi

has the support for 32 Bit Mac machines been dropped? I am running a Core
Duo with Snow Leopard and the system refuses to install the latest beta.

Thanks for your help!

lyx 2.0.1: .tex import with use of .cls and .sty files

[Jörg Kühne]

Dear user list



Is it generally possible to import a .tex with use of .cls and .sty files to Lyx?

If I import the example.tex to Lyx,

Lyx creates line breaks as follows:







cventry{2011--2012}



{Masters of Commerce}{The University of California}{Berkeley}{textit{GPA

-- 8.0}}{First Class Honours} % Arguments not required can be left empty



What can I do to avoid such errors in Lyx?



Regards



Joerg

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Richard Heck]

On 02/03/2014 11:36 AM, Steve Litt wrote:

On Mon, 03 Feb 2014 10:05:57 -0500
Richard Heck rgh...@lyx.org wrote:


On 02/03/2014 01:53 AM, Liviu Andronic wrote:

Dear Steve and Alex,

On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt
sl...@troubleshooters.com wrote:

On Fri, 31 Jan 2014 22:33:02 +0100
Alex Fernandez ely...@gmail.com wrote:

Ladies and gentlemen, if the preceding paragraph doesn't convince
us we need a good, solid, LyX to ePub and LyX to Mobi conversion

Last year we actually had a GSoC project specifically dealing with
ePub. Josh and Richard made progress on this front, and the code
simply awaits someone with the motivation and the skills to finish
the job. The almost finished feature is available in several GIT
branches here: http://git.lyx.org/?p=gsoc.git;a=summary .

Actually, mostly what this awaits is the release of 2.1, since the
main work left is to integrate this into trunk. There are still bugs
to be fixed, of course, in the underlying XHTML export routines, but
that's always true. Most of the ones Steve mentioned earlier have
already been fixed.

Richard

The instant 2.1 comes out, I'll compile it separate from my
Ubuntu-provided LyX, and try it out.


Sorry, to be clear: The ePub stuff will not be in 2.1. It came too late 
for that. It will go into trunk shortly after 2.1 and be in 2.2, which 
we expect to follow 2.1 much more quickly than usual.


Richard



Thanks,

SteveT

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

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Richard Heck]

On 02/03/2014 11:34 AM, Steve Litt wrote:

On Mon, 3 Feb 2014 07:53:49 +0100
Liviu Andronic landronim...@gmail.com wrote:


Dear Steve and Alex,

On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt
sl...@troubleshooters.com wrote:

On Fri, 31 Jan 2014 22:33:02 +0100
Alex Fernandez ely...@gmail.com wrote:

Ladies and gentlemen, if the preceding paragraph doesn't convince
us we need a good, solid, LyX to ePub and LyX to Mobi conversion



Last year we actually had a GSoC project specifically dealing with
ePub. Josh and Richard made progress on this front,

Did the progress include an Xhtml export that preserved semantics and
respected HTML semantics such as using h? for leveled headings, p
for paragraphs, and pre for lyx-code and environments derived from
it, and span for character styles? If you got that far and can write
it to disk, I can take it from there.


and the code
simply awaits someone with the motivation and the skills to finish the
job. The almost finished feature is available in several GIT branches
here: http://git.lyx.org/?p=gsoc.git;a=summary .

If I ever get a day or two to familiarize myself with it, I will. But
of course, I'm really lousy at C++, and in fact hate C++.

I think there are several missed opportunities:

1) If LyX insists on having a native format of XML, which by its nature
is human-confusing, it should at least be *well formed* XML so that
it can be handled by an XML parser, and if the programmer is more
skilled than I, XSLT. The day LyX native format is well formed, and
maybe even with a DTD, I'll make the converter: me, myself and I.


Unclear if this will ever happen. I started the project, but then got 
busy with other things. It is pretty monumental. But the goal would be 
to use Qt's built-in XML writing and reading, which means it will be 
well-formed.



2) The ePub converter shouldn't be a part of LyX: Most of it should be
standalone. There's no reason for LyX to need to know *anything*
about ePub. Just provide a sane Xhtml export, one that doesn't
substitute div for p, or p for h?, and calls a pre a
pre. Don't throw away the semantics: Don't convert styles to
appearances, and don't use div instead of HTML structural elements
like p, pre, and h?. Give me that, and I can do the rest.


That is what Josh did last summer. The XHTML -- ePub converter is 
written in Python.


Richard

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Liviu Andronic]

On Mon, Feb 3, 2014 at 8:02 PM, Richard Heck rgh...@lyx.org wrote:
 1) If LyX insists on having a native format of XML, which by its nature
 is human-confusing, it should at least be *well formed* XML so that
 it can be handled by an XML parser, and if the programmer is more
 skilled than I, XSLT. The day LyX native format is well formed, and
 maybe even with a DTD, I'll make the converter: me, myself and I.


 Unclear if this will ever happen. I started the project, but then got busy
 with other things. It is pretty monumental. But the goal would be to use
 Qt's built-in XML writing and reading, which means it will be well-formed.

The advantages to having an XML-based native format are numerous:
proper diff of LyX files; more standardized converters to and from
other XML-based formats; tools like pLyX would likely benefit from
this standardization, too. Some of our long-standing issues would be
addressed by such a change, so well worth a try I'd say.

Liviu

Re: lyx 2.0.1: .tex import with use of .cls and .sty files

[Scott Kostyshak]

Hi Jörg,

This is possible but should not be expected to work perfectly. It
depends on whether LyX has a layout file for the class. My suggestions
to you are to upgrade to a newer version of LyX (the importing of .tex
files gets better each version), and if you  have a problem, post an
enhancement request *with an example* of a .tex file you tried to
import (or make up a minimal example) and the error you got at
http://www.lyx.org/trac

Best,

Scott

On Mon, Feb 3, 2014 at 1:54 PM, Jörg Kühne joerg.kue...@gmx.net wrote:
 Dear user list

 Is it generally possible to import a .tex with use of .cls and .sty files to
 Lyx?
 If I import the example.tex to Lyx,
  Lyx creates line breaks as follows:


 \cventry{2011--2012}



 {Masters of Commerce}{The University of California}{Berkeley}{\textit{GPA

 -- 8.0}}{First Class Honours} % Arguments not required can be left empty



 What can I do to avoid such errors in Lyx?



 Regards



 Joerg

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Chris Menzel]

On 01/29/14, 02:41 , Richard Heck wrote:
...We have had
 this problem before, and there are other issues about Cocoa versus
 whatever versus whatever else. It is difficult to test every
 combination, and we have only a couple active OSX developers. Many
 of them use trunk (2.1.dev) for obvious sorts of reasons. So,
 well, we could really use a couple people who could test the OSX
 version on a more regular basis.

Well, I'm running 2.1.0 dev (with good stability) on both OS X 10.9
and Linux on a Chromebook (thanks to Crouton). Tell me what to do to
help.

-chris

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Steve Litt]

On Mon, 3 Feb 2014 20:39:09 +0100
Liviu Andronic landronim...@gmail.com wrote:

 On Mon, Feb 3, 2014 at 8:02 PM, Richard Heck rgh...@lyx.org wrote:
  1) If LyX insists on having a native format of XML, which by its
  nature is human-confusing, it should at least be *well formed* XML
  so that it can be handled by an XML parser, and if the programmer
  is more skilled than I, XSLT. The day LyX native format is well
  formed, and maybe even with a DTD, I'll make the converter: me,
  myself and I.
 
 
  Unclear if this will ever happen. I started the project, but then
  got busy with other things. It is pretty monumental. But the goal
  would be to use Qt's built-in XML writing and reading, which means
  it will be well-formed.
 
 The advantages to having an XML-based native format are numerous:
 proper diff of LyX files; more standardized converters to and from
 other XML-based formats; tools like pLyX would likely benefit from
 this standardization, too. Some of our long-standing issues would be
 addressed by such a change, so well worth a try I'd say.

Liviu,

You *do* mean *well formed* XML-based native format, right?

Yeah, we might as well: We've already done about all the human
readability damage we can do to the format. If it were well formed, at
least it would be simple to make a pretty-print for it.

If we *do* get well formed XML for LyX files, at the same time we
should probably make layout files XML too.  Each paragraph character and
character style (do we really still want to call paragraph styles by
the LaTeX centric name environment?) would have one section
describing its appearance in LyX, and sections describing its
appearance in each of several other output formats. The one for LaTeX
would be LaTeX. The one for Xhtml would be CSS. If it were done like
this, an arbitrary conversion program for a new format could just
list the styles, show the file with those styles applied, and allow the
converter program to supply its own definitions of each style.

This would go a long way toward changing the mission statement of LyX
from a front end for LaTeX to the fastest and easiest way to author
absolutely anything.

SteveT

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

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Steve Litt]

On Mon, 3 Feb 2014 20:20:03 -0500
Steve Litt sl...@troubleshooters.com wrote:


 Liviu,
 
 You *do* mean *well formed* XML-based native format, right?
 
 Yeah, we might as well: We've already done about all the human
 readability damage we can do to the format. If it were well formed, at
 least it would be simple to make a pretty-print for it.

My apologies, everyone, the preceding is a false statement on my part.

I just created a brand new LyX file in 2.0.6, which is the packaged LyX
for Ubuntu 13.10, and there wasn't a bit of XML in it, well formed or
otherwise. It was basically the same format human parseable format it's
been for 10 years, but with a lot more insets and options. But as far
as I can tell, the newlines in the format are meaningful, meaning one
can do a line by line parse, although with today's proliferation of
great features, many implemented as insets, the parse isn't as simple
as it was in 2005.

SteveT

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

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Richard Heck]

On 02/03/2014 08:04 PM, Chris Menzel wrote:

On 01/29/14, 02:41 , Richard Heck wrote:

...We have had
this problem before, and there are other issues about Cocoa versus
whatever versus whatever else. It is difficult to test every
combination, and we have only a couple active OSX developers. Many
of them use trunk (2.1.dev) for obvious sorts of reasons. So,
well, we could really use a couple people who could test the OSX
version on a more regular basis.

Well, I'm running 2.1.0 dev (with good stability) on both OS X 10.9
and Linux on a Chromebook (thanks to Crouton). Tell me what to do to
help.


It has been suggested that someone produce a homebrew recipe that would 
allow more
ordinary users to compile and test the most recent versions, or even 
develop some
system that would produce nightly, or perhaps weekly, builds. It would 
be best if this
could be done for both trunk (2.1.dev) and branch (2.0.8dev, as things 
stand). Those
of us on Linux can do this fairly easily, of course, but it's harder for 
people on OSX
(or, God forbid, Windows). I confess that the one time I tried to 
compile LyX on OSX

I failed and gave up.

Richard

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Liviu Andronic]

On Tue, Feb 4, 2014 at 2:38 AM, Steve Litt sl...@troubleshooters.com wrote:
 On Mon, 3 Feb 2014 20:20:03 -0500
 Steve Litt sl...@troubleshooters.com wrote:


 Liviu,

 You *do* mean *well formed* XML-based native format, right?

 Yeah, we might as well: We've already done about all the human
 readability damage we can do to the format. If it were well formed, at
 least it would be simple to make a pretty-print for it.

 My apologies, everyone, the preceding is a false statement on my part.

 I just created a brand new LyX file in 2.0.6, which is the packaged LyX
 for Ubuntu 13.10, and there wasn't a bit of XML in it, well formed or
 otherwise. It was basically the same format human parseable format it's
 been for 10 years, but with a lot more insets and options. But as far

Quick question: What are your reasons / needs for being able to
humanly parse the file format? Would a tool like pLyX address these
needs: http://wiki.lyx.org/Examples/FindAndReplaceLyXFormatElements ?

Liviu

 as I can tell, the newlines in the format are meaningful, meaning one
 can do a line by line parse, although with today's proliferation of
 great features, many implemented as insets, the parse isn't as simple
 as it was in 2005.

 SteveT

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



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Can't Export PDF from LyX

[Rizwan khan Jadoon]

I just installed Lyx 2.0  and I can't export any PDFs, although the message
at the bottom says, "Successful export to format: pdf2". I'm running
Windows 7 32bit operating system and have both Acrobat Reader 10 and Foxit
Reader installed, with Foxit being the default.  Also, the only options I'm
seeing under Preferences > File Handling > File Formats > PDF (pdflatex)
are "None" and "Custom".  Please help.

Thanks,
Rizwan khan jadoon

-- 
-
Rizwan khan jadoon
MS student

Re: Can't Export PDF from LyX

[Stephan Witt]

Am 03.02.2014 um 09:17 schrieb Rizwan khan Jadoon 
:

> I just installed Lyx 2.0  and I can't export any PDFs, although the message 
> at the bottom says, "Successful export to format: pdf2". I'm running Windows 
> 7 32bit operating system and have both Acrobat Reader 10 and Foxit Reader 
> installed, with Foxit being the default.  Also, the only options I'm seeing 
> under Preferences > File Handling > File Formats > PDF (pdflatex) are "None" 
> and "Custom".  Please help.

What does not work for you exactly?

Export produces an PDF file and saves it into the folder of the main document.

In case you're expecting the viewer opening your output document you shouldn't 
use "Export".
Please use "View" for that task.

Stephan

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 01/31/14, 20:28 , Rainer M Krug wrote:
> 
> 
> Le vendredi 31 janvier 2014, Richard Heck  > a écrit :
> 
> On 01/30/2014 03:04 AM, Rainer M Krug wrote:
> 
> On 01/29/14, 02:41 , Richard Heck wrote:
> 
> On 01/28/2014 03:14 PM, Scott Kostyshak wrote:
> 
> This should be fixed shortly and a new installer will be uploaded.
> 
> As often, this is due to changes in the underlying Qt platform that
> seem to exist only on certain versions of OSX. We have had this
> problem before, and there are other issues about Cocoa versus 
> whatever versus whatever else. It is difficult to test every 
> combination, and we have only a couple active OSX developers. Many 
> of them use trunk (2.1.dev) for obvious sorts of reasons. So, well,
> we could really use a couple people who could test the OSX version
> on a more regular basis.
> 
> To facilitate this, may I suggest to create a homebrew recipe to 
> facilitate the installation and update of the latest LyX? At least
> for me, I would likely use (and update) it regularly  as it is no
> hassle at all (in contrast to downloading and installing, or even
> compiling first.
> 
> 
> This is a great idea, but of course someone on OSX who knew how to 
> use homebrew would need to do it.
> 
> 
> I'll ask on the homebrew list if there would somebody be interested
> in helping. But apparently, it is not that difficult.

I am using this to the devel lits as this does not (yet?) concern a
"normal" user.

Looking into this, I am wondering: what are the settings to create the
LyX binary for Mac? I could not find a hotwo on how to compile on mac?

Cheers,

Rainer


> 
> Cheers,
> 
> Rainer
> 
> 
> 
> rh
> 
> 
> 
> 
> -- NEW GERMAN FAX NUMBER!!!
> 
> Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation 
> Biology, UCT), Dipl. Phys. (Germany)
> 
> Centre of Excellence for Invasion Biology Natural Sciences
> Building Office Suite 2039 Stellenbosch University Main Campus,
> Merriman Avenue Stellenbosch South Africa
> 
> Cell:   +27 - (0)83 9479 042 Fax:+27 - (0)86
> 516 2782 Fax:+49 - (0)321 2125 2244 email:
> rai...@krugs.de 
> 
> Skype:  RMkrug Google: r.m.k...@gmail.com
> 
> 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEbBAEBAgAGBQJS72ezAAoJENvXNx4PUvmCMiMH+KTsEB7QKNoXQtDwVfTrFUuZ
GEyhhOVHFFpWY9tsDEaGtzFDoCRFL8gPtyxdSKurQiL9zg+WCg6vQdJK02PIhl9d
FvaQWzMEE71JhUJeHiSJyJc/jI38EeObZthnnOqf8BW8hpgbZOPdic5HWokGR1QP
oy02Y42z4/25PaHMu7Q3ZntQZc+Ix8/imBIXUrsYbXYiCx56RQleoOWH0gddznKa
06HbiDmQ4ff9JrqACWzhGunZQxmRUmbcxT9KvnlWisJp7KMTm4IPJxpMgGGZre4Z
W7IvLVq19eXk9ADjmol/zDjIEmAIiy7tJg/q10XECY997ML3hB6XKmAdzrnfJA==
=0uWO
-END PGP SIGNATURE-

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Stephan Witt]

Am 03.02.2014 um 10:56 schrieb Rainer M Krug :

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> 
> 
> On 01/31/14, 20:28 , Rainer M Krug wrote:
>> 
>> 
>> Le vendredi 31 janvier 2014, Richard Heck > > a écrit :
>> 
>> On 01/30/2014 03:04 AM, Rainer M Krug wrote:
>> 
>> On 01/29/14, 02:41 , Richard Heck wrote:
>> 
>> On 01/28/2014 03:14 PM, Scott Kostyshak wrote:
>> 
>> This should be fixed shortly and a new installer will be uploaded.
>> 
>> As often, this is due to changes in the underlying Qt platform that
>> seem to exist only on certain versions of OSX. We have had this
>> problem before, and there are other issues about Cocoa versus 
>> whatever versus whatever else. It is difficult to test every 
>> combination, and we have only a couple active OSX developers. Many 
>> of them use trunk (2.1.dev) for obvious sorts of reasons. So, well,
>> we could really use a couple people who could test the OSX version
>> on a more regular basis.
>> 
>> To facilitate this, may I suggest to create a homebrew recipe to 
>> facilitate the installation and update of the latest LyX? At least
>> for me, I would likely use (and update) it regularly  as it is no
>> hassle at all (in contrast to downloading and installing, or even
>> compiling first.
>> 
>> 
>> This is a great idea, but of course someone on OSX who knew how to 
>> use homebrew would need to do it.
>> 
>> 
>> I'll ask on the homebrew list if there would somebody be interested
>> in helping. But apparently, it is not that difficult.
> 
> I am using this to the devel lits as this does not (yet?) concern a
> "normal" user.
> 
> Looking into this, I am wondering: what are the settings to create the
> LyX binary for Mac? I could not find a hotwo on how to compile on mac?

Possibly a little bit outdated - but did you consider INSTALL.MacOSX?

Stephan

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 02/03/14, 11:07 , Stephan Witt wrote:
> Am 03.02.2014 um 10:56 schrieb Rainer M Krug :
> 
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>> 
>> 
>> 
>> On 01/31/14, 20:28 , Rainer M Krug wrote:
>>> 
>>> 
>>> Le vendredi 31 janvier 2014, Richard Heck >> > a écrit :
>>> 
>>> On 01/30/2014 03:04 AM, Rainer M Krug wrote:
>>> 
>>> On 01/29/14, 02:41 , Richard Heck wrote:
>>> 
>>> On 01/28/2014 03:14 PM, Scott Kostyshak wrote:
>>> 
>>> This should be fixed shortly and a new installer will be
>>> uploaded.
>>> 
>>> As often, this is due to changes in the underlying Qt platform
>>> that seem to exist only on certain versions of OSX. We have had
>>> this problem before, and there are other issues about Cocoa
>>> versus whatever versus whatever else. It is difficult to test
>>> every combination, and we have only a couple active OSX
>>> developers. Many of them use trunk (2.1.dev) for obvious sorts
>>> of reasons. So, well, we could really use a couple people who
>>> could test the OSX version on a more regular basis.
>>> 
>>> To facilitate this, may I suggest to create a homebrew recipe
>>> to facilitate the installation and update of the latest LyX? At
>>> least for me, I would likely use (and update) it regularly  as
>>> it is no hassle at all (in contrast to downloading and
>>> installing, or even compiling first.
>>> 
>>> 
>>> This is a great idea, but of course someone on OSX who knew how
>>> to use homebrew would need to do it.
>>> 
>>> 
>>> I'll ask on the homebrew list if there would somebody be
>>> interested in helping. But apparently, it is not that
>>> difficult.
>> 
>> I am using this to the devel lits as this does not (yet?) concern
>> a "normal" user.
>> 
>> Looking into this, I am wondering: what are the settings to
>> create the LyX binary for Mac? I could not find a hotwo on how to
>> compile on mac?
> 
> Possibly a little bit outdated - but did you consider
> INSTALL.MacOSX?

Shame on me - there it is, in the obvious place.

Thanks, I'll look into it,

Rainer

> 
> Stephan
> 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS73C6AAoJENvXNx4PUvmC6WYIALVbED9DGwDNo5x7gYpImJCZ
38UW5FRanH8vB5//i6KKBNFsT6/bNCBp4gcR0LjdppGWgM1fgnCBw+TUtDLDPL3j
FYOw7D71+5lQAMT+ZgkVwQX0hrGCF2AJa1vYEUfJygrSv48VrMHDdYpCaLAw/zj6
imqgk/rx6pzaml3otn+BdqGIFzrkhLkfeS+VF08WIWXBhcLOZDG1EFLhBzgagLsd
FP1PI3b0jH8O5xKu5UHrxGCVjVOOx1ZG7hhOXz5EknaPtgGaaOEUc3mdlfpfjIXR
TFD0F47n8jpuGHSqjAJ1EARvUKqZaijQkDnafE0gL9asvscqplSehQaZuzn9Jns=
=stBe
-END PGP SIGNATURE-

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Stephan Witt]

Am 03.02.2014 um 11:34 schrieb Rainer M Krug :

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> 
> 
> On 02/03/14, 11:07 , Stephan Witt wrote:
>> Am 03.02.2014 um 10:56 schrieb Rainer M Krug :
>> 
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>> 
>>> 
>>> 
>>> On 01/31/14, 20:28 , Rainer M Krug wrote:
 
 
 Le vendredi 31 janvier 2014, Richard Heck > a écrit :
 
 On 01/30/2014 03:04 AM, Rainer M Krug wrote:
 
 On 01/29/14, 02:41 , Richard Heck wrote:
 
 On 01/28/2014 03:14 PM, Scott Kostyshak wrote:
 
 This should be fixed shortly and a new installer will be
 uploaded.
 
 As often, this is due to changes in the underlying Qt platform
 that seem to exist only on certain versions of OSX. We have had
 this problem before, and there are other issues about Cocoa
 versus whatever versus whatever else. It is difficult to test
 every combination, and we have only a couple active OSX
 developers. Many of them use trunk (2.1.dev) for obvious sorts
 of reasons. So, well, we could really use a couple people who
 could test the OSX version on a more regular basis.
 
 To facilitate this, may I suggest to create a homebrew recipe
 to facilitate the installation and update of the latest LyX? At
 least for me, I would likely use (and update) it regularly  as
 it is no hassle at all (in contrast to downloading and
 installing, or even compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how
 to use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be
 interested in helping. But apparently, it is not that
 difficult.
>>> 
>>> I am using this to the devel lits as this does not (yet?) concern
>>> a "normal" user.
>>> 
>>> Looking into this, I am wondering: what are the settings to
>>> create the LyX binary for Mac? I could not find a hotwo on how to
>>> compile on mac?
>> 
>> Possibly a little bit outdated - but did you consider
>> INSTALL.MacOSX?
> 
> Shame on me - there it is, in the obvious place.
> 
> Thanks, I'll look into it,

No problem. I'll happily update it's contents to reflect your
findings on this matter. For LyX 2.1.X e.g. the gettext requirement
doesn't exist anymore. The Qt version for production is 4.8.5.
For development I've tried 5.0, 5.1 and 5.2 too. 
Version 5.2 definitively doesn't work - the menu is missing
almost completely. On current Mac systems Qt-Carbon isn't
available anymore.

I'm using the script development/LyX-Mac-binary-release.sh.
Something like that (note the back slashes):

ARCH=x86_64
Qt4Version=4.8.5
Qt4API=-cocoa
LyXVersion=lyx-2.1.0beta2
QtConfigureOptions="-debug-and-release" Qt4API=${Qt4API} 
Qt4Version=${Qt4Version} \
 sh ${LyXVersion}/development/LyX-Mac-binary-release.sh \
   --with-sdkroot=10.8 --with-macosx-target=10.6 --with-arch=${ARCH} \
   --with-qt4-dir=$HOME/lyx-build/qt-${Qt4Version}-frameworks${Qt4API}-${ARCH}

Stephan

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Richard Heck]

On 02/03/2014 01:53 AM, Liviu Andronic wrote:

Dear Steve and Alex,

On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt  wrote:

On Fri, 31 Jan 2014 22:33:02 +0100
Alex Fernandez  wrote:

Ladies and gentlemen, if the preceding paragraph doesn't convince
us we need a good, solid, LyX to ePub and LyX to Mobi conversion



Last year we actually had a GSoC project specifically dealing with
ePub. Josh and Richard made progress on this front, and the code
simply awaits someone with the motivation and the skills to finish the
job. The almost finished feature is available in several GIT branches
here: http://git.lyx.org/?p=gsoc.git;a=summary .


Actually, mostly what this awaits is the release of 2.1, since the main 
work left is to integrate this into trunk. There are still bugs to be 
fixed, of course, in the underlying XHTML export routines, but that's 
always true. Most of the ones Steve mentioned earlier have already been 
fixed.


Richard

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Steve Litt]

On Mon, 03 Feb 2014 10:05:57 -0500
Richard Heck  wrote:

> On 02/03/2014 01:53 AM, Liviu Andronic wrote:
> > Dear Steve and Alex,
> >
> > On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt
> >  wrote:
> >> On Fri, 31 Jan 2014 22:33:02 +0100
> >> Alex Fernandez  wrote:
>  Ladies and gentlemen, if the preceding paragraph doesn't convince
>  us we need a good, solid, LyX to ePub and LyX to Mobi conversion
> >>
> > Last year we actually had a GSoC project specifically dealing with
> > ePub. Josh and Richard made progress on this front, and the code
> > simply awaits someone with the motivation and the skills to finish
> > the job. The almost finished feature is available in several GIT
> > branches here: http://git.lyx.org/?p=gsoc.git;a=summary .
> 
> Actually, mostly what this awaits is the release of 2.1, since the
> main work left is to integrate this into trunk. There are still bugs
> to be fixed, of course, in the underlying XHTML export routines, but
> that's always true. Most of the ones Steve mentioned earlier have
> already been fixed.
> 
> Richard

The instant 2.1 comes out, I'll compile it separate from my
Ubuntu-provided LyX, and try it out.

Thanks,

SteveT

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

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Steve Litt]

On Mon, 3 Feb 2014 07:53:49 +0100
Liviu Andronic  wrote:

> Dear Steve and Alex,
> 
> On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt
>  wrote:
> > On Fri, 31 Jan 2014 22:33:02 +0100
> > Alex Fernandez  wrote:
> >> > Ladies and gentlemen, if the preceding paragraph doesn't convince
> >> > us we need a good, solid, LyX to ePub and LyX to Mobi conversion
> >
> >
> Last year we actually had a GSoC project specifically dealing with
> ePub. Josh and Richard made progress on this front, 

Did the progress include an Xhtml export that preserved semantics and
respected HTML semantics such as using  for leveled headings, 
for paragraphs, and  for lyx-code and environments derived from
it, and  for character styles? If you got that far and can write
it to disk, I can take it from there.

> and the code
> simply awaits someone with the motivation and the skills to finish the
> job. The almost finished feature is available in several GIT branches
> here: http://git.lyx.org/?p=gsoc.git;a=summary .

If I ever get a day or two to familiarize myself with it, I will. But
of course, I'm really lousy at C++, and in fact hate C++.

I think there are several missed opportunities:

1) If LyX insists on having a native format of XML, which by its nature
   is human-confusing, it should at least be *well formed* XML so that
   it can be handled by an XML parser, and if the programmer is more
   skilled than I, XSLT. The day LyX native format is well formed, and
   maybe even with a DTD, I'll make the converter: me, myself and I.

2) The ePub converter shouldn't be a part of LyX: Most of it should be
   standalone. There's no reason for LyX to need to know *anything*
   about ePub. Just provide a sane Xhtml export, one that doesn't
   substitute  for , or  for , and calls a  a
   . Don't throw away the semantics: Don't convert styles to
   appearances, and don't use  instead of HTML structural elements
   like , , and . Give me that, and I can do the rest.

3) I honestly don't think you're ever going to get one programmer to do
   this whole thing. The likelihood is infinitesimal of finding one
   person who: A) has a burning ePub itch to scratch and B) is great at
   C++ and C) Is familiar with LyX's code base. The way to do this
   is as a pipeline, where person A exports what person B needs, and
   person B converts that to what person C needs, etc. The beauty of
   this would be is that, as LyX changes, only person A would need to
   change his code, unless, of course, the rest of the chain needs an
   enhancement. The way I envision it would be either that person A
   would be the person who makes a sane Xhtml export, and person B is
   me. Or, perhaps, if LyX native format is ever well formed and valid
   XML, Person A is me, converting LyX to an Xhtml subset, and person B
   is me, converting the subset to ePub. That way, as LyX changed, I'd
   need to change only the first program.

4) Back when Josh was doing this, neither I nor Rob Oakes knew what we
   know about ePub today. If we had, we could have given Josh and his
   crew much better guidance about what was needed. If anybody wants to
   continue on the road to LyX->ePub, I suggest that person(s) ask us
   lots of questions.

Thanks,

SteveT

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

Lyx 2.1 Beta 2 and 32bit Mac

[Dominik Schmidt]

Hi

has the support for 32 Bit Mac machines been dropped? I am running a Core
Duo with Snow Leopard and the system refuses to install the latest beta.

Thanks for your help!

lyx 2.0.1: .tex import with use of .cls and .sty files

[Jörg Kühne]

Dear user list

 

Is it generally possible to import a .tex with use of .cls and .sty files to Lyx?

If I import the example.tex to Lyx,

 Lyx creates line breaks as follows:



 



\cventry{2011--2012}

 

{Masters of Commerce}{The University of California}{Berkeley}{\textit{GPA

-- 8.0}}{First Class Honours} % Arguments not required can be left empty

 

What can I do to avoid such errors in Lyx?

 

Regards

 

Joerg

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Richard Heck]

On 02/03/2014 11:36 AM, Steve Litt wrote:

On Mon, 03 Feb 2014 10:05:57 -0500
Richard Heck  wrote:


On 02/03/2014 01:53 AM, Liviu Andronic wrote:

Dear Steve and Alex,

On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt
 wrote:

On Fri, 31 Jan 2014 22:33:02 +0100
Alex Fernandez  wrote:

Ladies and gentlemen, if the preceding paragraph doesn't convince
us we need a good, solid, LyX to ePub and LyX to Mobi conversion

Last year we actually had a GSoC project specifically dealing with
ePub. Josh and Richard made progress on this front, and the code
simply awaits someone with the motivation and the skills to finish
the job. The almost finished feature is available in several GIT
branches here: http://git.lyx.org/?p=gsoc.git;a=summary .

Actually, mostly what this awaits is the release of 2.1, since the
main work left is to integrate this into trunk. There are still bugs
to be fixed, of course, in the underlying XHTML export routines, but
that's always true. Most of the ones Steve mentioned earlier have
already been fixed.

Richard

The instant 2.1 comes out, I'll compile it separate from my
Ubuntu-provided LyX, and try it out.


Sorry, to be clear: The ePub stuff will not be in 2.1. It came too late 
for that. It will go into trunk shortly after 2.1 and be in 2.2, which 
we expect to follow 2.1 much more quickly than usual.


Richard



Thanks,

SteveT

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

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Richard Heck]

On 02/03/2014 11:34 AM, Steve Litt wrote:

On Mon, 3 Feb 2014 07:53:49 +0100
Liviu Andronic  wrote:


Dear Steve and Alex,

On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt
 wrote:

On Fri, 31 Jan 2014 22:33:02 +0100
Alex Fernandez  wrote:

Ladies and gentlemen, if the preceding paragraph doesn't convince
us we need a good, solid, LyX to ePub and LyX to Mobi conversion



Last year we actually had a GSoC project specifically dealing with
ePub. Josh and Richard made progress on this front,

Did the progress include an Xhtml export that preserved semantics and
respected HTML semantics such as using  for leveled headings, 
for paragraphs, and  for lyx-code and environments derived from
it, and  for character styles? If you got that far and can write
it to disk, I can take it from there.


and the code
simply awaits someone with the motivation and the skills to finish the
job. The almost finished feature is available in several GIT branches
here: http://git.lyx.org/?p=gsoc.git;a=summary .

If I ever get a day or two to familiarize myself with it, I will. But
of course, I'm really lousy at C++, and in fact hate C++.

I think there are several missed opportunities:

1) If LyX insists on having a native format of XML, which by its nature
is human-confusing, it should at least be *well formed* XML so that
it can be handled by an XML parser, and if the programmer is more
skilled than I, XSLT. The day LyX native format is well formed, and
maybe even with a DTD, I'll make the converter: me, myself and I.


Unclear if this will ever happen. I started the project, but then got 
busy with other things. It is pretty monumental. But the goal would be 
to use Qt's built-in XML writing and reading, which means it will be 
well-formed.



2) The ePub converter shouldn't be a part of LyX: Most of it should be
standalone. There's no reason for LyX to need to know *anything*
about ePub. Just provide a sane Xhtml export, one that doesn't
substitute  for , or  for , and calls a  a
. Don't throw away the semantics: Don't convert styles to
appearances, and don't use  instead of HTML structural elements
like , , and . Give me that, and I can do the rest.


That is what Josh did last summer. The XHTML --> ePub converter is 
written in Python.


Richard

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Liviu Andronic]

On Mon, Feb 3, 2014 at 8:02 PM, Richard Heck  wrote:
>> 1) If LyX insists on having a native format of XML, which by its nature
>> is human-confusing, it should at least be *well formed* XML so that
>> it can be handled by an XML parser, and if the programmer is more
>> skilled than I, XSLT. The day LyX native format is well formed, and
>> maybe even with a DTD, I'll make the converter: me, myself and I.
>
>
> Unclear if this will ever happen. I started the project, but then got busy
> with other things. It is pretty monumental. But the goal would be to use
> Qt's built-in XML writing and reading, which means it will be well-formed.
>
The advantages to having an XML-based native format are numerous:
proper diff of LyX files; more standardized converters to and from
other XML-based formats; tools like pLyX would likely benefit from
this standardization, too. Some of our long-standing issues would be
addressed by such a change, so well worth a try I'd say.

Liviu

Re: lyx 2.0.1: .tex import with use of .cls and .sty files

[Scott Kostyshak]

Hi Jörg,

This is possible but should not be expected to work perfectly. It
depends on whether LyX has a layout file for the class. My suggestions
to you are to upgrade to a newer version of LyX (the importing of .tex
files gets better each version), and if you  have a problem, post an
enhancement request *with an example* of a .tex file you tried to
import (or make up a minimal example) and the error you got at
http://www.lyx.org/trac

Best,

Scott

On Mon, Feb 3, 2014 at 1:54 PM, "Jörg Kühne"  wrote:
> Dear user list
>
> Is it generally possible to import a .tex with use of .cls and .sty files to
> Lyx?
> If I import the example.tex to Lyx,
>  Lyx creates line breaks as follows:
>
>
> \cventry{2011--2012}
>
>
>
> {Masters of Commerce}{The University of California}{Berkeley}{\textit{GPA
>
> -- 8.0}}{First Class Honours} % Arguments not required can be left empty
>
>
>
> What can I do to avoid such errors in Lyx?
>
>
>
> Regards
>
>
>
> Joerg

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Chris Menzel]

On 01/29/14, 02:41 , Richard Heck wrote:
>...We have had
> this problem before, and there are other issues about Cocoa versus
> whatever versus whatever else. It is difficult to test every
> combination, and we have only a couple active OSX developers. Many
> of them use trunk (2.1.dev) for obvious sorts of reasons. So,
> well, we could really use a couple people who could test the OSX
> version on a more regular basis.

Well, I'm running 2.1.0 dev (with good stability) on both OS X 10.9
and Linux on a Chromebook (thanks to Crouton). Tell me what to do to
help.

-chris

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Steve Litt]

On Mon, 3 Feb 2014 20:39:09 +0100
Liviu Andronic  wrote:

> On Mon, Feb 3, 2014 at 8:02 PM, Richard Heck  wrote:
> >> 1) If LyX insists on having a native format of XML, which by its
> >> nature is human-confusing, it should at least be *well formed* XML
> >> so that it can be handled by an XML parser, and if the programmer
> >> is more skilled than I, XSLT. The day LyX native format is well
> >> formed, and maybe even with a DTD, I'll make the converter: me,
> >> myself and I.
> >
> >
> > Unclear if this will ever happen. I started the project, but then
> > got busy with other things. It is pretty monumental. But the goal
> > would be to use Qt's built-in XML writing and reading, which means
> > it will be well-formed.
> >
> The advantages to having an XML-based native format are numerous:
> proper diff of LyX files; more standardized converters to and from
> other XML-based formats; tools like pLyX would likely benefit from
> this standardization, too. Some of our long-standing issues would be
> addressed by such a change, so well worth a try I'd say.

Liviu,

You *do* mean *well formed* XML-based native format, right?

Yeah, we might as well: We've already done about all the human
readability damage we can do to the format. If it were well formed, at
least it would be simple to make a pretty-print for it.

If we *do* get well formed XML for LyX files, at the same time we
should probably make layout files XML too.  Each paragraph character and
character style (do we really still want to call paragraph styles by
the LaTeX centric name "environment?") would have one section
describing its appearance in LyX, and sections describing its
appearance in each of several other output formats. The one for LaTeX
would be LaTeX. The one for Xhtml would be CSS. If it were done like
this, an arbitrary conversion program for a "new" format could just
list the styles, show the file with those styles applied, and allow the
converter program to supply its own definitions of each style.

This would go a long way toward changing the "mission statement" of LyX
from "a front end for LaTeX" to "the fastest and easiest way to author
absolutely anything".

SteveT

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

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Steve Litt]

On Mon, 3 Feb 2014 20:20:03 -0500
Steve Litt  wrote:


> Liviu,
> 
> You *do* mean *well formed* XML-based native format, right?
> 
> Yeah, we might as well: We've already done about all the human
> readability damage we can do to the format. If it were well formed, at
> least it would be simple to make a pretty-print for it.

My apologies, everyone, the preceding is a false statement on my part.

I just created a brand new LyX file in 2.0.6, which is the packaged LyX
for Ubuntu 13.10, and there wasn't a bit of XML in it, well formed or
otherwise. It was basically the same format human parseable format it's
been for 10 years, but with a lot more insets and options. But as far
as I can tell, the newlines in the format are meaningful, meaning one
can do a line by line parse, although with today's proliferation of
great features, many implemented as insets, the parse isn't as simple
as it was in 2005.

SteveT

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

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

[Richard Heck]

On 02/03/2014 08:04 PM, Chris Menzel wrote:

On 01/29/14, 02:41 , Richard Heck wrote:

...We have had
this problem before, and there are other issues about Cocoa versus
whatever versus whatever else. It is difficult to test every
combination, and we have only a couple active OSX developers. Many
of them use trunk (2.1.dev) for obvious sorts of reasons. So,
well, we could really use a couple people who could test the OSX
version on a more regular basis.

Well, I'm running 2.1.0 dev (with good stability) on both OS X 10.9
and Linux on a Chromebook (thanks to Crouton). Tell me what to do to
help.


It has been suggested that someone produce a homebrew recipe that would 
allow more
"ordinary users" to compile and test the most recent versions, or even 
develop some
system that would produce nightly, or perhaps weekly, builds. It would 
be best if this
could be done for both trunk (2.1.dev) and branch (2.0.8dev, as things 
stand). Those
of us on Linux can do this fairly easily, of course, but it's harder for 
people on OSX
(or, God forbid, Windows). I confess that the one time I tried to 
compile LyX on OSX

I failed and gave up.

Richard

Re: We need ePub/Mobi conversion: was: Book Frontmatter

[Liviu Andronic]

On Tue, Feb 4, 2014 at 2:38 AM, Steve Litt  wrote:
> On Mon, 3 Feb 2014 20:20:03 -0500
> Steve Litt  wrote:
>
>
>> Liviu,
>>
>> You *do* mean *well formed* XML-based native format, right?
>>
>> Yeah, we might as well: We've already done about all the human
>> readability damage we can do to the format. If it were well formed, at
>> least it would be simple to make a pretty-print for it.
>
> My apologies, everyone, the preceding is a false statement on my part.
>
> I just created a brand new LyX file in 2.0.6, which is the packaged LyX
> for Ubuntu 13.10, and there wasn't a bit of XML in it, well formed or
> otherwise. It was basically the same format human parseable format it's
> been for 10 years, but with a lot more insets and options. But as far
>
Quick question: What are your reasons / needs for being able to
"humanly" parse the file format? Would a tool like pLyX address these
needs: http://wiki.lyx.org/Examples/FindAndReplaceLyXFormatElements ?

Liviu

> as I can tell, the newlines in the format are meaningful, meaning one
> can do a line by line parse, although with today's proliferation of
> great features, many implemented as insets, the parse isn't as simple
> as it was in 2005.
>
> SteveT
>
> Steve Litt*  http://www.troubleshooters.com/
> Troubleshooting Training  *  Human Performance



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail