dspace 7 default license

[Bill Tantzen]

All,

In DSpace 7.3, the displayed license text does not respect the line breaks and extra whitespace in default.license (as it did in v5.10).

Is this a theming issue?  Is there a way to reintroduce the line breaks for readability?

Thanks for any advice!

~~Bill

--

Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp
________________________________________________________________
Bill Tantzen    University of Minnesota Libraries
612-626-9949 (U of M)    612-325-1777 (cell)

[Mark H. Wood]

On Tue, Aug 09, 2022 at 02:20:02PM -0500, 'Bill Tantzen' via DSpace Technical Support wrote:
> In DSpace 7.3, the displayed license text does not respect the line breaks
> and extra whitespace in default.license (as it did in v5.10).
>
> Is this a theming issue? Is there a way to reintroduce the line breaks for
> readability?

I sympathize. We're going to have that same issue here.

It's going to be a bit tricky, though. To fit a variety of display
widths, the text really should be filled. To do this *and* permit
arbitrary breaks, indents and the like requires some kind of embedded
markup.

And have we given sufficient thought to the accessibility of the
license text? If it's just a single ragged rectangle then this is
fairly easy. Structured text is more difficult.

--
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu

[Bill Tantzen]

Right, and I really don't want markup in a txt file...

--
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
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 dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/YvOfvD4WeWscFXH8%40IUPUI.Edu.

[Michael Plate]

Hi,

Am 10.08.22 um 14:13 schrieb 'Bill Tantzen' via DSpace Technical Support:

> Right, and I really don't want markup in a txt file...

[…]

we have the same problem with some metadata fields where we like to have
\n converted to <br/>.

I still have no time to start with Angular in DSpace, but my idea was a
pipe for that, so I just use <…| nl2br> in the template…
Or is that a wrong idea ?

Michael

[Mark H. Wood]

On Wed, Aug 10, 2022 at 07:13:32AM -0500, 'Bill Tantzen' via DSpace Technical Support wrote:
> Right, and I really don't want markup in a txt file...

Well, we could devise a really *simple* language. It could be as
simple as:

o leading whitespace means indent;

o one or more consecutive empty lines means a paragraph break.

But, to fit into a page that must be pourable into a viewport of any
width, the text must be *rendered*, not just flung out as-is.

Right now I think we're getting what happens when you stick arbitrary
character content with no markup inside a <div>. It works, but we
lose too much structure.

You could work around this a bit by altering the page template so that
the license text is surrounded by <pre></pre>, but that will only work
well at one size because it depends on the text being already
formatted to fit the screen's width.

There are similar difficulties with abstracts and the like, for which
there is an issue on file. I don't think that the same solution will
work for all of these. I just point out a general problem.