This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 23746 - Improve template & settings texts
Summary: Improve template & settings texts
Status: RESOLVED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC All
: P3 blocker (vote)
Assignee: issues@xml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-20 15:32 UTC by _ pkuzel
Modified: 2003-03-14 20:54 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ pkuzel 2002-05-20 15:32:06 UTC
Hi all,

I went through the resource bundles for XML module
and made some
recommendations about what needs changing. They're
in the attached
document. Please take a look and tell me what you
think.

-John




Suggested text changes:

In XML and DTD, rename "XML Document Wizard" to
just "XML Document"
        They're all supposed to be template names,
and the wizard is the New wizard, these
        are just additional panes.
Rename "XML and DTD" to just "XML", since DTD
isn't the only other type of file there any more.

Template Descriptions
=====================

OASIS XML Catalog
Using this template, you can create an OASIS XML
Catalog filethat maps external entity references
to local resources. You can then mount the catalog
under XML Entity Catalogs in the Runtime
tab of the Explorer.

XML Schema
Using this template, you can create an XML Schema
document that specifies the namspaces and 
data type constraints for an XML document.

XML Document
Allows you to create a new XML document. You can
create regular well-formed XML documents 
or documents that are constrained by a DTD or XML
Schema.

DTD Entity
Using this template you can create a new document
type definition (DTD). DTDs describe the 
tags that can be used in an XML file and indicates
the valid arrangement of those tags. 

XSL Stylesheet
Using this template, you can create an empty
extensible style sheet (XSL) document. Use XSL 
documents to specify display characteristics, tag
conversions, and addressing mechanisms for
 your XML document. 
 
XML Parsed Entity
What's this for again?

Cascading Style Sheet
Using this template, you can create an empty
cascading style sheet (CSS) document. Use a CSS 
to format the information from your XML document.


Wizard Text
===========

Select Document Type
Select the type of XML document you want to create
based on your document structure, data types,
and namespace requirements.

Well-Formed Document
DTD-Constrained Document
XML Schema-Constrained Document

DTD Options
Specify the following DTD options for your
document.

Schema Options
Specify the schema location and the namespace of
your document's root element.

XSL Transformation Dialog
=========================

Remove the "<Specify XSLT Script>" from the combo
box.

XML Options
===========

Tree Editor Settings > XML Editor Settings
        The docs no longer refer to the XML text
editor and the XML tree editor, now they're just
        XML Editor and Source Editor.
        
Also need tooltips for node view settings, I'll
write some up.
Comment 1 John Jullion-ceccarelli 2002-05-20 15:38:49 UTC
Petr, are you going to make these changes or should I? 
Also, I need a description of what exactly the XML Parsed 
Entity template does so I can check the existing template 
description.
Comment 2 _ lkramolis 2002-05-20 16:09:03 UTC
<http://www.w3.org/TR/2000/REC-xml-20001006#TextEntities>

XML Element content can refer to (include) external document which
need not to be a well formed XML documents and such included documents
are XML parsed entities and has usually .ent extension.
Comment 3 _ pkuzel 2002-05-20 17:33:28 UTC
John who will be faster? I bet on you :-).
Comment 4 _ lkramolis 2002-05-20 17:41:20 UTC
- "<Specify XSLT Script>" is necessary, please do not remove it.

- 'Tree Editor Settings > XML Editor Settings' is already done.
Comment 5 John Jullion-ceccarelli 2002-05-21 10:30:01 UTC
OK, I'll do it. 

Libor, Why is "<Specify XSLT Script>" necessary?

Also, can I make the following changes:

Sun's Resolver -> Sun Resolver
Prefer Public -> Prefer Public ID
Comment 6 _ pkuzel 2002-05-21 10:34:12 UTC
Catalog text changes are OK.
Comment 7 _ pkuzel 2002-06-03 12:27:40 UTC
Let these are considered while planning next release.
Comment 8 Marek Grummich 2002-07-19 21:03:56 UTC
Target milestone was changed from 'not determined' to TBD.
Comment 9 _ pkuzel 2003-03-14 20:54:43 UTC
It was integrated.