Bug 125754 - <para> usage in example-tutorial-en.xml conflicts with Docs Guide
<para> usage in example-tutorial-en.xml conflicts with Docs Guide
Product: Fedora Documentation
Classification: Fedora
Component: example-tutorial (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tammy Fox
Tammy Fox
Depends On:
  Show dependency treegraph
Reported: 2004-06-10 16:55 EDT by Mark Johnson
Modified: 2007-04-18 13:08 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-12 17:34:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mark Johnson 2004-06-10 16:55:36 EDT
Description of problem:

The Documentation Guide says:

"Additionally, the <para> tags should be justified around the
paragraph so that the opening <para> tag and the first word of that
paragraph are side by side. For example:

<para>This paragraph talk about using the <para> 
tag correctly.<para>"

But the example-tutorial-en.xml contains the following snippet:

      This is an example section. You can also use sect1, sect2, etc.

which contradicts what the Guide says.
Comment 1 Paul W. Frields 2004-07-30 18:33:07 EDT
Is there a reason why &lt;para&gt; tags have to be done in this way? I
find it easier to follow the markup (as an editor) when I see things
like the tutorial shows them. To me, the best possible situation would
be a single, uninterrupted "flow" of text that shifts indentation in
and out. I realize that the &lt;screen&gt; usage and a couple other
exceptions exist; not a problem.

More importantly, though, when one uses a block &lt;para&gt; it causes
Emacs/psgml to behave strangely when using M-q to fill. Maybe that's
bad Emacs usage; I'm an Emacs novice, so sue me. :-)
Comment 2 Karsten Wade 2004-08-02 18:54:56 EDT
Above behavior resolved using sgml-fill-paragraph (C-c C-q), when the
DTD has been properly parsed (C-c C-p).

FWIW, the process specified in the Documentation Guide is legacy
information and doesn't (likely) apply to the XML.

I'll grab this bug to fix when I get CVS access.
Comment 3 Tammy Fox 2004-08-12 17:34:08 EDT
It is legacy from the Documentation Guide we use for DocBook SGML. The
reason why this must be done is because having any space (carriage
return or blank spaces) after the &lt;para&gt; tag in DocBook SGML
causes a blank line in the PDF generated using DSSSL stylesheets. I
filed a bug on the DSSSL stylesheets for this but was told that it was
intended behavior and not a bug. So, to not get the blank line in the
PDF, we started this rule for &lt;para&gt; tags. I just tested it, and
it is not a problem with DocBook XML and XSL, so I am removing the
rule from the Docs Guide. (I never liked having to start the text
right after the tag either.)

Note You need to log in before you can comment on or make changes to this bug.