The issue with the bytecode-interpreter is a bit more complex, at least as far I can see. I could get it turned on only with a "broken" libfreetype I compiled from source, turning FT_LOAD_FORCE_AUTOHINT-Macro off (this means: breaking it).
This macro is used in upstream and patched sources, preventing native hinting even if available in system libfreetype - why this macro is used and how to replace it in a safe way, I don't know. Libfreetype prior to 2.2 ignored it in some cases (e.g. upstream build of ooo, not the ubuntu one with patches), which was a bug. New libfreetype therefore really forces autohinting - which is broken in 2.2.1 for setups with rgb-subpixel-rendering and in general does not look that good as native hinting. Fedora is using only autohinter, so they did not care about bytecode-interpreter and their patches are providing recognition of fontconfig-settings, except the one concerning the interpreter used by default in ubuntu libfreetype.
The issue with the bytecode- interpreter is a bit more complex, at least as far I can see. I could get it turned on only with a "broken" libfreetype I compiled from source, turning FT_LOAD_ FORCE_AUTOHINT- Macro off (this means: breaking it).
This macro is used in upstream and patched sources, preventing native hinting even if available in system libfreetype - why this macro is used and how to replace it in a safe way, I don't know. Libfreetype prior to 2.2 ignored it in some cases (e.g. upstream build of ooo, not the ubuntu one with patches), which was a bug. New libfreetype therefore really forces autohinting - which is broken in 2.2.1 for setups with rgb-subpixel- rendering and in general does not look that good as native hinting. Fedora is using only autohinter, so they did not care about bytecode- interpreter and their patches are providing recognition of fontconfig- settings, except the one concerning the interpreter used by default in ubuntu libfreetype.