[gui-dev] Re: [trans] Somethings in Finnish for verdyp

Philippe Verdy

2004-09-28 18:30:24 UTC

Using newer XSD and binding xsi attributes are unrelated.

Newer XSD schemas are conforming to XML and XSD 1.1 definitions. They work without change in LimeWire, despite their internal structure differ (there are additional container elements, that are ignored currently by LimeWire, that only checks for the presence of some elements, whatever their encapsulation level).

The "xsi:" namespace attribute comes from meta-data generated by LimeWire within XML documents. Unfortunately, these XML meta-data documents are already non-conforming and Xerces reject them, directly when trying to parse them, and long before they are validated against any schema.

There's little we can do, except modifying (hacking) these XML meta-data, to remove the unbound "xsi:" attribute, before parsing them with Xerces. Only if these documents parse correctly, we will be able to validate them against a schema, if we do that (currently we don't really validate them against a XSD schema, as we use our own XML DOM tree parser to extract only some elements, recognized by their name and not by their position.

The correct way to include a xsi attribute in XML meta data would be to include the "xsi" prefix binding within the XML meta-data, with a namespace definition, but XML documents will be a bit longer as this would mean adding:
xmlns:xsi="...some URL..."
in the element using the "xsi:..." attributes. the URL needs not be refered, it's just for the namespace, so we could as well write this binding like this:
xmlns:xsi="xmlns:xsi"
(this URL is using the "xmlns:" URI scheme)

The other way would mean removing the "xsi:" prefix, but then the attribute name that follows it would become part of the meta-data schema, and would need to be included in each XSD file.

Finally the other way would be to specify to Xerces that it should parse XML documents without namespaces, according to XML 1.0 rules (which had no namespaces, so that "xsi:" is not recognized as a separate namespace identifier prefix but is part of the attribute name).

----- Original Message -----
From: Sam Berlin
To: LimeWire Translation
Sent: Tuesday, September 28, 2004 4:55 PM
Subject: Re: [trans] Somethings in Finnish for verdyp

Hi Philippe,

Are there any backwards compatibility issues with using newer XSD schemas and binding the xsi attribute? Will the information still be parse-able by older LimeWires? We've been thinking about upgrading the xerces parser, as well, since we no longer need to use the really old one (which was Java 1.1.8 compliant) and the newer one is smaller and faster, and these changes would go hand-in-hand.

Thanks,
Sam

On Tuesday, September 28, 2004, at 10:51 AM, Philippe Verdy wrote:

Thanks. As I am working on upgrading the various localization files, I will propose to take these resource files in the library where I have commited them. I can't see why they are still taken from the legacy [gui]/com/limegroup/gnutella/gui/resources/ directory.
I imported this directory into the [lib] module, and I will propose patches in LimeWire to make these files accessible from there (this requires a small change in the code that handles these GUI "resources").

One note to LimeWire: the [schemas] modules is the place where I used to put incoming schemas. I have no more write access to it, so I cannot change it. The "xml/display/" folder is the only one I can put the translated properties. Note that LimeWire continues to use deprecated .xsd files that are still not complying with the current XML standard. Also LimeWire still sends invalid XML meta-data that can't be parsed with Xerces, because of the unbound "xsi:" attribute name prefix (this causes fatal errors that make meta-data sent in query hits completely ignored).
Compliant .xsd files are in the [schemas] module, but LimeWire still uses the old ones.

----- Original Message -----
From: Ilkka Mäkelä
To: ***@limewire.org
Sent: Tuesday, September 28, 2004 1:14 PM
Subject: [trans] Somethings in Finnish for verdyp

(See attached file: about.html)(See attached file: book.properties)
(See attached file: audio.properties)(See attached file: video.properties)

<image.tiff>

_______________________________________________
translate mailing list
***@lists.limewire.org
http://www.limewire.org/mailman/listinfo/translate

_______________________________________________
translate mailing list
***@lists.limewire.org
http://www.limewire.org/mailman/listinfo/translate