yes guys you are right but not to have the possibility to use bold character
or dotted list etcetera sometimes makes hard a good description.
On Wed, Jul 15, 2009 at 3:11 PM, Andrew Marlow marlow.and...@googlemail.com
wrote:
FWFW, I have seen lengthly and complex abstracts with alot of markup
FWFW, I have seen lengthly and complex abstracts with alot of markup
including math and/or chemistry markup, including embedded LaTeX.
On Tue, Jul 14, 2009 at 1:39 PM, Mark H. Wood mw...@iupui.edu wrote:
Now, *I* think that an abstract
should be a single brief block of text -- three, perhaps
On the one hand I tend to agree that markup shouldn't be part of
metadata.
On the other, if there are places where DSpace needs to write out,
say, XML with metadata as attribute values or element content then it
should be encoding it properly no matter what those values are.
And, strangely, I
As someone who has spent a lot of time talking with folks about
'shareable' metadata, I just want to second Mark's comment that we
really should not be putting html content into metadata fields. If you
want a feel for what this looks like downstream, do a search on p (or
other html tags of
Antonio,
It is unclear why your case is not working. I can assure you that a
default installation of DSpace Manakin XMLUI will allow you to place
html in the form fields for any Community/Collection and that will
render as HTML in the Community/collection views without being
escaped, this is
Dear Mark, it's the common behavior with all the DSpace installation i have
seen (MIT included).
The problem is that all the data in the field dc.description are saved as
plain text for security issues.
so the data must to be reconverted in html before being pushed to the UI.
so, do you know
Diggory
Cc: dspace-tech; dspace-de...@lists.sourceforge.net
Subject: Re: [Dspace-tech] [Dspace-devel] [Dspace-general] show HTML data
Dear Mark, it's the common behavior with all the DSpace installation i have
seen (MIT included).
The problem is that all the data in the field dc.description are saved
I'm going to chime in here as I've also recently been working with an
issue related to (read: learning about) html content within dc tags
and the rendering thereof within Manakin (cocoon).
Antonio, you and I are in the same situation. We both have html data
(actually stored with entity
On Mon, Jul 13, 2009 at 7:07 AM, Antonio Cuomoanto...@parliaments.info wrote:
Dear Mark, it's the common behavior with all the DSpace installation i have
seen (MIT included).
The problem is that all the data in the field dc.description are saved as
plain text for security issues.
I
Mark,
Many thanks for your comments!
And to the audience at large, for what it's worth, I'm certainly in
agreement with Mark and Alan concerning the use of html within
metadata fields. I believe the only reason we have this going on in
our repository is due to a messy recovery we had to
10 matches
Mail list logo
