XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> - Stylus Studio - Registrar en o... (1)
-> + Stylus Studio - Registrar en o... (2)
-> + Can a pipeline send a file by ... (2)
-> + After Updateing WIN10 to WIN11... (12)
-> + Where do I add the custom java... (3)
-> + Where is the Diagram tab? (5)
-> + Applying XSLT to Word DOCX/XML (2)
-> - CSV conversion via ConvertToXM... (1)
-> + Text symbols in SS not same as... (4)
-> + Exposing xquery as webservice ... (6)
-> + Syntax Identifier (2)
-> + Saving a Converted XML as an X... (5)
-> + Output document cannot be pars... (4)
-> - Archiving output from conversi... (1)
-> + EDIFACT guideline from Stylus ... (3)
-> + CSV file putting all the data ... (5)
-> + Can't install Home version 64b... (5)
-> + presale - Can I covers this sc... (5)
-> + Problem with UNB (5)
-> + Splitting EDIFACT files pipeli... (4)
-- [1-20] [21-40] [41-60] 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.