> - just have a couple of basic \ rules, and avoid quoted unicode > altogether, on the basis that we can use real unicode files (which we > already can in the next generation of the tools)
fine by me. > - use the ISO rules, that the spec currently indicates, i.e. &aaaa or > &#xHHHH I think this would be a nightmare - what happens to normal &'s - these must then be quoted. Also, are all the symbolic unicode names supported ´ etc? > - use the \uNNNN approach Andrew suggests (is this hex or decimal?) This is hexadecimal (as per the unicode spec for unicode codepoints). C# and Java use this notation - C# extends it to also have \UXXXXXXXX for 32 bit codepoints (as per the new unicode versions) > As for the other quoted characters, I don't see what the need for things > like \f (formfeed) is; what we need is to decide a minimum set which > might be: > - \r - carriage return > - \n - linefeed > - \t - tab > - \\ - backslash > - \" - literal " > > Is anything else needed? In characters, \' for literal ' Andrew _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
