[
https://issues.apache.org/jira/browse/DERBY-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-4628:
-----------------------------
Attachment: DERBY-4628.zip
DERBY-4628.stat
DERBY-4628.diff
Attaching DERBY-4628.diff, DERBY-4628.stat, and DERBY-4628.zip, with changes to
the following files:
M src/tuning/rtuntransform208.dita
M src/ref/rrefattrib56769.dita
M src/ref/rrefattrib26867.dita
M src/ref/crefmpref23947.dita
M src/ref/rrefattribcollation.dita
M src/ref/rrefsqlj75638.dita
M src/ref/refderby.ditamap
M src/devguide/derbydev.ditamap
M src/devguide/cdevin10613.dita
M src/devguide/tdevdvlpcollation.dita
M src/devguide/cdevcollation.dita
M src/tools/rtoolsijlocale.dita
M src/tools/derbytools.ditamap
M src/tools/ctools1004764.dita
M src/tools/rtoolsijpropref97949.dita
M src/tools/ctoolsijtools45180.dita
M src/tools/ctoolsijtools11318.dita
I changed "territory" (singular and plural) to "locale" where appropriate.
I'm afraid I took the liberty of making some formatting fixes at the same time,
so the diffs might not be that easy to decipher. You can see the changes in the
HTML files, however.
Two error messages that appear in the Reference Manual topic
rrefexcept71493.dita also contain references to "territory", but that change
will need to be made in the code source.
> 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
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Attachments: 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
