DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26617>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26617

[codec][patch] Quoted-printable codec (partial implementation), RFC1522 QCodec &  
BCodec

           Summary: [codec][patch] Quoted-printable codec (partial
                    implementation), RFC1522 QCodec &  BCodec
           Product: Commons
           Version: Nightly Builds
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Codec
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


The patch provides partial implementation of quoted-printable codec (rule #1 &
rule #2 as described in RFC 1521), Q codec and B codec (as specified in 1522). 

I decided to not implement rule #3, rule #4, rule #5 of the quoted-printable
spec yet, because the complete quoted-printable spec does not lend itself well
into byte[] oriented codec framework. I will happily complete the codec once the
steamable codec framework is ready. The motivation behind providing the codec in
a partial form is that it can already come in handy for those applications that
do not require quoted-printable line formatting (rules #3, #4, #5), for instance
Q codec.

I have also slightly changed URLCodec to make it more consistent with the new
codecs. I tool liberty of deprecating URLCodec#getEncoding method, because this
term encoding is used in RFC1522 to refer to the encoding/decoding algorithm,
whereas charset is used to refer to the character set associated with the
unencoded text. Let me know if you agree/disagree

I am aware that the patch is still far from being complete: javasdocs are
virtually non-existent and the B codec does not have the corresponding test
cases (quoted-printable & Q codec, however, come with a reasonble set of test
cases). If the overall structure and API for the new codecs gets approved, I'll
provide the missing bits and pieces


Oleg

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to