Re: proj manual, versioning, download location
Kristian Evers <[email protected]> Tue, 7 Jan 2020 14:19:52 +0000
| Newsgroups | gmane.comp.gis.proj-4.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============0670574200068973203== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_adee27b01ecc411c8aa160554ed3afb6sdfedk_" --_000_adee27b01ecc411c8aa160554ed3afb6sdfedk_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable It is entirely possible that RTD doesn't support generation of API document= ation using Doxygen and Breathe. We also have some custom CSS and the way w= e handle references isn't completely standard either (as far as I remember)= . /Kristian From: PROJ <[email protected]> On Behalf Of Howard Butler Sent: 7. januar 2020 15:13 To: [email protected] Subject: Re: [PROJ] proj manual, versioning, download location On Jan 7, 2020, at 1:11 AM, Kristian Evers <[email protected]<mailto:kreve@sdfe= .dk>> wrote: We can still use proj.org<http://proj.org/> with RTD, right? Another option is to use RTD's Sphinx templates to support multiple doc ver= sions but keep our own documentation setup. I don't know for sure if PROJ i= s doing any Sphinx stuff that is unsupported by RTD either. Howard --_000_adee27b01ecc411c8aa160554ed3afb6sdfedk_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman",serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} p.msonormal0, li.msonormal0, div.msonormal0 {mso-style-name:msonormal; mso-margin-top-alt:auto; margin-right:0cm; mso-margin-bottom-alt:auto; margin-left:0cm; font-size:12.0pt; font-family:"Times New Roman",serif;} span.EmailStyle18 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page WordSection1 {size:612.0pt 792.0pt; margin:3.0cm 2.0cm 3.0cm 2.0cm;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3D"EN-US" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri",sans-serif;color:#1F497D">It is entirely possible that RTD does= n’t support generation of API documentation using Doxygen and Breathe= . We also have some custom CSS and the way we handle references isn’t completely standard either (as far as I remember). = <o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri",sans-serif;color:#1F497D"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri",sans-serif;color:#1F497D">/Kristian<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri",sans-serif;color:#1F497D"><o:p> </o:p></span></p> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm = 0cm 0cm"> <p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:"= ;Calibri",sans-serif">From:</span></b><span style=3D"font-size:11.0pt;= font-family:"Calibri",sans-serif"> PROJ <[email protected]= geo.org> <b>On Behalf Of </b>Howard Butler<br> <b>Sent:</b> 7. januar 2020 15:13<br> <b>To:</b> [email protected]<br> <b>Subject:</b> Re: [PROJ] proj manual, versioning, download location<o:p><= /o:p></span></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <div> <p class=3D"MsoNormal"><br> <br> <o:p></o:p></p> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <div> <p class=3D"MsoNormal">On Jan 7, 2020, at 1:11 AM, Kristian Evers <<a hr= ef=3D"mailto:[email protected]">[email protected]</a>> wrote:<o:p></o:p></p> </div> <div> <div> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <div> <p class=3D"MsoNormal">We can still use <a href=3D"http://proj.org/">proj.o= rg</a> with RTD, right?<o:p></o:p></p> </div> </div> </div> </blockquote> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"color:black">Another option is to use= RTD's Sphinx templates to support multiple doc versions but keep our own d= ocumentation setup. I don't know for sure if PROJ is doing any Sphinx stuff= that is unsupported by RTD either.</span><o:p></o:p></p> <div> <p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>= </p> </div> <div> <p class=3D"MsoNormal"><span style=3D"color:black">Howard<o:p></o:p></span>= </p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> </body> </html> --_000_adee27b01ecc411c8aa160554ed3afb6sdfedk_-- --===============0670574200068973203== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KUFJPSiBtYWls aW5nIGxpc3QKUFJPSkBsaXN0cy5vc2dlby5vcmcKaHR0cHM6Ly9saXN0cy5vc2dlby5vcmcvbWFp bG1hbi9saXN0aW5mby9wcm9qCg== --===============0670574200068973203==--