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 9CBF6104D9 for ; Thu, 15 Aug 2013 17:18:12 +0000 (UTC) Received: (qmail 7984 invoked by uid 500); 15 Aug 2013 17:18:12 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 7597 invoked by uid 500); 15 Aug 2013 17:17:59 -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 7571 invoked by uid 99); 15 Aug 2013 17:17:50 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Aug 2013 17:17:50 +0000 Date: Thu, 15 Aug 2013 17:17:50 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DERBY-4628) The Derby docs would be clearer if we replaced our jargon term "territory" with the term "locale" which is used commonly across the Java ecosystem. 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-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741204#comment-13741204 ] ASF subversion and git services commented on DERBY-4628: -------------------------------------------------------- Commit 1514383 from [~chaase3] in branch 'docs/trunk' [ https://svn.apache.org/r1514383 ] DERBY-4628 The Derby docs would be clearer if we replaced our jargon term "territory" with the term "locale" which is used commonly across the Java ecosystem. Modified 5 Reference Manual topics (and map), 3 Developer's Guide topics (and map), 5 Tools Guide topics (and map), and 1 Tuning Derby topic. Patch: DERBY-4628.diff > The Derby docs would be clearer if we replaced our jargon term "territory" with the term "locale" which is used commonly across the Java ecosystem. > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-4628 > URL: https://issues.apache.org/jira/browse/DERBY-4628 > Project: Derby > Issue Type: Improvement > Components: Documentation > Affects Versions: 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.3.0, 10.9.1.0, 10.10.1.1 > Reporter: Rick Hillegas > Assignee: Kim Haase > Attachments: derby-4628-01-aa-useLocaleInMessagesRatherThanTerritory.diff, DERBY-4628.diff, DERBY-4628.stat, DERBY-4628.zip > > > When talking about locales, the Derby user guides employ a piece of jargon which Java programmers do not commonly use. The user guides speak about "territories" instead of "locales". Here, for instance, is a puzzling sentence from the section on the territory attribute in the Derby Reference Guide: > "When creating or upgrading a database, use this attribute to associate a non-default territory with the database." > What, a Java developer might ask, is a territory? Reading more material from that page, it may become apparent that a territory is nothing more or less than what the JDK's javadoc calls a locale. The possible values for the territory attribute are nothing more or less than the names of locales supported by the VM. Our discussion of language-sensitive issues would be clearer if we used the common term rather than our private jargon. > This jargon is used across the user guides. Correcting it would be a systemic change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira