You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2013/11/15 14:13:21 UTC
[jira] [Closed] (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.
[ https://issues.apache.org/jira/browse/DERBY-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas closed 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.
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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
> Fix For: 10.10.1.3, 10.11.0.0
>
> Attachments: DERBY-4628.diff, DERBY-4628.stat, DERBY-4628.zip, derby-4628-01-aa-useLocaleInMessagesRatherThanTerritory.diff, derby-4628-01-ab-useLocaleInMessagesRatherThanTerritory.diff
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)