Hello,

as it happens, yesterday I was working on getting fpdoc from trunk to generate proper CHMs again when RC1 happened.

It seems the major fpdoc restructures have been finished (78 patches since 2.6.0, mostly by Michael), and the docs now generate again. As soon as these changes can be considered validated by this release they can be merged to fixes26.

So for testing purposes I generated a snapshot based on "fixes26" FPC source, and due to the special occasion also the Lazarus RC1 tag. This is also the first release to contain the lazutils.chm

Please test an report irregularities in this thread.

http://www.stack.nl/~marcov/doc-chm_rc1.zip

Marco

Marco, is there any chance of a webpage somewhere showing the files recommended to build a release from source as of the current date?

i.e. "If you want to build RC1 on an unsupported system, use

http://svn.freepascal.org/svn/lazarus/tags/lazarus_1_0_RC1

and insert the content of

http://www.stack.nl/~marcov/doc-chm_rc1.zip

at XXXXXXX."

Hi Marco,

The CHM files are all double spaced in LHelp. This applies to class declarations, unit lists etc. The online (HTML) versions are not double spaced.
See attached screenshot.

Hi,

I'm using LHelp from a few weeks ago (yes I'll update it soon), so not sure if this is fixed in a newer version. ie: lazarus-rc1

If the LCL.CHM I see a HTTP link about latest version of the documentation can be found at <url>. If I click that URL, it doesn't do anything in LHelp, and it also doesn't try and open that link in my already running Firefox browser. :-/

Graeme Geldenhuys wrote

The CHM files are all double spaced in LHelp. This applies to class declarations, unit lists etc. The online (HTML) versions are not double spaced. See attached screenshot.

More lhelp problem, though the generated html doesn't deserve a beauty price with <p>'s in tables.

Could also be css (wrong css file) related, but I'm not that deep into html.

Hi Marco,

Marco van de Voort wrote

Could also be css (wrong css file) related, but I'm not that deep into html.

I remember having the same "double spacing" issue some months (maybe a year) back when I generated tiOPF HTML files. In the end it came down to the HTML output that changed slightly, and I still had a old stock CSS file. I updated my CSS file, and the double spacing disappeared in my HTML online help. So yes, maybe the issue is the wrong CSS file embedded in the CHM files.

Here is my tiOPF HTML output (no double spacing).
http://opensoft.homeip.net:8080/tiopf/core/index.html

Here is the fpdoc.css file I use:
http://opensoft.homeip.net:8080/tiopf/core/fpdoc.css

Hope that helps.

Hi Marco,

Please test an report irregularities in this thread.

On the first screen after opening the ref.chm file... "Michael van Canneyt" 's name is garbled. After all his hard work creating those FPC docs, I think we owe it to him to at least get his name right. ;-)

That's one way of other is that it were his patches that caused it :-)

Seriously, I think we are dealing with a 2.7.1 specific unicode issue, so the first thing to investigate if 2.6.1 also has this problem when the patches are merged.

As for the css- double height issue, I'll extract the css file from the old chm and compare.

(one can simply extract files using

chmls extract lcl.chm actnlist/taction.html

and chmls list lcl.chm lists files in the archive
)

About a year ago I could fix that by using your CSS file. But I never could figure out what really makes that difference, and found random behaviour regardless of what I tried.

DoDi

Note that FPC's fpdoc chms don't have it, what I think happened:

- last time I built with FPC's fpdoc.css
- afterwards, when committing I cleaned up paths in the generation script
- so now I used Lazarus' fpdoc.css

A diff between the two is at

http://www.stack.nl/~marcov/fpdoccss.diff

I found similar issues when doing plain html pages.

- there is a line terminator and there is a paragraph terminator.
- the paragraph spacing is defined by some code that is interpreted before in the html code or in the CSS file
- the browser might ignore empty lines and/or paragraphs or insert an empty space sized like a line or a paragraph-distance. I fond that this behavior in fact differs when using different browsers.

-Michael

to be added:

If using automatic enumerated and bulleted paragraphs there might be even more issues.

-Michael

IMO one feature of CSS is the definition of spacings, which should not be ignored by an browser.

- the browser might ignore empty lines and/or paragraphs or insert an empty space sized like a line or a paragraph-distance. I fond that this behavior in fact differs when using different browsers.

AFAIK a conforming browser should ignore non-HTML line breaks, except in special sections (<preformatted>).

DoDi