Thanks for that, but... I'm a little confused here.
I have to tell folks how to enter multiple lines in a spread sheet
(they're mostly going to be using Excel, a few will be using
OpenOffice Calc). That's the infrastructure and nothing I can do
about that (when people volunteer to do work at home, you don't want
to make it hard for them, you know?). I know that, on a Linux/Unix
box, you can simply do Ctrl-V followed by Ctrl-L and there you go
but what do they do in winders? Is <br> an actual pattern they
can type that will actually do something or would I need to pass the
CSV though sed to substitute that pattern with an actual
Ctrl-L (not too clear on this point)? Gotta keep it as simple as
If fiddling with XSL is needed, where do I do the fiddling? One of
I'm guessing structural.xsl might be a candidate (probably not
find . -type f -name '*xsl*' | xargs fgrep -l
<!-- Head metadata in item pages -->
and change that to "no" or "false" (and do I have to rebuild
something after editing)?
Sorry, just a little confused about all this.
On 09/03/2013 04:18 PM, helix84 wrote:
I know you won't like the approach, but literal newlines are preserved
if quoted. So this would be a valid one-line CSV with multiline value:
"first column","second column first line
second column second line"
However, the newlines will be lost when rendered by XSL. You may
however experiment with the disable-output-escaping in XSL to try to
render them literaly, or to render the <br> tag.
Compulsory reading: DSpace Mailing List Etiquette