• Chapter 1: Getting Started with Stylus Studio®
• Chapter 2: Editing and Querying XML
• Chapter 3: Converting Non-XML Files to XML
  • Introduction
  • DataDirect XML Converters
  • Custom XML Converters
  • The Custom XML Conversion Definition Editor
  • Parts of an Input File
  • Working with Regions
  • Working with Fields
  • Controlling XML Output
    • Specifying Element Names
    • Specifying Format
    • Omitting Regions and Fields, and Rows
    • Pattern Matching
    • Using Lookup Lists
    • Using Key=Value Characters
  • Creating a Custom XML Conversion Definition
  • Using Custom XML Conversion Definitions in Stylus Studio
  • Working with EDI Conversions
  • The Converter URL Scheme
  • Custom XML Conversion Definitions Properties Reference
• Chapter 4: Working with XSLT
• Chapter 5: Creating XSLT Using the XSLT Mapper
• Chapter 6: Debugging Stylesheets
• Chapter 7: Defining XML Schemas
• Chapter 8: Defining Document Type Definitions
• Chapter 9: Writing XPath Expressions
• Chapter 10: Working with XQuery in Stylus Studio
• Chapter 11: Composing Web Service Calls
• Chapter 12: Working with WSDL Documents
• Chapter 13: Building XML Pipelines
• Chapter 14: Publishing XML Data
• Chapter 15: Integrating with Third-Party File Systems
• Chapter 16: Extending Stylus Studio
• Chapter 17: The Stylus Studio Java API
• Chapter 18: Stylus Studio GUI Reference

Home > Online Product Documentation > Table of Contents > Using Key=Value Characters

Using Key=Value Characters

The Key=Value Character Region property allows you to set the separator for key=value pairs as seen in the input file. When Stylus Studio converts an input file to XML, it uses the value on the left side of the key=value character for the element name, and the value on the right for the element value. Consider the following input file:

Triumph Inventory,Year and Quantity
               
Yr2003=24
               
Yr2004=12
               
Yr2005=15
               

            

If you set the Key=Value Character property to =, Stylus Studio creates the following XML document when you preview the custom XML conversion:

<?xml version="1.0" encoding="utf-8"?>
               
<root>
               
	<row>
               
		<field>Triumph Inventory</field>
               
		<field>Year and Quantity</field>
               
	</row>
               
	<row>
               
		<Yr2003>24</Yr2003>
               
	</row>
               
	<row>
               
		<Yr2004>12</Yr2004>
               
	</row>
               
	<row>
               
		<Yr2005>15</Yr2005>
               
	</row>
               
</root>