You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by "Dmitry M. Kononov (JIRA)" <ji...@apache.org> on 2006/03/02 14:59:40 UTC
[jira] Created: (HARMONY-156) InputStreamReader.getEncoding() and
OutputStreamWriter.getEncoding() should return a historical charset name.
InputStreamReader.getEncoding() and OutputStreamWriter.getEncoding() should return a historical charset name.
-------------------------------------------------------------------------------------------------------------
Key: HARMONY-156
URL: http://issues.apache.org/jira/browse/HARMONY-156
Project: Harmony
Type: Bug
Components: Classlib
Reporter: Dmitry M. Kononov
Priority: Minor
InputStreamReader.getEncoding() and OutputStreamWriter.getEncoding() return canonical names on the given charsets instead of historical ones. For example,
new OutputStreamWriter(new ByteArrayOutputStream(), "UTF-16BE").getEncoding()
has to return the "UnicodeBigUnmarked" string as a historical name. But it returns "UTF-16BE", that is a canonical name.
The java spec reads the historical names as the charset names defined for compatibility with previous versions of the Java platform.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (HARMONY-156) InputStreamReader.getEncoding() and OutputStreamWriter.getEncoding() should return a historical charset name.
Posted by "Dmitry M. Kononov" <dm...@gmail.com>.
> >> I can provide the patch of tests(to get all historical name) and the
> >> mapping implementation, but before that, I hope I can get some better
> >> idea from the mailing list to avoid this ugly solution:-\.
I think this is only possible solution.
Thanks.
--
Dmitry M. Kononov
Intel Managed Runtime Division
Re: [jira] Commented: (HARMONY-156) InputStreamReader.getEncoding()
and OutputStreamWriter.getEncoding() should return a historical charset name.
Posted by Geir Magnusson Jr <ge...@pobox.com>.
Paulex Yang wrote:
> Geir Magnusson Jr wrote:
>>
>>
>> Paulex Yang wrote:
>>> Ah, thank you very much, but...I have some concerns whether we can
>>> look at the Sun's bug database. Any official ideas from Harmony
>>> PPMC? ;-)
>>
>>
>> I actually asked that question, and don't have an answer yet. Are
>> there any listed terms of use or such?
> I have no idea, that's why I have concern...unknown world is source of
> fear:)
Ok - we need to check. I'll ask again.
>>
>> <aside>
>> Lets not distinguish the PPMC that way - no need to place any special
>> empahsis there.
>> </aside>
> I'm sorry for my possible abruptness, I didn't intend to emphasis anything.
Oh! Sorry for the miscommunication. There was no abruptness on your
part. What I was getting at was that I've seen some projects evolve
into a culture where the PMC (PPMC in this case) was held as an elite
body, and maybe I'm trying too hard here, but I want to ensure that
won't happen w/ harmony...
Please forgive my lack of explanation.
geir
Re: [jira] Commented: (HARMONY-156) InputStreamReader.getEncoding()
and OutputStreamWriter.getEncoding() should return a historical charset name.
Posted by Paulex Yang <pa...@gmail.com>.
Geir Magnusson Jr wrote:
>
>
> Paulex Yang wrote:
>> Ah, thank you very much, but...I have some concerns whether we can
>> look at the Sun's bug database. Any official ideas from Harmony
>> PPMC? ;-)
>
>
> I actually asked that question, and don't have an answer yet. Are
> there any listed terms of use or such?
I have no idea, that's why I have concern...unknown world is source of
fear:)
>
> <aside>
> Lets not distinguish the PPMC that way - no need to place any special
> empahsis there.
> </aside>
I'm sorry for my possible abruptness, I didn't intend to emphasis anything.
>
>
> geir
>
>>
>> karan malhi wrote:
>>> You might want to look at this
>>> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6201170
>>>
>>> Paulex Yang (JIRA) wrote:
>>>
>>>> [
>>>> http://issues.apache.org/jira/browse/HARMONY-156?page=comments#action_12368656
>>>> ]
>>>> Paulex Yang commented on HARMONY-156:
>>>> -------------------------------------
>>>>
>>>> All the spec about Charset historical name is:
>>>> " Some charsets have an historical name that is defined for
>>>> compatibility with previous versions of the Java platform. A
>>>> charset's historical name is either its canonical name or one of
>>>> its aliases."
>>>>
>>>>> From this paragraph, I personally think the historical name is
>>>>> specific to RI without any public standard:(, so the only way to
>>>>> be compatible with RI is write testcases to get all historical
>>>>> names of RI supported Charsets, and store them in an map.
>>>>
>>>> I can provide the patch of tests(to get all historical name) and
>>>> the mapping implementation, but before that, I hope I can get some
>>>> better idea from the mailing list to avoid this ugly solution:-\.
>>>>
>>>>
>>>>
>>>>> InputStreamReader.getEncoding() and
>>>>> OutputStreamWriter.getEncoding() should return a historical
>>>>> charset name.
>>>>> -------------------------------------------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> Key: HARMONY-156
>>>>> URL: http://issues.apache.org/jira/browse/HARMONY-156
>>>>> Project: Harmony
>>>>> Type: Bug
>>>>> Components: Classlib
>>>>> Reporter: Dmitry M. Kononov
>>>>> Priority: Minor
>>>>>
>>>>
>>>>
>>>>
>>>>> InputStreamReader.getEncoding() and
>>>>> OutputStreamWriter.getEncoding() return canonical names on the
>>>>> given charsets instead of historical ones. For example,
>>>>> new OutputStreamWriter(new ByteArrayOutputStream(),
>>>>> "UTF-16BE").getEncoding()
>>>>> has to return the "UnicodeBigUnmarked" string as a historical
>>>>> name. But it returns "UTF-16BE", that is a canonical name.
>>>>> The java spec reads the historical names as the charset names
>>>>> defined for compatibility with previous versions of the Java
>>>>> platform.
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>
--
Paulex Yang
China Software Development Lab
IBM
Re: [jira] Commented: (HARMONY-156) InputStreamReader.getEncoding()
and OutputStreamWriter.getEncoding() should return a historical charset name.
Posted by karan malhi <ka...@gmail.com>.
Geir Magnusson Jr wrote:
> The issue is one of exposure - would there be any problem if our
> developers were exposed to the code in the Sun bug database.
You are right. I didnt realize that bugs database could expose
developers to code
> I believe the answer is "no" as long as we don't copy anything.
>
> geir
>
>>
>> Geir Magnusson Jr wrote:
>>
>>>
>>>
>>> Paulex Yang wrote:
>>>
>>>> Ah, thank you very much, but...I have some concerns whether we can
>>>> look at the Sun's bug database. Any official ideas from Harmony
>>>> PPMC? ;-)
>>>
>>>
>>>
>>>
>>> I actually asked that question, and don't have an answer yet. Are
>>> there any listed terms of use or such?
>>>
>>> <aside>
>>> Lets not distinguish the PPMC that way - no need to place any
>>> special empahsis there.
>>> </aside>
>>>
>>>
>>> geir
>>>
>>>>
>>>> karan malhi wrote:
>>>>
>>>>> You might want to look at this
>>>>> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6201170
>>>>>
>>>>> Paulex Yang (JIRA) wrote:
>>>>>
>>>>>> [
>>>>>> http://issues.apache.org/jira/browse/HARMONY-156?page=comments#action_12368656
>>>>>> ]
>>>>>> Paulex Yang commented on HARMONY-156:
>>>>>> -------------------------------------
>>>>>>
>>>>>> All the spec about Charset historical name is:
>>>>>> " Some charsets have an historical name that is defined for
>>>>>> compatibility with previous versions of the Java platform. A
>>>>>> charset's historical name is either its canonical name or one of
>>>>>> its aliases."
>>>>>>
>>>>>>> From this paragraph, I personally think the historical name is
>>>>>>> specific to RI without any public standard:(, so the only way
>>>>>>> to be compatible with RI is write testcases to get all
>>>>>>> historical names of RI supported Charsets, and store them in an
>>>>>>> map.
>>>>>>
>>>>>>
>>>>>>
>>>>>> I can provide the patch of tests(to get all historical name) and
>>>>>> the mapping implementation, but before that, I hope I can get
>>>>>> some better idea from the mailing list to avoid this ugly
>>>>>> solution:-\.
>>>>>>
>>>>>>
>>>>>>
>>>>>>> InputStreamReader.getEncoding() and
>>>>>>> OutputStreamWriter.getEncoding() should return a historical
>>>>>>> charset name.
>>>>>>> -------------------------------------------------------------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>> Key: HARMONY-156
>>>>>>> URL: http://issues.apache.org/jira/browse/HARMONY-156
>>>>>>> Project: Harmony
>>>>>>> Type: Bug
>>>>>>> Components: Classlib
>>>>>>> Reporter: Dmitry M. Kononov
>>>>>>> Priority: Minor
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> InputStreamReader.getEncoding() and
>>>>>>> OutputStreamWriter.getEncoding() return canonical names on the
>>>>>>> given charsets instead of historical ones. For example,
>>>>>>> new OutputStreamWriter(new ByteArrayOutputStream(),
>>>>>>> "UTF-16BE").getEncoding()
>>>>>>> has to return the "UnicodeBigUnmarked" string as a historical
>>>>>>> name. But it returns "UTF-16BE", that is a canonical name.
>>>>>>> The java spec reads the historical names as the charset names
>>>>>>> defined for compatibility with previous versions of the Java
>>>>>>> platform.
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
--
Karan Singh
Re: [jira] Commented: (HARMONY-156) InputStreamReader.getEncoding()
and OutputStreamWriter.getEncoding() should return a historical charset name.
Posted by Geir Magnusson Jr <ge...@pobox.com>.
karan malhi wrote:
> http://www.sun.com/termsofuse.html
> This was the only Terms of Use for the sun.com website. I couldnt find
> anything specific for the bugs database.
> Section 10.4 lists some things regarding use of Sun material. I think
> that just like javadocs, the bugs database is also public information.
> And since we are not copying or distributing that stuff, but just
> providing a link to their material, I dont think that violates any
> terms. If linking does violate, then probably putting links to the sun
> javadocs for javax.* classes in Harmony would also be an issue.
The issue is one of exposure - would there be any problem if our
developers were exposed to the code in the Sun bug database.
I believe the answer is "no" as long as we don't copy anything.
geir
>
> Geir Magnusson Jr wrote:
>
>>
>>
>> Paulex Yang wrote:
>>
>>> Ah, thank you very much, but...I have some concerns whether we can
>>> look at the Sun's bug database. Any official ideas from Harmony
>>> PPMC? ;-)
>>
>>
>>
>> I actually asked that question, and don't have an answer yet. Are
>> there any listed terms of use or such?
>>
>> <aside>
>> Lets not distinguish the PPMC that way - no need to place any special
>> empahsis there.
>> </aside>
>>
>>
>> geir
>>
>>>
>>> karan malhi wrote:
>>>
>>>> You might want to look at this
>>>> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6201170
>>>>
>>>> Paulex Yang (JIRA) wrote:
>>>>
>>>>> [
>>>>> http://issues.apache.org/jira/browse/HARMONY-156?page=comments#action_12368656
>>>>> ]
>>>>> Paulex Yang commented on HARMONY-156:
>>>>> -------------------------------------
>>>>>
>>>>> All the spec about Charset historical name is:
>>>>> " Some charsets have an historical name that is defined for
>>>>> compatibility with previous versions of the Java platform. A
>>>>> charset's historical name is either its canonical name or one of
>>>>> its aliases."
>>>>>
>>>>>> From this paragraph, I personally think the historical name is
>>>>>> specific to RI without any public standard:(, so the only way to
>>>>>> be compatible with RI is write testcases to get all historical
>>>>>> names of RI supported Charsets, and store them in an map.
>>>>>
>>>>>
>>>>> I can provide the patch of tests(to get all historical name) and
>>>>> the mapping implementation, but before that, I hope I can get some
>>>>> better idea from the mailing list to avoid this ugly solution:-\.
>>>>>
>>>>>
>>>>>
>>>>>> InputStreamReader.getEncoding() and
>>>>>> OutputStreamWriter.getEncoding() should return a historical
>>>>>> charset name.
>>>>>> -------------------------------------------------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>> Key: HARMONY-156
>>>>>> URL: http://issues.apache.org/jira/browse/HARMONY-156
>>>>>> Project: Harmony
>>>>>> Type: Bug
>>>>>> Components: Classlib
>>>>>> Reporter: Dmitry M. Kononov
>>>>>> Priority: Minor
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> InputStreamReader.getEncoding() and
>>>>>> OutputStreamWriter.getEncoding() return canonical names on the
>>>>>> given charsets instead of historical ones. For example,
>>>>>> new OutputStreamWriter(new ByteArrayOutputStream(),
>>>>>> "UTF-16BE").getEncoding()
>>>>>> has to return the "UnicodeBigUnmarked" string as a historical
>>>>>> name. But it returns "UTF-16BE", that is a canonical name.
>>>>>> The java spec reads the historical names as the charset names
>>>>>> defined for compatibility with previous versions of the Java
>>>>>> platform.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
Re: [jira] Commented: (HARMONY-156) InputStreamReader.getEncoding()
and OutputStreamWriter.getEncoding() should return a historical charset name.
Posted by karan malhi <ka...@gmail.com>.
http://www.sun.com/termsofuse.html
This was the only Terms of Use for the sun.com website. I couldnt find
anything specific for the bugs database.
Section 10.4 lists some things regarding use of Sun material. I think
that just like javadocs, the bugs database is also public information.
And since we are not copying or distributing that stuff, but just
providing a link to their material, I dont think that violates any
terms. If linking does violate, then probably putting links to the sun
javadocs for javax.* classes in Harmony would also be an issue.
Geir Magnusson Jr wrote:
>
>
> Paulex Yang wrote:
>
>> Ah, thank you very much, but...I have some concerns whether we can
>> look at the Sun's bug database. Any official ideas from Harmony
>> PPMC? ;-)
>
>
>
> I actually asked that question, and don't have an answer yet. Are
> there any listed terms of use or such?
>
> <aside>
> Lets not distinguish the PPMC that way - no need to place any special
> empahsis there.
> </aside>
>
>
> geir
>
>>
>> karan malhi wrote:
>>
>>> You might want to look at this
>>> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6201170
>>>
>>> Paulex Yang (JIRA) wrote:
>>>
>>>> [
>>>> http://issues.apache.org/jira/browse/HARMONY-156?page=comments#action_12368656
>>>> ]
>>>> Paulex Yang commented on HARMONY-156:
>>>> -------------------------------------
>>>>
>>>> All the spec about Charset historical name is:
>>>> " Some charsets have an historical name that is defined for
>>>> compatibility with previous versions of the Java platform. A
>>>> charset's historical name is either its canonical name or one of
>>>> its aliases."
>>>>
>>>>> From this paragraph, I personally think the historical name is
>>>>> specific to RI without any public standard:(, so the only way to
>>>>> be compatible with RI is write testcases to get all historical
>>>>> names of RI supported Charsets, and store them in an map.
>>>>
>>>>
>>>> I can provide the patch of tests(to get all historical name) and
>>>> the mapping implementation, but before that, I hope I can get some
>>>> better idea from the mailing list to avoid this ugly solution:-\.
>>>>
>>>>
>>>>
>>>>> InputStreamReader.getEncoding() and
>>>>> OutputStreamWriter.getEncoding() should return a historical
>>>>> charset name.
>>>>> -------------------------------------------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> Key: HARMONY-156
>>>>> URL: http://issues.apache.org/jira/browse/HARMONY-156
>>>>> Project: Harmony
>>>>> Type: Bug
>>>>> Components: Classlib
>>>>> Reporter: Dmitry M. Kononov
>>>>> Priority: Minor
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> InputStreamReader.getEncoding() and
>>>>> OutputStreamWriter.getEncoding() return canonical names on the
>>>>> given charsets instead of historical ones. For example,
>>>>> new OutputStreamWriter(new ByteArrayOutputStream(),
>>>>> "UTF-16BE").getEncoding()
>>>>> has to return the "UnicodeBigUnmarked" string as a historical
>>>>> name. But it returns "UTF-16BE", that is a canonical name.
>>>>> The java spec reads the historical names as the charset names
>>>>> defined for compatibility with previous versions of the Java
>>>>> platform.
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>
--
Karan Singh
Re: [jira] Commented: (HARMONY-156) InputStreamReader.getEncoding()
and OutputStreamWriter.getEncoding() should return a historical charset name.
Posted by Geir Magnusson Jr <ge...@pobox.com>.
Paulex Yang wrote:
> Ah, thank you very much, but...I have some concerns whether we can look
> at the Sun's bug database. Any official ideas from Harmony PPMC? ;-)
I actually asked that question, and don't have an answer yet. Are there
any listed terms of use or such?
<aside>
Lets not distinguish the PPMC that way - no need to place any special
empahsis there.
</aside>
geir
>
> karan malhi wrote:
>> You might want to look at this
>> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6201170
>>
>> Paulex Yang (JIRA) wrote:
>>
>>> [
>>> http://issues.apache.org/jira/browse/HARMONY-156?page=comments#action_12368656
>>> ]
>>> Paulex Yang commented on HARMONY-156:
>>> -------------------------------------
>>>
>>> All the spec about Charset historical name is:
>>> " Some charsets have an historical name that is defined for
>>> compatibility with previous versions of the Java platform. A
>>> charset's historical name is either its canonical name or one of its
>>> aliases."
>>>
>>>> From this paragraph, I personally think the historical name is
>>>> specific to RI without any public standard:(, so the only way to be
>>>> compatible with RI is write testcases to get all historical names of
>>>> RI supported Charsets, and store them in an map.
>>>
>>> I can provide the patch of tests(to get all historical name) and the
>>> mapping implementation, but before that, I hope I can get some better
>>> idea from the mailing list to avoid this ugly solution:-\.
>>>
>>>
>>>
>>>> InputStreamReader.getEncoding() and OutputStreamWriter.getEncoding()
>>>> should return a historical charset name.
>>>> -------------------------------------------------------------------------------------------------------------
>>>>
>>>>
>>>> Key: HARMONY-156
>>>> URL: http://issues.apache.org/jira/browse/HARMONY-156
>>>> Project: Harmony
>>>> Type: Bug
>>>> Components: Classlib
>>>> Reporter: Dmitry M. Kononov
>>>> Priority: Minor
>>>>
>>>
>>>
>>>
>>>> InputStreamReader.getEncoding() and OutputStreamWriter.getEncoding()
>>>> return canonical names on the given charsets instead of historical
>>>> ones. For example,
>>>> new OutputStreamWriter(new ByteArrayOutputStream(),
>>>> "UTF-16BE").getEncoding()
>>>> has to return the "UnicodeBigUnmarked" string as a historical name.
>>>> But it returns "UTF-16BE", that is a canonical name.
>>>> The java spec reads the historical names as the charset names
>>>> defined for compatibility with previous versions of the Java platform.
>>>>
>>>
>>>
>>>
>>
>
>
Re: [jira] Commented: (HARMONY-156) InputStreamReader.getEncoding()
and OutputStreamWriter.getEncoding() should return a historical charset name.
Posted by Paulex Yang <pa...@gmail.com>.
Ah, thank you very much, but...I have some concerns whether we can look
at the Sun's bug database. Any official ideas from Harmony PPMC? ;-)
karan malhi wrote:
> You might want to look at this
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6201170
>
> Paulex Yang (JIRA) wrote:
>
>> [
>> http://issues.apache.org/jira/browse/HARMONY-156?page=comments#action_12368656
>> ]
>> Paulex Yang commented on HARMONY-156:
>> -------------------------------------
>>
>> All the spec about Charset historical name is:
>> " Some charsets have an historical name that is defined for
>> compatibility with previous versions of the Java platform. A
>> charset's historical name is either its canonical name or one of its
>> aliases."
>>
>>> From this paragraph, I personally think the historical name is
>>> specific to RI without any public standard:(, so the only way to be
>>> compatible with RI is write testcases to get all historical names of
>>> RI supported Charsets, and store them in an map.
>>
>> I can provide the patch of tests(to get all historical name) and the
>> mapping implementation, but before that, I hope I can get some better
>> idea from the mailing list to avoid this ugly solution:-\.
>>
>>
>>
>>> InputStreamReader.getEncoding() and OutputStreamWriter.getEncoding()
>>> should return a historical charset name.
>>> -------------------------------------------------------------------------------------------------------------
>>>
>>>
>>> Key: HARMONY-156
>>> URL: http://issues.apache.org/jira/browse/HARMONY-156
>>> Project: Harmony
>>> Type: Bug
>>> Components: Classlib
>>> Reporter: Dmitry M. Kononov
>>> Priority: Minor
>>>
>>
>>
>>
>>> InputStreamReader.getEncoding() and OutputStreamWriter.getEncoding()
>>> return canonical names on the given charsets instead of historical
>>> ones. For example,
>>> new OutputStreamWriter(new ByteArrayOutputStream(),
>>> "UTF-16BE").getEncoding()
>>> has to return the "UnicodeBigUnmarked" string as a historical name.
>>> But it returns "UTF-16BE", that is a canonical name.
>>> The java spec reads the historical names as the charset names
>>> defined for compatibility with previous versions of the Java platform.
>>>
>>
>>
>>
>
--
Paulex Yang
China Software Development Lab
IBM
Re: [jira] Commented: (HARMONY-156) InputStreamReader.getEncoding()
and OutputStreamWriter.getEncoding() should return a historical charset name.
Posted by karan malhi <ka...@gmail.com>.
You might want to look at this
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6201170
Paulex Yang (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/HARMONY-156?page=comments#action_12368656 ]
>
>Paulex Yang commented on HARMONY-156:
>-------------------------------------
>
>All the spec about Charset historical name is:
>" Some charsets have an historical name that is defined for compatibility with previous versions of the Java platform. A charset's historical name is either its canonical name or one of its aliases."
>
>>>From this paragraph, I personally think the historical name is specific to RI without any public standard:(, so the only way to be compatible with RI is write testcases to get all historical names of RI supported Charsets, and store them in an map.
>
>I can provide the patch of tests(to get all historical name) and the mapping implementation, but before that, I hope I can get some better idea from the mailing list to avoid this ugly solution:-\.
>
>
>
>>InputStreamReader.getEncoding() and OutputStreamWriter.getEncoding() should return a historical charset name.
>>-------------------------------------------------------------------------------------------------------------
>>
>> Key: HARMONY-156
>> URL: http://issues.apache.org/jira/browse/HARMONY-156
>> Project: Harmony
>> Type: Bug
>> Components: Classlib
>> Reporter: Dmitry M. Kononov
>> Priority: Minor
>>
>>
>
>
>
>>InputStreamReader.getEncoding() and OutputStreamWriter.getEncoding() return canonical names on the given charsets instead of historical ones. For example,
>> new OutputStreamWriter(new ByteArrayOutputStream(), "UTF-16BE").getEncoding()
>>has to return the "UnicodeBigUnmarked" string as a historical name. But it returns "UTF-16BE", that is a canonical name.
>>The java spec reads the historical names as the charset names defined for compatibility with previous versions of the Java platform.
>>
>>
>
>
>
--
Karan Singh
[jira] Commented: (HARMONY-156) InputStreamReader.getEncoding() and
OutputStreamWriter.getEncoding() should return a historical charset name.
Posted by "Paulex Yang (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-156?page=comments#action_12368656 ]
Paulex Yang commented on HARMONY-156:
-------------------------------------
All the spec about Charset historical name is:
" Some charsets have an historical name that is defined for compatibility with previous versions of the Java platform. A charset's historical name is either its canonical name or one of its aliases."
>From this paragraph, I personally think the historical name is specific to RI without any public standard:(, so the only way to be compatible with RI is write testcases to get all historical names of RI supported Charsets, and store them in an map.
I can provide the patch of tests(to get all historical name) and the mapping implementation, but before that, I hope I can get some better idea from the mailing list to avoid this ugly solution:-\.
> InputStreamReader.getEncoding() and OutputStreamWriter.getEncoding() should return a historical charset name.
> -------------------------------------------------------------------------------------------------------------
>
> Key: HARMONY-156
> URL: http://issues.apache.org/jira/browse/HARMONY-156
> Project: Harmony
> Type: Bug
> Components: Classlib
> Reporter: Dmitry M. Kononov
> Priority: Minor
>
> InputStreamReader.getEncoding() and OutputStreamWriter.getEncoding() return canonical names on the given charsets instead of historical ones. For example,
> new OutputStreamWriter(new ByteArrayOutputStream(), "UTF-16BE").getEncoding()
> has to return the "UnicodeBigUnmarked" string as a historical name. But it returns "UTF-16BE", that is a canonical name.
> The java spec reads the historical names as the charset names defined for compatibility with previous versions of the Java platform.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira