I added the download link for MCP documents. It all seems to work except that
the links don't have an "alt" text like it does with the ISO 19139. So when
I hover over the link I don't get any text displayed. I expected it to
display "Save this metadata as a Version 1.4 ISO19139 Marine Community
Profile XML file"
Can someone confirm if they are seeing the same issue. If so I will create
a ticket.
I added the link by using the following config override.
I can confirm that this works for me with mcp-1.4 and ANZMEST config overrides similar to yours - could be that you have a different language in use? The string for the 'alt' attribute is in the schema plugin directory eg. iso19139.mcp-1.4/loc/eng/strings.xml - but localized strings.xml files for languages other than english don't exist (be glad to add them if you have them though).
Cheers and thanks,
Simon
________________________________________
From: ianwallen [ianwallen@anonymised.com]
Sent: Saturday, 10 November 2012 4:34 AM
To: geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] alt text null for MCP download icons
I added the download link for MCP documents. It all seems to work except that
the links don't have an "alt" text like it does with the ISO 19139. So when
I hover over the link I don't get any text displayed. I expected it to
display "Save this metadata as a Version 1.4 ISO19139 Marine Community
Profile XML file"
Can someone confirm if they are seeing the same issue. If so I will create
a ticket.
I added the link by using the following config override.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
But what is weird is that the language on the web pages that was causing the
issue was English. All the content on the page was English. So I'm not sure
how changing the default language would make this fail.
I just did a test and if I create the fre/strings.xml with at least one
entry - does not have to be the "xml_iso19139.mcp-1.4" entry - then it
works. It almost looks like there is a bug in that if it cannot load the
strings.xml for the default language then it will not load any of the other
languages.
Does this make sense - or is this how it is suppose to work?