As we're developing our new DSpace implementation, we're looking to put 
customized licenses on collections, and I noticed something odd.

The license display code in the xmlui interface does simple HTML parsing 
(the 'default.license' text file can have basic HTML in it, and it's parsed 
appropriately), but when you go to edit a collection, the license there 
CANNOT have HTML in it whatsoever.

We have one particular collection which we needed to have a customized 
license on (with some external links) and I'm running into problems with 
this.

My question is:

Why does this code have a simple HTML parser, but the collection version 
only allow for text? Is there a logical reason behind this?

Is there a simple way to work around this and ALLOW HTML in the collection 
versions?  (Note: We do NOT use the jspui, only the xmlui)

Thanks,

Alex

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Reply via email to