<div dir="ltr">I've looked around the internet for examples of using expanded entities as ulink URLs, but in all the instances I've found they use the entire link, such as:<div><br></div><div><!ENTITIY myurl "<a href="http://www.thisismy.com/url">http://www.thisismy.com/url</a>"> or, the entire <ulink> tag structure as the entity.</div>
<div><br></div><div style>What I'm looking to do is use an entity to represent just part of a URL, leading up to the final file. I'm trying to put links to files distributed via HTTP, and while the filenames should remain fairly constant the DNS name/HTTP link of the URL may change names, and not having to go update individual URLs all through a document would be a huge time-saver.</div>
<div style><br></div><div style>What seems to work when locally built (HTML, PDF, etc. on local machine) is putting the entity in the .ent file like <!ENTITY MYURL "<a href="http://docs.mysite.com/itfiles/tutorial">http://docs.mysite.com/itfiles/tutorial</a>"> and the ulink as:</div>
<div style><br></div><div style><ulink url="&MYURL;/awesomefile.txt">file</ulink><br></div><div style><br></div><div style>This correctly generates the URL to the external site in the PDF, HTML, etc. However, when this is packaged as an RPM and deployed on the documentation site, it makes the final URL as displayed "<a href="http://docs.mysite.com/awesomefile.txt">http://docs.mysite.com/awesomefile.txt</a>" instead of pointing to the correct external link (which happens to be on the same server, just a different URL).</div>
<div style><br></div><div style>I saw a post about using correct XML, and putting the entity as "&MYURL;", but this just makes the URL "<a href="http://docs.mysite.com/&MYURL/awesomefile.txt">http://docs.mysite.com/&MYURL/awesomefile.txt</a>" without expanding the entity, taking the literal text.</div>
<div style><br></div><div style>Is there a proper way to do this, if at all?</div><div style><br></div><div style>Thanks in advance.</div><div><div><br></div>-- <br>Adam D.<br>
</div></div>