<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Inconsolata; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">Backwards compatibility... well, compatibility to MEI 2010 was severely broken already with v. 2.0.0, and I doubt anyone has adapted the 2012 <source> encoding yet. I don't think that should be the reason for not changing anything.</span><br style="font-family: Inconsolata; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "></blockquote><br></div><div>I have no "horse in the race" for the source encoding problem, but I would like to jump in on this point. If we're breaking compatibility, then this is a 3.0.0 issue.</div><div><br></div><div>-Andrew</div></body></html>