Re: [jira] Commented: (HARMONY-68) java.nio.charset.Charset.isSupported(String charsetName) does not throw IllegalCharsetNameException for spoiled standard sharset name

2006-02-21 Thread Tim Ellison
That seems like a reasonable interpretation, but who knows what the spec writer really meant?! and the result is the same, we will continue to match the reference implementation behavior by returning false. Thanks Tim Karan Malhi wrote: > Hi Tim, > > I would add something to this discussion. My

Re: [jira] Commented: (HARMONY-68) java.nio.charset.Charset.isSupported(String charsetName) does not throw IllegalCharsetNameException for spoiled standard sharset name

2006-02-20 Thread Karan Malhi
Hi Tim, I would add something to this discussion. My interpretation is that if the charset name does not comply with RFC 2278 , only then an IllegalCharsetNameException should be thrown. The spec says that charset should start with character or digit, but it does not specifically mention that it w

Re: [jira] Commented: (HARMONY-68) java.nio.charset.Charset.isSupported(String charsetName) does not throw IllegalCharsetNameException for spoiled standard sharset name

2006-02-20 Thread Tim Ellison
Thanks, I had initially read over the additional restriction on the first character. This strikes me as one of those cases where the reference impl. wins over the specification. I think Svetlana's test was written to the spec. If we discover an app that relies upon isSupported throwing an Illeg

Re: [jira] Commented: (HARMONY-68) java.nio.charset.Charset.isSupported(String charsetName) does not throw IllegalCharsetNameException for spoiled standard sharset name

2006-02-18 Thread karan malhi
Here is text from the j2se1.4.2 spec A charset name must begin with either a letter or a digit. The empty string is not a legal charset name. Charset names are not case-sensitive; that is, case is always ignored when comparing charset names. Charset names generally follow the conventions docume

Re: [jira] Commented: (HARMONY-68) java.nio.charset.Charset.isSupported(String charsetName) does not throw IllegalCharsetNameException for spoiled standard sharset name

2006-02-18 Thread Richard Liang
Hello Tim, I'm wondering why I did not just copy the first sentence. :-) "A charset name **must** begin with either a letter or a digit." Does this mean if the charset name which begin with neither a letter nor a digit should be regarded as an illegal charset name? Richard Liang China Softw

Re: [jira] Commented: (HARMONY-68) java.nio.charset.Charset.isSupported(String charsetName) does not throw IllegalCharsetNameException for spoiled standard sharset name

2006-02-17 Thread Tim Ellison
Richard Liang wrote: > Hello Tim, > > I think this is caused by different understanding of the java spec: > > A charset name **must** begin with either a letter or a digit. The empty > string is not a legal charset name > > What do think the implication of "must" here? :-) But the name isn'

Re: [jira] Commented: (HARMONY-68) java.nio.charset.Charset.isSupported(String charsetName) does not throw IllegalCharsetNameException for spoiled standard sharset name

2006-02-17 Thread Richard Liang
Hello Tim, I think this is caused by different understanding of the java spec: A charset name **must** begin with either a letter or a digit. The empty string is not a legal charset name What do think the implication of "must" here? :-) Richard Liang China Software Development Lab, IBM

[jira] Commented: (HARMONY-68) java.nio.charset.Charset.isSupported(String charsetName) does not throw IllegalCharsetNameException for spoiled standard sharset name

2006-02-17 Thread Tim Ellison (JIRA)
[ http://issues.apache.org/jira/browse/HARMONY-68?page=comments#action_12366784 ] Tim Ellison commented on HARMONY-68: The test looks invalid to me. You shoud only expect an java.nio.charset.IllegalCharsetNameException if the name itself contains disa