- updated roadmap (utf-8 handling in Reader)

This commit is contained in:
Baptiste Lepilleur 2010-02-21 14:24:52 +00:00
parent 3a1b93be1c
commit 8c2f18cd1d

View File

@ -2,11 +2,9 @@
\section ms_release Makes JsonCpp ready for release \section ms_release Makes JsonCpp ready for release
- Build system clean-up: - Build system clean-up:
- Fix build on Windows (shared-library build is broken) - Fix build on Windows (shared-library build is broken)
- Fix doxygen build issue (discard doxygen dependency check, always rebuild)
- Add enable/disable flag for static and shared library build - Add enable/disable flag for static and shared library build
- Enhance help - Enhance help
- Test with recent Scons checkpoint - Platform portability check: (Notes: was ok on last check)
- Platform portability check:
- linux/gcc, - linux/gcc,
- solaris/cc, - solaris/cc,
- windows/msvc678, - windows/msvc678,
@ -14,17 +12,16 @@
- Add JsonCpp version to header as numeric for use in preprocessor test - Add JsonCpp version to header as numeric for use in preprocessor test
- Remove buggy experimental hash stuff - Remove buggy experimental hash stuff
- Release on sourceforge download - Release on sourceforge download
\section ms_unicode Clean-up unicode handling
- Ensure reader properly convert \u and \U unicode sequence to UTF8
- Ensure writer emit only UTF8 string.
- Provides hook to convert string to/from utf8/other encoding.
- look into iconv, icu and windows API
\section ms_strict Adds a strict mode to reader/parser \section ms_strict Adds a strict mode to reader/parser
Strict JSON support as specific in RFC 4627 (http://www.ietf.org/rfc/rfc4627.txt?number=4627). Strict JSON support as specific in RFC 4627 (http://www.ietf.org/rfc/rfc4627.txt?number=4627).
- Enforce only object or array as root element - Enforce only object or array as root element
- Disable comment support - Disable comment support
- Get jsonchecker failing tests to pass in strict mode
\section ms_separation Expose json reader/writer API that do not impose using Json::Value. \section ms_separation Expose json reader/writer API that do not impose using Json::Value.
Some typical use-case involve an application specific structure to/from a JSON document. Some typical use-case involve an application specific structure to/from a JSON document.
- Event base parser to allow unserializing a Json document directly in datastructure instead of
using the intermediate Json::Value.
- "Stream" based parser to serialized a Json document without using Json::Value as input.
- Performance oriented parser/writer: - Performance oriented parser/writer:
- Provides an event based parser. Should allow pulling & skipping events for ease of use. - Provides an event based parser. Should allow pulling & skipping events for ease of use.
- Provides a JSON document builder: fast only. - Provides a JSON document builder: fast only.