db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6379) Manuals are inconsistent in their use of the <shortdesc> element
Date Tue, 10 Jun 2014 20:49:01 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kim Haase updated DERBY-6379:

    Attachment: DERBY-6379-ref-clauses.zip

Attaching DERBY-6379-ref-clauses.diff, DERBY-6379-ref-clauses.stat, and DERBY-6379-ref-clauses.zip,
with changes to the dozen or so topics on SQL clauses. This patch omits the CONSTRAINTS clause,
which is being fixed in the latest patch for DERBY-6571, but includes the WHEN clause, which
is found under the "CREATE TRIGGER statement" topic rather than the "SQL clauses" topic.

M       src/ref/rrefsqlj13658.dita
M       src/ref/rrefsqlj15309.dita
M       src/ref/rrefsqlj31783.dita
M       src/ref/rrefsqlj14854.dita
M       src/ref/rrefsqljwindow.dita
M       src/ref/rrefsqlj21583.dita
M       src/ref/rrefsqljwhenclause.dita
M       src/ref/rrefsqljusing.dita
M       src/ref/rrefsqlj33602.dita
M       src/ref/rrefsqlj32654.dita
M       src/ref/rrefsqljexternalname.dita
M       src/ref/rrefsqljoffsetfetch.dita

Will commit tomorrow.

> Manuals are inconsistent in their use of the <shortdesc> element
> ----------------------------------------------------------------
>                 Key: DERBY-6379
>                 URL: https://issues.apache.org/jira/browse/DERBY-6379
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions:
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>             Fix For:,
>         Attachments: DERBY-6379-adminconcepts.diff, DERBY-6379-adminconcepts.stat, DERBY-6379-adminreference.diff,
DERBY-6379-adminreference.stat, DERBY-6379-admintasks.diff, DERBY-6379-admintasks.stat, DERBY-6379-devguide-branch.diff,
DERBY-6379-devguide-branch.diff, DERBY-6379-devguide.diff, DERBY-6379-devguide.stat, DERBY-6379-ref-clauses.diff,
DERBY-6379-ref-clauses.stat, DERBY-6379-ref-clauses.zip, DERBY-6379-ref-diag.diff, DERBY-6379-ref-diag.stat,
DERBY-6379-ref-diag.zip, DERBY-6379-ref-diag.zip, DERBY-6379-ref-exprs.diff, DERBY-6379-ref-exprs.stat,
DERBY-6379-ref-exprs.zip, DERBY-6379-ref-stmts-2.diff, DERBY-6379-ref-stmts-2.stat, DERBY-6379-ref-stmts-2.zip,
DERBY-6379-ref-stmts.diff, DERBY-6379-ref-stmts.stat, DERBY-6379-ref-stmts.zip, DERBY-6379-reffuncs.diff,
DERBY-6379-reffuncs.stat, DERBY-6379-refprocs.diff, DERBY-6379-refprocs.stat, DERBY-6379-toolstuning.stat
> When topics are organized as subtopics of other topics, our tools generate a list of
the subtopics at the end of the parent topic. If the DITA source of the subtopic begins with
a <shortdesc> element, the contents of the <shortdesc> appear under the subtopic
title in the parent topic. These contents also form the first paragraph of the subtopic. It
does not seem to be possible to suppress the list of subtopics; they appear in the HTML output,
but not in the PDF.
> Generally, the documentation is not consistent in its use of the <shortdesc> element.
> I'll add more detail in a comment.

This message was sent by Atlassian JIRA

View raw message