[rfc-i] Using <artwork>

scott.mansfield at ericsson.com (Scott Mansfield) Wed, 04 March 2015 07:14 UTC

From: "scott.mansfield at ericsson.com"
Date: Wed, 04 Mar 2015 07:14:23 +0000
Subject: [rfc-i] Using <artwork>
In-Reply-To: <EF35EE4B92789843B1DECBC0E245586439DD1503@eusaamb105.ericsson.se>
References: <EF35EE4B92789843B1DECBC0E245586439DD1503@eusaamb105.ericsson.se>
Message-ID: <EF35EE4B92789843B1DECBC0E245586439DD1EE6@eusaamb105.ericsson.se>

I have been looking through xml2rfc documentation and examples and there seems to be support for more complicated artwork in non-text versions of IDs but I can't seem to make it work in 2.4.9.

I look through the last 6 months of archives on this list and didn't see this question addressed, so hopefully I'm not asking something that has been already asked.

I notice <artwork> talks about <src> as a potential to point to a graphics file.

I have xml2rfc.2.4.9 on my laptop.

When I look at the xml2rfc tool, I don't see an option to generate a pdf.  So I'm trying to determine how integrate a graphic into the XML of an internet draft and generate html or pdf using xml2rfc.

I've tried a number of permutations:  using <artwork src="file:///C:/Untitled.bmp<file:///C:\Untitled.bmp>">, using the type attribute,  I also tried just putting the file name in there and generating using -html.  But nothing I do seems to put the graphic file in html output.

Currently I have two ways to add a jpeg or ppt slide to an ID.  One is I use word and the other is to generate a text file with enough space where the picture goes then hack the pdf file.  I don't like either of these options because I have to keep two parallel versions, one that is used for the txt for submission (using XML) and the other is the kludged one with the pretty pictures.

Any pointers or suggestions?

If this isn't the correct place to ask please point me to the right place.

Thanks,
-scott.

Scott Mansfield
Ericsson Inc.
+1 724 931 9316

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20150304/5928e18e/attachment.html>