[sword-devel] XML whitespace - significant and insignificant?

[David Haslam]

Of course there’s no absolute need for XML to be easily read by humans.

We can linearize an XML file and thereby eliminate all non-text whitespace. The OSIS still validates and osis2mod should therefore still work even though the input file is just one very long line.

So Tom’s problem has a solution providing he doesn’t need to read the file with his own eyes.

There again a multiline XML file does not need to have indents. It’s still valid without any.

David

Sent from ProtonMail Mobile

On Fri, Feb 8, 2019 at 19:12, Tom Sullivan <info at beforgiven.info> wrote:

> Y'all:
>
> I had to make my own somewhat limited pretty-printer python program
> because most XML editors put or remove single spaces in the oddest,
> hardest-to-find places.
>
> Thus I am (soon) submitting a new OSIS XML using this custom
> not-so-pretty-printer.
>
> For what it is worth.
>
> Tom
>
> Tom Sullivan
> info at BeForgiven.INFO
> FAX: 815-301-2835
> ---------------------
>
> On 2/8/19 2:02 PM, David Haslam wrote:
>> Here's a question that I'd like our OSIS experts to ponder.
>>
>> In XML, there's a longstanding topic relating to whitespace.
>>
>> See http://usingxml.com/Basics/XmlSpace
>>
>> When we make a module from an OSIS file, are there any aspects of XML whitespace that can make a significant difference to how the module displays text or features?
>>
>> E.g. Might we inadvertently get a space inserted between a tagged word and a note tag?
>>
>> i.e. As maybe the result of performing a "pretty print" operation on the OSIS source text.
>>
>> cf. I'm sure you can think of other potential areas of interest.
>>
>> AFAIK, this has never been discussed before among us.
>>
>> With various software tools available for making "innocuous" changes to XML files, it's certainly the case that there's nothing to dissuade module providers from using them to "prettify" the OSIS file, even though there might - theoretically at least - be consequences.
>>
>>
>> Best regards,
>>
>> David
>>
>> Sent with ProtonMail Secure Email.
>>
>>
>>
>> _______________________________________________
>> sword-devel mailing list: sword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>>
>> ______________________________________________________________________
>> This email has been scanned by the Symantec Email Security.cloud service.
>> For more information please visit http://www.symanteccloud.com
>> ______________________________________________________________________
>>
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20190208/24b361f8/attachment.html>