Re: editorial problem in example in 6.1

This looks like a browser bug. The <pre> elements should never line 
break. I tested Chrome and Firefox - both behave well on Windows 10.

But Microsoft Edge *does* wrap them, as you describe. Could you confirm 
your browser and operating system? The solution with """ around all 
strings will not suffice because # comments and even single words still 
do wrap on Edge.

I am checking with our resident CSS expert in the meantime.

Holger


On 8/02/2017 13:52, Peter F. Patel-Schneider wrote:
> Although the actual character sequence in the string may not include a
> newline, a browser may break the string on display, giving the appearance of
> illegal syntax.
>
> It is probably better to use """ for all strings, even very short ones, just
> so that there is no possibility of the appearance of illegality.
>
> peter
>
>
> On 02/07/2017 07:49 PM, Holger Knublauch wrote:
>> This parses OK for me. Are we talking about the same query:
>>
>> sh:PatternConstraintComponent
>>      a sh:ConstraintComponent ;
>>      sh:parameter [
>>          sh:path sh:pattern ;
>>      ] ;
>>      sh:parameter [
>>          sh:path sh:flags ;
>>          sh:optional true ;
>>      ] ;
>>      sh:validator shimpl:hasPattern .
>>
>> shimpl:hasPattern
>>      a sh:SPARQLAskValidator ;
>>      sh:message "Value does not match pattern {$pattern}" ;
>>      sh:ask "ASK { FILTER (!isBlank($value) && IF(bound($flags),
>> regex(str($value), $pattern, $flags), regex(str($value), $pattern))) }" .
>>
>> Thanks,
>> Holger
>>
>>
>> On 8/02/2017 12:58, Peter F. Patel-Schneider wrote:
>>> The example in 6.1 has what appears to be an incorrectly delimited multi-line
>>> literal.
>>>
>>> Peter F. Patel-Schneider
>>> Nuance Communications
>>>
>>

Received on Wednesday, 8 February 2017 05:10:33 UTC