Handling of HTML in notes during export with RIS/MODS
skornblith
exports notes as HTML. While this is fine for RDF, it really shouldn't
be happening for BibTeX (and it's not anymore, as of a few minutes
ago), and we're not sure whether this is really what we want for RIS
and MODS export. There are several options:
1) Export notes as HTML.
2) Export notes as plain text. This breaks round-tripping of rich text
formatting.
3) Replace <p> and <br/> tags with newlines, but leave other HTML
formatting intact, so that HTML is only present if there was rich text
in the note, and rich text formatting still round-trips.
4) Show an option to determine whether notes should be exported as
HTML or plain text on export.
With options (1) and (4), we could determine whether a note was HTML
on import by checking for the presence of a <p> tag. With option (3),
plain text notes would be imported properly as long as they don't
contain a < or >.
Any opinions?
Bruce D'Arcus
> Zotero handles notes internally as HTML, but, at the moment, it also
> exports notes as HTML. While this is fine for RDF, it really shouldn't
> be happening for BibTeX (and it's not anymore, as of a few minutes
> ago), and we're not sure whether this is really what we want for RIS
> and MODS export.
MODS and RIS are kind of apples and oranges WRT to HTML.
MODS Is an XML language that should allow embedding HTML (or XHTML) in
its notes element, but I'm not sure if it does (?). If it doesn't,
then you need to strip the markup entirely. In any case, this isn't
really up to us, but to how the MODS schema is defined.
RIS is just a plain text format without any validation infrastructure
around it. So we can do whatever we want.
> There are several options:
>
> 1) Export notes as HTML.
> 2) Export notes as plain text. This breaks round-tripping of rich text
> formatting.
> 3) Replace <p> and <br/> tags with newlines, but leave other HTML
> formatting intact, so that HTML is only present if there was rich text
> in the note, and rich text formatting still round-trips.
> 4) Show an option to determine whether notes should be exported as
> HTML or plain text on export.
>
> With options (1) and (4), we could determine whether a note was HTML
> on import by checking for the presence of a <p> tag. With option (3),
> plain text notes would be imported properly as long as they don't
> contain a < or >.
>
> Any opinions?
I'd prefer #4, where the preference could also include #3 as an
option: full HTML, plain + inline HTML, and plain.
Bruce
Dan Stillman
> On Fri, May 27, 2011 at 4:10 PM, skornblith<si...@simonster.com> wrote
>> Zotero handles notes internally as HTML, but, at the moment, it also
>> exports notes as HTML. While this is fine for RDF, it really shouldn't
>> be happening for BibTeX (and it's not anymore, as of a few minutes
>> ago), and we're not sure whether this is really what we want for RIS
>> and MODS export.
> MODS and RIS are kind of apples and oranges WRT to HTML.
>
> MODS Is an XML language that should allow embedding HTML (or XHTML) in
> its notes element, but I'm not sure if it does (?). If it doesn't,
> then you need to strip the markup entirely. In any case, this isn't
> really up to us, but to how the MODS schema is defined.
It's not up to us whether we include raw HTML in MODS. But if it doesn't
allow it, it's still up to us whether we include escaped HTML.
Bruce D'Arcus
I'm in the "escaped markup is evil" camp, so that's where I stand.
I'll post a note on the MODS list about this.
Bruce
Richard Karnesky
http://listserv.loc.gov/cgi-bin/wa?A2=ind0407&L=MODS&P=R273&I=-3
the extension element would allow rich text notes. I'd agree with the
example: give plain text notes in MODS (for use by other clients), but
also include the rich text as an extension. This is obviously some
amount of duplication/size bloat in exported files, but it seems the
advantages outweigh this.
--Rick
Bruce D'Arcus
On May 27, 2011 6:15 PM, "Richard Karnesky" <karn...@gmail.com> wrote:
>
> You had asked a few years ago:
> http://listserv.loc.gov/cgi-bin/wa?A2=ind0407&L=MODS&P=R273&I=-3
Doh! How embarrassing.
> the extension element would allow rich text notes. I'd agree with the
> example: give plain text notes in MODS (for use by other clients), but
> also include the rich text as an extension. This is obviously some
> amount of duplication/size bloat in exported files, but it seems the
> advantages outweigh this.
Yes.
Bruce
> --Rick
>
> --
> You received this message because you are subscribed to the Google Groups "zotero-dev" group.
> To post to this group, send email to zoter...@googlegroups.com.
> To unsubscribe from this group, send email to zotero-dev+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/zotero-dev?hl=en.
>
