Bug 817741

Summary:	Spelling: lowercase java, and word boundaries
Product:	[Community] PressGang CCMS	Reporter:	Misty Stanley-Jones <misty>
Component:	Web-UI	Assignee:	Matthew Casperson <mcaspers>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.x	CC:	cbredesen, lcarlon, topic-tool-list
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-04 01:10:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Misty Stanley-Jones 2012-05-01 05:30:00 UTC

Lowercase "java" is probably incorrect with whitespace around it, but surrounded by _ or - or inside a <filename>, <code>, <literal>, <command>, or other similar tag, it is probably OK. I can't find any instances in topic 304.

Comment 1 Matthew Casperson 2012-05-04 00:24:34 UTC

In what situation would the word java by _ or - ever not be a <filename>, <code>, <literal>, <command>?

Comment 2 Matthew Casperson 2012-05-04 01:05:11 UTC

In the case of topic 304 the XML

<title>Optional: Set java_sdk_1.6.0.</title>

is returning the word java_sdk_1.6.0, which is being split up into the word java, sdk, 1, 6, and 0. "java_sdk_1.6.0" should be enclosed in a literal or something similar.

Comment 3 Matthew Casperson 2012-05-04 01:10:42 UTC

The spell checker has been modified to not split words based on an underscore or dash. This still doesn't resolve the issue with terms like "java_sdk_1.6.0" since it contains periods. Such terms will still have to be enclosed in the appropriate docbook tags.

Comment 4 Misty Stanley-Jones 2012-05-04 01:14:42 UTC

Well spotted. Thanks!