× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Henrik,

I have no idea what the details of the XML document that Kurt is writing to
XML are. I was just suggesting an RPG solution to his problem.

most XML readers ignores the number of decimals as long as they are zero

It sounds like you're saying that most XML readers will return the same
values for the following 3 values:

<value>123.0</value>
<value>123.00</value>
<value>123.000</value>

Is that what you meant? Because that's not the case with any XML parser I've
used. Or are you talking about something that runs on top of a parser (a
'reader'?) where you tell it to convert the character string into a number?
If so, then that's possibly true, but it doesn't have anything to do with
this. Since Kurt is trying to *write* a value to XML, he doesn't know
whether the eventual reader will pay attention to the number of decimals -
he's just trying to get the correct value into the XML document. If the WSDL
or DTD says the value should include e.g. 3 decimal places, then he has to
supply 3 decimal places, even if they're all zero.

As far as whether currency should be passed as an attribute, surely that's
up to the XML document in question?

Rory

On Tue, Apr 6, 2010 at 9:44 AM, <hr@xxxxxxxxxxxx> wrote:

Hi Rory,

most XML readers ignores the number of decimals as long as they are
zero and currency should be passed as a attribute, so what is the
problem ?

/henrik


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.