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
