> > Indeed, even manually quoting or escaping colons in /etc/passwd > > completely breaks the given entries. > > > > I'm again very reluctant to push Tomasz to introduce a complex > > escaping machanism for passwd fields, allowing the use of colons in > > the GECOS field. > > > > This would be VERY likely to potentially break out all custom > > utilities relying on a basic analysis of passwd to but out fields. > > > > So, here, I mark the bug as wontfix and wait for comments to convince > > me that it's really worth the effort and absolutely not dangerous. > > OK. Point taken. > But I have questions about this: > > - is sip:[EMAIL PROTECTED] it is URI/URL or not ? if yes probably > correct format of above is "sip://[EMAIL PROTECTED]/". > > - anyone know some template/example code URI/URL syntax checker ?
Well, we'd better ask the bug submitter for this.....So let's put him in copy of this mail so that he sees your answer. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
