Hi Nicky,

I think your issue is that your content is not properly UTF8 encoded.
I had a quick peak and it looks like the dash between 1853 and 1890 is
iso-8859-1, not UTF8.

You probably copied and pasted some text from a non UTF8 editor,
introducing the wrong dash. I would have guessed that the GGE would
have reported this issue though.

I always suggest to run the gadget spec through an XML validator
before submitting for directory inclusion, as this is a known issue
that the directory will just ignore any gadget not UTF8 encoded, even
though it will not report any error.

Jerome

On Apr 15, 8:53 am, nicky <[email protected]> wrote:
> http://hosting.gmodules.com/ig/gadgets/file/109548057311228444554/gau...
>
> The gadget itself seems to work fine on iGoogle in firefox, ie7.
> Firebug doesn't show anything.
>
> I originally coded it as a type HTML gadget. The dynamic height worked
> nicely on Ning. I submittted to the Google gadget directory.
>
> However, it repeatedly failed submission to two popular third party
> directories (Mini Apps & Google modules). Wondering if this was down
> to the way I coded it, I changed it to a type URL gadget to see if
> that approach made a difference.
>
> It hasn't, plus dynamic height doesn't work on Ning now. So, I will
> most likely change it back to a type HTML gadget.
> I had a colon ":" in the directory_title line 9 which I also removed.
>
> I am awaiting a response from the directories concerned.Mini apps
> directory always gives this error:
>
> not well-formed (invalid token) line: 8 
> inhttp://hosting.gmodules.com/ig/gadgets/file/109548057311228444554/gau...
>
> Would be grateful for any insight.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"iGoogle Developer Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Gadgets-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to