G'day Mark
> Be careful here that the program doesn't expect to
> see the property "one" associated with the string
> "two three + four five + six seven".
Thanks for pointing that out. No, I checked the GUI and the plusses
should not be there.
> Note the space before the \ to get spaces between
> words. End of line can be either \n or \r\n.
Yes, the link Jeff gave also made me realise that leading spaces are
ignored. Therefore, to have a space between the words on both lines,
the space must precede the slash, and not simply precede the first
word on the next line. I also see that the space before the slash is
not compulsory -- you only need it of you need to have a space in the
line.
I suspect that for my purposes, \n would be sufficient to indicate
real breaks in the GUI.
Thanks again.
Samuel (leuce)
Jeff Higgins - 02 Mar 2008 20:15 GMT
Samuel Murray wrote:
> G'day Mark
>
[quoted text clipped - 17 lines]
> I suspect that for my purposes, \n would be sufficient to indicate
> real breaks in the GUI.
one = two three\n\ <-- (the properties file processor) only requires this
three four\n\ (unseen) line terminator == \n, or \r, or \r\n.
five six\r\ <-- (the GUI) may choke on this \r
7 8
Samuel Murray - 03 Mar 2008 08:24 GMT
> Samuel Murray wrote:
> > I suspect that for my purposes, \n would be sufficient to indicate
> > real breaks in the GUI.
> one = two three\n\ <-- (the properties file processor) only requires this
> three four\n\ (unseen) line terminator == \n, or \r, or \r\n.
> five six\r\ <-- (the GUI) may choke on this \r
Yes, that's what I meant, thanks. \n for the break in the GUI and
another slash for the break in the code.
Samuel (leuce)
Jeff Higgins - 02 Mar 2008 20:17 GMT
Samuel Murray wrote:
> I suspect that for my purposes, \n would be sufficient to indicate
> real breaks in the GUI.
one = two three\n\ <-- (the properties file processor) only requires this
three four\n\ (unseen) line terminator == \n, or \r, or \r\n.
five six\r\ <-- (the GUI) may choke on this \r
7 8
If I've understood your comment.