Return-Path: 
 <derby-dev-return-107069-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
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 8BB9E102E7
	for <apmail-db-derby-dev-archive@www.apache.org>;
 Tue, 22 Oct 2013 13:58:52 +0000 (UTC)
Received: (qmail 5614 invoked by uid 500); 22 Oct 2013 13:58:51 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 5378 invoked by uid 500); 22 Oct 2013 13:58:44 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:derby-dev-help@db.apache.org>
List-Unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 5325 invoked by uid 99); 22 Oct 2013 13:58:42 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Oct 2013 13:58:42 +0000
Date: Tue, 22 Oct 2013 13:58:42 +0000 (UTC)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12673975.1381869241668.104013.1382450322565@arcas>
In-Reply-To: <JIRA.12673975.1381869241668@arcas>
References: <JIRA.12673975.1381869241668@arcas>
Subject: [jira] [Commented] (DERBY-6379) Manuals are inconsistent in their
 use of the <shortdesc> 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:comment-tabpanel&focusedCommentId=13801832#comment-13801832 ] 

Knut Anders Hatlen commented on DERBY-6379:
-------------------------------------------

I think IBM JCE is mentioned because that particular functionality does not work with the JCE libraries that come with Oracle's JDK since the public prime specified by the DRDA spec is too short. More details here: [http://db.apache.org/derby/docs/10.10/adminguide/cadminapps811695.html]. I'm not sure, though, why this is listed as a difference between embedded and network.

+1 to removing 3.0 from the topic title.

I think the "Network Server console" means the standard output destination of the network server process. That is, when it says a message goes to derby.log and the network server console, it means that the network server writes the message to derby.log and System.out.

> 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: 10.10.1.1
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>
> 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
(v6.1#6144)