Here's a diagnosis of the missing PDF.  I tested building the PDF with "a2x 
--fop root.adoc" and received this error:

a2x: ERROR: "xmllint" --nonet --noout --valid 
"/home/rjs7/Evergreen/docs/root.xml" returned non-zero exit status 4

Same output for branches rel_2_12, rel_3_0 and master.  If I run that "xmllint" 
command, I get these more detailed errors:

/home/rjs7/Evergreen/docs/root.xml:11000: element anchor: validity error : ID 
register_workstation already defined
<simpara><anchor id="register_workstation" xreflabel="[register_workstation]"/>
                                                                             ^
/home/rjs7/Evergreen/docs/root.xml:4338: element link: validity error : IDREF 
attribute linkend references an unknown ID "_evergreen_2_12_1_release_notes"

Remington

--
Remington Steed
Electronic Resources Specialist
Hekman Library, Calvin College
http://library.calvin.edu/

From: Open-ils-general 
[mailto:[email protected]] On Behalf Of 
Prince, Catherine
Sent: Monday, October 23, 2017 3:30 PM
To: Evergreen Discussion Group <[email protected]>
Subject: [OPEN-ILS-GENERAL] broken link

Hi all,

I am wanting to download the 2.12 PDF version of the documentation from 
http://docs.evergreen-ils.org/ .  The link for the 2.12 is not found 
(http://docs.evergreen-ils.org/2.12/Evergreen_Documentation.pdf).  I see at the 
bottom of the page that it indicates to submit a LP bug for issues in the 
documentation.  Since this issue isn't technically IN the documentation it is 
getting to the documentation, I decided to post to the list.

Does anyone have a copy of the 2.12 pdf or can fix the link to the pdf?

Thanks,

[cid:[email protected]]Catherine M. Prince
NC Cardinal Systems Librarian
NC Dept. of Natural and Cultural Resources
919.807.7426  |  [email protected]<mailto:[email protected]>


109 E. Jones St. | 4640 Mail Service Center
Raleigh, North Carolina 27699-4640

Email correspondence to and from this address is subject to the North Carolina 
Public Records Law and may be disclosed to third parties.

Reply via email to