Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5B1F9102ED for ; Wed, 16 Apr 2014 20:12:16 +0000 (UTC) Received: (qmail 63066 invoked by uid 500); 16 Apr 2014 20:12:15 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 63035 invoked by uid 500); 16 Apr 2014 20:12:15 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 63025 invoked by uid 99); 16 Apr 2014 20:12:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Apr 2014 20:12:15 +0000 Date: Wed, 16 Apr 2014 20:12:15 +0000 (UTC) From: "Kim Haase (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Reopened] (DERBY-6379) Manuals are inconsistent in their use of the element MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase reopened DERBY-6379: ------------------------------ It turns out that the element is essential for search engine optimization. Its contents are used for the description attribute of a meta element in the generated HTML. It appears that the contents of the description attribute are in turn used by search engines. This means that all topics that we want found by search engines should have a shortdesc element that includes keywords relevant to that topic. In practice, this means that we need to add shortdesc elements to the Tools Guide, Tuning Derby, and the remaining topics in the Reference Manual. > Manuals are inconsistent in their use of the element > ---------------------------------------------------------------- > > Key: DERBY-6379 > URL: https://issues.apache.org/jira/browse/DERBY-6379 > Project: Derby > Issue Type: Improvement > Components: Documentation > Affects Versions: 10.10.1.1 > Reporter: Kim Haase > Assignee: Kim Haase > Priority: Minor > Fix For: 10.11.0.0, 10.10.2.0 > > 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-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 element, the contents of the 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 element. > I'll add more detail in a comment. -- This message was sent by Atlassian JIRA (v6.2#6252)