On 2018-04-03, Steve Litt wrote:
> On Mon, 2 Apr 2018 10:34:19 +1000
> Alan Tyree wrote:
>> Hello Steve,
>> I would think YAML is the best choice here. It is easy to type and
>> easy for the beginner to understand. You could provide simple
>> templates for the most common cases. My own feeling is
On Mon, 2 Apr 2018 10:34:19 +1000
Alan Tyree wrote:
> Hello Steve,
> I would think YAML is the best choice here. It is easy to type and
> easy for the beginner to understand. You could provide simple
> templates for the most common cases. My own feeling is that anything
> more complicated is goin
t; the expense of Asciidoc's "we do it all for you."
>
> One of my tasks in order to reach Minimum Viable Product (MVP) status
> is to give the author a way of storing the book's metadata. By metadata
> I mean stuff like author, title, copyright, etc, combined with build
&g
order to reach Minimum Viable Product (MVP) status
> is to give the author a way of storing the book's metadata. By metadata
> I mean stuff like author, title, copyright, etc, combined with build
> info like CSS files to be inserted to link styles with their
> appearances in H
ks in order to reach Minimum Viable Product (MVP) status
is to give the author a way of storing the book's metadata. By metadata
I mean stuff like author, title, copyright, etc, combined with build
info like CSS files to be inserted to link styles with their
appearances in HTML and ePub outpu
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 abou
OK, thanks.
On 12/05/2012 06:46 PM, Nico Williams wrote:
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?
You'll find what you've done in the preferences file at,
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?
Ah, I see it, Tools->Preferences->File Handling->File Formats.
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
>> the File->Export menu item. And I'd lik
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
> the File->Export menu item. And I'd like to be able to record in the
>
This can be done. In File Fo
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
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 pre-rendering said metadata.
Did you look into the possibility of adding a new
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 pre-rendering said metadata.
>
Did you look into the possibility of
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 metadat
Hi all,
Besides the book's content, can anyone think of any metadata or
filenames needed to create a kindle, that is not included in the
following list?
###author###
###title###
###date###
Hi,
I got the following from a friend a long while back, maybe the tool is of
use to people on this list.
Subject: Reading File Metadata with extract and libextractor
$extract -b a.pdf
Skapar bibtexfil av metadata från a.pdf :-)
Se
http://www.linuxjournal.com/article/7552
/Christian
"rgheck" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> itsme213 wrote:
>> Is there any way to associate user-defined metadata (such as tags) with
>> lyx elements? e.g. can I say paragraph 1 is "hero" and paragraph 2 is
>> "vi
itsme213 wrote:
Is there any way to associate user-defined metadata (such as tags) with lyx
elements? e.g. can I say paragraph 1 is "hero" and paragraph 2 is "villain"?
Is there a way to get this metadata in any of the outputs e.g. as "role=..."
in docbook or &
Is there any way to associate user-defined metadata (such as tags) with lyx
elements? e.g. can I say paragraph 1 is "hero" and paragraph 2 is "villain"?
Is there a way to get this metadata in any of the outputs e.g. as "role=..."
in docbook or "class=..." in xhtml?
Thanks -- Sophie
> Some classes (I know this from the Springer LNCS article class) don't
> like the hyperref redefinitions for implicit hyperlinks. However, in
> such cases hyperref can still be used to tag the PDF metadata, just
> pass it an implicit = false as option.
>
> The followin
r, in
such cases hyperref can still be used to tag the PDF metadata, just
pass it an implicit = false as option.
The following is an example snipped from my preamble in such cases (it
wraps the usepackage into an \ifpdf, as hyperref caused problems here
if one does not use p
Pavel Sanda schrieb:
thanks for help. however hyperref causes that number of
tex errors pop up during latex compilation.
It shouldn't. Assure that hyperref is loaded in your preamble as the
first package if possible.
regagards Uwe
rref causes that number of
tex errors pop up during latex compilation.
finally i made script using pdftk, which adds metadata
to completed pdf.
pavel
Sanda Pavel schrieb:
is there any possibility howto setup title and author in lyx document
in the way, that generated pdf has these strings in metadata ?
Yes ther is. Here is an example preamble sequence to get this:
% link all cross references and URLs in pdf output
\usepackage[colorlinks
hi all,
is there any possibility howto setup title and author in lyx document
in the way, that generated pdf has these strings in metadata ?
thanks
pavel
s are available in lyx to access document
> > metadata and use it in the document.
..
>
> If you use RCS, I guess you can just put $Id:$ or whatever a the right
> place in your doc... But there are small problemes with that ($ is math
> mode, and you may have some characters (
On Thu, Feb 21, 2002 at 07:23:12PM +0100, Yannick Patois wrote:
> If you use RCS, I guess you can just put $Id:$ or whatever a
> the right place in your doc... But there are small problemes
> with that ($ is math mode, and you may have some characters
> (like _) that tex doesnt like very much...),
On Thu, 21 Feb 2002 19:23:12 +0100 (CET) wrote Yannick Patois <[EMAIL PROTECTED]>:
> Hi,
>
> On Thu, 21 Feb 2002, Ryan McBride wrote:
>
> > I'm wondering what facilities are available in lyx to access document
> > metadata and use it in the document. For exa
Hi,
On Thu, 21 Feb 2002, Ryan McBride wrote:
> I'm wondering what facilities are available in lyx to access document
> metadata and use it in the document. For example there may be a
> requirement to include the path and filename of a document in the
> footer. Also, if you have
I'm wondering what facilities are available in lyx to access document
metadata and use it in the document. For example there may be a
requirement to include the path and filename of a document in the
footer. Also, if you have a document under version control, is there a
way to access the ve
32 matches
Mail list logo
