<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Apr 12, 2013 at 3:14 PM, Matěj Cepl <span dir="ltr"><<a href="mailto:mcepl@redhat.com" target="_blank">mcepl@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 12/04/13 08:04, John Austin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sword should support basic indents and line breaks. Content providers<br>
should be able to control the formatting of their texts and should not<br>
be required to assign their content to artificial <p>...</p> or other<br>
containers to do so. Although these containers might be useful, the text<br>
of some translation styles cannot be fit nicely into them. But often<br>
content providers do rightly desire their texts to appear with<br>
formatting similar to their printed texts, since this is exactly what<br>
the translators deemed easiest to read and understand.<br>
</blockquote>
<br></div>
If I may give my 0.02 CZK, I would think that the answer is simple: No. This goes against the fundamental rule of XML, which is the separation of the content (and structure) from presentation.<br>
<br>
All whitespace in XML is collapsible and irrelevant for anything more than separating words from each other. If you want your text to look different, than please no <font> elements, no <milestone type="x-p-indent"/>, or other abomination like that. We were there (e.g., see whole discussion about <font> element in HTML 3.2) and it was not nice. Elements in XML document are just abstract entities without ANY notion of how they are supposed to be rendered in the end.<br>
<br>
The only thing you should do is to fix your stylesheet or program rendering the XML document into whatever output you expect.<br></blockquote><div><br></div><div style>This is a (debate-ably) good theory.</div><div style>
<br></div><div style>Sword applications don't allow a module creator to specify a stylesheet, and those which allow users to specify stylesheets are a world of hurt because the older code in the Sword filters is not very stylesheet friendly. Ergo markup is the only avenue open to module creators.</div>
<div style><br></div><div style>--Greg</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Best,<br>
<br>
Matěj Cepl<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
<a href="http://www.ceplovi.cz/matej/" target="_blank">http://www.ceplovi.cz/matej/</a>, Jabber: <a href="mailto:mcepl@ceplovi.cz" target="_blank">mcepl@ceplovi.cz</a><br>
GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC<br>
<br>
<br>
</font></span><br>_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br></blockquote></div><br></div></div>