[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.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.3.0, 10.9.1.0, 10.10.1.1
• Fix Version/s: 10.10.2.0, 10.11.1.1
• Component/s: Documentation
• Assignee: Camilla Haase
• Reporter: Richard N. Hillegas
• Created: 23/Apr/10 16:21
• Updated: 16/Apr/14 02:41
• Resolved: 29/Aug/13 15:45

Description

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.