[osis-core] Regex News!

[Chris Little]

Right, but the question is whether this will suffice for Troy, or whether 
a translation of 0x20 to 0xA0 (that may not necessarily be reversible) 
will be objected to.

--Chris

On Wed, 11 Feb 2004, Patrick Durusau wrote:

> Chris,
> 
> Should not be a problem since non-breaking space is by definition not 
> XML 1.0 whitespace.
> 
>  From the spec:
> 
> http://www.w3.org/TR/2004/REC-xml-20040204/#NT-S
> 
> S   ::=   (#x20 | #x9 | #xD | #xA)+
> 
> Hope you are having a great day!
> 
> Patrick
> 
> Chris Little wrote:
> > Patrick,
> > 
> > Sounds okay, but I'll go ahead and play the devil's advocate (read: look 
> > at things from Troy's position)...
> > 
> > I think one of Troy's desires was to be able to encode _anything_ as a 
> > valid osisGenRef, and I presume this change is partly/mostly intended to 
> > placate him.  Since spaces are part of some morphology codes, how should 
> > he encode those?  Non-breaking space?
> > 
> > If so, Troy, does that work for you?
> > 
> > --Chris
> > 
> > Patrick Durusau wrote:
> > 
> >> Greetings!
> >>
> >> The new addition to the regexes reads as follows:
> >>
> >> |(\\[^\s])
> >>
> >> This means that any single character (excluding space, including all 
> >> Unicode (which means PUA) can be used in any of the OSIS regex 
> >> expressions.
> >>
> >> Must be preceded by a "\" if the character is one of the ones we have 
> >> reserved for use in ID or REF syntax.
> >>
> >> Those characters are: ".", ":", "!", "[", "]", "@", "-" and "\".
> >>
> >> This is only for the portion following the prefix, which is terminated 
> >> by a ":".
> >>
> >> All applications are required to recognize the "\" as an escape 
> >> character applying to the single character that follows it.
> >>
> >> Hope everyone is having a great day!
> >>
> >> Patrick
> >>
> > 
> > _______________________________________________
> > osis-core mailing list
> > osis-core@bibletechnologieswg.org
> > http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> > 
> 
> 
>