[Seaside-dev] Issue 336 in seaside: try to clarify the naming around codecs

[codesite-noreply at google.com]

Status: Accepted
Owner: ----
Labels: Type-CleanUp Priority-Medium Version-Seaside2.9

New issue 336 by jfitzell: try to clarify the naming around codecs
http://code.google.com/p/seaside/issues/detail?id=336

After much discussion on the list, rough consensus has emerged around the
idea of clarifying the naming and use of encodings in the codecs. The
suggestion agreed upon was to try to present the view of both an external
and internal encoding for each codec.

The options supported for now would be:

latin-1/native (WALatin1SqueakCodec)
utf-8/native (WAUtf8SqueakCodec)
utf-8/utf-8 (possibly a subclass of WANullCodec that does no encoding but
advertises itself as utf-8 on both sides?)

I am not clear whether WAGenericSqueakCodec uses native encoding internally
or a byte stream of some sort. If native, then I guess we also support
*/native.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings