Comment 11 for bug 615565

As I understand it, this whole mess stems from [TtSs]commaaccent being missed out of earlier Unicode standards, and [TtSs]cedilla being used in the interim: the locl table fixes being an attempt to smooth things over. Reading material:

  http://partners.adobe.com/public/developer/en/opentype/aglfn13.txt (first two 2003 changelogs)
  http://forum.fontlab.com/fontlab-studio-tips-and-tricks/handling-romanian-glyphs-in-opentype-fonts-updated-as-of-2009-t337.0.html (suggested best practice + example howto for Fontlab)

Assuming that we're doing that (ignoring the original issue with the wrong glyphs), then we're at least doing the same as everyone else and being consistent. ...It could well be that other parts of the stack need fixing in the long-run (keyboard input, toolkit, applications, ...) but that's not a reason to stunt deploying the advanced metadata tables now. The suggested localisation mapping on that page is:

  languagesystem latn dflt;
  languagesystem latn ROM;
  languagesystem latn MOL;

  feature locl { # Localized Forms
    # Latin
    language ROM exclude_dflt; # Romanian
    lookup locl_ROM {
      sub [Scedilla scedilla] by [uni0218 uni0219];
      sub [uni0162 uni0163] by [uni021A uni021B];
    } locl_ROM;
    language MOL exclude_dflt; # Moldavian
    lookup locl_ROM;
  } locl;