Perhaps there is a limit on how much "properties" an object can use, or the length of the name of the objects. Any practical reason you are using associative arrays? Perhaps you can change it to a simple array:
var airportPages = ; ... airportPages.push ([airportTitle, [pg]); ... for (a=0; a<airportPages.length; a++) $.writeln (airportPages[a]+" "+airportPages[a]);
(This also adds the advantage that you can sort on page numbers!)
In fact I realized later why it wasn't working. This is the same root matter than my post on xmlElement contents.
I think that the properties were correctly defined in some way but the strings must have contained the markers.
i.e. the property looked to be "toto" but i was in fact <xmlMarker>toto</xmlMarker>
I didn't check that from then as I made things differently but I think this is the source for all my troubles.
As you presumed, I changed to an array approach that did the trick once I understood the markers trick.
Why object in the first place ? I like the fact to call a value associationg the object and the property. With an array you have to loop for every element to check if the data is the one you want. I find object more straight. But maybe I am wrong ?
Anyway, that was my vision.
Thx for your interest. And plus, you gave me one key feature for using arrays better than objects : sorting !