[Xerte] Re: Query re formatting?

Julian Tenney Julian.Tenney at nottingham.ac.uk
Fri May 3 12:54:32 BST 2013


It'll be the ones where the text is escaped and held on a node attribute, rather than CDATAed and held as the node's payload. It isn't easy to escape the XML, load it into the editor, edit it and escape it again on the way out in those cases. You're sort of taking this to places it isn't really intended to go.

Things are better in bootstrap, because all text is CDATA, so HTML is safe, but it's not entirely safe in the toolkit.

From: xerte-bounces at lists.nottingham.ac.uk [mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Fay Cross
Sent: 03 May 2013 12:26
To: Xerte discussion list
Subject: [Xerte] Re: Query re formatting?

I've just tried < in text on a few pages and it's displaying as text for me.  Is it a problem on just some pages types?  Which ones?


I can fix the table <br> problem though.  It's adding brs in where ever there are line breaks which currently even includes in table markup.  So, for example:

<table><tr><td>Hello</td></tr></table>

... will look fine but...

<table>
<tr>
<td>Hello</td>
</tr>
</table>

... will add in lots of unnecessary brs.

I'll get it to ignore those between table tags.

From: xerte-bounces at lists.nottingham.ac.uk<mailto:xerte-bounces at lists.nottingham.ac.uk> [mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Alistair McNaught
Sent: 03 May 2013 10:04
To: xerte at lists.nottingham.ac.uk<mailto:xerte at lists.nottingham.ac.uk>
Subject: [Xerte] Query re formatting?

A colleague and I have been working on creating a training module for publishers on accessibility metadata. The metadata is in XML format and we are trying to embed it in XOT pages to illustrate different metadata and how it describes different parts of a book cover.

However it is proving a bit unpredictable in the code. Can anyone advise us on the following?

-- how does text containing the < character to work? It seems completely capricious, sometimes switching between displaying the < and trying to interpret it as markup even after you've got it all correct. In two editing sessions, I was unable to form an understanding of what the editor was doing to my text

-- the application appears to insert a predictable (but not controllable) number of blank lines (as <br>) above each <table> inserted in a text box. Can this be controlled?

Any advice would be welcome. Obviously it's brilliant to now have tables working in XOT but it would be nice if they weren't so stuffed with BRs. And is there a way to understand < behaviour or should we be using latex instead?

Many thanks

Alistair



Alistair McNaught
Senior Advisor
JISC TechDis Service
Higher Education Academy | Innovation Way | York | YO10 5BR
Mobile - +44 (0)7870567659
Skype - alistair_techdis
Twitter - @alistairm
Web - www.jisctechdis.ac.uk<http://www.jisctechdis.ac.uk/> | www.scoop.it/t/inclusive-teaching-and-learning<http://www.scoop.it/t/inclusive-teaching-and-learning>

This email is confidential and may be privileged. If you are not the intended recipient please accept our apologies. Please do not disclose, copy, or distribute information in this email nor take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Please inform us that this message has gone astray before deleting it. Please note that views expressed in this email are those of the author and do not necessarily represent those of the Higher Education Academy. Please note that this e-mail has been created in the knowledge that Internet e-mail is not a secure communications medium. We advise that you understand and observe this lack of security when e-mailing us. Although we have taken steps to ensure this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. The Higher Education Academy Registered No 4930131
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte/attachments/20130503/3f783fae/attachment.html>


More information about the Xerte mailing list