Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2010-08

fpdoc + XML description file + indentation whitespace

2 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Graeme Geldenhuys

Hi,

What is supposed to happen with whitespace in the XML Description files. For example. Say you edit an XML file with your favourite text editor, and you have a long description. So you add newlines (by pressing ENTER), then indent the text to the DESCR node for easier human reading. It seems fpdoc inserts that indented (spacing) whitespace as actual space characters (part of the help content) in the help content. This is seen all over the place, but not always noticed in the final output.

Examples:

LaTeX:
automatically ignores whitespace and will place words next to each other with a single space. So this issue is never noticed.

HTML:
The web browser will ignore whitespace unless that whitespaces was inside a PRE tag in the XML Description file. See example URL below.

IPF:
IPF -> INF keeps all whitespace exactly as you typed it inside the XML Description files. So if you do indented text, you are going to have huge sections of spaces between some words.

TXT and MAN
Both have misaligned text due to this problem as well.

RTL
?? I have not tested this output format.

Here is an example of indentation inside a PRE tag in the XML Description file causing misaligned output when viewed with the web browser. See the Description section.

http://lazarus-ccr.sourceforge.net/docs/lcl/comctrls/ttreenode.moveto.html

With INF, TXT (slightly better due to manual line wrapping implementation) and MAN the problem is much worse because they teat the content exactly as the user entered it. So indentation, to make human readable XML, is not recommended. Is there some way fpdoc could help alleviate the problem, or is it the job of the output writer to trim such spaces (though this will be very hard to catch all cases because you will never know exactly when you should or shouldn't trim spaces).

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/

Reply by email

Michael Van Canneyt
to Graeme Geldenhuys
Graeme Geldenhuys wrote 9 lines
Hi, What is supposed to happen with whitespace in the XML Description files. For example. Say you edit an XML file with your favourite text editor, and you have a long description. So you add newlines (by pressing ENTER), then indent the text to the DESCR node for easier human reading. It seems fpdoc inserts that indented (spacing) whitespace as actual space characters (part of the help content) in the help content. This is seen all over the place, but not always noticed in the final output.

[snip]

Show quoted text 7 lines
With INF, TXT (slightly better due to manual line wrapping implementation) and MAN the problem is much worse because they teat the content exactly as the user entered it. So indentation, to make human readable XML, is not recommended. Is there some way fpdoc could help alleviate the problem, or is it the job of the output writer to trim such spaces (though this will be very hard to catch all cases because you will never know exactly when you should or shouldn't trim spaces).

You must catch the spaces in the output engine; there is no other way.

Michael.

Reply by email