From jose.carlos.pereira at ist.utl.pt  Mon Feb  7 22:32:36 2011
From: jose.carlos.pereira at ist.utl.pt (Carlos Pereira)
Date: Mon, 07 Feb 2011 21:32:36 +0000
Subject: [Expat-discuss] Character data
Message-ID: <4D5064F4.50402@ist.utl.pt>

Hi,

data that looks like this in a XML file:

<foo>
1234 4567 891011
</foo>

is sometimes passed through a character data callback as this:
1234 45

and then in a second call:
67 891011

As this integer data has no fixed size, there seems to be no obvious way to
know whether the XML file contained these 3 numbers:
1234 4567 891011

or these these 4 numbers:
1234 45 67 891011

The only way I see to go around this issue is to add some special 
character (a i in this example), to mark where each number actually 
ends, for example:

1234i 4567i 891011i

could be passed in the callback as:
1234i 45

and then in another call:
67i 891011i

so I could see that 45 and 67i belong to the same number. However, this 
seems a bit ugly... what about XML formats that may include large blocks 
of numerical data (for example X3D...)?? is there a better solution? 
what am I missing here?

Thanks a lot for your help!
Carlos Pereira


From robert.bielik at xponaut.se  Mon Feb  7 22:10:53 2011
From: robert.bielik at xponaut.se (Robert Bielik)
Date: Mon, 07 Feb 2011 22:10:53 +0100
Subject: [Expat-discuss] Character data
In-Reply-To: <4D5064F4.50402@ist.utl.pt>
References: <4D5064F4.50402@ist.utl.pt>
Message-ID: <4D505FDD.2090504@xponaut.se>

Carlos Pereira skrev 2011-02-07 22:32:
>
> so I could see that 45 and 67i belong to the same number. However, this seems a bit ugly... what about XML formats that may include large blocks of numerical data (for example X3D...)?? is there a better solution? what am I missing here?

Just append the character data during parsing, so that at first call the chardata string is:

chData = "1234 45"

then after next char data callback it is:

chData = "1234 4567 891011"

then you process the chData string in your endElement ("foo") handler.

Regards,
/Rob

From jose.carlos.pereira at ist.utl.pt  Tue Feb  8 00:09:22 2011
From: jose.carlos.pereira at ist.utl.pt (Carlos Pereira)
Date: Mon, 07 Feb 2011 23:09:22 +0000
Subject: [Expat-discuss] Character data
In-Reply-To: <4D505FDD.2090504@xponaut.se>
References: <4D5064F4.50402@ist.utl.pt> <4D505FDD.2090504@xponaut.se>
Message-ID: <4D507BA2.5080405@ist.utl.pt>

On 02/07/11 21:10, Robert Bielik wrote:
> Carlos Pereira skrev 2011-02-07 22:32:
>>
>> so I could see that 45 and 67i belong to the same number. However, 
>> this seems a bit ugly... what about XML formats that may include 
>> large blocks of numerical data (for example X3D...)?? is there a 
>> better solution? what am I missing here?
>
> Just append the character data during parsing, so that at first call 
> the chardata string is:
That's good advice, thanks. In some cases these data blocks may well 
contain thousands of double or int values, so I am trying to parse and 
save them to final arrays as soon as possible.

my mistake is I am removing (\t\n ) delimiters, before properly parsing 
this.

Thanks a lot for clarifying this for me!
Carlos


>
> chData = "1234 45"
>
> then after next char data callback it is:
>
> chData = "1234 4567 891011"
>
> then you process the chData string in your endElement ("foo") handler.
>
> Regards,
> /Rob
> _______________________________________________
> Expat-discuss mailing list
> Expat-discuss at libexpat.org
> http://mail.libexpat.org/mailman/listinfo/expat-discuss
>


From boris at codesynthesis.com  Wed Feb 16 13:48:01 2011
From: boris at codesynthesis.com (Boris Kolpackov)
Date: Wed, 16 Feb 2011 12:48:01 +0000 (UTC)
Subject: [Expat-discuss] [ANN] CodeSynthesis XSD/e 3.2.0 released
Message-ID: <ijgh20$4il$2@dough.gmane.org>

Hi,

I am pleased to announce the availability of CodeSynthesis XSD/e 3.2.0.

CodeSynthesis XSD/e is an open-source (GPL2 + free/commercial proprietary
licenses), dependency-free XML Schema to C++ compiler for mobile, embedded,
and light-weight applications. It provides XML parsing, serialization, XML
Schema validation and XML data binding while maintaining a small footprint
and portability. XSD/e uses Expat as the underlying XML parser.

Major new features in this release:

  * Mapping of XML Schema enumerations (xs:enumeration) to C++ enums.

  * Configurable application character encoding (UTF-8 or ISO-8859-1).

  * Support for custom memory allocators.

  * Support for schema evolution using substitution groups. Both the
    'ignore' and 'passthrough' models for unknown content are supported.

  * Generation of clone functions for variable-length types.

  * Improved support for XML Schema facet validation, including
    xs:pattern.

This release also adds official support, instructions, and sample
configuration files for the following platforms/toolchains:

Android/Android NDK
Symbian/CSL-GCC (GCCE)
Integrity 178b/Green Hills MULTI C/C++

It is now also possible to build the XSD/e runtime library for iPhoneOS/iOS
with the XCode project.

For the complete list of new features in this release see:

http://www.codesynthesis.com/pipermail/xsde-announcements/2011/000010.html

Supported mobile/embedded targets include Embedded Linux, VxWorks, QNX,
LynxOS, Integrity 178b, iPhoneOS/iOS, Android, Symbian, and Windows
CE/Mobile. Precompiled binary distributions are available for GNU/Linux,
Mac OS X, Solaris, and Windows host development platforms.

More information, documentation, source code, and precompiled binaries
are available from:

http://www.codesynthesis.com/products/xsde/

Enjoy,
	Boris


From jzhang at ximpleware.com  Fri Feb 25 23:23:48 2011
From: jzhang at ximpleware.com (jimmy Zhang)
Date: Fri, 25 Feb 2011 14:23:48 -0800
Subject: [Expat-discuss] [ANN]VTD-XML 2.10
In-Reply-To: <mailman.51.1297940403.13922.expat-discuss@libexpat.org>
References: <mailman.51.1297940403.13922.expat-discuss@libexpat.org>
Message-ID: <594903E20C1D45E98FECEE2EB98406D9@JimmyZhangPC>

VTD-XML 2.10 is now released. It can be downloaded at 
https://sourceforge.net/projects/vtd-xml/files/vtd-xml/ximpleware_2.10/.
This release includes a number of new features and enhancement.

* The core API of VTD-XML has been expanded. Users can now perform 
cut/paste/insert on an empty element.
* This release also adds the support of deeper location cache support for 
parsing and indexing. This feature is useful for application performance 
tuning for
processing various XML documents.
* The java version also added support for processing zip and gzip files. 
Direct processing of httpURL based XML is enhanced.
* Extended Java version now support Iso-8859-10~16 encoding.
* A full featured C++ port is released.
* C version of VTD-XML now make use of thread local storage to achieve 
thread safety for multi-threaded application.
* There are also a number of bugs fixed. Special thanks to Jozef Aerts, John 
Sillers, Chris Tornau and a number of other users for input and suggestions