id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
5226	XML encodings and byte-order marker (BOM) support	pinkduck	team	"JOSM 3366 loads OSM files in UTF-8 without optional leading byte-order marker, but fails if the optional BOM is present. It does not currently accept UTF16 (with or without byte-order marker), or UTF16-LE or UTF16-BE encodings. Where the .osm load fails JOSM currently reports either:

Could not read file '<filename>'.
Error is:
Line 1 column 1: Content is now allowed in prolog.

or

Could not read file '<filename>'.
Error is:
Line 1 column 2: The markup in the document preceding the root element must be well-formed.

Supporting standard XML encodings would improve cross-platform support and prevent needless errors for valid XML files.

http://en.wikipedia.org/wiki/Mapping_of_Unicode_characters#Byte_order_mark

http://en.wikipedia.org/wiki/UTF-16#Byte_order_encoding_schemes"	enhancement	closed	normal		Core	latest	fixed	XML,encoding,BOM,UTF-16,UTF-16LE,UTF16-BE,UTF-8,Byte-order Marker