[#SES-244] non-standard UTF-8 encoding used for binary tuple/table results format

Issue Details [XML]

Key:	SES-244
Type:	Bug
Status:	Closed
Resolution:	Fixed
Priority:	Major
Assignee:	Arjohn Kampman
Reporter:	Arjohn Kampman
Votes:	0
Watchers:	0

Operations

If you were logged in you would be able to see more operations.

Sesame

non-standard UTF-8 encoding used for binary tuple/table results format

Created: 28/Feb/06 11:34 AM Updated: 18/Sep/08 04:43 AM

Component/s:

HTTP Server

Affects Version/s:

2.0-alpha-3, 2.0-alpha-2, 2.0-alpha-1, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2, 1.2-RC2, 1.2-RC1, 1.1.3, 1.1.2, 1.1.1

Fix Version/s:

2.0-beta2

Issue Links:

Dependency

This issue is a dependency for:
	~~SES-245~~ Binary table/tuple results format doe...

Description

The reader and writer for Sesame's binary tuple/table results format are based on java.io.DataInputStream and java.io.DataOutputStream. These classes read and write a non-standard, Java-specific version of UTF-8 (known as "modified UTF-8"), which hurts interoperability with other platforms. Standard UTF-8 encoding is available through InputStreamReader and InputStreamWriter, which should be used instead.

For more information:
http://java.sun.com/developer/technicalArticles/Intl/Supplementary/
http://en.wikipedia.org/wiki/UTF8#Modified_UTF-8_in_Java

All

Comments

Change History

Sort Order:

[ Permlink ]

Comment by Arjohn Kampman [28/Feb/07 07:47 PM]

Format now uses standard UTF-8 encoding for strings. Format version number has been updated to '2'. Fix available in revision 2442:
http://src.aduna-software.org/viewvc/org.openrdf/?rev=2442&view=rev