On Tue, August 14, 2012 15:47, michael.vancann...@wisa.be wrote: > On Tue, 14 Aug 2012, Tomas Hajny wrote: >> On Tue, August 14, 2012 15:15, michael.vancann...@wisa.be wrote: >>> On Tue, 14 Aug 2012, Reinier Olislagers wrote: >>>> On 14-8-2012 14:40, michael.vancanneyt-0is9kj9s...@public.gmane.org >>>> wrote: >>>>> On Tue, 14 Aug 2012, Reinier Olislagers wrote: >>>>>> On 14-8-2012 13:50, >>>>>> michael.vancanneyt-0is9kj9sb0a-xmd5yjdbdmrexy1tmh2...@public.gmane.org >>>>>> wrote: >>>>>>> On Tue, 14 Aug 2012, Reinier Olislagers wrote: >>>>>>>> On 14-8-2012 11:34, Marco van de Voort wrote: >>>>>>>>> In our previous episode, Reinier Olislagers said: >>>>>>>>>>> in packages\fcl-res\xml) but not in the bin directory. >>>>>>>>>>> >>>>>>>>>>> IIRC, fpdoc picks up fpdoc.css when generating HTML/CHM output. >>>>>>>>>>> Shouldn't fpdoc.css be also present under the bin directory >>>>>>>>>>> then? >>>>>>> The only question is: where should we put it ? >>>> <snip> >>>>>> On my Laz install (installed by Win installer) I only have >>>>>> bin,msg,units >>>>>> under the fpc directory. >>>>>> Perhaps there are others in other versions... >>>>>> >>>>>> What about the fpc root directory then? >>>>> >>>>> I think it is better to have it in fpc/docs. >>>> Ok. >>>> So: >>>> <fpc>\docs for Windows and >>>> on Linux/Unix/(OSX??) Jonas' suggestion >>>> $PREFIX/share/doc/fpc-$fpcversion/ >>> >>> Seems like the reasonable thing, yes. >> >> Actually, the file is more a configuration file for fpdoc than its >> documentation, isn't it? From this point of view, shouldn't >> SysUtils.GetAppConfigDir serve as the most reasonable location? > > It is definitely not a config file. It is a file that must be copied to > every project you want to document with fpdoc.
If I understand it correctly, this is only the case for plain HTML whereas CHM includes it internally (and from this point of view it is much more a configuration file influencing the output than part of fpdoc documentation - see also the comment from Marco). >From certain point of view it is unfortunate that the same file (equally named and potentially even equally placed) is used as the default template for generation of new documents with fpdoc and also for viewing of the (distributed) FPC documentation because fpdoc users may want to change the style of their generated documents but they may not be interested in changing the design of our FPC documentation. Tomas _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
