Hi, this is pretty awesome indeed!
Would it be possible to do somethin OTR-like (in the sense of hiding
extra data) for exchanging cursor movement operations / cursor
location, and changes (typing, ...)? That would make it possible to
collaboratively edit LyX docs.
On Wed, Jul 31, 2013 at 3:00 PM, Steve Litt wrote:
> Oh, I should have made it clear that style preservation would be my top
> priority. But you remind me of something: Assuming one writes
> completely styles-based HTML, the conversion to either LyX or LaTeX
> would be trivial -- everything would
On Mon, Jul 8, 2013 at 8:52 PM, Steve Litt wrote:
> [...]
Let me do a broken disk impression...
I've used XHTML + XSLT successfully to convert to other XML schemas.
XHTML doesn't quite preserve enough metadata for me though, so I've
also written a LyX -> XML converter[0] that preserves as much m
A quick search for "odt xslt" finds some possibly useful tools and other things:
http://stackoverflow.com/questions/13031514/html-to-odt-xslt
http://opendocumentfellowship.com/projects/odftools
http://wiki.openoffice.org/wiki/ODF_Toolkit/Efforts/ODTransform
http://open.comsultia.com/docbook2odf/
h
On Wed, May 1, 2013 at 7:21 AM, ehud.kaplan wrote:
> I had tried to convert from a Lyx document (a Ph.D. thesis, ~140 pages) to
> LibreOffice (File/Export/HTML). Much of it worked, but there were many
> problems:
>
> Equation numbers moved from right to left
> Figures were totally distorted (size
On Tue, Apr 9, 2013 at 1:36 PM, Liviu Andronic wrote:
> On Tue, Apr 9, 2013 at 8:20 PM, Nico Williams wrote:
>> textual user, I prefer everything as textual as possible. I'd even
>> like a search feature for menus/functions, and in general I'd like
>>
> That&
Since we're piling on...
I don't mind the sort of ribbon menu as they've evolved to be at MSFT,
but I do prefer pull-down menus with *text* instead of icons. I'm a
textual user, I prefer everything as textual as possible. I'd even
like a search feature for menus/functions, and in general I'd lik
On Tue, Feb 26, 2013 at 2:14 AM, Rainer M Krug wrote:
> On 26/02/13 03:08, Nico Williams wrote:
>> It'd be nice to have a LyX diff/merge feature. (We've had a thread about
>> this.)
>
> Yes - and I think it would be *really* useful.
>
> Maybe a Google Sum
Mind you, merging LyX contents via a VCS is not easy...
What I've been doing so far with my colleagues is to pass around a
"your turn" e-mail, then we each make our edits in turn with change
tracking, and one of us (or the next one to get a turn) merges edits.
It'd be nice to have a LyX diff/merg
On Wed, Jan 23, 2013 at 5:01 PM, Steve Litt wrote:
> On Wed, 23 Jan 2013 14:20:57 -0600, Nico Williams said:
>
>> Well, there's http://yaxml.rubyforge.org/ , which is a tool that
>> converts between (in both directions) YAXML and YAML. Pair this with
>> my lyx2xml
On Wed, Jan 23, 2013 at 1:57 PM, Steve Litt wrote:
> On Wed, 23 Jan 2013 15:15:15 + (UTC), Guenter Milde said:
>> Please don't be discouraged to continue the work on and publication of
>> the lyx2xml script. I think it is a useful addition to LyX.
>
> I have a question for you...
>
> When is s
On Wed, Jan 23, 2013 at 9:15 AM, Guenter Milde wrote:
> On 2013-01-22, Nico Williams wrote:
>> There was a thread about this a while back and the conclusion was that
>> I'm on my own with this, that for now my lyx2xml is not to be part of
>> LyX. Partly there's a
On Tue, Jan 22, 2013 at 8:52 AM, Richard Heck wrote:
> On 01/22/2013 02:38 AM, Nico Williams wrote:
>> Hmm, the thought occurs that my lyx2xml script wouldn't be broken by any
>> changes to.lyx, not if it was always chained with lyx2lyx so that it's input
>> were a
Hmm, the thought occurs that my lyx2xml script wouldn't be broken by any
changes to.lyx, not if it was always chained with lyx2lyx so that it's
input were always in a version supported by lyx2xml...
I've been using LyXHTML and writing an XSL to convert from that.
That's left me unsatisfied.
I think the right approach is to have a LyX XML schema, export to
that, then apply an XSL to convert to whatever format you want. I've
written a script to convert .lyx to XML using a very simple-minded
ap
On Jan 2, 2013 8:13 AM, "Richard Heck" wrote:
>
> On 01/02/2013 01:40 AM, Liviu Andronic wrote:
>>
>> On Tue, Jan 1, 2013 at 4:32 PM, Richard Heck wrote:
>>>
>>> all of this explanation, and these files, there. Better yet, for the
files,
>>> create a git repo on github (or somewhere) and point at
On Fri, Dec 28, 2012 at 2:17 PM, Nico Williams wrote:
> Never mind, found it: paragraph settings.
No, \labelwidthstring is something else. It'd be nice to be able to
title References sections something else. In RFC typesetting we need
to be able to have "Normative References"
Never mind, found it: paragraph settings.
When using the bibliography environment a section is created called
'References'. It's possible to add bibliography all over a document,
each set of which will be in its own section, but they're all called
"References". Is there any way to change this other than editing the
.lyx to change the \la
FWIW, I edit XML in vim plenty. It's not awesome, but it's not
particularly painful either. XML is not unfriendly to $EDITOR, but it
is more verbose. The great value that XML provides is in technologies
like XPath, XQuery, and XSLT. I ache for the power of XSLT in
association with LyX.
But als
On Tue, Dec 18, 2012 at 10:43 PM, Steve Litt wrote:
> On Tue, 18 Dec 2012 10:22:17 +0100
> Rainer M Krug wrote:
>> This all sounds very exciting and extremely useful for import /
>> export / collaboration, but there is one aspect which I would be
>> missing in an XML file: At the moment, I can op
On Mon, Dec 17, 2012 at 3:15 PM, Alex Vergara Gil wrote:
>
>> On Mon, Dec 17, 2012 at 2:25 PM, Richard Heck wrote:
>>>
>>> I'm not so sure. If someone were to write a converter that mapped LyX's
>>> XML
>>> onto ODT's, or whatever, then yes. But that would still need doing.
>>
>>
>> Yes, of cours
On Mon, Dec 17, 2012 at 2:25 PM, Richard Heck wrote:
> I'm not so sure. If someone were to write a converter that mapped LyX's XML
> onto ODT's, or whatever, then yes. But that would still need doing.
Yes, of course. However, I think it should be easier to write such
XSLs to map from a straightf
On Mon, Dec 17, 2012 at 2:02 PM, stefano franchi
wrote:
> Sounds like a great idea. One question: would having an external but
> faithful XML Lyx file allow XLS-translations to XML-based word-processing
> formats?
> That would solve once and for all (hopefully) the problem of the Lyx-->Word
> conv
On Mon, Dec 17, 2012 at 12:21 PM, Richard Heck wrote:
> On 12/17/2012 11:45 AM, Alex Vergara Gil wrote:
>>> There still are long-term plans to convert the native LyX format to XML.
>>> But it turns out to be more work than one might expect.
>>>
>>> rh
>>
>> Really nice to hear about this, is there
I've been using custom insets to represent metadata that LyX doesn't
natively handle. I'd like this to get rendered when printing or
exporting to, say, PDF. The rendering would first take the form of lyx
code, so that LyX needn't have too much change. How would I go about
making this happen? Co
I've written a Python script for converting .lyx files to XML.
There's no DTD or schema, but it's a straightforward mapping of .lyx
format to XML. Things like \being_layout ... \end_layout become
... and so on. This is much more faithful a
mapping to XML than LyXHTML, or any of the other XML expo
On Thu, Dec 13, 2012 at 5:58 AM, Eric Weir wrote:
> On Apr 20, 2012, at 11:23 AM, stefano franchi wrote:
>> Moreover, it is not even clear that BibTeX will remain the only
>> database format for TeX users. Biber, a much more flexible and heavily
>> developed BibTeX replacement, is starting to inte
On Wed, Dec 12, 2012 at 7:49 AM, Pavel Sanda wrote:
> Gregory Jefferis wrote:
> One solution would be to detect merge conflicts and call our diff algorithm
> for the different versions.
> This would be beautiful but an order of magnitude harder to implement (surely
> not me:)
That's what I wan
On Tuesday, December 11, 2012, Pavel Sanda wrote:
> Nico Williams wrote:
> > I believe merging is easier than locking, even for small teams.
>
> That's because you probably work with people with computer science
> background.
> The moment you step out of these waters
On Tue, Dec 11, 2012 at 12:25 PM, Pavel Sanda wrote:
> Nico Williams wrote:
>> It is precisely because locking doesn't scale that we have branching
>> and merging. Locking simply does not scale. This is true even of
>> documents (as opposed to source code).
>
&g
On Tue, Dec 11, 2012 at 10:26 AM, Pavel Sanda wrote:
> We currently use integrated SVN support of LyX for this.
> The merge conflicts are avoided by locking the whole document or childern
> (parts of the text).
It is precisely because locking doesn't scale that we have branching
and merging. Lo
On Mon, Dec 10, 2012 at 5:22 PM, José Matos wrote:
> On 12/10/2012 10:46 PM, Nico Williams wrote:
>> Why is there no bibliography environment in the DocBook document
>> classes? There must be a reason, of course, but then, bibtex is still
>> supported, so that's strang
Why is there no bibliography environment in the DocBook document
classes? There must be a reason, of course, but then, bibtex is still
supported, so that's strange...
Nico
--
On Fri, Dec 7, 2012 at 6:02 AM, Rainer M Krug wrote:
> On 07/12/12 12:45, Gregory Jefferis wrote:
>> Has anyone tried using latexdiff for change comparison in not merging?
>> Presumably a small script to export both versions to latex, invoke latexdiff
>> and then generate the marked-up PDF (whic
On Thu, Dec 6, 2012 at 4:29 AM, Oleg Parashchenko wrote:
> Some time ago I experimented with LyX<->XML roundtrip. In my idea, XML
> was not one-to-one mapping of .lyx structure, but an XML format
>
> * which convenient for processing and generation, and
> * with enough hints to restore one-to-one
OK, thanks.
On Wed, Dec 5, 2012 at 3:20 PM, Nico Williams wrote:
> Ah, I see it, Tools->Preferences->File Handling->File Formats.
OK, this is getting there. How can I deliver these things with a package?
On Wed, Dec 5, 2012 at 3:37 PM, Alex Vergara Gil wrote:
> Can you point me the address to the wiki please.
> I agree that having a bidirectional conversion is nice at first glance (or
> first step approximation lets say) but what I really expect in the future is
> to have the .lyx format natively
Ah, I see it, Tools->Preferences->File Handling->File Formats.
On Wed, Dec 5, 2012 at 12:44 PM, Pavel Sanda wrote:
> Jean-Marc Lasgouttes wrote:
>> Le 04/12/2012 18:10, Nico Williams a écrit :
>>> What would the exact command-line invocation be?
>>
>> Unfortunately, it seems that there is no lfun to do that. The only one is
On Wed, Dec 5, 2012 at 2:20 PM, Liviu Andronic wrote:
> On Wed, Dec 5, 2012 at 9:08 PM, Nico Williams wrote:
>> do this, but I don't know where to start. And even my lyx2rfc tool,
>> if that's the only way to do this, I'd like to be able to invoke from
>>
On Wed, Dec 5, 2012 at 8:15 AM, Alex Vergara Gil wrote:
> The question is why to have a .lyx format in plain text? Isn't xml a better
> one? I know plain text is easy to edit but we really doesn't work with it
> since LyX do this for us. The advantages would be obvious:
> Insertion/Deletion of met
On Wed, Dec 5, 2012 at 1:13 AM, Liviu Andronic wrote:
> On Tue, Dec 4, 2012 at 8:21 PM, Nico Williams wrote:
>> It'd also be nice to be able to define a filter that must be applied
>> before rendering. Such a filter might convert metadata into LyX
>> directives, thus p
Never mind. I really had to define LabelStrings for all my insets,
and then View->Open All Insets was enough. And apparently they are
inserted open anyways. I've closed the ticket I opened for this.
On Tue, Dec 4, 2012 at 12:56 PM, Jean-Marc Lasgouttes
wrote:
> Le 04/12/2012 19:53, Jürgen Spitzmüller a écrit :
>> You are talking about "conglomerate"-style flex insets, right?
>> Currently, they are always inserted "collapsed" and you need to
>> manually uncollapse them. We could introduce a la
It'd be nice to have a custom inset type just for metadata, that is,
one that doesn't get rendered.
It'd also be nice to be able to define a filter that must be applied
before rendering. Such a filter might convert metadata into LyX
directives, thus pre-rendering said metadata.
I'll file a reque
I'm using custom insets to represent various metadata. The problem I
run into is that there's no way in the LyX display to see what each
inset is. If I click inside such an inset the layout is shown as
plain -- nothing in the UI shows the inset type.
In some cases I'm resorting to using param=va
Ideally the syntax should be something like: lyx --merge --out=doc3
doc1 doc2, and the result should be a merged document with change
tracking so that the user can do all semantic merging. In this mode
LyX should not open a window nor require user interaction, as the idea
is to use this as a merge
What would the exact command-line invocation be?
Nico
--
Hi,
I'd like to use LyX + git (or some such VCS) to cooperatively edit
documents. This requires a diff/merge tool that is LyX-aware and can
result in LyX documents that contain diffs that users can merge
manually. Are there any such tools? Thanks,
Nico
--
On Wed, Aug 8, 2012 at 1:13 AM, Jerry wrote:
> I just tried a quick experiment with pandoc, saving a 3.5 page LyX document
> (article class) of mostly lorem ipsum as LaTeX and then using pandoc to
> convert that to .docx, Word's XML format. I then viewed the .docx in
> Microsoft Word 2011 for O
Using XHTMP export has the benefit that you can then use XSLT. I've
used this successfully to export LyX format to an unrelated XML
schema.
Nico
--
On Wed, May 30, 2012 at 11:24 AM, Allen Barker wrote:
> I've set up a repo on github for the program.
>
> The code:
> https://github.com/abarker/lyxNotebook
>
> For a quick overview, see the first section of the documentation:
> https://github.com/abarker/lyxNotebook/blob/master/lyxNotebookDocs.pd
On Mon, May 28, 2012 at 8:34 AM, Richard Heck wrote:
> If you're at all serious about this program, then I'd suggest
> you create a git repo for it somewhere like gitorious, and
> then people can have easy access, as well as follow the
> changes you're making. List it as pre-alpha or whatever,
> a
strace lyx running as root and not, then look to see what system calls
are failing in the latter case leading up to the segfault. That might
give you a clue as to where else to look.
Nico
--
FWIW, I've put up a github repo with my LyX->xml2rfc tool, though it's
still a work in progress: https://github.com/nicowilliams/lyx2rfc
BTW, I can't get "lyx -e lyxhtml ..." to work. lyx -e xhtml does
work, but then there are some differences from the LyXHTML option in
the File->Export menu. Th
On Mon, May 14, 2012 at 9:30 AM, Richard Heck wrote:
> On 05/14/2012 10:26 AM, Nico Williams wrote:
>>
>> Richard,
>>
>> Does LyX XHTML output preserve enough LyX metadata to be suitable as
>> an import format?
>
> You mean back into LyX?
Yes. With XML
Richard,
Does LyX XHTML output preserve enough LyX metadata to be suitable as
an import format?
Nico
--
Well, thanks lots for your help. I have something that's very close.
Close enough that I can now author I-Ds in LyX. I've found one more
bug in the LyX XHTML output, and I filed a bug for it (bibitem anchor
generation is not working properly), and I can work around it.
Cheers!
Nico
--
On Thu, May 10, 2012 at 10:09 AM, Richard Heck wrote:
>> I don't know how to create a custom inset that does.. [...]
>
> Try putting this into Local Layout, under Document>Settings:
Excellent, that worked great.
> I guess if you want these as metadata, you should also add:
> InTitle 1
> to ea
On Thu, May 10, 2012 at 8:27 PM, Richard Heck wrote:
> On 05/10/2012 04:52 PM, Nico Williams wrote:
>> On Thu, May 10, 2012 at 3:31 PM, Richard Heck wrote:
>> Here's a LyX snippet:
>
> OK, I see the problem. The vertical space gets moved, for reasons
> that probably
On Thu, May 10, 2012 at 3:31 PM, Richard Heck wrote:
> Actually, it looks like this got fixed a while ago. In a simple text
> document I get:
I'm running LyX 2.0.0. The vspace I had was in an author inset, FWIW.
The output you show is certainly fine.
> If you want to post a simple example file
On Thu, May 10, 2012 at 10:02 AM, Richard Heck wrote:
> On 05/09/2012 02:29 AM, Nico Williams wrote:
>>> [Actually, I'm noticing one problem with LyXHTML: it doesn't preserve
>>> vertical spacing in any way, not even as horizontal spacing! I'm
>>> tal
> [Actually, I'm noticing one problem with LyXHTML: it doesn't preserve
> vertical spacing in any way, not even as horizontal spacing! I'm
> talking about Insert->Formatting->Vertical Space. I suspect that
> there are other such things that aren't preserved. For now I'll live.
> Vertical space
On Tue, May 8, 2012 at 10:58 PM, Richard Heck wrote:
> On 05/08/2012 07:30 PM, Nico Williams wrote:
>> LyXHTML looks very promising. It certainly preserves everything I
>> have in my [admittedly small] test file. If it preserves custom inset
>> names then I could probably
On Tue, May 8, 2012 at 12:40 AM, Guenter Milde wrote:
> So how about XHTML as starting point for your XSLT transformations?
LyXHTML looks very promising. It certainly preserves everything I
have in my [admittedly small] test file. If it preserves custom inset
names then I could probably use cus
On Tue, May 8, 2012 at 12:40 AM, Guenter Milde wrote:
> So how about XHTML as starting point for your XSLT transformations?
>
> Otherwise, you could use the native XHTML formatter as a model for adding
> "native XML" output.
>
> Another starting point would be the external "elyxer" tool: a Python
Is there canonical documentation of the LyX file format? I can't find
it... I did find this: http://wiki.lyx.org/Devel/LyXFileFormat , but
that's just a changelog. There's nothing else obvious in
http://wiki.lyx.org/Devel/ ... The development/FORMAT file in the
source tree is also a changelog.
On Mon, May 7, 2012 at 12:56 PM, Nico Williams wrote:
> Ah, that works. Thanks! I'll take a look and see if the native
> DocBook export works for me.
Nope, it still doesn't allow more than one author in docbook, though
it does merge all the authors listed in the LyX document source.
No, i got that. I don't actually care for docbook. I want a straightforward
translation to XML that preserves all data and metadata. If I need a
specific schema I can always use XSLT to get output in that form.
Nico
--
On Mon, May 7, 2012 at 12:41 PM, Pavel Sanda wrote:
> Nico Williams wrote:
>> This I hadn't seen. One thing to note is that the LyX I'm running (on
>> Ubuntu) has no option to save as or export to SGML or DocBook. I
>> gather from the link you gave me tha
On Mon, May 7, 2012 at 12:07 PM, Pavel Sanda wrote:
> Nico Williams wrote:
>> How does LyX represent documents internally? If it does it in an
>> objectified form then it should be fairly straightforward to walk the
>> document tree and emit XML, no? Or, looking at
On Mon, May 7, 2012 at 12:07 PM, Pavel Sanda wrote:
> Nico Williams wrote:
>> The LaTeX->XML tools I've tried leave me... sad. They tend to drop
>> some things. For example: vertical space, which becomes a simple
>> newline in a paragraph's text. It would
The LaTeX->XML tools I've tried leave me... sad. They tend to drop
some things. For example: vertical space, which becomes a simple
newline in a paragraph's text. It would be better to translate
vertical space into elements -- that'd be much, much more
useful in XSLT than embedded newlines!
So
On Mon, May 7, 2012 at 11:04 AM, Pavel Sanda wrote:
> Nico Williams wrote:
>> - a vi editing mode (I looked at the list archives, I know this has
>> come up before)
>>
>> - a way to export to xml2rfc's XML schema
>
> asking for the obvious - have you trie
I love LyX. I want two things it doesn't have/do today:
- a vi editing mode (I looked at the list archives, I know this has
come up before)
- a way to export to xml2rfc's XML schema
For the latter I'm playing with TeX4ht and htlatex, followed by
applying an XSLT stylesheet. First I export to
77 matches
Mail list logo
