At 10:04 AM 23-09-05, you wrote:
>I'd advise using <seg> for this rather than <space>, which is 
>specifically for "significant space in the copy text" - not for 
>regular inter-word spacing.

Agreed, unless it's important to specify the size of spaces (where 
they vary through justification, or where their size might be 
significant in concrete poetry, for example).


>Martin Holmes wrote:
>>Hi there,
>>Processing of actual whitespace can be a bit flaky in various XSLT
>>processors, and it can be difficult to get the right balance of
>>xsl:strip-space and xsl:preserve-space to get the results you want in
>>a way that is reliably portable between systems. Where spaces are
>>important (as they may often be when you're encoding below the word
>>level), I'd suggest encoding the actual spaces, using perhaps a space
>>tag or a seg tag. That way you can always ensure they're properly
>>described, and properly processed in any output system. It does make
>>the code hard to read, but when you're encoding at this level the
>>text is usually pretty hard to read anyway.
>>At 08:32 AM 23-09-05, Martin Mueller wrote:
>>>Is there a set of rules or best practices about what to do with space
>>>between words when you encode down to the word level? We have in one
>>>project used space between <w> elements, and the parser respects
>>>this, although it seems theoretically wrong. One could also deal with
>>>the space at the processing level and have a rule to the effect that
>>>a word element is followed by a space unless the content of the next
>>>element begins with a punctuation mark, etc.
>>>I'll be grateful for advice.
>>Martin Holmes
>>University of Victoria Humanities Computing and Media Centre
>Dorothy Carr Porter, Program Coordinator
>Collaboratory for Research in Computing for Humanities
>University of Kentucky
>351 William T. Young Library
>Lexington, KY  40506
>[log in to unmask]          859-257-9549

Martin Holmes
University of Victoria Humanities Computing and Media Centre