Bart Schaefer wrote:
> I'd be cautious about treating everything up to the first colon in a
> $"..." string as a msgid key, though. Error messages are going to
> look like $"thing that failed: reason it failed" a lot of the time. Or
> would that have to be written "thing that failed: "$"reason it failed"
> for this to work in the first place? Anyway, it might be better to
> adopt something like $"{msgid}original text" and treat both $"{message}"
> and $"message" the same when only one of the two parts is found.
Fine, that gives us an easier test for whether there's a special msgid
anyway. (I would still propose that msgid has to consist only of shell
identifier characters for simplicity.)
--
Peter Stephenson <[EMAIL PROTECTED]>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
