XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » Stylus Studio Technical Forum » Another whitespace issue with EDI to XM
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + JVM/stylus studio abort on sav... (3)
-> + using oasis catalog in pipelin... (6)
-> - Another whitespace issue with ... (2)
-> ->Another whitespace issue ...
-> + saxon 9.1.0.2 (2)
-> + xslt change namespace (4)
-> - xslt change namespace (1)
-> + HL7 Conversion (3)
-> + mixed content mapping (2)
-> + HL7 to XML to HL7 (5)
-> + newest version of Saxon SA? (3)
-> + ORM / ORU Seqments (7)
-> + XSLT is causing Java.lang OutO... (3)
-> + Create POJOs from EDI (4)
-> - Embedded message (1)
-> + How to create Documentation fo... (2)
-> + xslt transformation (2)
-> - remove BOM (1)
-> + Changing data as it goes into... (5)
-> + How to (graphically) map one X... (2)
-> + Stylus Studio 2008 Release 2 -... (2)
-- Previous [961-980] [981-1000] [1001-1020] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
andy standleySubject: Another whitespace issue with EDI to XM
Author: andy standley
Date: 13 Oct 2008 05:12 PM
When I convert an EDIFACT file with

FTX+AAA+++THIS IS A SENTENCE THAT IS LONGER THAN THE 70 CHARACTERS ALLOWED FOR :ONE DATA ELEMENT'

the xml conveter ends up with
<FTX>
<FTX01>AAA</FTX01>
<FTX0401>THIS IS A SENTENCE THAT IS LONGER THAN THE 70 CHARACTERS ALLOWED FOR</FTX0401>
<FTX0401>ONE DATA ELEMENT</FTX0401>

and when converted back to EDIFACT IT BECOMES

FTX+AAA+++THIS IS A SENTENCE THAT IS LONGER THAN THE 70 CHARACTERS ALLOWED FOR:ONE DATA ELEMENT'

so the FTX loses its meaning.

Is there anyway to preserve this whitespace?

andy
Posttop
Tony LavinioSubject: Another whitespace issue with EDI to XM
Author: Tony Lavinio
Date: 23 Feb 2009 12:44 PM
No, because that whitespace is invalid.
See http://www.unece.org/trade/edifact/untdid/d422_s.htm#compressing

The general idea used in most forms of EDI is that when text is split
across multiple elements, when rejoined spaces should be inserted.
We've seen more sophisticated joiners, but depending on trailing spaces
isn't guaranteed to survice the serialization/deserialization steps.

   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.